From: Amaury Pouly <amaury.pouly_at_gmail.com>
Date: Mon, 2 Dec 2013 12:23:39 +0000

>
> 2) For plugins for which it is suitable, add a pluginlib fallback which
> can provide a minimal set of functionality
>
I thought it would be useful to provide a few examples:

Example 1: cube
The cube plugin currently has one more action than pluginlib provides. Thus
a trivial way to provide fallback is to just drop one action like "pause"
for example or to map "pause" to some repeated action like select repeat
and mapping select to "mode". That provides a reason fallback, maybe not
the most natural but it can be overridden for better experience.

Example 2: chessclock
The chessclock plugin may need more action than pluginlib provides but many
targets actually ran into this problem and already use the same button for
different action in different context (like select for ok in settings and
play/stop in main screen). It would be very easy to map this to
pluginliband provide reasonable user experience, while still allowing
a better
experience using a custom map on targets which have more keys.

This has the advantage of keeping the current keymaps which took a lot of
time to write while providing a decent default for new targets.
Received on 2013-12-02