On 29 Oct 2014, at 11:51 PM, Leo Yu <[email protected]> wrote: > I am just curious about iOS StoryBoard. A lot of people i talked to seems to > like using it for creating their apps. To me, it adds a level of difficulty > to control how controllers are created and destroyed.
This list is for discussion of the Objective-C programming language itself; [email protected] is for questions about the Cocoa application frameworks, which are only one use for the language. I’ll give you my _experience_ of OO tools in general; don’t expect nuance or detail on your literal question. Go to cocoa-dev for that. I really shouldn’t do even this. I’m chary of using a technical list for “opinion” unrelated to a concrete topic. I’ve seen novices resist object-oriented tools, including frameworks and their helper applications, as “difficult,” usually because those tools deprive them of “control” or “how it’s really done.” I can’t comment on your situation, but the complaint usually comes of not having studied (and used) the tool enough to understand how to adapt it to the results they want. They rarely have to duplicate its function by hand, repeatedly, and probably less-correctly. Working by hand is sometimes the best way, but it’s not the first thought to have. The results should be what matter, not whether you got them with your own hands. This assumes a well-implemented tool; Storyboard _for iOS_ is well-implemented, as such things go. It is used not just by “a lot of” developers, but by the great majority, for most parts of their applications. > Also, is it actually hard for a group of developers to share or to modify a > storyboard ? Merging independent work on storyboards and NIBs is impossible. Nuance elsewhere, such as cocoa-dev. — F _______________________________________________ Do not post admin requests to the list. They will be ignored. Objc-language mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/objc-language/archive%40mail-archive.com This email sent to [email protected]
