That's very true, and I readily agree with you, but this is a school project and we have to implement the versioning in iFolder.
-----Original Message----- From: Tim Uckun [mailto:[EMAIL PROTECTED] Sent: Wed 2006-10-04 5:22 PM To: Brandon Saxe Cc: Johnson, Chad; [email protected] Subject: Re: [Ifolder-dev] iFolder server code Why not just use subversion with a tortoise front end if that's what you want.? If you want to automate update and commit a simple windows task to call svn update and svn commit might to do the trick. Come to think of it you could also hack tortoise svn to provide almost all the functionality of ifolders without too much hassle I would think. Just my $.02 On 10/3/06, Brandon Saxe <[EMAIL PROTECTED]> wrote: > I've thought of doing this myself, except that I thought it would be better > to mount the filesystem that is hosting the ifolders to an autoversioning > subversion server. > > I'm not sure of the implications of this, but I thought it would be better > than trying to change the ifolder source and adding features that are done > already using other tools (in this case, subversion). > > > > "Johnson, Chad" <[EMAIL PROTECTED]> wrote: > Hi, > > I'm working with a small team to add versioning capabilities to the iFolder > project. I am looking for any documentation about how the source code for > the server is structured - codewise (purpose of classes, etc.) and filewise > (purpose of source files/directories). Basically we're looking for the entry > point in the code. > > Anything anyone can pass along would be great. Thanks! > > > Chad > _______________________________________________ > ifolder-dev mailing list > [email protected] > http://forge.novell.com/mailman/listinfo/ifolder-dev > > > _______________________________________________ > ifolder-dev mailing list > [email protected] > http://forge.novell.com/mailman/listinfo/ifolder-dev > > _______________________________________________ ifolder-dev mailing list [email protected] http://forge.novell.com/mailman/listinfo/ifolder-dev
