[IPhone Development] xcode4 iPhone application development experience

I have been learning about iPhone development for more than half a month, because the project requires the iPhone development experience. At the beginning, I learned how to use two books: Basic tutorial on iPhone 4 and iPad development and iPhone 4 applications.ProgramIntroduction to development and practice, as well as an iPhone development cheat book (version 2nd), but there is no time to read it.

This article is available only because xcode3.2 is used as an example to explain and operate with the operation method.Article. Some features may not be new to xcode4, but they are not experienced by window developers.

I. Integration window

Xcode4 puts all interfaces in a single window, so you don't have to worry about switching the window. This is done in most development tools in windows. In xcode3.2, you still need to use interface Builder (IB) as a separate program. That is, to double-click the XIB file, you need to open a new window to edit it, it is not required in version 4. As shown in:

On the far left is the project browser, which allows you to customize the group of files, not necessarily the same as the file directory structure.

The second on the left is the XIB Editor, which is the original interface builder. You can drag the control directly to the interface and display the interface structure.

The rightmost is the property window and toolbar, which are similar to vs.net. The better thing is the automatic association with help. In addition, all connections can be checked through this attribute window.

The third on the left is the header file corresponding to the class set by XIB.Code.This is very convenient.You can directlyRight-click to drag (or press Ctrl + mouse to drag)A control is added to the header file.Connect or createIboutlet attribute or ibaction event. As shown in:

Ii. template Improvement

Originally, because IB is independent, you need to manually associate the corresponding class to create the XIB file. Now, you only need to select whether to generate the XIB file to automatically generate the association between the two files.

Iii. file navigation bar

On the top of the editing window, the location of the file being edited is displayed, which allows you to quickly jump to your upper-level file or directory. As shown in:

There are two advantages: one is that there are two arrows on the far left, you can navigate forward or backward, and quickly switch code files. I often locate the main. M file when performing errors. It is troublesome to switch the code file through the project file browser, but it is very fast to use this arrow. You can also use the shortcut key Ctrl + command (the win key under the black apple) + the left arrow to return quickly.

The other is to open the code file to automatically display the corresponding header file on the right, or open the header file (. h), automatically display the implemented code file (. m), you can set whether to automatically jump to or manually on the navigation bar of the code box on the right. I used to set it to automatic, so that I can open the. M file later. By the way, I can see the file information of. h. After all, there is a small amount of code in the H file. However, it seems that there is no way to split up or down code files, which is expected to be improved in later versions.

4. Code prompt

This feature is available in all development tools under win, but it is somewhat different. The reminder code can be selected by words. For example, if you enter Vi, you can remind viewwillappear, you can press a tab key to match each word view, and then enter W to quickly match viewwill.

5. multi-screen support

Mac programs seem to support multi-screen operations by nature, which is very convenient to use. vs2010 started to support multi-screen operations.

6. llvm compiler 2.0

Llvm compiler is a next-region open-source compilation technology that fully supports C, objective-C, and C ++.

Llvm is twice faster than GCC, And the created program runs faster. Because it makes better use of the modern Chip structure.

Llvm and xcode 4 are fully integrated. Keyword highlighting and code integrity are all analyzed by llvm syntax analyzer. In this way, you can understand your code well during editing.

Because the llvm engine is used, xcode 4 can discover errors in your code during editing without the need for compilation.

The efficiency of this compiler is very high. The speed of compiling and releasing it to the simulator using Android is extremely slow. This compiler is almost controlled within 5 seconds. Of course, it depends on the performance of the machine, I am using a black apple, so it may be slower.