I'm just as confused. The only thing that I came up with was to maybe have a group of components that matches Flex's controls (Button, TileList, etc). You could lay a group of those components out and use component parameters that corresponds to a Flex property. Once you were finished the layout process, you could run the JSFL and voila, you'd have your mxml which you could then use with Flex, adding DataProviders, scripts, etc.
Of course, you'd also have to be able to import from mxml into an .fla or the workflow would be one directional.
Is this what anyone else had in mind?
Tim
On 7/11/06,
John Grden <[EMAIL PROTECTED]> wrote:
I'm sorry to be the noob on the block, but how does this work out practically?
I mean, if you have an FLA with movieclips that have movieclips that have movieclips embedded blah blah blah, how's that worked out in mxml? An mxml file for each movieclip? Ok, I can see that, then you have to come up with some logic for packages based on the movieclips relationships? what if the movieclips aren't bound to a class? where do you park those? I mean, you'd have to create some package/class for each right?
On top of all that, how would you account for movieclips that don't show up until frameX? Would that just be a "state"?
Are you suggesting a full FLA conversion no matter how wacky it is or are you thinking just certain types of FLA's that follow some sort of pattern/guideline?
And although it sounds like fun, what'd be the major benefit of having something like this? Just the ability to compile with the new / free / fast compiler? And how would it be apart of someone's work flow?
IE: Do I have to export everytime I make a change in the FLA, then compile?
Or, do I create/get the FLA, convert via JSFL command, then edit within the mxml after that point?
if it's scenario #2, then what happens to the FLA and it's library of assets (bitmaps, sound, flv)? do you export all of them out, then embed for the application to use?
Sounds like fun, and would be interesting to see, but not sure that starting from scratch wouldn't be better/easier. I mean, sounds like if Flasc could work to be used with the new compiler of MTASC, that'd pretty well help out with the problem that this might solve.
Sorry, just thinking off the top of my head, it DOES sound like fun ;)On 7/11/06, Michael Stuhr < [EMAIL PROTECTED] > wrote:Ralf Bokelberg schrieb:
> Nice idea, but the question is, what to do with the resulting mxml?
send it to the free compiler, and lets see what results we get :-)
point is: the free compiler needs a layout tool like flex has one.
it's a 'nische', and if it isn't too complicated one should try.
micha
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
--John Grden
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
