Comparison between Android Intent and iOS StoryBoard

Comparison between Android Intent and iOS StoryBoard

Comparison between Android Intent and iOS StoryBoard Segue

-If Intent can also add a prepareForSegue callback

Beautiful Life of the sun and fire god (http://blog.csdn.net/opengl_es)

This article follows the "signature-non-commercial use-consistency" creation public agreement

Reprinted please keep this sentence: Sun huoshen's beautiful life-this blog focuses on Agile development and mobile and IOT device research: iOS, Android, Html5, Arduino, pcDuino, otherwise, this blog post is rejected or reprinted. Thank you for your cooperation.

Not much time recently, but it is a pity that such a good idea will not leave a footprint first and gradually dissipate over time.

Here, I want to talk about Apple's qie for Android in recent years. It's only accurate to use this word for readers.

In addition to this Seque pair Intent, there is also the prototype cell mechanism in the StoryBoard. It may be a coincidence that it is consistent with the List mechanism in Android.

This may also be a natural thing. As early as in iOS 3, I had encapsulated this part to make a custom cell take a table as the parameter, in the factory method of the custom cell, you can directly call the table cache cell to obtain the result. The class name of the custom cell is the identifier. If there is one, the returned result is created.

However, this coupling is too strong, and then a base class is created. All the custom cells inherit from the base class of the cell. This function is solidified.

However, I always wanted to refactor the deque method. Later I found that the table view needs to be derived, which is not conducive to the versatility of the project.

Until the introduction of the original cell type in the storyboard finally completed this wish. Before that, I had been complaining about apple and could not learn from android.

However, it seems that apple has started learning. Is it too late? Nokia has put down its face. Can it be regenerated ?! Who knows.

Everything is hard to expect. Every one of us is groping forward until the end of the day, can really understand, it will not waste this life.

The following sections will be completed after time. The outline will be listed first:

1. Description of the android intent mechanism;

2. Early apple page Jump;

3. The introduction of storyboard brings seque;

4. Compared to seque, if intent can call back a method similar to prepareForSegue when it is transferred to the next page, it can be used to operate the activity generated by the system! However, the intent's ability to pass values is sufficient to solve most of the problems. This can be ignored. Besides, fragment is king. Just like the first android app I have done, it is used to simulate iOS, the activity manager is used to manually present the code-created activity interface to the window, and then look at the android source code to find that this is the early design of people, but it is outdated.

Let's take a look at this content. I hope I can understand the related content of storyboard.

Sometimes, it can be used as a level of understanding; it can be understood and a level; but it is not a general level to be systematically explained, and it takes a lot of time to sort it out, at least you have a system in mind.

However, I do not have time to provide an outline. I hope it will be time to complete it.

In iOS development, how does one call the segue in storyBoard?

[Self authentication mseguewithidentifier: @ "SegueName" sender: self];

How does IOS storyboard achieve two different viewcontroller jumps through judgment?

Storyboard is only used for interface layout, and the real judgment must be implemented in the code. NavigationController: push the viewcontroller according to the judgment. The code is better written by yourself, and the impression on yourself is the most profound. You can only remember what others wrote when you use it. You will never forget it for a while.