Object-Oriented ActionScript 3.0

Customer Reviews

Average Customer Review




Object-Oriented ActionScript 3.0, November 29, 2008
By Luke V. Ferry (Brea, CA USA)
Found this book to be a great resource. Provides practical implementations not only for Actionscript but Object-Oriented concepts in general. Enjoyed the Case Studies where concepts are used to construct working examples.



Good Book, November 12, 2008
By David B. Kunz
I haven't made it all the way through it yet but it's good so far. Mainly shows the differences between AS 1.0 and 3.0 but does point out some changes to 2.0. Over all well written and thorough. Delivered in less than a week! Thanks!



Learn the princeple of OOP, September 19, 2008
By Saeed Ashour (Tripoli, Libya)
Object-Oriented ActionScript 3.0 takes readers through the best OOP practices and techniques. Next to great code tips an tricks it teaches you how to organize your planning and workflow. Covering the principles of OOP that you need to know, and then given a guide to designing and implementing applications in ActionScript 3.0. Next, we step up a gear, showing you the Flex builder development environment and teaching about creating reusable, extensible component frameworks--manager classes, animation and effects classes, UI widgets, and more. lastly, we look at some more advanced topics such as communication between Flash and the browser and Web services. case studies are included that apply the knowledge presented, giving you real-world projects to learn from and adapt for use in your own work. It is also a useful guide that helps you with the transition from AS 2.0 to AS 3.0
I recommend this book for any programmer who wants to get into AS3 with Flex or for a Flash developer who is looking to take their skill set to the next level




Object Oriented ActionScript 3.0 - Friends of Ed, August 22, 2008
By Joseph Delaplaine
As someone new to AS 3.0, coming from a designer background and previously using AS 2, I was looking for an explanation of ActionScript 3.0 and an introduction to OOP. I was hoping for simple to understand explanations using "big picture" generalities that then moved down into specifics and offered code to illustrate each point. This book is partially that, but unfortunately it is technically over my head at this point in my development. I will definitely revisit this book after I get more coding experience. That being said, it does an excellent job explaining differences between AS 1 through AS 3, as well as many other concepts. In general, the book's "readability" would be improved if some chapters were in a different order and short, simple projects were added along the way to better illustrate each new concept. I'm thinking specifically of the chapters on Planning, Patterns and Workflow. It isn't until the middle of the book that this begins to happen. I think the book bogs down in detail early on, for example, the chapter on Flex is written with the assumption readers are not only familiar with Flex, but prefer using it over coding directly in the Flash application. Simply stating Flex's advantages immediately and briefly would improve the rest of the chapter. Also, highlighting new blocks of code as they appear would make them stand out immediately. I found myself searching blocks of code to understand the point being made.



OverPriced as only half the book is on any use, April 13, 2008
By Peter Holgate (Lincolnshire)
The intended audience is for readers who "...have some previous experience developing in Actionscript...", and that "Some familiarity with the Flash or Flex authoring environments...".
SO - why do we get a whole chapter dedicated to a section on using Flex, but assumes that the reader already knows the Flash IDE?
Furthermore, why is there a whole chapter on coding standards and practices?
These are just two of the wastes of paper, therefore MY MONEY before getting down to the OOP concepts.
If you do buy, watch out for the errata, and the publishers (Friends of Ed) have errors on their reporting page, which is, possibly, the reason there is no corrections sheet for this book

Once we get to the OOP stage, there is a major dearth of answers to the question WHY? I'm a newcomer to true OOP, so this book is not a good way to delve into OOP.