Oooh, and if Versions and/or a SVN menu item used Growl notifications (like CCMenu, http://ccmenu.sourceforge.net) when updates are pending on the server... That would be really nice when working in active repositories—resolving conflicts early makes them a lot easier...

 - Quinn


On Feb 12, 2009, at 4:08 PM, Quinn Taylor wrote:

I know what you mean, Versions is certainly the pretty face of SVN to me. Command-line SVN is still comfortable to me, but imagine my pain in going to work and having to use CVS...

While a menu item could be configured to point to any SVN working copies, I admit that it would be nice if it had the option to integrate with Versions by reading its prefs file and using the working copies configured in Versions.

The Versions devs could make this easier by exposing the bookmarks a little more easily... Scraping through ~/Library/Preferences/ com.picodev.Versions.plist (either in Property List Editor or 0xED) doesn't turn up any plaintext representations of working copies. If that was available, it would be pretty simple to whip together a menu item. Of course, most of the work has already been done and exists in Versions, so it would probably be even better if there was an OS X framework for using the same code Versions does.... </idle wishing>

- Quinn


On Feb 12, 2009, at 2:57 PM, footydirec...@googlemail.com wrote:

Yes, thats what I was thinking of, why didnt I think it was an SVN
function not Versions? just so used to treating Versions as my
repository handler, stopped thinking of them outside Versions :-)

I can appreciate it may be a nuisance for those managing lot of
repositories.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to