Re: [Flashcoders] Best way to learn OO Analysis and Design withActionScript

2006-08-19 Thread Muzak
Have a look at ARP.
http://osflash.org/arp

It's a lightweight framework that takes MVC to the next level.

mailing list:
http://ariaware.com/mailman/listinfo/arp_ariaware.com

manual
http://www.ariaware.com/products/arp/manual.php

regards,
Muzak

- Original Message - 
From: David Bellerive [EMAIL PROTECTED]
To: flashcoders@chattyfig.figleaf.com
Sent: Friday, August 18, 2006 3:41 PM
Subject: [Flashcoders] Best way to learn OO Analysis and Design withActionScript


 Hi everyone!

 I'm having real difficulty understanding how to
 properly architect and structure Flash applications
 using ActionScript 2.0.

 I've read Colin Moock's excellent Essential
 ActionScript 2.0 and several other books and articles
 on the topic and while I can safely say that I do
 understand the syntax, I can't seem to write an entire
 application using OO design mainly because I can't
 figure out what should be in a class, which class
 should do what, which class should extend MovieClip,
 which class should use composition instead, which
 class should start the application, etc.

 I'm sure a lot of excellent Flash developpers in this
 mailing list didn't have previous coding experience
 before they started Flash (like myself) and managed to
 become the ActionScript 2.0 OO pros aroud here.

 Any help / tips ?


___
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


Re: [Flashcoders] Best way to learn OO Analysis and Design withActionScript

2006-08-19 Thread Count Schemula

FWIW, I thought this book did a good job of of getting me past the
jargon. Much more accessible to me than the Moock Essential AS2 has
been. The Moock book is really good, but, I find it tough read. I'm
not really a programmer though, it's just another hat I have to wear
sometimes...

http://www.friendsofed.com/book.html?isbn=1590596196

On 8/18/06, Mike Mountain [EMAIL PROTECTED] wrote:

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

___
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


RE: [Flashcoders] Best way to learn OO Analysis and Design withActionScript

2006-08-18 Thread Mike Mountain
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


Re: [Flashcoders] Best way to learn OO Analysis and Design withActionScript

2006-08-18 Thread James Marsden
I used to have a problem with this too, hating the 'verbal smokescreen' 
as you put it, but it's crucial to be in sync with specialist language 
and concepts in order to cut through misunderstanding between peers. I 
don't think it's about making ourselves more important, but making sure 
you're able to communicate complex ideas quickly.


I'm a Fine art graduate, and there's no environment worse than that for 
absurdly long winded conceptual bullshit - at least OOP concepts 
actually lock people's understandings together!


J


Mike Mountain wrote:


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

 

 


___
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