>Not totally sure what you mean by that... Map symbols to classes via some kind of package explorer wizard: if you create a movieclip in Flash, it goes into the Flash Library as a symbol. When you right-click this new symbol in the Library and choose 'properties' you'll see a wizard in which you can associate the symbol with an actionscript class. It would be nice to have the same capability in this hypothetical Library plugin for Eclipse, only you can surf to the class and choose it instead of having to write 'com.arp.blah.blah...'.
> 2. Import existing Libraries from Flash and maintain symbols' package paths > Existing libraries in what format? A designer creates a new Flash file and creates the visual interface. He/she arranges his native Flash IDE Library, naming symbols and such. A developer then goes into Eclipse and from this hypothetical plugin can import that native Flash Library. >There may be issues with components/EULA. >yep, will need to look into that This is keeping people from sharing source and that is bad. Can't they just open source the components? Come on! (Bangs fist on keyboard.) Mike _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
