We've moved recently to using Subversion over CVS. I would highly recommend you move to that too as it adds some flexibility as you grow, easily renaming/moving things without loosing history is a big plus for Subversion, especially if you are running into issues deciding exactly what structure you are happy with.
I've actually spent a lot of time recently thinking about these problems. We have an application that contains Flash, FlashCom, ASP.NET, WinForms, C++, and SQL Server. Getting a good directory structure has been pretty difficult honestly, but I think it is do-able. The things that I've learn to accept is that some things you won't figure out until you start using it within the team and people find it hard to work with and decide to move things around. I posted a first entry to this problem a while ago that might help http://www.rewindlife.com/archives/000208.cfm (some of the info I plan to change in a post soon as I've had more time to think about the problem) For me the thing that I can recommend is to checkout the Jakarta recommendations for directories http://jakarta.apache.org/site/dirlayout.html , also checkout the book pragmatic version control using subversion. Microsoft also has some discussion on their website which I don't have handy right now. I was actually pretty shocked to find so little information on this subject, I guess very few people actually try to store multiple languages in one storage location or even have an application that isn't all written in one language. Another thing is to get used to sometimes having to split a project into "client" and "server", or if you are multiple platforms supported then "w32" and "osx", I had a hard time accepting this as a solution but there's no way around it that I've found. Also jesse mentioned the lib folder, I do the same thing but inside I actually split it by "as", "csharp", etc. As for development model, each one of our developers has his own setup locally which allows them to work anywhere easily when traveling, be able to test/etc then check everything in when they are ready. You can get a free development version of Flex for each developer, and have the server run a real license. Once a developer is ready they can check in we their code and then automated build process takes place, builds all the different items, runs the unit tests, and deploys it to our development server where it can go through more testing and eventually we have a release. I don't know if this model will work for you, it all really depends on what you are working on. If you are working on a single solution for a client with only one release then this is probably overkill, if you are working on a product that has to be maintained long-term then having these extra steps is a pain at first to setup but can really save you a lot of time down the line. Finally, although our process doesn't currently integrate Flex (we don't use Flex for any of our products yet), it wouldn't be hard to replace our Flash interfaces with Flex, Macromedia includes a command line compiler so that's great for automating the build process, or you can just deploy your mxml files to the development server if that is what you prefer (I prefer pre-compiling). HTH Chafic http://www.blinex.com blog: http://www.rewindlife.com Team Macromedia Member -----Original Message----- From: temporal_illusion [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 05, 2005 6:15 PM To: [email protected] Subject: [flexcoders] Development Environment Setup Q's I've been thinking recently on how to setup a good development environment for multiple developers on the same Flex application. Using CVS or Subversion would be the goal. Getting a production or test version out of CVS could be done with Ant, that seems simple enough. Where I run into problems is the structure of the different files on the server side and how to get those into the module/modules in CVS properly. In all my previous projects with CVS it's been a single language involved, so having all the Java files in one module (or a few if there were shared libraries) was easy. In this case there's the actual app directory with mxml and as files. Then there's the directory with the remote java objects files (which is shared between apps). And the directory with shared as files (also shared between apps). And in my case there's also going to be the internal web services in cfc files. Making seperate modules for each of these doesn't feel right. And configuring the server side so each developer has their own directory so they can rip apart what they're working on safely doesn't seem right either. But I don't think I can install a local copy of Flex and ColdFusion on each machine to develop from (can I?). Any wisdom from the experienced here? Jason Yahoo! Groups Links 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/
