[josm-dev] Shortcuts

2012-02-15 Thread Dirk Stöcker

Hello,

together with akks I developed an automatically generated shortcut 
overview at http://josm.openstreetmap.de/wiki/DevelopersGuide/ShortcutsList


Every yellow and red entry in this table should be fixed. The additional 
modifiers are deprecated. Instead proper groups (including ALT1 or ALT2) 
must be choosen. In these cases, where groups are hard to find I made 
groups DIRECT, DIRECT2 and DIRECT3 available, which allow to choose any 
shortcut. To use the proper keys main version for plugins must be 4928, 
as the codes for ALT1 and ALT2 changed and DIRECT2+3 are new.


Please help to fix these conflicts and deprecations. For conflicts, the 
core should remain and plugins be changed.


Keep in mind that e.g. MNEMONICS cannot be moved (they always have ALT 
key).


See also http://josm.openstreetmap.de/ticket/7226

Ciao
--
http://www.dstoecker.eu/ (PGP key available)


___
josm-dev mailing list
josm-dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/josm-dev


Re: [josm-dev] Shortcuts

2012-02-15 Thread Pieren
On Wed, Feb 15, 2012 at 9:24 AM, Dirk Stöcker
openstreet...@dstoecker.de wrote:

 Please help to fix these conflicts and deprecations. For conflicts, the core
 should remain and plugins be changed.

As a plugin maintainer, I would like to see from the JOSM core the
following points:
- reserve some shortcuts for plugins 'forever'. It is unfair to allow
plugins shortcuts and once users have their habits, force them to
change just because core is suddenly using it. Of course, it does not
solve conflicts between plugins but devs can manage that.
- allow the plugin to overwrite the core shortcut with a pop-up dialog
explaining the 'why' (and leaving the user to accept or refuse). This
is a way to keep long-term users with their habits and show to new
comers the shortcut issue e.g. with the documentation (after all, it
can be redefined manually later in the prefs).

Pieren

___
josm-dev mailing list
josm-dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/josm-dev


Re: [josm-dev] Shortcuts

2012-02-15 Thread Dirk Stöcker

On Wed, 15 Feb 2012, Pieren wrote:


As a plugin maintainer, I would like to see from the JOSM core the
following points:
- reserve some shortcuts for plugins 'forever'. It is unfair to allow
plugins shortcuts and once users have their habits, force them to
change just because core is suddenly using it. Of course, it does not
solve conflicts between plugins but devs can manage that.


No. We now have a shortcut list and we will try to prevent conflicts in 
the future by proper selecting new shortcuts, but when core needs a key, 
then plugins will be second in line and have to move.



- allow the plugin to overwrite the core shortcut with a pop-up dialog
explaining the 'why' (and leaving the user to accept or refuse). This
is a way to keep long-term users with their habits and show to new
comers the shortcut issue e.g. with the documentation (after all, it
can be redefined manually later in the prefs).


Also a no for me. If plugin shortcut needs to change the plugin can issue 
a warning, that from now on the shortcut is different and that users may 
change it back to their old behaviour themselves.


What you want is the reverse and this means keeping old behaviour for 
everybody instead of moving into the future. The documentation will always 
reflect the newest state, so software also should try to keep newest 
state.


You can call the shortcut preferences from such a dialog, so the user can 
directly access these prefs from the dialog.


Ciao
--
http://www.dstoecker.eu/ (PGP key available)


___
josm-dev mailing list
josm-dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/josm-dev


Re: [josm-dev] Shortcuts

2012-02-15 Thread Martin Koppenhoefer
2012/2/15 Dirk Stöcker openstreet...@dstoecker.de:
 What you want is the reverse and this means keeping old behaviour for
 everybody instead of moving into the future.


what is the benefit of moving into the future by changing shortcuts?
This is fighting against peoples habits and ergo also bad for
usability (of the experienced users, for new users this is not an
issue, I agree). Keeping old behaviour should be the standard for
interface issues, if there is not very good reason to do so. Sorry for
this rant, then from someone beeing not even a code contributor, but I
really suffered hard from the recent change of shortcut w (before
buildings plugin, I use this VERY often, now refine way, which I
never use).

Anyway, I am happy to read that there will be a list for shortcuts
now, so that developers can choose new shortcuts without accidentially
redefining existent ones.

cheers,
Martin

___
josm-dev mailing list
josm-dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/josm-dev


Re: [josm-dev] Shortcuts

2012-02-15 Thread Dirk Stöcker

On Wed, 15 Feb 2012, Martin Koppenhoefer wrote:


2012/2/15 Dirk Stöcker openstreet...@dstoecker.de:

What you want is the reverse and this means keeping old behaviour for
everybody instead of moving into the future.


what is the benefit of moving into the future by changing shortcuts?
This is fighting against peoples habits and ergo also bad for
usability (of the experienced users, for new users this is not an
issue, I agree). Keeping old behaviour should be the standard for
interface issues, if there is not very good reason to do so. Sorry for


When we change a shortcut, then there is a reason, e.g. a conflict. So 
some people need to change their behaviour, as keeping old style is out of 
question. So rather than get mixed setup depending on installation 
specific the default should be the one we document on the webpage.



this rant, then from someone beeing not even a code contributor, but I
really suffered hard from the recent change of shortcut w (before
buildings plugin, I use this VERY often, now refine way, which I
never use).


You can change that as you know.

We have too many shortcut conflicts and we need to unify this. And this 
means that some users need to accept changes. The other option would be to 
keep the chaos we currently have.


If the default would be to keep everything as is, we copy all these 
troubles a long time into the future. So we have one break now and later 
on wikis and forums on docs refer to one setup and not to a user specific 
setup.


Ciao
--
http://www.dstoecker.eu/ (PGP key available)___
josm-dev mailing list
josm-dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/josm-dev


Re: [josm-dev] Shortcuts

2012-02-15 Thread Pieren
On Wed, Feb 15, 2012 at 6:12 PM, Dirk Stöcker
openstreet...@dstoecker.de wrote:

 If the default would be to keep everything as is, we copy all these troubles
 a long time into the future. So we have one break now and later on wikis and
 forums on docs refer to one setup and not to a user specific setup.

Fixing current conflicts is one point.
Saying at any time in the future, the josm core can take over
existing plugins shortcuts because we find it so cute and plugins will
have to accept it (1) is another one. This is a kind of arrongance
and disrespect of JOSM plugins users and devs.

Pieren

(1) when core needs a key, then plugins will be second in line and
have to move.

___
josm-dev mailing list
josm-dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/josm-dev


Re: [josm-dev] Shortcuts

2012-02-15 Thread colliar
Am 15.02.2012 09:24, schrieb Dirk Stöcker:
 Hello,
 
 together with akks I developed an automatically generated shortcut
 overview at http://josm.openstreetmap.de/wiki/DevelopersGuide/ShortcutsList

Thanks for your work, you two.

Why do we have two shortcuts for draw action (A and N) ?

Cheers
Colliar



signature.asc
Description: OpenPGP digital signature
___
josm-dev mailing list
josm-dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/josm-dev