Here is a brief write-up about my take on Flex 1.5. Not very exhaustive but highlights few features I like best. More to follow in eventual post along with my development phases. Out of the many "features (Flex 1.5 features)": of Flex 1.5, I particularly liked RSL or the Runtime Shared Library, Remote Object and the History Manager the best.

*RSL* is an SWF which can have shared assets such as images, components, and even other SWF files. This file is extracted from an SWC file before distributing, and is cached locally by the Flash player. So, next time the Flex application is requested, the Flash Player loads the RSL from the local client's cache. The Flash player will try to get a new SWF File only when the RSL descriptor file or its dependencies change. Eventually, RSL allows us to have common external assets sharable across different applications and are more aptly usable for larger Flex Applications.

An RSL can be used after it is being defined or created with the .SWS extension.


Then the RSL is accessed from your web directory


or a pre-compiled SWC file

*Remote Object* allows __Remoting__ in Flex, thus allowing us to call methods on Java Objects that is on a Java Application Server, __e.g.__ "JRun (JRun)":, where Flex is running. @RemoteObject@ thus allows us to access JavaBeans including __Plain Old Java Objects__ which are in the web application classpath. The bottomline is, @@ uses AMF, the encoding used Flash Remoting and as we all know, AMF is way faster and native to the Flash Player than other methods of communication like Web-Services, SOAP.</p>

*History Manager* is another cool feature that have been pending in Flash for eons and when implemented, we still wished that it to be more better. History Manager allows the back and forward browser buttons to go back or forward to its previous/next states and this works beautifully across most modern standard browsers.

*Bookmarks* for "Flex (Flex)": on "Macromedia (Macromedia)":

* "Flex, Getting Started (Getting started with Flex)":
* "Flex Installation (Flex Installation)":
* "Essentials for Developing Flex Applications (Essentials for Developing Macromedia Flex Applications)":
* "Flex Documentation (Flex Documentation)":
* "Flex Trial (Flex Trial)":
* "Flex Doc (Flex Doc)": (zipped), for "Flash Resouce Manager (Flash Resouce Manager)":
* "Flex ActionScript & MXML Reference (Flex ActionScript and MXML Reference)":

*Flex related Blogs*

* "Christophe Coenraets (Christophe Coenraets)":
* "Eric Anderson (Eric Anderson)":
* "Everything Flex (Everything Flex)":
* "Flex Authority (Flex Authority)":
* "Flex Daddy (Flex Daddy)":
* "Kevin Hoyt (Kevin Hoyt)":
* "Manish Jethani (Manish Jethani)":
* "Matt Chotin (Matt Chotin)":
* "Matt Woodward (Matt Woodward)":
* "Merhl Interactive (Merhl Interactive)":
* "MF Worx (MF Worx)":
* "Peter Ent (Peter Ent)":


# Remember to visit "Rich Internet Apps (Rich Internet Apps from Iteration::Two)": for useful Flex related resources and articles.
# "Flex Builder (Flex Builder)": is an easy to use tool to assist in developing Flex Applications.
# POJO or Plain Old Java Object is a normal Java Object that is not a JavaBean, an EntityBean, a SessionBean, etc., and does not serve any other special role or implement any special interfaces of any of the Java frameworks (EJB, JDBC, DAO, JDO, etc...).</mx:remoteobject>