I hate to keep flogging this topic, but I couldn't stop thinking about this all through lunch. I will make the following comments and then move on to more useful things.
1. The mere existance of this thread suggests to me that Adobe hasn't done an adequate job explaining what purpose Flex serves, and how it's supposed to integrate with current workflows. Maybe they will when they release, but they haven't yet. 2. I don't buy the argument that Flex is *just* for making forms apps. There are a number of features in Flex that would be highly desireable for the Flash IDE, such as the ability to use XML to define a Flash file. If I want to take advantage of these features, I'm going to have to use Flex, regardless of whether I am a Forms Developer or a Non-forms Developer. 3. I am all for Adobe having a wide variety of IDEs, including Flash Newbie Edition, Flash for Recovering VB Coders Edition, and Flash Super-Ultra-Mega Enterprise Edition. But I am questioning the decision to segment the product line in such a way that requires me to invest in two overlapping but distinct tools. I love Flash. If Flex brings more "traditional" developers on board with Flash I think that's great. But I wanted to share my perspective as someone who's been developing Flash for years, that these developments are somewhat perplexing. _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
