Programming Flex 3: The Comprehensive Guide to Creating Rich Internet Applications with Adobe Flex
|
| List Price: | $54.99 |
| Price: | $34.64 & eligible for FREE Super Saver Shipping on orders over $25. Details |
Availability: Usually ships in 24 hours
Ships from and sold by Amazon.com
28 new or used available from $29.00
Average customer review:Product Description
- Learn the underlying details of the Flex framework
- Program with MXML and ActionScript
- Arrange the layout and deal with UI components
- Work with media
- Manage state for applications and components
- Use transitions and effects
- Debug your Flex applications
- Create custom components
- Embed Flex applications in web browsers
- Build AIR applications for the desktop
Flex 3 will put you at the forefront of the RIA revolution on both the Web and the desktop. Programming Flex 3 will help you get the most from this amazing and sophisticated technology.
Product Details
- Amazon Sales Rank: #23422 in Books
- Published on: 2008-09-26
- Original language: English
- Number of items: 1
- Binding: Paperback
- 657 pages
Editorial Reviews
About the Author
Customer Reviews
Flex 3 book with it's own unique strengths
This book has many things to commend it, and in particular it is very strong on:
* The internal startup sequence of a Flex application
* Loading one Flex application into another Flex application
* Working with fonts
* Programmatic skinning
* Runtime CSS
* Building custom components
I think the book is weak on a few things as well, such as the Flex Builder IDE and remoting. In reference to remoting, the authors make the following surprising statement on page 471:
"Several of the remoting gateway products have added support for a Flex data component called RemoteObject. However, because we have found no practical use for RemoteObject, we are omitting any discussion of RemoteObject".
Well, I must report that I have found a practical use for it: namely, it's one of the central objects in Blaze DS and LCDS remoting. If you want to learn how to use it, you'll have to read Flex 3 Bible (12 pages on it), Rich Internet Applications with Adobe Flex & Java (referenced on 41 pages), or Adobe's help contents.
I believe these authors have a slight tendency to favor ActionScript and Flash APIs over MXML and Flex APIs, a preference that a reader can either choose to follow or not. I don't believe this book would be as good for novice Flex users as some of the others I have read. I think that when authors delve into relatively arcane, advanced features of an API before they get to the common simple things, it tends to make it harder for beginners. For example, here within the first 100 pages of a 600 page book they cover class introspection, loading one Flex application into another, application domains, and resource bundles... all before the novice reader has even been introduced to a simple CheckBox control. The order in which they cover topics is pretty much preserved from "Programming Flex 2", except for the fact that the chapter on application components has been moved forward quite a bit.
Well thought out and comprehensive
It is clear the authors of Programming Flex 3 worked very hard to write a comprehensive, easy-to-read publication. Their examples are great - very simple such that they highlight the concepts being presented. I have been working with Flex for a couple years but reading this book definitely brought my game up a notch based on a more clear understanding of the Flex framework, authoring components, and several other key principles.
If I had to offer one critique, I'd have liked to see some more coverage of synchronous network communication with Flex (sockets, Flash Media Server, etc.), but the dedicated chapter on AIR more than makes up for this.
Good content but poor correlation
I'm only about a quarter of the way through the book, but have already noticed some things.
The book's content is great. Its very thorough and covers a lot of useful material.
Unfortunately, the authors miss the mark on correlating their examples to their figures. Most of the code examples have no figure to show what the code renders. And most of the figures that are there, don't correlate to the code examples.




