It really depends on whether you are using a version control system that replicates the repository's directory structure for a given project on each user's system (typical for code-oriented version control or configuration management systems such as SVN or VSS), or whether you are using a system that normally places all checked-out files for a project in the same directory (typical for document-oriented content management systems like Documentum). I have worked with both types of system, and have found that the optimum directory structure is quite different between the two.
-Fred Ridder > From: TSlager at isdcorporation.com > To: framers at lists.frameusers.com > Date: Tue, 18 May 2010 16:41:27 -0400 > Subject: folder structure > > I inherited a book with chapters and files in a complex directory structure. > We are changing from one version-control software to another, so now would be > a good time to change the folder structure. > > The complex structure makes it difficult to check out all the files in a book > at once. It seems to me that it would be easier to have files that are common > across products in a common files folder, and to have all the rest of the .FM > files for each product/FM book in a single folder, with images in an adjacent > folder. > > I am wondering if there are recommendations for file structure, and what are > the gotchas I'm likely to encounter if I move things around. > > Thanks. tims > > Tim Slager | ISD Tech Pubs | 616.494.1373 _________________________________________________________________ The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multicalendar&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5
