Tal, I would still use Subversion.
Think of Subversion as as an electronic filing system. You can organize code into project trees, with sub-folders and so forth. As you come across code snippets that you want to save, copy them to a file and commit the file to a project tree or sub-folder, based upon the domain of functionality. Add related code snippets to the same domains. That way, you have related code snippets in a common area, making recall easier. The advantage of using a VCS is that you can make trackable modifications to the code over time, as your functional requirements change or as you discover bugs, etc. to existing code. In terms of a GUI, for Windows, it seems that most use Tortoise SVN: http://tortoisesvn.net/ There are cross-platform GUIs such as RapidSVN (http://rapidsvn.tigris.org/ ), but it all depends upon personal preferences. More links here: http://subversion.tigris.org/links.html#all-clients There are also Subversion extensions for editors, such as Emacs, like psvn.el (http://www.xsteve.at/prg/vc_svn/) which enable a blending of functionality into environments that you may already be using, such as ESS. Last but not least, there are also commercial variants of Subversion clients, which of course have a cost associated with them. These are also listed on the clients link above. An alternative would be to create a local wiki, the implementation details, as with a Subversion repo, would be dependent upon whether or not you are the only person that needs access or if access and/or content modification are to be shared. HTH, Marc On Nov 22, 2009, at 11:45 AM, Tal Galili wrote: > Hello Marc and Jeff, > Thank you for replying. > > I am using winXP, and any recommendation for GUI based system will > be welcomed. > > However, my initial question was not how to maintain code that I > write and develop, but rather how to keep a "filing system" for > other peoples code that I find useful. > Here are some simple examples: > A code to allow me to start a window with "history" recording turned > on. > A code to have wider margins so to allow more space for the plot > labels. > A code for creating an ellipse plot of a matrix of correlations. > All of these example are things I wouldn't put into a Subversion > system or a new package. > > I hope my question was made more clear, and your answer will be much > appreciated. > > Best, > Tal > On Sun, Nov 22, 2009 at 7:13 PM, Marc Schwartz > <marc_schwa...@me.com> wrote: > On Nov 22, 2009, at 10:53 AM, Tal Galili wrote: > > Hello all, > > When using R for some time, one comes across more and more useful > functions. > But naturally we can't remember all of them, so I imagine some of > you save > these snippets of code. > My question to you is how do you manage that code? > Do you use special software, or archiving system? > > Any advice is welcomed. > > Tal > > > One word: Subversion (http://subversion.tigris.org/) > > A version control system is a critical part of any code management > process. > > If you or other users may not be comfortable at the command line > using it, there are a plethora of GUI based clients for Subversion > available depending upon the operating systems you are using. > > HTH, > > Marc Schwartz > > [[alternative HTML version deleted]] ______________________________________________ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
