Joeflash’s Enigmacopaedia


Flash-Flex Series on CMX: Flash S9 Skinning for a Flex DragPanel Component

Posted in Flash, Flex, Community MX, Flex Builder 2, Flex 3, Flex 2, Flash CS3, Flex Builder 3 by Joeflash on the June 25th, 2008

In part 3, part 4, and part 5 of the Flash-Flex Integration Series on Community MX, we show you how to build a scale-9 skin in Flash, apply it to a custom Flex component, and build a draggable, resizable “panel” component application in Flex. You can see the finished demo for this tutorial trilogy below.

This movie requires Flash Player 9

The skin was designed in Flash CS3, and implemented in Flex Builder 3. To find out how this was done, you can purchase these tutorials at the links below.

Flash-Flex Integration - Part 3: Flex Component Skinning with Scale-9
Flash-Flex Integration - Part 4: Skinning the Scale-9 Flex Component
Flash-Flex Integration - Part 5: Building the DragPanel Component

Flex Builder 3 Startup JVM Termination Error

Posted in Flex Builder 2, Flex Builder 3, Eclipse by Joeflash on the March 26th, 2008

So I just installed a new version of my firewall software, and now neither FB 2 or FB 3 will start. I get a JVM termination error popup, that’s it. As fortune would have it, Neil Webb had blogged about the same problem just today. So I looked up the issue on the Adobe bugbase, and there I found the answer after a little investigation.

JVM termination error dialog

Turns out I had some JVM performance tuning set in my shortcut.

-refresh -clean -vmargs -Xms512m -Xmx1024m

…and apparently it was too high. The moment I ran FlexBuilder.exe directly or the shortcut with a lower max mem at -Xmx768m , it worked, no problem. I found I could push it all the way up to 958m, but no more. At 959m, it crashes, just as before.

No idea why installing new software would affect the maximum memory allocation for the JVM, or why a max of 958. But at least it’s working now.

\*replaces hair torn out of scalp\*

Update 02-04-2008: logged an official bug with the Adobe JIRA bugbase

Flex Powertools: Explorers article on Community MX

Posted in Flex, Tools, Community MX, Flex Builder 2, Flex 3, Flex 2, Flex Builder 3 by Joeflash on the March 17th, 2008

I’ve a new article on Community MX entitled Flex Powertools: Explorers, in which I review over 20 of my favourite Flex 2 and 3 explorer utilities and resources, which includes component explorers, styling & skinning explorers and resources, visual effects explorers and benchmark explorers.

Annoying Warnings Begone! (getting rid of compiler warnings in Flex Builder)

Posted in Flex, Flex Builder 2, Flex 2 by Joeflash on the December 31st, 2007

If you’re like me and still do manual versioning of files during a project (I do for spiking or prototyping), … and a bunch of the legacy versions of the file in your open project still give you annoying warnings or errors and you don’t want them to appear in the Problems view, you don’t have to close the project or move any files. Just remove them from the Flex Applications list under [project] > Properties > Flex Applications, and Clean your project.

The annoying warnings or errors for the undesirable files should then go away in the Problems view.

External Classpaths in Flex Builder 2

Posted in Flex, Flex Builder 2, Flex 2 by Joeflash on the November 21st, 2007

One of the questions that I get asked occasionally from other developers learning Flex is, “How do I make the code completion work with an external project?”

What you may be trying to do is linking to an external folder, by way of Navigator view > [Project Folder] > right-click > New > Folder > Advanced > Link to folder in the file system > [folder path]. This will indeed create a reference to a folder external to your project, or even your workspace, but it will not help Flex reference an external classpath for compilation or code completion.

For that, we need to configure an external compilation source. For this, we select Navigator view > [Project Folder] > right-click > Properties > Flex Build Path > Source path > Add folder > [folder path].

Keep in mind that for external classpath referencing to work, you don’t want to direct to an external project source folder, but the root classpath such as the “com” or “net” or other root class package, otherwise the classpath referencing for code completion in the editor will be misdirected.