Posted by Blair McGlashan on Mar 30, 2001; 9:23am
URL: https://forum.world.st/SCCS-integration-problems-tp3359998p3360002.html

Bob

"Bob Jarvis" <[hidden email]> wrote in message
news:[hidden email]...
> I'm working on getting Dolphin to work with external version control
systems
> such as RCS or Visual SourceSafe, and I'm making some progress.  (For
those
> interested, go to
> http://www.nls.net/mp/jarvis/Bob/DolphinGoodies.htm and download the
> appropriate files).  The problem I have now is that the process is too
> manual, and I'd like to automate the checkout process so that if you make
a
> change to e.g. a class which is part of a package under source control,
the
> appropriate file should be automagically checked out.  OK, so off I go
> looking through the image for appropriate events to hook into, and there
in
> Package is the #changed event.  I concoct a bit of code, hook into
Package's
> #changed event, change a Package, and wahoo!  I get the appropriate event!
> I make another change to the same package and...no event.  A bit more
> investigation reveals that Package only triggers a #changed event if the
> 'changed' status of the package is changed - e.g. when the package goes
from
> 'unchanged' to 'changed'.  Drat...
>
> Anyone got any ideas?  I suppose I *could* check out all files in the
> package when any change is made, but that defeats the purpose of having
> multiple files (in PAX format) so that potentially multiple developers can
> work on multiple parts of a package with (minimal) interference.
Andy/Blair
> - any chance of getting Package changed so it triggers some event whenever
a
> change is made?

The individual objects in the package (classes, resources, etc) are also
flagged individually as "changed", and events are triggered when they are
changed/added (see the events published by SmalltalkSystem and
ResourceManager). These are the events that are picked up by the various
browers to keep them in sync.

Regards

Blair