Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>As with all "Best practices" and "Design Patterns" it depends what you want to do. Every choice you make has trade offs. It is good to understand those trade offs and make the decision to act accordingly with what you need to develop. </p> <p>Your question is so open ended; I might be able to write a book without answering. </p> <p>A few thoughts on your bullet points: </p> <blockquote> <p>I stumbled across lots of software written in Air/Flex with nearly infinity global vars :-) </p> </blockquote> <p>This is a common approach when using the Cairngorm framework which makes use of a ModelLocator. In many apps the ModelLocator turns into one big global Value Object used everywhere in the app. I talk about how I deal with this blog post: <a href="http://www.jeffryhouser.com/index.cfm/2008/3/27/Learning-Cairngorm-Part-6-Dealing-with-the-Singleton" rel="nofollow noreferrer">http://www.jeffryhouser.com/index.cfm/2008/3/27/Learning-Cairngorm-Part-6-Dealing-with-the-Singleton</a> </p> <blockquote> <p>Most of the software I saw was not object-oriented</p> </blockquote> <p>Despite all the interest about Object Oriented programming, I've never seen any project architecture take a Object Oriented Approach, academically speaking. At best I would call all development a hybrid between Object Oriented concepts and procedural concepts. Many folks I've spoken to seem to claim that any use of encapsulation is OO; while not using encapsulation is procedural. That is, of course, ridiculous </p> <p>When building Flex Components, you'll be writing a lot of code in the Flex Component LifeCycle methods (createChildren(), commitProperties(), measure(), and updateDisplayList() ); but you probably won't be creating your own object orient architecture. </p> <blockquote> <p>How can I pack the asynchronous method calls nicely?</p> </blockquote> <p>I'm not sure what you mean by pack in this context.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload