Some time back I filed a request that might have been written in some pretty
much unknown language since it was written from the point of view of a
plugin developer that knows the open api.
However I believe it has merit if you are unlucky enough to work with a
Version Control System that leaves file read-only by default (clearcase, cvs
edit mode, p4,...)
Right now every time we use a refactoring or an intention whose primary
target is read-only, we have to try the action twice before it can be done:
first to get to the point for the file to be made writable than the other to
really perform the action.
Scenario: intention to create a method in some other class
1) Alt-Enter navigate to target class and then triggers the read-only action
that the VCS should have implemented to make the file writable. The action
could reevaluate the writability of the file again and continue if the file
was writable. Unfortunately it doesn't do it automatically and you have to
start over again manually.
2) Go back to original file (the action aborted AFTER the navigation!), then
redo the action.
It is so unlike IDEA. It makes IDEA break the development flow which it
otherwise maintain so well (I strongly believe that its transparency is the
reason why it is so popular).
Please vote for it if you agree with me: