— Forest and the Trees

Flex SDK 3.4 Extracting DataVisualization Source

Adobe released a new sdk for Flex which fixes a cross-scripting security threat. So, you download the sdk, unzip it, create a new directory for 3.4.0 in your flex sdks directory. Also extract the data viz zip and put its files in the appropriate directories in the 3.4.0 directory that you just added. (You could do this different ways as well.)

Then in Flex Builder, right click on a project, choose Properties, Flex Compiler, Configure Flex SDKs. And add your new SDK.

So, pretty sure there are plenty of posts on how to do the above. But, now you need to extract the DataViz source. This post explains that. And here’s what you can copy and paste into Terminal to get it to work if you’re on a mac.

java -jar “/Applications/Adobe Flex Builder 3 Plug-in/sdks/3.4.0/lib/DMV-source.jar” “/Library/Application Support/Adobe/Flex” “/Applications/Adobe Flex Builder 3 Plug-in/sdks/3.4.0″

The blog changes the straight quotes to curly quotes, so, you’ll probably have to change that.

  1. [...] Also, check this post for the command to type into terminal. March 31, 2008 | Filed Under Code, Data, Flex Charting, Visualization, charting  [...]

  2. Doug says: October 13, 20099:00 am

    Just stumbled across this link – covers the same thing, but might be helpful.

  3. Zach says: May 9, 20119:59 am

    I know this was a long time ago but… has anyone gotten the debugger to be able to recognize the source (i.e. allowing one to do breakpoints in the datavisualization source)?

  4. Doug says: May 9, 201111:51 am

    Flex uses the already compiled data viz swc for compiling swfs that use the data viz components. I.e., the source code you see isn’t actually used. So, adding breakpoints is going to be a hack.
    Best approach is probably to extend the class you want to debug, override the function you want to debug, and add breakpoints to that. Sadly, there are a lot of private vars in the data viz source – so you might just have to copy the entire class. I guess you could also copy the entire library, change the package names, and reference that in your code. As far as I know, there isn’t a more elegant solution.
    Hope that helps, Doug

Submit comment