@David: > We are indeed working on speed for the Flex Builder 2 compiler and > don't > know yet how far we will get, but this is a priority.
That's great to hear. I'm still haunted by nightmares of the last project I compiled in the Flash IDE (+45 seconds for each compilation). Also psyched to hear that (at least it seems) the Flex2 compiler will be able to be run from the command line and integrated into i.e. Eclipse. The problem with Flash MX 2004 IMHO is that it tried to be all things to all people: the drawing and animation interface for designers pales in comparison to more mature products like Photoshop and After Effects, and I don't think I need to comment on the actions panel ;) I think it's all about the right tools for the right job. I prefer to do my interface design in Illustrator and compile assets into an SWF with swfmill. For me, this is *much* quicker than working in the Flash IDE (on OS X no less). While there are certainly commercial motives for offering a program that can be used by all members of a team putting together a website, I think that the more MM starts to see Flash and Flex as part of a larger build environment, and less as a one-stop-solution (though Flash 8 and Flex both look great), the better for both MM and the Flash dev community at large. @Hank: > I dont mean to diminish the significance of speed, because it is > clearly critical. But for me, the fact that in flex2 everything is > already syntax checked, as it is in the eclipse java environment, is a > huge performance win that might just overshadow mtasc's performance > benefits. I am not absolutely sure I feel this way becuase I havent > done enough project building in flex2, but I do know that when > programming in java, the fact that I can scan my project outline and > *know* that there are no compiler errors or warnings is a huge > performance win. It cannot be understated. I don't know about the other devs on this list, but for me compilation speed is WAY more important than syntax checking... I run into very few typing errors, and when I do I can usually track them down fairly quickly with my log. I do very iterative development, making small, isolated changes, adding a feature here, changing an interface there, and compiling many, many times an hour. A difference of 10 seconds adds up to hours a week in saved time, and since I'm easily distracted (who isn't?) a fast compiler also helps to keep me in flow. ___________________ Ben Jackson Diretor de Desenvolvimento [EMAIL PROTECTED] http://www.incomumdesign.com _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
