Put 'em in seperate projects, or sub-projects. Like: com.company.project.admin.* com.company.project.client.
Or: com.company.projectadmin.* com.company.projectclient.* You should take advantage of the fact you may be using similiar code; both of the above in the same Flex project allows you to easily do that. ----- Original Message ----- From: "Stefan Schmalhaus" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Thursday, July 27, 2006 4:38 AM Subject: [flexcoders] Backend/Frontend Application Development (Cairngorm) I'm going to develop a Flex (Cairngorm-based) intranet application for training resources. There will be a backend part for user and content administration, and there will be a frontend for the end user. Both parts, backend and fronted, will presumably share a lot of the underlying data structure, value objects, views, etc. They will definitely use the same AMFPHP services. What's the best way to tackle this? Should I treat them as two different Flex projects? Or can I develop them within one Flex project but with two different MXML application files? Your ideas and thoughts are very much appreciated. Stefan -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
