First knowledge beeframework - beeframework, First, Knowledge

Due to the needs of recent projects, Hybrid development became a new knowledge I started to learn. I learned about two development frameworks-BeeFramework and Samurai a long time ago, but because I have never had the time to study, I just put it aside. I have only recently started to study in depth, but it's just a doorstep. 

I am a pure OC developer. I didn't have any foundation in XML and CSS before. Here is a brief summary of the difficulties and problems I encountered when I started learning Bee. It can be used for review in the future, or for other people who want to learn. 

Why would you choose to use Bee instead of Samurai? In fact, it is not because Bee is stronger than Samurai. In terms of being powerful and "new", Samurai should be better than Bee. The reason I chose Bee is because the current project needs to be used, and Bee has been updated for a long time and is basically stable, and Samurai is still growing. In order to avoid more troubles caused by its update, I decided to use it first. Bee, will also learn to use Samurai in the future. It's a bit long-winded. Closer to home.

Bee: https://github.com/gavinkwoe/BeeFramework
Samurai: https://github.com/hackers-painters/samurai-native

Introduction to BeeFramework

github: BeeFramework is a semi-hybrid framework that allows you to create mobile apps using Objective-C and XML/CSS for the iPhone and iPad and more , created and maintained by Gavin.Kwoe and QFish.

BeeFramework is an iOS application development framework, founded by domestic developer Guo Hongyu and open source on Github. After more than a year of development, BeeFramework has received widespread attention on Github, with more than 1,000 stars and more than 400 forks.

BeeFramework is a semi-hybrid (semi-hybrid) framework that uses XML, CSS, and Objective-C to build iOS applications. It is based on MVC and is suitable for the development of large-scale apps. There are quite mature products such as Qzone and Watsons China.

The detailed description of Bee is in the document directory of the project-developer_manual
New Bee Project
First attempt
The version of BeeFramework I used is 0.6.0, and there may be some differences between different versions.
In the past, a new Bee demo was created like a new project, and the framework folder and the services folder were imported, and the compilation found #import reports an error, the reason for the error is: 'libxml/tree.h' file not found. This problem is actually very easy to solve. You will get the answer when you search on the Internet. After Xcode4.2, you can click on the project in the upper left corner after adding libxml2.dylb, and then proceed to Build Settings (here No matter whether it is Project or targets), find the Search Paths tab, there is a Header Search Paths entry under it, double-click the debug option, and add /usr/include/libxml2.

However, after this problem is solved, there will be ARC problems.

Because the newly created project is ARC, and Bee’s file is MRC.

I did this operation and added all files -fno-objc-arc

But there are new problems.

So far I did not continue, because this method is too cumbersome, I think this should not be the right way, of course I have consulted experts and great gods in the exchange group , In short, I gave up this approach.

Later I read a blog, and it was mainly because this blog solved my problem. Those who did not understand the opinions given by others before also got the answers in this blog.

Blog address: http://syxiaqj.github.io/2014/02/28/bee-learning-1/#0-tsina-1-24637-397232819ff9a47a7b7e80a40613cfe1 Author: Lang Hua Yi Duo Duo

The second attempt

Referring to the blog content, I made preparations:
1. Download BeeFramework
2. Download the Bee project template: Bee-Xcode-Template-master
3. Download tool: xproj (author QFish), use To batch ARC and non-ARC shell scripts.

Then start creating a new project

1. Install the Bee project template
Unzip Bee-Xcode-Template-master, terminal cd to this directory , Execute the following command

sh install.sh

2. New Bee project

The project framework is basically in place for the new Bee project using the template.

When you compile it, you will find an error in the project, indicating that the reference to Bee.h cannot be found, because the BeeFramework has not been added yet.

3. Add BeeFramework

Add the framework folder in the BeeFramework project to the project

4. Add in batches`- fno-objc-arc`

Because BeeFramework is a non-RAC framework, all new projects created after Xcode5.0 are ARC projects by default, so BeeFramework needs to be mixed.
All files in the framework directory need to be added -fno-objc-arc in Build Phases, but there are so many files, it will be more troublesome to add them one by one. Either use command or shift, but we still have a small tool to use, xproj.
The specific usage method is in github, or you can refer to the blog mentioned above.

Of course, you can also manage BeeFramework through CocoaPods.

At this time, compile and run again, you will find that there are no errors, but there is nothing on the interface.

The next step is to write the interface. Create a new xml file, which is included in the Bee template. I am not very proficient in xml, so I write so much first, and I will continue to study.

~The first time I use markdown to write a blog, the format is still not very good, forgive me. ~

Due to the needs of recent projects, Hybrid development has become a new knowledge I started to learn. I learned about two development frameworks-BeeFramework and Samurai a long time ago, but because I have never had the time to study, I just put it aside. I have only recently started to study in depth, but it's just a doorstep. 

I am a pure OC developer. I didn't have any foundation in XML and CSS before. Here is a brief summary of the difficulties and problems I encountered when I started learning Bee. It can be used for review in the future, or for other people who want to learn. 

Why would you choose to use Bee instead of Samurai? In fact, it is not because Bee is stronger than Samurai. In terms of being powerful and "new", Samurai should be better than Bee. The reason I chose Bee is because the current project needs to be used, and Bee has been updated for a long time and is basically stable, and Samurai is still growing. In order to avoid more troubles caused by its update, I decided to use it first. Bee, will also learn to use Samurai in the future. It's a bit long-winded. Closer to home.