Adobe Flex Builder Error

if anyone can explain the detailed explanation to this one… please don’t hesitate to post a comment…


Adobe FlexBuilder : The SWC-cache

There is no question about it… without Adobe FlexBuilder building Flex RIA’s would be such an uphill battle for all but the diehard fans… I would not claim to love Adobe FlexBuilder, but I do recognize it as a decent IDE which definitely makes it possible to do enterprise scale RIA’s as well as small app’s and movies.

However, the secret to getting everything right when building enterprise scale systems is to understand some of the inner workings of the IDE… and one of the good things to know is the way Adobe FlexBuilder caches different stuff.

One phenomena that we experience on my team from time to time is when Adobe FlexBuilder seems to refuse to recognize an updated SWC – this is more often true when working with RSL’s and precompiled SWC’s than not, but to identify a distinct pattern has thus far been difficult (read: “impossible”).

So for the workaround, a sure way to force the Adobe FlexBuilder to rebuild its SWC cache is to remove the files for the current workspace and then call clean on the solution.

You will find the SWC-cache files in the “[workspace]\.metadata\.plugins\com.adobe.flexbuilder.codemodel\SwcCache\” directory.

Sometimes the same thing happens for projects already open, however the procedure is identical… just remove the files under “[workspace]\ .metadata\.plugins\com.adobe.flexbuilder.codemodel\projects\”.

Adobe Flex

Adobe Flex Data Visualization Watermark

Once in a while even the most professional individual finds themselves forced into a corner by circumstances over which they don’t have control… and on rare occasions it happens even though the individual do everything right…

…one such situation recently happened to me when I had to deploy an Adobe Flex solution using undigested Runtime Shared Libraries, Flex Modules and Data Visualization in one cool cocktail… after having been unable to rid myself and the solution for the annoying Flex watermark declaring that the chart was shown with a graph compiled with non-registered version of the Adobe Flex SDK, I consulted good ol’ Uncle Google for an answer…

If you don’t know what I am talking about… this is the watermark I am talking about… displayed in grayed out letters displaying “Flex Data Visualization Trial”…

Quickly I came to the JIRA entry for the problem stating that it was not a bug if you remembered to load the Framework RSL prior to loading the Visualization RSL…

However, this didn’t change a thing as I was already loading the framework prior to data visualization – I did however try, and yes, it wasn’t the solution…

Left with no official solution and a deadline I didn’t want to break for no one, I quickly had to become innovative and ingenious… I therefore dived down into the source code of the Adobe Flex SDK and eventually found my way to the sources for the data visualization components… once I had created an Adobe Flex Class library for the sources, compiling a SWC and referencing it from my application was easy.

To my great satisfaction, the homebrewed SWC proved to have no watermark when loaded as undigested RSL from a Flex module !

This solution not only solves the problem with the watermark, but it also allows me full control of which classes to include in the library allowing me to effectively cut the size of the visualization library in half based on the classes necessary for this particular application.

I have read the EULA from Adobe, and I don’t think I am in conflict when doing this… however, if anyone at Adobe reads this, please advice otherwise in case.

Please don’t hesitate to write me if you problems getting this solution to work for you…

PS… off course I have a licensed edition of Adobe Flex Builder, so this is not the issue here.


Updated RSL for Flex Data Visualization 3.0.1

Due to a bug in the signing process at Adobe, it appears that the cacheable RSL for the datavisualization components in Flex Builder doesn’t work in 3.0.1.

Adobe has updated the RSL and made it available here.

Go ahead and replace it in your Flex Builder 3.0.1 installation and you’ll hopefully be set.

Read more about it on blogs@adobe…


Adobe Flex Builder 3 Plugin – Only works with Eclipse 3.3 (Europa)

This is probably old news, but at least to me its new…

Adobe Flex Builder 3 Plugin ONLY works with Eclipse 3.3 (Europa) and not 3.4 (Ganymedes) which is the current release.
This is just too bad, but due to Eclipse’s XCopy installation we can still have Ganymedes installed side-by-side with the Eclipse in which we are running Flex Builder.
Unfortunately the problems are not just minor inconveniences, but they are actual showstoppers… such as the MXML editor failing to show files…


Adobe Flex : Change between Debug and Production Builds

Sometimes FlexAnt is just too troublesome to get working correctly (extisting projects tends to be difficulty to FlexAntify) so you need an easy way to toggle between Debug and Production builds…

Instead of going through your projects and setting the variables to Debug=false (even if you have a script / application that does it for you) it makes more sense to use the optimizer application from the Adobe SDK.

Then all you have to do is to call the following command on your binaries…
optimizer bin-debug/[binary].swf –output bin/[binary].swf –keep-as3-metadata=Bindable,Managed,ChangeEvent,NonCommittingChangeEvent,Transient

You can read more about the Optimizer here…


Adobe Flex

Adobe Flex Builder 3 released !

Through 4 long beta’s we have been waiting for the moment when the Adobe Flex Builder 3.0 got relased… that moment is here now.

Im gonna install it in a test machine to ensure that it doesn’t break our projects. There are no reason to believe that anything should be broken on the account of going from the milestone 4 Beta to the release… but no reason to take chances as I more than one time have experienced that making assumptions about something like this can have disastrous consequences.

Anyways… here it is: