Hello Flex, My group is planning development for an AIR app to replace our current CFML/HTML application. We would also like to have a 'Light" Flex version that leaves off a few features from the AIR version. I am new to designing large scale Flex/AIR applications and I would like your input on how to set up my project(s) so as to avoid as many unknown future problems as possible.
My goals for this architecture are: * AIR and Flex apps should share as much common code as is practical for easy maintenance * SVN friendly for multiple developers * Minimize headaches when compiling projects for localhost, development server, testing/staging servers, and production servers * Minimize download size for frequent updates (we are discussing making separate modules that can be updated independently) * "common sense" organization for developers that are new to OOP, Frameworks, and FlexBuilder/Eclipse My current approach is made up of guesses and assumptions and I am not opposed to changing anything at this point. I have set up 4 projects: a cfc project for providing data from the server, an air project for air specific code, flex project for flex specific code, and a flex library project for common code. We are all researching like crazy but we must keep showing tangible progress for the rest of the company to see. Any pointers or pitfalls you know of for such a project are much appreciated. Thanks! David -- [Image:Our Hero] David Henry http://ColdFusionPowered.com/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;160198600;22374440;w Archive: http://www.houseoffusion.com/groups/Flex/message.cfm/messageid:4995 Subscription: http://www.houseoffusion.com/groups/Flex/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.37
