Wow that is great! So basically, the method in which clients retrieve their SWF files are the same as getting a plain old SWF file created using Flash?
So the Flex SWF (which gets compiled on the developers machine) simply gets copied to the Web Server hosting the application. That is great! I hated the fact that there was this elaborate ADDITIONAL server component, that was required to hand out .mxml files (which of course, end up being swf files in their final form). If I hear you correctly then, there is NO Data functionality built into the BASIC Flex 2.0 Architecture? For a SWF file to have the ability to Send/Receive Data to a Server (whichever flavor that may be), a type of "connector" must be purchased beforehand, in order for that functionality to be enabled? Does the developer have "crippled versions" of these connectors available to them, so that they can write the apps and actually test them? Or do they have to fork out right away for these connectors, in order to give their Flex Apps the ability to exchange data with servers? THIS is the part that I need clarified in a major way, so that I can get a handle on my software costs for the year. I just hope I can afford all this stuff, so that I can simply write functional Flex Apps to tease my clients with. You know, it's really the developers that sell your products for you - getting their clients excited and showing "what can be possible", but if it's so cost prohibitive where the developer can't even afford it, it's kind of a moot point. Can you shed more light on that topic? Thanks again for everything :) Mike -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Watts Sent: Wednesday, April 05, 2006 12:44 PM To: Flashcoders mailing list Subject: RE: [Flashcoders] Flex Apps versus Flash Projector apps > Other than Flex 2.0 being more advanced than 1.5, what are the major > differences between the 2? By default, compilation is done on the developer's workstation, not on a server. By default, you can build Flex 2 applications without any server component; they can talk to a server using web services, etc. By default, you can distribute Flex 2 applications just like you would any other sort of SWF. There are server-side components to Flex - Flex Data Services and the CF-Flex connector. Flex Data Services allows you to push data to Flex clients, among other things. The CF-Flex connector allows you to more easily exchange data between ColdFusion and Flex. If you use those server-side components, you'll have to (a) purchase them and (b) deploy them on the production servers where you use them. Personally, I think the biggest difference between Flex 2 and previous versions is the performance of the 8.5 player - applications load faster, run faster, and can handle larger data sets in my limited experience. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! _______________________________________________ Flashcoders@chattyfig.figleaf.com 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 _______________________________________________ Flashcoders@chattyfig.figleaf.com 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
