Alan Shaw wrote: > What with all the recent events I feel somewhat like a python digesting > an elephant. > > Anyway for AS3 we'll have a command-line compiler from Macromedia > useable in Eclipse, and mxml for Flex. Does this subsume the > functionality of swfmill? > Is there a need for a swfmill tool in the new environment? > > I'm thinking right now about mtasc's ability to take as input a library > swf of assets > and add code to it. (Please no "skeletons" or "injecting" -- that makes > it sound like > a horror movie!)
There will always be a place for swfmill, as with mtasc (if it wasn't about to die a horrible death). Flex is a Flash based technology, but it is not the essence of flash. I think people are forgetting this. Not /everyone/ will jump onto the Flex bandwagon, and not /everyone/ will be able to afford to pay for yet another license. To all: just because Macromedia have finally come through with a genius master plan for Flash development in Flex 2 doesn't mean that everyone should suddenly stop developing open source flash tools. Why should the arrival of Flex2 imply the end of mtasc or swfmill? Flash is still there! Personally I think there is HUGE benefit in allowing projects such as ActionStep, ASWing, Deng and others to continue to be developed outside of the Macromedia toolset. It's not about competition, remember. This was discussed several times throughout the OFLA conference. It's about choice. And please, stop digesting elephants .. you are making me feel quite paranoid ;-) - IE _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
