Rockbox mail archiveSubject: having pluginlib-action handling more/all plugin.
having pluginlib-action handling more/all plugin.
From: Jean-Louis Biasini <jlbiasini_at_gmail.com>
Date: Wed, 04 Jan 2012 17:05:20 +0100
1) what I do for now
I'm working on keymaps and manual for the new fuze+ port. I suppose that
you already know the kind of harrassing boring task this can be. If not
you may have a look to the kind of patch that one has to provide:
(both patch are incomplete I'm still missing keymaps for demo and app)
2) the problem
The problem is not only that it is extremly long and boring to do, but
that this way there is a high probability of error or wrongly set
keymaps. I don't think that a lot of us want to really take the time to
carefully think about the best way to control each plugin one by one
before setting the keymaps in the code for a new target, then DOING IT
ALLOVER AGAIN in manual. The likely consequence of that (as keymaps are
mandatory to have plugin compiling) can be poorly implemented keymaps in
plugin for new target. (making a lot of then unusable for example, this
is exactly what happened on Fuze+ case) Which means also that someone
has to go do the harrassing job ALLOVER AGAIN. A lot of time and energy
are wasted on uninterresting task
3) a possible solution?
I saw that some plugin are relying on pluginlib-action for their keymaps
which bring 2 major speed up: keymaps get set in a general way (only one
keymap for all) AND it is possible to write the manual in a way that
takes all keymaps for those plugin from one single file (keymap-xxx.tex).
4) question to all
Somehow a lot of plugin still not use the keymaps privided by
pluginlib-action for now. Is there any good reason for that?
5) Answer I already get:
- Sagarota told me this would be related to the fact some small old
device might not have enough key to be used through pluginlib-action.
-> this could be turned around with an alternative
pluginlib-action keymaps for those target
-> or we could even let the old method for those old target
and set pluginlib-action for bigger/new ones.
- I saw that some plungin need more keys that pluginlib-action can
provide in a general/clean way
-> for such plugin I would recommand have all possible
keymaps from pluginlib-action (i. e. direction key, exit, select)
6) what I would do if there are no opposition/problem
- Rewriting plugin (all or the more as possible) to have keymaps set for
all plugin pluginlib-action
- Rewriting manual plugin (all or the more as possible) to have keymaps
set for all plugin in keymaps-xxx.tex
this would be much more interresting usefull as to write keymaps/manual
for a single target (even if indeed this would take me much more time)
Thanks in advance for any comment and/or direction on this,
Happy new year
Received on 2012-01-04