Pushed

[Luke Bayes]

Hey Folks,

Sorry for the long radio silence, I haven't been doing much Flash work these days, so it's been difficult to prioritize some of this stuff.

Just wanted to let everyone know that I've pushed a new build to Github and RubyGems.

This build updates the default dependency versions to:

- Flex SDK 4.6.x

- Flash Player 11.1.x

And it also includes the following:

- Updates to the ADT/ADL - graciously provided by Simon Gregory

- Flex compiler options cleanup - graciously provided by Alan Pinstein

- Compc cleanup from Simon Gregory

- Fixed some installation errors that were cropping up in modern RubyGem installations.

You can get the latest with:

gem install flashsdk --pre

Thanks,

Luke Bayes

[Luke Bayes]

Somehow I failed to say Thank You to Simon and Alan in the last email.

So, here it is -

Big Thanks to Simon and Alan for doing this work and being so patient with me on getting it out there.

Thanks!

lb.

--
You received this message because you are subscribed to the Google Groups "ProjectSprouts" group.
To post to this group, send email to project...@googlegroups.com
To unsubscribe from this group, send email to projectsprout...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/projectsprouts?hl=en
 
For other info you can visit our project at: http://projectsprouts.org, or on Github at: http://github.com/lukebayes/project-sprouts

[Alan Pinstein]

:) Thanks, Luke!

And thanks to you for Sprout!  It is really awesome, particularly given how horrible Flash Builder is at managing complex projects.

FYI Flex 4.6 requires 10.3, whereas Flex 4.5 only required 10.2, so beware when upgrading.

On that point, Luke how do you manage to have multiple Flex SDKs installed for a single project? Is it possible?

Alan

[Luke Bayes]

Hey Alan,

I have definitely gotten multiple SDKs into a single build before, but it was quite some time ago.

The flashsdk includes different rake targets for flex3 and flex4, so it should be easy to compile against different top level versions at that point.

If you want to compile against different minor revisions in the same rakefile, you'll have to get more creative.

I believe the SDKs are generally backwards compatible, so you should be able to load the most recent flashsdk gem, but then in any given task, you'll want to set the 'executable' to a path on disk (relative is probably good) where you've manually downloaded and unpacked the sdk version.

This might look something like:

mxmlc 'bin/SomeProject-4.4.swf' do |t|

  t.executable = 'sdks/4.4.x./bin/mxmlc'

  t.input = 'src/SomeProject.as'

end

mxmlc 'bin/SomeProject-4.6.swf' do |t|

  t.executable = 'sdks/4.6.x./bin/mxmlc'

  t.input = 'src/SomeProject.as'

end

I believe that'll work - please let me know if it doesn't.

 

Thanks,

Luke

[Alan Pinstein]

Oh I was thinking more along the lines of using the same *compiler* but with different SDK's. I am not sure if mxmlc even does that...

Frankly I couldn't even figure out how to simply configure the project to use a different SDK. The 1.0 upgrade re-arranged a lot of that stuff to be more magical (ie how it bootstraps the SDK downloads) and I had a hard time finding how to even control it at the entire project level.

Alan

[Luke Bayes]

Ah - 

There was lots of artificial separation in the pre-1.0 versions of Sprouts that led to some confusion related to which bits required which versions of which other bits. I decided to assemble the Adobe stuff into larger, single units in order to simplify deployment and dependencies, but it's possible that I went too far with it.

Worst case, you should always be able to manually place any SWC files (even SDK SWCs) into your project lib folder and load them using the library_path parameter on your MXMLC task.

Hopefully, the compiler will ignore the built-in SWCs and not compile both into your SWF, but I can't guarantee that...

Please let me know if this works for your use case.

lb.