>> I see it beneficial (for me at least) to replace the Flash IDE with an editor (Brady?) and a compiler.
so do I. and that's why I'm saying it'd kill FLEX server sales. why have very restrictive licensing for the flex server if all you want to get is an easier way to make the SWF? just adding fuel... barry.b -----Original Message----- From: Chris Velevitch [mailto:[EMAIL PROTECTED] Sent: Wednesday, 5 May 2004 10:40 AM To: CFAussie Mailing List Subject: [cfaussie] Comparing Flex and Flash (Re: Cold Fusion vs ASP) On Tue, 4 May 2004 15:53:11 -0700, Sean A Corfield <[EMAIL PROTECTED]> wrote: > On May 3, 2004, at 6:37 PM, Chris Velevitch wrote: >> That's a fine strategy for developing business in a new market. But the >> problem is, Macromedia has reinvented Flash, basically making more >> attractive for existing developers who currently use Macromedia tools. > > Flex is primarily aimed at a new market rather than existing Macromedia > developers - J2EE and .NET application developers are not, currently, > Macromedia developers in the sense you mean (if I understand you > correctly). That may be so, but it doesn't mean there can't be some unintended uses for the technology. > >> But I need to statically generate swf files and MXML makes that whole >> process easier. > > MXML relies on server-side machinery provided by the Flex system - it's > far more than a compiler. The notion of releasing a "standalone MXML > compiler" doesn't really make sense when you understand what MXML > provides (the data modeling, the remote service binding etc - that all > depends on server-side machinery). You haven't really shown how Flex plus a server differs from Flash IDE plus a server. Both Flex and Flash IDE generates .swf files. These .swf files run on the same Flash Player. The Flash Player can connect to remote services (web services, Flash Remoting, etc). That is they both rely on some "server-side machinery" (ie Flash Remoting, Web services etc). Prior to the release of Flex, using the Flash IDE you are abe to create .swf files that connect to remote services. The Flash IDE has components to allow you to create a .swf file to connect to web services. In order to connect to remote services, you have to have a data model in the Flash IDE. I see no real differences from the perspective of application development. As I see it, the basic difference between Flex and Flash IDE are:- 1. The language format for Flex is straight XML text (.mxml) and the language format for Flash IDE is a propriety binary file (.fla). 2. Flex compiles the .swf file on the server, Flash IDE compiles the .swf on the client. 3. Flex as a better set of components than Flash, but they are an improved version of the components that ship with Flash IDE. (If you have Flex, you'll notice there is a flexforflash directory which contains all the Flex components for use with Flash IDE) 4. Flex is easier and more productive that Flash IDE. 5. I haven't tried this, but I suspect Flex allows you mix MXML tags with CFML, JSP, etc tags thereby making the input dynamic to the .swf generator whereas, Flash IDE relies on static input. 6. Flex automatically generates and deploys .swf files, Flash IDE requires manual generation and deployment. I think the really big deal about Flex is the language format. I new to developing Flash-based UI's and I find it slow going using the existing Flash IDE. I've done a couple of Flex tutorials, and seems quicker. Others have also commented that Flex is quicker to develop applications. I see it beneficial (for me at least) to replace the Flash IDE with an editor (Brady?) and a compiler. Chris --- 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 --- 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
