Rockbox.org home
release
dev builds
extras
themes manual
wiki
device status forums
mailing lists
IRC bugs
patches
dev guide



Rockbox mail archive

Subject: Plugins and keymap

Plugins and keymap

From: Amaury Pouly <amaury.pouly_at_gmail.com>
Date: Mon, 2 Dec 2013 11:54:25 +0000

Hi All,
I'm sorry to brought up this painful topic once more, but I feel I need
some solution here and some feedback.
The issue is that at the moment I have ports in progress: Fuze+, ZEN, ZEN X-
Fi, ZEN Mozaic, ZEN X-Fi2, ZEN X-Fi3 and NWZ-E360/E370. If you do the math,
removing touchscreen targets and so on, that's at least 3 very different
keymaps (+variants). Doing the keymapping for Rockbox itself is already
quite a thing but doing it for the plugins is just a nightmare at the
moment, it takes a *huge* amount of time and one cannot enable the
pluginswithout fixing all of them, which is
unfortunate.
I see a few things to do at the moment, like conversion some old-time
resistant to pluginlib (yes battery_bench I'm pointing at you) but we all
know pluginlib just cannot be used for everything.

First off, if you have any magical solution, please tell me. Second, I
suggest we apply one or more of those suggestion:
1) Come up with a whitelist to disable some plugins, so that one can
compile only plugins which can be run/have a keymap
2) For plugins for which it is suitable, add a pluginlib fallback which can
provide a minimal set of functionality
3) At the opposite of 1), have not-yet-mapped plugins display a message on
launch saying that they have not been mapped yet and help is wanted
4) Augment the "plugins" setting configure to have three possible values:
"" meaning none, "yes" meaning all and "pla" to only compile the pluginsusing
pluginlib.

What do you think ?

Amaury Pouly
Received on 2013-12-02


Page was last modified "Jan 10 2012" The Rockbox Crew
aaa