A plead for classpath setup usability

Folks, I've been struggling with the following problem and wondered if it were possible to squeeze it into next EAP (should be trivial). We're setting up GWT's hosted mode, and one step requires GWT app sources to be added to the *classpath*. This enables GWT HostedMode to pick-up modifications to the UI on the fly and recompile. See http://www.mulesource.org/display/GALAXY/IDEA+Setup . The problem is the Classpath Configuration step. Adding a dir entry always appends it *to the end* of the dependencies list, but it has to be the first one. I see 2 ways to solve it:

  1. Whenever I'm adding anything to the classpath, *honor the current cursor position*. E.g. if I select the first dependency and add anything, it should be added right there where my current focus is, not to the end.
  2. Add Move to Top/Bottom button or action (less preferrable).


Let me know if it makes sense and is worth a JIRA.

Thanks,
Andrew

3 comments
Comment actions Permalink

For everyone to understand the scope of the problem - in order to move the dependency from the bottom to the top for a medium-sized project we're talking ~50 clicks on Move Up button. And no, holding down the shortcut doesn't help, the button just stays depressed with no multiple actions as one could expect.

0
Comment actions Permalink

Andrew Perepelytsya wrote:

Folks, I've been struggling with the following problem and wondered if it were possible to squeeze it into next EAP (should be trivial). We're setting up GWT's hosted mode, and one step requires GWT app sources to be added to the classpath. This enables GWT HostedMode to pick-up modifications to t
he UI on the fly and recompile. See http://www.mulesource.org/display/GALAXY/IDEA+Setup . The problem is the Classpath Configuration step. Adding a dir entry always appends it to the end of the dependencies list, but it has to be the first one. I see 2 ways to solve it:
1. Whenever I'm adding anything to the classpath, honor the current cursor position. E.g. if I select the first dependency and add anything, it should be added right there where my current focus is, not to the end.
2. Add Move to Top/Bottom button or action (less preferrable).

Let me know if it makes sense and is worth a JIRA.

Thanks,
Andrew

---
Original message URL: http://www.jetbrains.net/devnet/message/5242750#5242750

I'd imagine Drag/drop support would be the ideal 3rd option.
N.

0
Comment actions Permalink

I'd imagine Drag/drop support would be the ideal 3rd option.
N.

To some extent, but dragging 2 screens up is not fun in my books. Fine with 'local' reshuffle. On the same note, moving of multiple selected entries comes in handy quite often to me.

And having just said that I realized there's a bit perverted way to achieve what I want: add a dependency (ends up at the bottom), select all except this one, move down. Voila! The required dependency is on top! But boy, this is not the way to do it, it's turning things inside-out.

0

Please sign in to leave a comment.