Compare Android Intent with IOS StoryBoard segue-intent If you can add a Prepareforsegue callback.

Compare Android Intent with IOS StoryBoard Segue

-Intent If you can add a Prepareforsegue callback.

The beautiful Life of the Sun Vulcan (http://blog.csdn.net/opengl_es)

This article follows "Attribution-non-commercial use-consistent" authoring public agreement

Reprint Please keep this sentence: Sun Vulcan's Beautiful Life-this blog focuses on Agile development and mobile and IoT device research: IOS, Android, HTML5, Arduino, Pcduino , Otherwise, the article from this blog refused to reprint or re-reproduced, thank you for your cooperation.

The recent time is not much, but such a good idea, do not leave a footprint, slowly dissipate over time, that is how pity.

You can still spit it out here. Apple's many qie on Android in recent years, the reader of the matter, can only use this word accurate.

In addition to this seque to Intent, and the prototype cell mechanism in StoryBoard, it may be coincidental that this coincidence is consistent with the mechanism of the list in Android.

This may also be a natural thing, as early as IOS 3, I have to be lazy, I have encapsulated this part, let a custom cell with a table parameter, in the custom cell factory method directly call table's cache cell get, to the custom cell The class name is identified, and if there is a return cache, no new one is returned.

However, this coupling is too strong, and then a base class is built, all the custom cells inherit from the cell base class, this part of the function is considered to be cured.

But always think of the Deque method to refactor, and later found that the table view needs to be derived, this is not conducive to the universality of the project, this is dropped.

Until the introduction of the storyboard Zhongyuan cell, finally completed this wish, before, has been scolding Apple, can not learn from Android.

But now it seems that Apple is starting to learn, is it too late? Nokia put down the face, whether it can regenerate it?! Who knows.

Everything is difficult, each of us is groping forward, until the end, can really understand, it will not waste life.

The following sections have time to be well thought out, first of all to outline:

1, Android intent mechanism description;

2, Apple early interface jump;

3, the introduction of storyboard, brought the Seque;

4, compared to seque,intent if you can move to the next page, the first callback a similar prepareforsegue method is good, so can be very tolerant of operating system generated activity! But intent's ability to transmit value is estimated enough to solve most problems, this can be ignored, moreover, fragment is the king, as I did the first Android app, incredibly is for the simulation of IOS, using the Activity manager, the code created by the activity interface manually Alternate rendering to the window, later look at the Android source code, only to find that this is someone's early design, but is outdated.

Probably the content, even spit with the chatter, hoping to be able to storyboard the relevant content of the chatter understand.

Sometimes, it will be used, is a level of understanding, can be said to understand, but also a level, but to systematically explain it, that is not the general level, it takes a lot of time to organize, at least your ideas are systematic.

But I do not have the time, provide an outline, I hope there will be time to fill it.