mx.effects.easing -- fl.transitions.easing

[jonas]

I was wondering if anyone knows a way around the whole easing
discrepancy using the mx.effects.easing vs fl.transitions.easing.

I love working with the textmate/flex sdk combo, but none of my
designers have a clue beyond the flash ide. If they were to compile a
project we're working on right now, it'd crash looking for the flex mx
easing classes, I'd love for it to work on both sides of the fence.

Is there anyway to build a workaround into the rakefile -- passing
more info to the mxmlc source path?

Ideas appreciated.

[Luke Bayes]

I'm not sure about the easing disparities, but it should be pretty trivial to knock out a JSFL script that executes rake from Authoring if you want to expose your build process to the design team.

Another idea that would be kind of painful to maintain - you could create some slightly different build tasks for authoring-driven builds eg;

MXMLC.new(:compile_main) do |t|
   t.cp << flex_path
end

MXMLC.new(:compile_main_from_auth) do |t|
   t.cp << auth_path
end

To be honest, we usually treat authoring builds as code-free asset libraries whenever possible and then simply point our engineering builds at the resulting asset swf. This generally does limit the amount and type of work that can be done in authoring, but if your application is in any way dynamic, the last thing you want is timeline driven animations anyway.

Luke

[jonas j]

ok, that actually sounds really nice. let the designers build their asset libraries, spit out an swf and access it from code... I currently don't have much of a clue how I'd do that, but I think I remember seeing people make some posts about it.

Thx Luke.

j.

[Luke Bayes]

We're actually working with some really great designers right now on a project and created some really simple JSFL scripts that work off of simple asset naming conventions. As long as the designer suffixes their library symbol with '-full' or '-thumb', our JSFL script will spit out a swf file for that symbol.

It's pretty painless and the script only took an hour or so to write. The designers seem to like it because in this case, we're loading those assets at runtime and they can see new skins just by hitting a JSFL command and reloading the latest source.


Luke