Could you all trascribe any and all ideas onto this wiki page:
http://inkscape.org/cgi-bin/wiki.pl?ScribusInteroperability
That way everyone can review and adapt parts of the ideas prior to and during our upcoming 2nd meeting.
Jon
On Sat, 2004-09-04 at 09:04, bulia byak wrote:
the Esc key is easier to hit than any of the Function keys because it is on the top right and isolated, making it relatively easy to hit without looking.
Exactly. And by this measure PgUp/PgDn are easy to reach because they're at the edge of a group of keys and therefore easy to find without looking. And this is also why e.g. function keys are broken into groups, so that each one is either at the edge or close to it.
key. And most importantly they're VERY intuitive for the meaning of Raise/Lower/etc - their labels are obvious synonyms of the
But they are EVEN MORE intuitive for scrolling the Page Up and Page Down.
Sure, but what it we don't need to move by pages, not having any pages in the first place? We have a very isotropic canvas where x/y directions are on the same terms, so the arrow keys with various modifiers are the best for moving the canvas itself or objects on the canvas.
Note that I don't propose that Scribus uses plain PgUp/PgDn for z-order, but with some modifiers. Maybe we can then adopt the same modifiers for these keys too.
this is what Xara uses, and I _STILL_ have to spend a fraction of a second thinking before I press them when in Xara, even though I've been using Xara for many years. Very unintuitive.
I think it is a matter of opinion what is best, I think it is unfair to presume that what you prefer is the most obvious or intuitive particularly when you yourself know that your bias is towards keybindings used by Xara.
Sure, but note that in this case, I'm arguing AGAINST Xara-like bindings :)
And already taken in Inkscape, btw.
The keybindings in Inkscape can still be changed, it is not like there has been a version 1.0 release with any implied promise of stability and maintainance.
No doubt. If you or anyone else proposes a well-thought-out keybindings change (which includes exactly what changes to what, taking into account the entire current keymap) I'll be happy to discuss.
Inkscape particularly made me understand why trying to have keybindings for everything can be a problem, once a keybinding is set users are reluctant to change to a better one because they are already used to it.
Yeah, but rest assured that I will have guts to change it despite user screams - provided you convince me that it's really a change to a BETTER one :)
This is particularly horrendous, definately goes against the Gnome Guidelines and probably goes against the KDE style guide as most applications use F1 for help.
It's logical and very convenient.
Logic all depends on your starting point. Again you are being very subjective, convenient is debatable.
Of course. I'd like to hear from anyone who uses Inkscape heavily and finds F1 for selector inconvenient.
It is certainly consistant to use Function keys for all the tools,
Yes, that's the logic I was referring to. It's the first and most often used tool, and F1 is the first and easiest to reach function key. So they're a natural match.
things like work within the Gnome Human Interface Guidelines. People using Inkscape very heavily will get used to keybindings but consistant guidelines across the whole desktop works well because means less specific keybindings users have to learn and less confusion when they switch from application.
Yes, that's why we're talking about Scribus/Inkscape unification! :)
To put it in perspecitive dont you just hate it when command line applications dont follow the style used by GNU applications for command line arguements.
Sometimes there may be good reasons to provide alternative syntax.
The tutorials are the closest Inkscape has to help files for now so it is only a minor point, but it will become a glaring inconsistancy if Inkscape is going to try to follow the Gnome Guidelines.
F1 for help is good for new users, but they will only need to use it a few times at first. Besides it's unlikely that F1 failure to call Help will really stumble them, since there's a Help menu. On the other hand, F1 as Selector brings lasting benefits for power users :)
This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel