Ramon Smits

Tell me your secrets and i'll tell you mine

Recent Posts

Tags

Community

Email Notifications

Patterns & Practices / Guidelines

EntLib

Nant

Blogs that I monitor

Archives

SourceSafe Spy screenshot

A couple of collegues wanted to know what kind of popup you would get when SourceSafe Spy will notify you and with what information.
SourceSafe Spy popup

I think it is pretty cool but that's because I'm a bit biased...

Comments

Erwyn van der Meer said:

This looks pretty cool indeed. I will give it a try tomorrow.
# August 11, 2005 2:03 AM

Robert te Kaat said:

Can you explain why one would want a popup for every single file that gets checked in/out/whatever? I understand that it can be helpful when you're waiting for someone else to checkin a document which you need to edit as well, but in a big project, files get checked in and out every minute, so I guess the popups (or emails!?!) will get pretty annoying.
... or am I missing something here?
# August 11, 2005 4:47 AM

Damien Guard said:

I imagine on small teams where you check in blocks of work as opposed to individual files it would be quite useful.

I know it would be useful here if it ran on Subversion.

[)
# August 11, 2005 4:51 AM

Robert te Kaat said:

But VSS doesn't support checking in blocks of files (like an atomic action).
# August 11, 2005 8:39 AM

Ramon Smits said:

@Robert : You are right about the many popups that could get on the screen. In the current dev tree I've already modified the code so that you only get a sound notification when there haven't been notifications the last 5 seconds.

I could ofcourse add the option to only display one popup to notify that the journal has changed. But then you would have to open the main window to see what changes occured. So that is not really usefull.

About SVN... I use SVN as a repository for SourceSafe Spy.. :) SVN is so much easier to work with then SourceSafe.

In the next version I want to add a regex pattern matcher for the the resource string. This way you can get a notification for a piece of tree that has changed. This way you can see what CI's are changed. This ofcourse will only work if you have well designed repository tree.
# August 12, 2005 5:19 AM
Leave a Comment

(required) 

(required) 

(optional)

(required) 


Please add 1 and 6 and type the answer here: