On 4/14/06, Alan Horkan <horkana@...44...> wrote:
Yes, mostly expanded, as there was not a lot to change :) Anyway, this process should be user-driven. If after some of our changes, someone prefers old Inkscape bindings, he or she is welcome to submit
In practice a user would need to be very disgruntled to bother making that much effort, whereas it is relatively little effort to do it preventatively.
OK, when we do some really major changes such as F1 for Help, I'll make sure to make the old layout available as an alternative.
It would be ridiculous
hold off on the firey rhetoric please, implying my suggestions are ridiculous might be seen as hostile (I'm trying to get used to it but your word choice still seems harsh)
This was said not about your suggestions, but about some reductio-ad-absurdum scenario I described. Anyway, I'm ready to apologize for the word if it sounded harsh.
however having a keybinding for something like Preferences indicates a design problem as users shouldn't need to be changing preferences on a regular basis
Perfect example. Maybe over time we won't need preferences that often, and the key may be freed (though I doubt it). But now we DO need preferences pretty often, and I see no reason not to assign a key to them. By the way, both Xara and AI do have a key for preferences.
or take another example if inkscape had really good tools for batch exporting a keybinding might not seem necessary for export since the rest of process is streamlined.
I don't see the logic here. Even if we have batch export, this will not make regular export less necessary. Rather, we may need one more key for batch export too.
Initially I felt the same way since the Inkscape developers had a change first ask questions later policy I thought changing thing later would be possible. When I tried to make changes there was massive resistance and any change was tied in to several other changes making it very difficult to make any changes at all let alone.
As promised, now you have the easy way to try to disentangle this mess by editing your own copy of default.xml. Or, just try xara.xml :)
If working tech support has teaches you anything is that software churn and the required retraining is a huge pain in the ass. If and when things like keybindigns get changed you dont want to be changing them too often.
So far we haven't abused the possibility :)
We need to get this absolutely clear you want to have keybindings based on the "real everyday users of the program". You want to optimize for the fastest most efficient professional work possible of people using Inkscape everyday (some other similarly huge amount of time). You want a Vi/Emacs powerhouse of an application, which is fine. The risk here is of a users accidentally hitting and doing something not easily reversable or getting trapped in a mode of some kind.
We don't have any "modes" afaik except for tools, which have a clear visual indication.
You draw an interesting distinction between recommendations, and discussions.
Recommendations like HIG are written "in general". Discussions are live and focused. That's the main distinction.
I will be happy to see more people tweaking their shortcuts and submitting their profiles, and to consider incorporating their proposals into the default set.
Numero uno:
F1 for Help
Thanks in advance.
Yeah, I know :) OK, so now you have xara.xml which implements it. Try it for the next version at least. Why don't we return to this for 0.45 if there's interest.
Found it agian, searched for 'horkana illustrator' and turned up a post I made on the Koffice list. Anyway here is the Macromedia Fireworks MX keybindings lists: http://www.maths.tcd.ie/~horkana/shortcuts/keys.html
That's helpful, though it looks like it only lists menu commands and not e.g. tools.
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org