At 15:12 -0700 2006/05/31, Oleg Kobchenko wrote:
--- Joey K Tuttle <[EMAIL PROTECTED]> wrote:
only Mac application (that I use) which uses <cntrl> at
all for these things. The command (Apple/Splat) key is
used instead of control. Modifiers for 3+key chords use
This is addressed in the keyboard mapper in Java
action code that instead of Ctrl uses a cross-platform
modifier. Same for menu.
int ACCL = Toolkit.getDefaultToolkit().getMenuShortcutKeyMask();
menu.add(new AbstractAction("Reset") {
public void actionPerformed(ActionEvent e) {
...
}
}).setAccelerator(KeyStroke.getKeyStroke(KeyEvent.VK_R, ACCL));
Thanks for the pointer, I'll dig into that a bit.
Not all combinations should be cross-platform --
only system-wide like Copy, Paste, New, Open, etc.
Ctrl+W should stay Ctrl+W, because Command-W is
close window, which would be good to wire somehow too,
as an equivalent of Alt-F4.
I agree, and adding fuel to the fire, Alt-F4 is ignored on
the Mac (along with whatever other favored Windows Fkeys do
I suspect).
> Even pasting one line, I have to make sure not to bring
the EOL with it, or I have to copy it down to execute it.
This is common to any environment. In shell terminal
you end up with unintended execution.
Oleg, I make a point of selecting an "unterminated" line if
I don't intend to execute the copied text -- but generally
I find it very convenient to copy it with the EOL (or multiple
lines) and have all of them executed.
What I was complaining about above was the opposite - when I
"unintentionally" (or intentionally, thinking of my usual habits)
include a copied EOL in an IDE paste - the line is stuffed into
the session and then, after copying it down, I have two copies
of it in my work area - ugly.
> As I write this, I tried an experiment. I tried to copy
some examples from an email authored by Roger. Because of
This could be done with a new action: Menu-Run-Clipboard (Display)
with a key like Ctrl/Cmd+Shift+V.
Or it could work like a shell terminal with only the down-side
of "unintended execution" in those cases where an EOL was
unintentionally included.
Alternatively, you open a new script window paste there
and execute line-by-line or the whole window.
Yes, I agree that is a sensible way to work within the IDE as
is - but I think there are then implications about stacks and
line recalls etc. All of these things are why I quite agree when:
At 18:57 -0400 2006/05/31, Brian Schott wrote:
The Mac IDE editor uses control instead of command
for all of cut/copy/paste and is very annoying in this way.
Command+O for open and script file would be nice instead of
control+O as would command+N instead of control+N for a new
ijs window. Also the Home and End keys are ignored. Also
there is no syntax coloring available. Also there is no
close window key which should be command+W. Less of a
problem is the lack of command+P for print.
I gather that all IDE's require shift+arrow for
moving between lines, but that is awkward, too.
And I use vi mostly because I get little extra from
J's IDE.
Plus, it would be nice to have use of right click and so on.
I realize this means more work on varients of the IDE (and the
consequent introduction of bugs, increased maintenance problems
etc.) -- the reason I usually just shrug and avoid using IDE
except for the cases where what I'm doing requires it.
- joey
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
