[news.eclipse.tools] Re: Removing or disabling the Rename action

[deinsel@xxxxxxxxxx (Dave)]

Randy Hudson wrote:

Randy you make a good point.

> What if the user didn't create the file??

> The Platform seems to be designed to support a simple Java IDE.  Outside of
> Java editing, there are many instances where multiple files exist, but
> conceptually there is just one User-editable concept.  There seems to be no
> way to handle this scenario in Eclipse.  For example, an EJB deployment
> descriptor (one file), and a Tool's extensions to that file (a second file).
> In this case, the second file is linked to the first, and needs to be
> versioned, etc., but the user should not be able to rename the file, or
> perhaps the user shouldn't be able to read it at all.

> I think in Dave's case there is a Project type that requires a file to
> exist.  When you create the project, you get this file for free, and it is
> an invalid state for the file to be missing from the project.  Eclipse
> should give the Tools such power to protect the file in this case.  And
> stating that a user could always delete the file from the file system (some
> other post) only points out the vulnerability of a file-based IDE.

> Another reply to this thread wrote:
> "Even if you could disable the rename action, end users could just
> rename the file at the OS file-system level and do a "refresh from local"
> within Eclipse."

> "David Springgay" <david_springgay@xxxxxxx> wrote in message
> news:9lj3pf$8h7$1@xxxxxxxxxxxxxxxx
> > David,
> >
> > I don't quite get it.  Why do you want to disable rename?  If the user
> > creates a file they have the right to rename it.  You, as a plugin
> > developer, should listen for this rename through the general resource
> > listener mechanism available in core and adapt to the new name.
> >
> > The existing rename action is plugin independent.  We treat all file types
> > in the same generic way according to user preferences.  In your plugin you
> > think rename should be disabled for sql files.  In another plugin they may
> > think rename is acceptable for sql files.  We can't program the action
> > specically to suit your needs.  It may break another plugin, and it
> > violates the generality of the platform.
> >
> > So the question is, why do you want to disable the action?  Is there a
> > particular scenario which you feel is being handled incorrectly?  Tell us
> > what the problem is and perhaps we'll understand your solution or suggest
> > a more plugin independent way.
> >
> > Dave
> >
> >