I find the hardest thing to get my head around is the absurd amount of Jargon involved in OOP - for what are essentially simple concepts. I really wish we wouldn't perpetuate the practice of trying to make ourselves important by using such a verbal smokescreen. Once you get past the copious amounts of conceptual diarrohea the actual fundamentals are fairly easy to understand. I know it's easier to define concepts using singular terms, but it would seem that OOP tends to go overboard with this a hell of a lot. OOP dictionary anyone? This is componounded by other concepts being explained within the bounds of this "jargon" - One question inevitably leads to many more.
M > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Mike Britton > Sent: 18 August 2006 15:33 > To: Flashcoders mailing list > Subject: Re: [Flashcoders] Best way to learn OO Analysis and > Design withActionScript > > I second James' recommendation of Headfirst Design Patterns. > I also recommend downloading an Enterprise Architect trial > http://www.sparxsystems.com/ or Poseidon > http://gentleware.com/index.php and learning some UML. It > helps me to step outside of the code and focus on the logic > behind the business decisions. Understanding sequence > diagrams ("user clicks button, event is passed to manager, > etc) first can help you sketch out class diagrams that > eventually turn into really scalable systems. Then later, > people can wade right in and add to it. > > Most important: try not to learn everything at once. Give > your brain time to wrap around small chunks of new info. > > My .02 > > > Mike _______________________________________________ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
