I keep the Flex source in subversion and the Flex project settings out. Source being .as and .mxml. Project settnigs being .project and .settings. "Project settings" is clearer than "project."
Yes, I uncheck the "non-embedded" option when working with source control. -Mike Chabot On Dec 12, 2007 9:17 PM, DannyT <[EMAIL PROTECTED]> wrote: > > > > > Well that's reassuring as I use: > > Trunk/client/ > Trunk/server/ > > Can you explain what you mean by keep the flex project files separate from > the source AND keep them out of subversion? > > Also i've read about not including non-embedded files in output directory, > which sounds logical to me, do you do this? > > Cheers, mucho appreciated > > Dan > > On 13/12/2007, Mike Chabot <mchabe > > > > > > > > > > > > > > > I have it set up as this: > > /trunk/FlexSource/ > > /trunk/WebSite/ > > > > I keep Flex project files separate from the source code and keep the > > project files out of Subversion. > > > > The setup has been working well for me. The people on the project that > > have nothing to do with Flex can just check out the /trunk/WebSite/ > > folder. > > > > Someone else I know has their's set up like this: > > /trunk/ui/ (flex code) > > /trunk/services/ (java web services that supply flex) > > > > -Mike Chabot > > > > > > On Dec 12, 2007 8:21 PM, DannyT <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > I've seen a couple of threads on this but not enough for a definitive > > > conclusion. > > > > > > I'm trying to define a standard practice for source controlling a flex > and > > > back-end project (namely flex -> remoting -> .net ( -> sql?) > > > > > > Do people tend to treat their server-side projects as a separate project > in > > > a separate repository? > > > > > > With everything in the one repository you can keep local compilation > > > consistent and check-in build scripts, however by splitting up into > multiple > > > projects you're keeping flexibilty and managability by not bloating your > > > repository. > > > > > > I guess it'll come down to preference but was just wondering what others > are > > > doing, as a general rule our developers currently will be dealing with > both > > > client side and server side projects but down the line i'd like to see > > > clearer separation of roles. > > > > > > Any thoughts or practices people can throw in would be much appreciated. > > > > > > Dan > > > > > > -- > > > http://danny-t.co.uk > > > > > > > > > > -- > > http://danny-t.co.uk > >
