1. Build a single uber-IDE capable of serving traditional Flash developers
and Flex developers. Of course, given the fundamental differences between
how these development models work, this would essentially consist of
shoehorning two IDEs within one program - there would be very little
commonality between them. Because they'd be building all this stuff from
scratch, it would presumably be more expensive and less reliable.
I don't necessarily agree with you here. The Flash IDE *could* have a
robust and useful "code view" that could also be used to build flex apps
without ever creating an fla file. That could be used to edit classes and
even timeline code, while the traditional Flash IDE view could be used to
make fla files, edit timeline animations, etc. I think it *could* be one
uber-IDE, as you called it, without necessarily being either more expensive
or less reliable. The root of the problem is that it's more profitable to
have two IDEs, because one makes developers from other languages happy and
one makes the users of previous Flash versions happy, and in the middle is a
rather large group of people who will have to pay for both. Making one IDE
would only make those in the middle happy, and would require Adobe to
rethink a lot of their existing code base instead of simply "polishing up"
the existing code base. More work and less profit doesn't make for a good
business model.
ryanm
_______________________________________________
[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
