Select Page

360Flex -Day 3 (morning)

I will post a few photos later from this morning when Ted Patrick was speaking later, but for now here are a few notes:

Ted Patrick’s morning presentation (bear with my notes, all should be totally accurate in wording) :
A bit of showing of Flex and how it can be used with the new Adobe CS3 that is set to release soon (I believe someone told me end of this month 07? – I could be wrong).

Fireworks (CS3) was shown on how you can layout components, images, etc. and export them as working MXML to Flex 2. Awesome stuff. I imagine this will really help bridge the designer/developer world a bit when it comes to new apps, etc.

"Borneo" – The next Flex Data Service

  • Scalability and performance
  • Integration w/LifeCycle
  • <mx:WebService>

"Moxie" – The next version of the Flex SDK and Builder

  • Language intelligence
  • Integrated profiler
  • Design View Enhancements
  • Data Integration

-Enhanced Datagrid and lists

The intelligence will include the ability to rename methods through a function called ‘refactor’ (like Java somewhat)

Code Search –
Shows references to variables, methods, etc. across all apps/files in a project when a search is performed.

Ted went on to give a few examples on the ‘Flex Ecosystem’ and how Flex has become much bigger than just to Adobe.

First example was from ESRI and how they have created components that extends vector mapping. Pretty nice flipping from Vector to wraster graphics, and showing the global map in a non-flat view. (if that makes sense)

Next Example was from Farata Systems where they created a FlexBI application that customize reports such as highlighting filtered results in a datagrid.

He also mentioned the Google Group – FlexLib, and reminded that it is a huge resource of open source components such as ‘super tab navigator’ and sliders, etc.

Ebay actionscript library to be released along with references to their SOAP toolkit.


Mike Chamber’s presentation on Apollo (for all those not absolutely familiar with Apollo, kinda like me 🙂 )

Notes and comments from his slides, no comments from me:

Apollo is a cross-operating system run-time that allows developers to leverage there existing web development skills (Flash, Flex).

Apollo is runtime.

Apollo can be built using the following technologies

  • flash/Flex/actionscript
  • html/js/css/ajax
  • combination of these technologies
  • pdf can be leveraged with any application

html engine:

  • web kit open source engine
  • used in safari, khtml

why Webkit?

  • open project thtat we could contribute too
  • proven technology that developers and end users are familiar with
  • minimum effect on Apollo runtime
  • Apollo functionality/APIs

    • Offline/Occasionally connected
    • Applications can run in the background
    • Network
    • http
    • xml-rpc/soap/Rest based web services
    • binary and xml sockets
    • File I/O
    • Custom Chrome
    • shape
    • alpha

    Scripting support

    • Depends on container being used
    • Actionscript 3 – Flash/Flex
    • Javascript – HTML/CSS/Ajax
    • Cross environment communication and scripting will be possible.
    • Complete access to Flash Player and HTML DOMs and APIs