My idea on how to handle version-control integration in an achievable timeframe without having to write massive GUI's and build in ways to drive X products...
Say you are using subversion for version control. Adding, renaming or deleting members of your project will affect files on the file system. These file-level operations need to be propagated to the version- control system but there is no way to react to them. Probably the easiest way for a user to cope with would be allowing scripts to be triggered on item create, rename, folder move or delete. So if I renamed class FooPainter to BarRender, I would want the script invoked with sufficient information that I could have a script DoShellCommand "svn rename ~/dev/Andy\ stuff/FooPainter ~/dev/Andy\ stuff/BarRender" Presumably this would provide enough for other scriptable or command- line version control systems to be similarly updated (I only know svn and cvs). -- Please comment! http://www.realsoftware.com/feedback/viewreport.php?reportid=bpyuxlng _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
