Is ActionScript 3.0 Hard or Not?
You must be logged in to the O'Reilly Network to post a talkback.

Showing messages 1 through 4 of 4.

• from a designers' point of view...it is hard and stupid!
  2008-01-10 04:35:49  its-a-mess [Reply | View]
  
  
  I think in the development of Flash the problem is, that there should have been made an important choise much earlier: There is that irritating ambiguity of a design-tool and programming-tool: Why not going on with developing more handy interface-solutions like the new "Custom Tweening-tool". As a designer I am condemned to program because I want to build excellent performing fullscreen websites, with elements sometimes placed relative to screensize, contents relatively stacked over each other etc. Imagine if movie-editing and dvd-creation in Final Cut Studio or Adobe After Effects worked like Flash/Actionscript! (it would make me sick) I think it is possible to make a GUI that covers actionscript: What about an environment with elements connected to eachother with arrows/connectors that have their "while,if,then,else,for conditions in them". Most (logistic) business process simulation programs work that way. I understand the advantages of OOP; but why do I e.g. have to "import.flash.*" (i thought i was already in the application) and why do I have to create name-sensitive *.as --> package --> class-constructions...Aaaargh! From my point of view it is just not logical. So, what a nightmare it is to struggle through the O'Reilly's Essential AS3.0-book. Aftyer 350 pages you think: "Aha, now we're finaly gonna see how the magic work." The only thing you discover is that it takes pages of typing with minimal result showed via "trace". The big question has not been answered for me: How do I combine and where do I combine OOP, timeline scripting and Flash-authoring (designing) so I can make an excellent looking and performing webapplication? (excuses for bad english, i am dutch)
• from a designers' point of view...it is hard and stupid!
  2008-01-21 13:03:34  Colin Moock [Reply | View]
  
  
  i completely agree that more tool innovation is needed. you give really interesting examples of a GUI for creating a specific type of interactive content. now that flash is being treated as a platform, we'll hopefully see many more content-creation tools released by adobe and third parties.
  
  regarding Essential ActionScript 3.0, the goal of that book is to provide a deep reference guide for the ActionScript 3.0 programming language. if you're looking for a "how-to" book, you might consider something more example based, such as O'Reilly's ActionScript 3.0 Cookbook.
  
  regarding object-oriented programming with content created in the flash authoring tool, take a look at the symbol-to-class linkage tool in the Library (right-click on the symbol, then click "Linkage").

• It's the buttons that are killing me
  2007-12-22 18:10:09  mindymcadams [Reply | View]
  
  
  Usually I don't need to move a ball around, or attachMovie. I have to build simple interfaces. Five buttons, five frame labels. Divide up some animated content, make it accessible via buttons. The listener business and the additional code required by AS3 for the most common symbol I need to use -- simple, "click me" buttons -- has made AS3 seem, to me, all those things you have so elegantly argued against here.
  
  Your examples are great. But it is the AS3 button scripting that has driven me back to AS2.
  
• It's the buttons that are killing me
  2008-01-21 13:05:19  Colin Moock [Reply | View]
  
  
  the button event handling issue is certainly important. as i wrote in the article, i think adobe needs to figure out a way to support an improved version of on()/onClipEvent() with proper tool support. maybe thermo or bordeaux will provide the feature-set you need.