The thing which I liked the most about the ENVY
environment is that they'd done a really robust O-O
analysis of code management (Editions, Versions, etc).

That would certainly be my starting point -- and then
with what we've got in Minnestore, the persistence
issues could be handled nicely.

Ranjan

--- "Jarvis, Robert P. (Contingent)"
<Jarvisb at timken.com> wrote:
> Speaking of "other useful tasks", has anyone got a
> line on an existing code
> management/versioning system (in the vein of Envy or
> StORE or what was that
> thing for Visual Smalltalk?) which could be ported
> to Squeak?
> Alternatively, would anyone care to offer
> suggestions, concerns, etc, on how
> to approach this?  I'm interested in the problem,
> and would like to
> implement it in Squeak (i.e. I don't want to do an
> interface to RCS or
> whatever).  I suppose I could prowl through a
> VisualWorks image and "borrow"
> ideas from  StORE but, aside from the legal and
> ethical considerations, that
> seems like cheating.  Comments, ideas, and/or
> pointers to existing work
> appreciated.
> 
> Bob Jarvis
> Compuware @ Timken
> 
> 
> 
> 
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com