Thomas Martitz wrote:
I'm just playing around with the idea. I call it out-sourcing.
I think having the settings as plugin would be very beneficial regarding
the bin size. I also think that there is no real point having the
settings in the core (correct me if there's a good reason).
Note: With settings I purely mean the settings menu which can be
accessed by the main menu and other screens.
I think it should be feasible and it seems like a logical step to me.
Although it's just an idea, I didn't think too much about cons, I'm sure
there cons which I didn't think of yet.
As a non-developer who reads the dev list to learn about Rockbox (and
who aspires to contribute to Rockbox--cash now, code later) I think that
while there are real problems with the idea, thinking about it for the
long term has some merit.
I see possibly two sets of settings: 1) things that are endemic to the
player (player-specific), and 2) things that are Rockbox-specific.
Perhaps the player-specific code could be made a plugin-like module that
differs for each model, and the Rockbox-oriented code should remain as
it is.
Just a blue-sky suggestion. Grains of salt required.
Mark Allums
