settings plugin/class

[reven]

yeah i was thinking if this was left up to a seperate plugin, and if it was possible it would be easier for you.

i would prefer if you (sub) would just use the screenImageBounds thingy to reposition the image to cope with overscan, since you would only have to put that line of code in one place (and then it would work with every plugin).
we would just need a method like pluginHelper.setScreenImageBounds(rectangle). since when the user wants to adjust the screenImageBounds we would have to set it first to the full image (most likely 0,0,720,480) and then once then figured out the best image size, then call that method again.

so is my logic sound with the plugin crap? does every one think it would work?

[reven]

ive been thinking some more about this, and i think it would probably be even easier if each plugin that implement the interface just provided an array of "control" or "widget" (or some other similar type name) to the settings plugin. the settings plugin would handle the drawing and key pushes etc of these controls, eg a plugin could provide these controls as a list
numberUpDownBox for SlideShowInterval,
checkbox for ShowTransistions,
numberUpDownBox for ZoomingSize
checkbox for AutoPlayMusic

etc, that way it would be extremely easy for a plugin to implement this interface, since every thing would be handled by the plugin and the plugin just has to handle the controls. so at first the settings plugin would need to make the controls: checkbox, up down box (strings would work best come to think it,or just objects with a tostring method overriden), textbox (just for displaying things like help etc), label (simple version of textbox?).

it might be better to split these control up into "Pages" which would be like tabs, each with a name and list of controls, that way the pages names would be listed as menu buttons (back will always be added to the menu to reselect the settings you want).

im not sure about the rest of the developers but im really keen on setting something up, but it needs to be agreed upon by every developer, of course this plugin would have to be open source