February 26, 2008
In Deepa’s talk @ 360 in Atlanta she also goes over MXML-G… which is really just a beautiful abstraction of Flash’s drawing API using XML.
It’s very cool. Very handy for rapid prototyping and skinning.
Thermo is essentially an eclipse plugin that heavily leverages MXML - G.
Update: I talked to Deepa… she mentioned that it actually includes “more” than the drawing API currently offers…
6 Comments |
AIR, AS3, Flex, FlexBuilder |
Permalink
Posted by Clint Modien
February 26, 2008
This is a awesome news… !!
Today at 360 Flex Deepa Subramaniam announced that Adobe is working on a mobile version of Flex. They are taking into account the ramifications of creating a mobile framework for Flex 4. This does not mean that it will be released at the same time as Flex 4 but they are accounting for it in the planning as they are for Thermo which is scheduled to be released on the same timeline as the Flex 4 release.
The items that Deepa said they were going to implement were…
- Eclipse based
- ActionScript MXML / AS3 Editor
- Debugger
- Profiler
- Support for lower memory devices as well as higher memory devices
This is HUGE news for Flex developers to be able to create applications for Mobile Devices….
Next is AIR for Mobile??
6 Comments |
AIR, AS3, Flex, Flex Mobile, FlexBuilder, adobe |
Permalink
Posted by Clint Modien
December 11, 2007
So I know this has been blogged about before… but I feel like it’s a relatively obscure little gem in the Flex/Flash world so I thought I’d throw it up on the wall again with the hope that it might give other people the desire to create useful Flex/Flash/AIR plug-ins.
One of the readers of my last post on my Flex Builder 4 wishlist commented that Flex Builder shouldn’t be built on Eclipse and Adobe should open it up to other vendors such as JetBrains (of IntelliJ/ReSharper fame). While I am a huge fan of ReSharper and IntelliJ… I believe the reasons for having the Flex Builder code base built on the Eclipse platform far outweigh the benefits of having it be built as an IDEA plugin.
The largest reason being that the Eclipse core is open source and according to the EPL any code derived from the Eclipse source must also be open source. This means the core of Flex Builder… the Eclipse code that was derived for Flex Builder… which includes editor code, debugger code, workbench code… must also be open source.
You can find the Flex Builder 2 source based on Eclipse 3.1.2 here: http://www.adobe.com/go/4b243413
Aside:
The flexibility of the Eclipse platform to adapt itself as development tasks evolve will be a cornerstone to it’s usefulness as an IDE and will act as a catalyst to propel the evolution of Adobe’s Flash/Flex/AIR tooling. Evidence of this can be found in an excellent plugin built by Stephen (Spike) Milligan (main contributor to the CFEclipse plugin) at http://www.yellowbadger.com/ which was targeted at the Flex 1.x/AS2 framework and built on the Eclipse platform. I had discovered and was using this plugin a full year before the Zorn (Flex Builder 2) release had been rumored. I was also using Eclipse for all my Java development at IBM and lately… I’ve been using it to teach myself Ruby. Having one editor with multiple perspectives for doing radically different development projects is my dream come true. Eclipse is not without it’s fault’s and does have some shortcomings (It can be a memory pig with a capital P1GB). But ram is cheap… Who doesn’t run 2 gigs?
3 Comments |
AIR, Flex, FlexBuilder | Tagged: AIR, Flex 1, Flex 2, Flex Builder |
Permalink
Posted by Clint Modien
May 11, 2007
So everyone is telling me I should post more… so I thought I would share this little pearl.
When adding a SWC to your project you can also add the ability to step in when debugging or F3 (or ctrl+click) into the class definitions contained in the SWC file by adding the directory where the source code lives to the SWC’s source attachment property. This also gives you the ability to step into the source code.
Here’s a screen-shot example of linking the Cairngorm 2.1 source with the Cairngorm.swc.

OK… no more excuses… love the swc… embrace the swc.. they’re apart of flex too.
6 Comments |
Flex, FlexBuilder |
Permalink
Posted by Clint Modien
November 21, 2006
For my future ref… because I have to hunt for this everytime…
It’s located in the .metadata folder when Flexbuilder throws an error. Full path is ${WorkspaceDir}/.metadata/.log
2 Comments |
Flex, FlexBuilder |
Permalink
Posted by Clint Modien