In our team of Programmers we need the function of logging a prg when we
edit it. All other users must only have "read only" rights. When I toggle
from "read only" in the edit mode, the editor must control the actuality of
the prg and update it, if necessary. At last, it is useful to toggle between
"read only" and "edit-mode" about a shortcut. Other editors, like ED4W from
GetSoft, have this function and I think it is indispensable for a team of
programmers.



Greetings



O.Bauer

Oliver,

> In our team of Programmers we need the function of logging a prg when we
> edit it. All other users must only have "read only" rights. When I toggle
> from "read only" in the edit mode, the editor must control the actuality of
> the prg and update it, if necessary. At last, it is useful to toggle between
> "read only" and "edit-mode" about a shortcut. Other editors, like ED4W from
> GetSoft, have this function and I think it is indispensable for a team of
> programmers.

I use Ed4W, and the automatic lock/unlock of files is a feature I use
heavily even though I am on my own.  However, I have two things to say
about this:

1.  It is NO replacement for proper management, where tasks are managed.

2.  In environments where multiple developers need to edit the same files,
a version control system is a MUST, preferably one like Subversion which
can handle two people editing the same file at the same time, and then
merge the two versions into the repository.

Not only will Subversion gracefully and transparently merge the two
versions, it offers the safeguard of being able to revert to a previous
version.

If you want to physically block people from editing the same file, then the
next version of Subversion will handle this, but in the meantime you can
also use VSS or PVCS or such like.

Regards,

Phil Ide

***************************************
* Xbase++ FAQ, Libraries and Sources: *
* goto: http://www.idep.org.uk/xbase  *
***************************************

This space available for advertizing.

On Thu, 17 Mar 2005 11:00:03 +0000, Phil Ide wrote:

> If you want to physically block people from editing the same file, then the
> next version of Subversion will handle this, but in the meantime you can
> also use VSS or PVCS or such like.

I just can double Phils statement. But after working for quite a while with
Subversion, I can't see a real benefit in locking files which are in use by
someone else.

One more comment:

I used to work VSS for a long time without major problems.

Funny enough, after switching to Subversion, I accidentially found a lot of
reports on the internet about total data losses and really BIG problems
with VSS... especially funny is this quote from a "Subversion vs. VSS"
document:

"Visual SourceSafe?  It would be safer to print out all your code,
    run it through a shredder, and set it on fire."

(Complete text: http://www.wadhome.org/svn_vs_vss.txt )

Thomas

Xbase++ FAQ : www.software-braun.de/xbasecentral/xbfaq/
"I'm thinking of thinking of calling her right after my afternoon nap.
 I'm thinking of thinking of sending her flowers right after Bonnie gets
back.
 So many fishes left in the sea.
 So many fishies, but no one for meeeee...
 I'm thinking of thinking of hooking a love soon after supper is done."
		-- G'Kar's song, "The Parliament of Dreams"

On Thu, 17 Mar 2005 19:06:47 +0100, Thomas Braun wrote:

> I used to work VSS for a long time without major problems.
               ^^^<---------
Please insert  "with" here

Thank you for listening 

Thomas

Xbase++ FAQ : www.software-braun.de/xbasecentral/xbfaq/
"What's a little foreplay compared to cannibalism?" 	- David Randall

Thomas,

> I just can double Phils statement. But after working for quite a while with
> Subversion, I can't see a real benefit in locking files which are in use by
> someone else.

ACK.  Aside from code, we also have repositories for critical
documentation.  For example, we have one which stores the disaster recovery
plan. When we agree on an update to the document, both myself and my
colleague update it at the same time - me updating the procedures to be
followed at the Cavenham site and he the same for the Bournemouth site.
Not having to lock the document (in fact, since it is a Word document, the
very fact the we can both edit at the same time is a huge bonus) makes
contention a non-issue.

> I used to work VSS for a long time without major problems.

Me too, although having come from a PVCS background, I found its lack of
features disturbing.

> "Visual SourceSafe?  It would be safer to print out all your code,
>     run it through a shredder, and set it on fire."

ROFL!

Regards,

Phil Ide

***************************************
* Xbase++ FAQ, Libraries and Sources: *
* goto: http://www.idep.org.uk/xbase  *
***************************************

Columbus had a fourth ship - it sailed over the edge.