[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] Feature request: prompt for lock on *opening* file with svn:needs-lock

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-03-14 14:18:10 CET

"Jon Skeet" <Jon.Skeet@clearswift.com> wrote on 03/14/2006 04:27:45 AM:

> We have some Word files under Subversion which we'd like people to lock
> before editing.
> We've applied the svn:needs-lock property.
> Unfortunately, Eclipse doesn't get told when a user tries to edit a Word
> file. (Interestingly, opening it within Eclipse "inline" it seems to
> make it writable immediately, which doesn't help - using "System editor"
> it launches Word separately and keeps it read-only.)
> So, the feature request is that *optionally*, when you even *open* a
> file with svn:needs-lock (but where the lock hasn't been acquired)
> Subclipse asks you whether or not to acquire the lock. I don't know
> whether it's feasible - I don't know whether Eclipse has a hook which
> lets you know when you open a file. If possible though, it would be nice
> :)
> (It's not an issue for files edited within Eclipse's own editors,
> because Subclipse prompts at the ideal time in that situation.)

Eclipse does not provide a way to be notified of this action. If this is
something you really wanted, you should open a Bug with the Eclipse Team
group to extend the Team API to extend the API to handle this situation.
Either they could add a new validateOpen() event, or perhaps if an
external editor is being used on a file they could call validateEdit()
before opening the editor. The latter seems reasonable.


Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Mar 14 14:20:18 2006

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.