Is there a setting, that takes care of managing edit rights
on prg-files in a multi-user environment.

IOW. can other users be prevented to edit a file that is
opened with VX?

Regards,
Frans Vermeulen.

Frans Vermeulen wrote:

> Is there a setting, that takes care of managing edit rights
> on prg-files in a multi-user environment.

This is a very old-fashioned way of organising development with multiple
developers who work on the same project.

> IOW. can other users be prevented to edit a file that is
> opened with VX?

Use a version control system like Subversion, where each developer can work
freely on his local working copy of the project while the "current" version
is in a file repository on a server. 

Please consider reading the first chapter of the online Subversion book,
that shows the fundamental concepts:

http://svnbook.red-bean.com/nightly/en/index.html

(AFAIK) Unfortunately, so far the VX IDE does not have any options to
integrate with any VCS system - but for Subversion, there are various
graphical frontends available that makes managing the repository and
working copies very easy. I'm working with TortoiseSVN, which integrates
with Windows explorer very well.

Thomas

Thomas,

In my case, SVN is highly overkill.
We work with 3 developers, and problems rarely occur,
however, they should not occur at all !

Old fashioned, maybe it is. But that's the way fi.
multi-edit works, and I have to face that fact.
And I am looking for a way with VX to coexist
with other editors.

Anyway, thanks for the reply,
Frans Vermeulen


Op 30-07-2010 15:33, Thomas Braun schreef:
> Frans Vermeulen wrote:
>
>> Is there a setting, that takes care of managing edit rights
>> on prg-files in a multi-user environment.
>
> This is a very old-fashioned way of organising development with multiple
> developers who work on the same project.
>
>> IOW. can other users be prevented to edit a file that is
>> opened with VX?
>
> Use a version control system like Subversion, where each developer can work
> freely on his local working copy of the project while the "current" version
> is in a file repository on a server.
>
> Please consider reading the first chapter of the online Subversion book,
> that shows the fundamental concepts:
>
> http://svnbook.red-bean.com/nightly/en/index.html
>
> (AFAIK) Unfortunately, so far the VX IDE does not have any options to
> integrate with any VCS system - but for Subversion, there are various
> graphical frontends available that makes managing the repository and
> working copies very easy. I'm working with TortoiseSVN, which integrates
> with Windows explorer very well.
>
> Thomas

Frans Vermeulen wrote:

> In my case, SVN is highly overkill.

No - depending on the required setup it is installed in 10 minutes to a few
hours.

I'm a single developer and still I'm using it, mostly to be able to roll
back to almost any point in my source history (I'm committing changes
almost daily to the repository) but also to be able to create new
development branches without blocking maintenance of currently running
projects.

> We work with 3 developers, and problems rarely occur,
> however, they should not occur at all !

With 3 developers, revision control is an absolute *must*... IMHO

> Old fashioned, maybe it is. But that's the way fi.
> multi-edit works, and I have to face that fact.

I'm working with Multiedit as well.

> And I am looking for a way with VX to coexist
> with other editors.

I never understood what VX can do what Multiedit can't.

regards
Thomas

Thomas,

>> In my case, SVN is highly overkill.
> 
> No - depending on the required setup it is installed in 10 minutes to a few
> hours.
> 
> I'm a single developer and still I'm using it, mostly to be able to roll
> back to almost any point in my source history (I'm committing changes
> almost daily to the repository) but also to be able to create new
> development branches without blocking maintenance of currently running
> projects.

Can you give a short description how your installation looks like e.g. 
-	all on one computer or server and workstation
-	do you make use of an apache server or do you use the proprietary server
etc.

Peter

SVN is it's own server. It installs like and set up is like an FTP server.

Jim

On 08/02/2010 03:58 PM, Peter Alderliesten wrote:
> Thomas,
> 
>>> In my case, SVN is highly overkill.
>>
>> No - depending on the required setup it is installed in 10 minutes to a few
>> hours.
>>
>> I'm a single developer and still I'm using it, mostly to be able to roll
>> back to almost any point in my source history (I'm committing changes
>> almost daily to the repository) but also to be able to create new
>> development branches without blocking maintenance of currently running
>> projects.
> 
> Can you give a short description how your installation looks like e.g. 
> -	all on one computer or server and workstation
> -	do you make use of an apache server or do you use the proprietary server
> etc.
> 
> Peter

Found this. You may want to host off site. This can give lots of
flexibility and also serves as off site backup.

http://www.svnhostingcomparison.com/

Jim

On 08/02/2010 10:27 PM, James Loughner wrote:
> SVN is it's own server. It installs like and set up is like an FTP server.
> 
> Jim
> 
> On 08/02/2010 03:58 PM, Peter Alderliesten wrote:
>> Thomas,
>>
>>>> In my case, SVN is highly overkill.
>>>
>>> No - depending on the required setup it is installed in 10 minutes to a few
>>> hours.
>>>
>>> I'm a single developer and still I'm using it, mostly to be able to roll
>>> back to almost any point in my source history (I'm committing changes
>>> almost daily to the repository) but also to be able to create new
>>> development branches without blocking maintenance of currently running
>>> projects.
>>
>> Can you give a short description how your installation looks like e.g. 
>> -	all on one computer or server and workstation
>> -	do you make use of an apache server or do you use the proprietary server
>> etc.
>>
>> Peter
>

Peter Alderliesten wrote:

> Can you give a short description how your installation looks like e.g. 
> -	all on one computer or server and workstation
> -	do you make use of an apache server or do you use the proprietary server

First I started with a local installation with the dedicated svn server -
just to be able to have a change history for myself as a single developer.

But then I had a fellow developer for some weeks who worked with me on the
same project, so I moved Subversion to a public, Apache-based server that
is owned by the company I'm working at.

Access rights are given on a per-project basis.

Since then I'm using the repository via HTTPS URLs - I also use this to
keep the source files on my workstation in the office and on my Laptop in
sync.

I'm also maintaining the website of the company, so all the changes to the
HTML files are submitted into the SVN repository as well.

best regards
Thomas

> > In my case, SVN is highly overkill.
> 
> No - depending on the required setup it is installed in 10 minutes to a few
> hours.

I will have a closer look at SVN.
For the moment I would be happy if VX could lock the file that's being edited.

> I never understood what VX can do what Multiedit can't.

What hammer would be preferred to hit a nail?
Depends on a lot of factors. If SVN is the right tool 
for a job, than SVN it is. I think all pro's and con's 
of VX have been discussed a long time ago, 
and I have little to add.

With best regards,
Frans Vermeulen