Thanks to Mental's work, we now have shortcuts configurable by editing a simple XML file. I changed the format of that file, commented and categorized the shortcuts, and also listed there all Inkscape verbs that don't have shortcuts, so that it's easier for the user to bind them to keys. Also there's much work ahead to convert as much non-verb commands as possible to verbs, so that they can be configurable as well.
I also added an alternative keymap that emulates the keyboard of Xara X/Xara Xtreme/Xara LX. Since Inkscape has considerably more shortcuts than Xara, those keys that are not used by Xara retain their Inkscape bindings, thus making it easier for users to migrate from Inkscape to Xara or back. Of course, some of Xara's keys are not enabled because Inkscape does not yet have corresponding tools or commands.
The files in share/keys are:
inkscape.xml - Inkscape bindings
default.xml - initially this is a copy of inkscape.xml, but you can overwrite it with any other profile;
xara.xml - Xara bindings; to enable, copy it to default.xml; to disable, copy inkscape.xml to default.xml again.
Later, Inkscape installer and/or preferences dialog will need to be enabled to switch keymaps without the user having to copy files (coding help welcome, as always).
You can also customize some of your keybindings without overwriting the main default.xml. If your profile directory (~/.inkscape on Linux) contains a keys subdirectory with a default.xml file, the keybindings from that file will overlay (i.e. add to, and override in case of a conflict) the default bindings. This file may list just a few keybindings that you want to change; the format of your own default.xml is the same as that of the main default.xml.
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
On Thu, 13 Apr 2006, bulia byak wrote:
Date: Thu, 13 Apr 2006 11:13:10 -0400 From: bulia byak <buliabyak@...400...> To: Inkscape-Devel inkscape-devel@lists.sourceforge.net, Inkscape Users List inkscape-user@lists.sourceforge.net Subject: [Inkscape-devel] NEW: Xara keyboard shortcuts
Thanks to Mental's work, we now have shortcuts configurable by editing a simple XML file. I changed the format of that file, commented and categorized the shortcuts, and also listed there all Inkscape verbs that don't have shortcuts, so that it's easier for the user to bind them to keys. Also there's much work ahead to convert as much non-verb commands as possible to verbs, so that they can be configurable as well.
I also added an alternative keymap that emulates the keyboard of Xara X/Xara Xtreme/Xara LX. Since Inkscape has considerably more shortcuts than Xara, those keys that are not used by Xara retain their Inkscape bindings, thus making it easier for users to migrate from Inkscape to Xara or back. Of course, some of Xara's keys are not enabled because Inkscape does not yet have corresponding tools or commands.
The files in share/keys are:
inkscape.xml - Inkscape bindings
default.xml - initially this is a copy of inkscape.xml, but you can overwrite it with any other profile;
This is a slightly confusing naming scheme. I will try to explain, this default very quickly becomes different from the hardcoded default which developers have written in the code and what is really holds is the current user settings. Perhaps this could be adjusted, unless of course I'm needlessly overcomplicating and the situation is simpler than I think (and it probably is if I understand your later comment correctly).
Also I would like to humbly suggest a set like sodipodi.xml or classic.xml which would for future reference freeze the keybindings Inkscape has now and has long had and many users seem to be quite happy with.
That way future users can have the old the old keybinding they like from Sodipodi up until now and the developers can objectively decide what the best default keybindings should be without pissing off existing users already comfortable with the keybindings such as they are.
Later, Inkscape installer and/or preferences dialog will need to be enabled to switch keymaps without the user having to copy files (coding help welcome, as always).
(And maybe export them to some kind of readable text or html list format if some enterprising soul hasn't already hacked together scripts to do that)
You can also customize some of your keybindings without overwriting the main default.xml. If your profile directory (~/.inkscape on Linux) contains a keys subdirectory with a default.xml file, the keybindings from that file will overlay (i.e. add to, and override in case of a conflict) the default bindings. This file may list just a few keybindings that you want to change; the format of your own default.xml is the same as that of the main default.xml.
Oh, right I think is see now the system defaults and user defaults are seperated so my earlier comment is moot.
Thanks for all the work, now I'd better get started on a keyset in the style of Macromedia Freehand or Adobe Illustrator (I had a list lying around somewhere, the tricky part will be matching corresponding features).
Thanks agian.
Sincerely
Alan Horkan
Inkscape http://inkscape.org Abiword http://www.abisource.com Open Clip Art http://OpenClipArt.org
Alan's Diary http://advogato.org/person/AlanHorkan/
On 4/13/06, Alan Horkan <horkana@...44...> wrote:
Also I would like to humbly suggest a set like sodipodi.xml or classic.xml which would for future reference freeze the keybindings Inkscape has now and has long had and many users seem to be quite happy with.
What Inkscape has _now_ is very very far from Sodipodi :) And it's always being developed and expanded, changing with every version. Those who want keys corresponding to Inkscape 0.XX can just download that version of inkscape.xml from SVN or sourceforge archive.
Thanks for all the work, now I'd better get started on a keyset in the style of Macromedia Freehand or Adobe Illustrator (I had a list lying around somewhere, the tricky part will be matching corresponding features).
That would be much appreciated. I remembered about that list of yours but could not find it now. You can start the AI and/or FH profiles and do what you can do, then submit them so I and others will complete and polish them.
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
On Fri, 14 Apr 2006, bulia byak wrote:
Date: Fri, 14 Apr 2006 01:29:17 -0300 From: bulia byak <buliabyak@...400...> To: Alan Horkan <horkana@...44...> Cc: Inkscape-Devel inkscape-devel@lists.sourceforge.net Subject: Re: [Inkscape-devel] NEW: Xara keyboard shortcuts
On 4/13/06, Alan Horkan <horkana@...44...> wrote:
Also I would like to humbly suggest a set like sodipodi.xml or classic.xml which would for future reference freeze the keybindings Inkscape has now and has long had and many users seem to be quite happy with.
What Inkscape has _now_ is very very far from Sodipodi :) And it's always being developed and expanded, changing with every version.
I was assuming you mostly expanded rather than outright changed the keybindings but in case you did change things I suggested the alternative of a "classic" set of keybindings.
Those who want keys corresponding to Inkscape 0.XX can just download that version of inkscape.xml from SVN or sourceforge archive.
That isn't particularly convenient. Users will certainly balk at this prospect, even experienced users and complain loudly if their favourite keybindings are changed.
The Gnome HIG advises against trying to have keybindings for absolutely everything. I understand now why, because Inkscape has keybindings for just about everything it is very hard to add any new keybindings. On top of that the most appropriate keybinding for a task is often taken for something else and as we saw before attempts to change one keybinding quickly cascades into a massive task requiring many changes. (The desire to have keybindings for everything also means there will be a tendancy to want to use individual menu items for everything instead of consolidating things into dialogs and trying bigger ways to streamline the workflow, not that I have any great examples right now.)
By providing a snapshot of the keybindings as they are now it would reduce the massive pressure against changing any of the existing keybindings. It would give developers more leeway to choose the most appropriate keybindings without being totally constrained by what was used in the past.
I strongly believe the default keybindings should try to be easier for beginners to learn. Also there are many users who are familiar with Adobe and Macromedia products (between them they dominate most of the commercial market for Vector graphics drawing) and they share a subset of common keybindings. Trying to match those common keybindings (identify that list of shared keybindings will be a bit of hassle) but it would make Inkscape appeal to the widest possible audience.
This assumes Inkscape wants to atttract more users.
Thanks for all the work, now I'd better get started on a keyset in the style of Macromedia Freehand or Adobe Illustrator (I had a list lying around somewhere, the tricky part will be matching corresponding features).
I'll try and dig out those lists...
Anyone with a copy of Macromedia can easily export the list of keybindings as HTML or text if they look in the preferences dialog.
Jasc Web Draw keybindings http://www.maths.tcd.ie/~horkana/inkscape/WebDraw_Keyboard_Shortcuts.html
Macromedia Freehand keybindings http://www.maths.tcd.ie/~horkana/inkscape/freehand/FreeHandMX_keybindings.tx...
Adobe Illustrator Keybindings http://www.maths.tcd.ie/~horkana/inkscape/illustrator/Illustrator%20CS%20Def...
I had a side by side list for Adobe and Macromedia in nicely formatted HTML around somewhere, I'll see if I can dig it up later.
That would be much appreciated. I remembered about that list of yours but could not find it now. You can start the AI and/or FH profiles and do what you can do, then submit them so I and others will complete and polish them.
Could be a few days before I get stuck in and get started (and I'll try to hang around on IRC while I'm doing it). If anyone does start on either of those before then please mail the list, and create a report in the tracker to help avoid any duplication of effort.
Sincerely
Alan Horkan http://advogato.org/person/AlanHorkan/
On 4/14/06, Alan Horkan <horkana@...44...> wrote:
What Inkscape has _now_ is very very far from Sodipodi :) And it's always being developed and expanded, changing with every version.
I was assuming you mostly expanded rather than outright changed the keybindings but in case you did change things I suggested the alternative of a "classic" set of keybindings.
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 the corresponding profile file and we'll include it in the list of alternatives. I see no reason for us to do this preventively. Why do a snapshot of 0.44 and not e.g. 0.43 or 0.45?
The Gnome HIG advises against trying to have keybindings for absolutely everything. I understand now why, because Inkscape has keybindings for just about everything it is very hard to add any new keybindings.
It would be ridiculous not to have convenient shortcuts for something widely used _now_ in anticipation of some other feature that will arrive years later and will need the same keys.
I see no reason not to have, at all times, a set of shortcuts that best reflects the current functionality of the program. Moreover, I think the fact that we had such a set from the beginning was a very important factor in Inkscape success.
Can it happen that we'll want to switch some shortcuts to different actions in the default set? Yes, absolutely. I see no tragedy in that, provided this is driven by the real needs of the users and is given good discussion by real everyday users of the program.
Is it true that some of the shortcuts were assigned to little-used commands that could easily do without keyboard access? Probably. But again, the practice and discussion is the best way to find it out, not blindly following some recommendations.
In fact, the primary value of the customizable profiles is exactly in this - to facilitate experimentation and encourage discussion. 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.
Is it true that the current default set has few unused keys left? Not really. Both single-letter and F-keys spaces for switching tools have plenty of room still, so we can easily accommodate many new tools. And within each tool, many of the existing keys will have easy to guess meanings, same or similar to those in other tools. We also have quite some room to grow in terms of improving consistency and always doing what the user expects, which often means adding more functionality to the existing keys used in new contexts, without having to use any new keyboard combinations.
I strongly believe the default keybindings should try to be easier for beginners to learn.
Absolutely. But the way to achieve this is not artificial limiting of shortcuts. This is best achieved through _consistency_. We are doing pretty well in this - in most situations, most keys behave in predictable ways. Though of course there's room for improvement.
Jasc Web Draw keybindings http://www.maths.tcd.ie/~horkana/inkscape/WebDraw_Keyboard_Shortcuts.html
This one is really small. I don't know if it's worth making a profile from. All of the things that we share already have the same keys, and the rest does not apply to us.
Macromedia Freehand keybindings http://www.maths.tcd.ie/~horkana/inkscape/freehand/FreeHandMX_keybindings.tx...
That one is helpful, with good explanations. Quite ripe for making a profile out of.
Adobe Illustrator Keybindings http://www.maths.tcd.ie/~horkana/inkscape/illustrator/Illustrator%20CS%20Def...
This one is less helpful, perhaps only a real Illustrator user can make sense of these.
I had a side by side list for Adobe and Macromedia in nicely formatted HTML around somewhere, I'll see if I can dig it up later.
That will be very useful.
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
On Fri, 14 Apr 2006, bulia byak wrote:
On 4/14/06, Alan Horkan <horkana@...44...> wrote:
What Inkscape has _now_ is very very far from Sodipodi :) And it's always being developed and expanded, changing with every version.
I was assuming you mostly expanded rather than outright changed the keybindings but in case you did change things I suggested the alternative of a "classic" set of keybindings.
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.
the corresponding profile file and we'll include it in the list of alternatives. I see no reason for us to do this preventively. Why do a snapshot of 0.44 and not e.g. 0.43 or 0.45?
One would hope the Inkscape keybindings would not fluctuate so wildly as to need more than one "classic" profile.
The Gnome HIG advises against trying to have keybindings for absolutely everything. I understand now why, because Inkscape has keybindings for just about everything it is very hard to add any new keybindings.
(The HIG as usual has to be taken with grain of sceptical salt. It gives direction but very little idea of the intention, and enough room to move that you could convince yourself Inkscape doesn't have a lot of keybindings and follows the guidelines perfectly.)
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)
not to have convenient shortcuts for something widely used _now_ in
yes, if it is something widely used which requires fast frequent access
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 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.
as Inkscape evolves and workflow improves a few keybindings will be improved
anticipation of some other feature that will arrive years later and will need the same keys.
While I like to err on the side of having plenty of keybindigns I can see the downside of having keybindins for almost everything.
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.
Are keybindings choosen because they are the most appropriate or because they are the only ones available at the time? I doubt you were entirely happy with all your keybinding choices and even you will want to review them at some point.
I see no reason not to have,
You have never tried to get bulia byak to change his mind! :)
at all times, a set of shortcuts that best reflects the current functionality of the program. Moreover, I think the fact that we had such a set from the beginning was a very important factor in Inkscape success.
On balance it has been very good. However I want to chagne the keybindings so I can forsee that will be difficult if it happens. 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.
Can it happen that we'll want to switch some shortcuts to different actions in the default set? Yes, absolutely. I see no tragedy in that,
It is easy for developers to make the change but harder for users to adapt, but frequent and expert users like yourself are best able to adapt.
provided this is driven by the real needs of the users and is given good discussion by real everyday users of the program.
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. (It is amazing how often user get trapped in Overwrite mode. I got bitten repeatedly by Windows silently changing keyboard layout on me thanks to a "helpful" shortcut.)
I have seen users who essentially relearn everything from scratch each time the uses a computer, I will call "forever beginners". I'm like this when it comes to filling at paperwork at the Bank, others have a similar reaction to programming their video recorder.) This is part of the reason why I put so high a value on having a shallow learning curve and making it easier for users to transfer knowledge such as consistent keybindings across Gnome or as I mentioned before those keybindigs which both Macromedia and Adobe saw fit to use for the same tasks in their drawing apps.
Our two goals - two different user archetypes - do overlap mostly. however we are not deciding the keybindings in vacuum and any evaluation has to include what keybindings are known from other applications and from past versions of Inkscape and factor that in too.
Is it true that some of the shortcuts were assigned to little-used commands that could easily do without keyboard access? Probably. But again, the practice and discussion is the best way to find it out, not blindly following some recommendations.
Is it true that some of the shortcuts were assigned to little-used commands that could easily do without keyboard access? Yes. You draw an interesting distinction between recommendations, and discussions.
In fact, the primary value of the customizable profiles is exactly in this - to facilitate experimentation and encourage discussion.
How long do you give it before someone makes Inkshop* packages? :)
[* Gimpshop is a version of the GNU Image Manipulation program with Photoshop settings. I'm joking about Inkshop, I hope Inkscape will continue to be inclusive and things will turn out differently as is happening here.]
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.
We also have quite some room to grow in terms of improving consistency and always doing what the user expects, which often means adding more functionality to the existing keys used in new contexts, without having to use any new keyboard combinations.
That sounds risky, users might expect the wrong context but we'll burn that bridge when we come to it.
I strongly believe the default keybindings should try to be easier for beginners to learn.
Absolutely. But the way to achieve this is not artificial limiting of shortcuts. This is best achieved through _consistency_. We are doing pretty well in this - in most situations, most keys behave in predictable ways. Though of course there's room for improvement.
Jasc Web Draw keybindings http://www.maths.tcd.ie/~horkana/inkscape/WebDraw_Keyboard_Shortcuts.html
This one is really small.
I included it because I had it lying around and it was easiest to find, I might do it myself but as you say probably not worth bothering with. I have a soft spot for WebDraw even if it did cause me to obsessively edit the SVG markup directly it was a shame Corel abandoned it entirely after they purchased Jasc.
Macromedia Freehand keybindings http://www.maths.tcd.ie/~horkana/inkscape/freehand/FreeHandMX_keybindings.tx...
That one is helpful, with good explanations. Quite ripe for making a profile out of.
Adobe Illustrator Keybindings http://www.maths.tcd.ie/~horkana/inkscape/illustrator/Illustrator%20CS%20Def...
This one is less helpful, perhaps only a real Illustrator user can make sense of these.
I had a side by side list for Adobe and Macromedia in nicely formatted HTML around somewhere, I'll see if I can dig it up later.
That will be very useful.
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
N.B. Read the footnote: "This table was created by exporting the keybinding sets from Fireworks and then crudely fitting them all together in one table. This may be wildly inaccurate."
Sincerely
Alan Horkan
Inkscape http://inkscape.org Abiword http://www.abisource.com Open Clip Art http://OpenClipArt.org
Alan's Diary http://advogato.org/person/AlanHorkan/
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
On Sat, 15 Apr 2006, bulia byak wrote:
Date: Sat, 15 Apr 2006 14:36:59 -0400 From: bulia byak <buliabyak@...400...> To: Alan Horkan <horkana@...44...> Cc: Inkscape-Devel inkscape-devel@lists.sourceforge.net Subject: Re: [Inkscape-devel] NEW: Xara keyboard shortcuts
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
I agree the guidelines can be taken to absurd extremes and I always try very hard to figure out _why_ and take a best guess at the intent behind the guideline.
apologize for the word if it sounded harsh.
now worries.
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.
(I like having _Edit, Pr_efernces so that in effect you do have fast access using the keyboard combination Alt+E E.)
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 :)
I might try Xara but I prefer to have transferrable easily marketable skills and use Illustrator keybindings (I'd be working on it right now if I didn't have to rummage through SVN to get at the default.xml file).
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 :)
True. Much as I want to change the keybindings it is best to change a group of them rather than changing them incrementally over several releases.
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.
I'd like to have a short list of proposed changes to the defaults ofr 0.45 or more likely 0.46
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.
I didn't grab tools at the time and I have long since uninstalled the trial copy of Macromedia. If anyone else could post keybinding lists it would be helpful.
Thanks
On 4/15/06, Alan Horkan <horkana@...44...> wrote:
I might try Xara but I prefer to have transferrable easily marketable skills and use Illustrator keybindings (I'd be working on it right now if I didn't have to rummage through SVN to get at the default.xml file).
Here's the direct download link:
http://svn.sourceforge.net/viewcvs.cgi/*checkout*/inkscape/inkscape/trunk/sh...
And for Xara keys:
http://svn.sourceforge.net/viewcvs.cgi/*checkout*/inkscape/inkscape/trunk/sh...
When making an AI profile, please leave in comments a list of all AI keys that you could not assign to anything - we may be able to assign them later.
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
So cool, I just wrote to the developer who submitted a patch for adobe illustrator keyboard shortcuts so long ago about the configs and making an illustrator config file. Anyhow, he is the new Creative Commons graphic designer (and also the original developer/founder) of gedit.
Cool! Mental you rule with your bad self.
Jon
On Thu, 2006-04-13 at 11:13 -0400, bulia byak wrote:
Thanks to Mental's work, we now have shortcuts configurable by editing a simple XML file. I changed the format of that file, commented and categorized the shortcuts, and also listed there all Inkscape verbs that don't have shortcuts, so that it's easier for the user to bind them to keys. Also there's much work ahead to convert as much non-verb commands as possible to verbs, so that they can be configurable as well.
I also added an alternative keymap that emulates the keyboard of Xara X/Xara Xtreme/Xara LX. Since Inkscape has considerably more shortcuts than Xara, those keys that are not used by Xara retain their Inkscape bindings, thus making it easier for users to migrate from Inkscape to Xara or back. Of course, some of Xara's keys are not enabled because Inkscape does not yet have corresponding tools or commands.
The files in share/keys are:
inkscape.xml - Inkscape bindings
default.xml - initially this is a copy of inkscape.xml, but you can overwrite it with any other profile;
xara.xml - Xara bindings; to enable, copy it to default.xml; to disable, copy inkscape.xml to default.xml again.
Later, Inkscape installer and/or preferences dialog will need to be enabled to switch keymaps without the user having to copy files (coding help welcome, as always).
You can also customize some of your keybindings without overwriting the main default.xml. If your profile directory (~/.inkscape on Linux) contains a keys subdirectory with a default.xml file, the keybindings from that file will overlay (i.e. add to, and override in case of a conflict) the default bindings. This file may list just a few keybindings that you want to change; the format of your own default.xml is the same as that of the main default.xml.
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid%110944&bid$1720&dat%... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
participants (3)
-
Alan Horkan -
bulia byak -
Jon Phillips