on 2/28/07 2:39 PM, Tim Jones at [EMAIL PROTECTED] wrote: > On Feb 28, 2007, at 12:05 PM, Mike Woodworth wrote: > >> ugh... then you have to diff it. if this is gonna happen, store it >> in a separate file so we don't have to commit it to the repo. > > Good point, but the primary rbvcp file is very lightweight and > shouldn't change much unless you're adding or removing modules. It > basically tells the IDE what the parts of the project are and where > the actual rbbas, rsrc and rbfrm files are located on the > filesystem. So, saving the information as a newly defined > Project.layout file or as part of the primary rbvcp file should not > hamper proper version control management.
There real problem with storing layout information as part of the project (in one of the existing files or as a new file) is that other team members would then have each other's layouts forced on them. Can see having the layout information persisted in a preference file but please not anything that would ever be checked in. Chris _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
