Flex Data Visualization Library

1 view
Skip to first unread message

Luke Bayes

unread,
Sep 30, 2009, 1:24:57 PM9/30/09
to project...@googlegroups.com
Hey Folks,

I just pushed a new library gem for the Flex Data Visualization SWC.

You can include this library in your ActionScript 3 or Flex projects
from the project model, or an MXMLCTask as follows:

# Using Project Model will auto-include for all Task Helpers:

project_model :model do |m|
 m.libraries << :flexdatavis
end

# Manually reference the library, and add as dependency for relevant
build tasks:

library :flexdatavis

mxmlc 'bin/SomeProject.swf' => :flexdatavis do |t|
end


This library will only include the SWC, and I haven't tested
completely - there may still be some manual steps required to get JAR
files into your SDK.

One option I'm considering, is the post-install Ruby hook that's part
of Library tasks. We can append arbitrary ruby code to get executed
after a library is downloaded and unpacked. This could conceivably
copy files over to the SDK, assuming we have a fixed SDK version we're
hooking up to?

Another option, is to put some Ruby files somewhere like script/ or
config/ that your rakefile includes - these could then automate the
copying if necessary with more detailed knowledge of the particular
project.

If anyone has some better ideas, I'm all ears. How would Rails
accomplish something similar? I keep thinking a vendor/ folder would
be a good place for these sorts of things - seems like there's a good
argument for not checking giant SDKs into version control, but on the
other hand, if you're actually modifying what was downloaded - that
seems like something you'd want to limit to a per-project setting -
rather than changing how every project on your system behaves.


Thanks,

Luke

Reply all
Reply to author
Forward
0 new messages