Chris Velevitch wrote:If you choose Flash for the client, it doesn't mean you've chosen FLEX on the server.
I think I'm part of the target audience for Flex - I'm a text-based programmer, used to compilers and similar technologies (think C, C++,
Java etc) and if I want to produce a Flash user interface my only choice until very recently was to struggle with the timeline-based metaphor of the Flash authoring environment. The MX 2004 Pro forms & screens idiom has helped but it's still not very natural for someone like me to build Flash UIs. Flex makes it much more natural: a text-based programming language (XML / ECMAScript) and a compiler. That means - for me - choosing Flash for the client pretty much does mean choosing Flex on the server...
Sean, you say it's not natural for you to build Flash UIs. Is it natural for you to build non-Flash UIs? Are you a UI person?
Your issues with the Flash authoring environment is understandable, afterall, other IDEs for building UIs generated text code. Will there be a Flash authoring environment that will generate MXML? Will that IDE seamlessly interact with source code control (SCC) systems, bug tracking systems and configuration management (CM) systems? As "a text-based programmer, used to compilers and similar technologies" aren't these the sort of tools and capabilities that you'd expect?
If there existed an IDE that generated text files and seamlessly integrated with SCC, bug tracking and CM systems and a compiler generate SWF binaries, would be there really be a case for FLEX?
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
