[Scummvm-devel] Backend-specific options and when the common launcher isn't the best fit

[Michael Nicholls]

On 26 October 2010 13:58, Angus Lees <alees at google.com> wrote:
> ScummVM folks: what is the right way to add backend-specific options?
> I'm led to believe that some of the ports #ifdef in their own options
> in the common gui dialogs but I haven't looked at the details - is
> that the best/only way?

Thanks Gus, that is what I was trying to ask, but you have worded it a lot
better.

> I dream of being able to replace the launcher with some normal Android
> code that used native Android widgets (so they are actually capable of
> being clicked on with a fat finger on a small screen, skipping
> desktop-centric idioms like double-clicking and tabs, and options I
> know don't exist on Android like midi hardware).
> If I was to toss the launcher and just call into MetaEngine, etc
> directly would that upset lots of people?  I can see that might cause
> a support burden for the rest of ScummVM so I understand if it isn't
> something you'd want to see in the main ScummVM tree.

Relating to both points, I was wondering if it is permissible to put some of
the right click/touchscreen suggestions into the code and then use the native
android menu to bring up a preference pane to allow the different suggestions
to be toggled. This would purely be a developer/debug menu to allow the
testing of things until a clear idea of what is needed is established,
at which point
proper integration can be added.
That way people could hook there code in and get it committed so that other
devs can try things out.

Ultimately I think a native Android launcher would be great, but I can also see
how it might be difficult to integrate and maintain.

Cheers,
Mike