[Scummvm-devel] PORTERS: New OSystem API for loading/storing default config file

[Max Horn]

Am Mi, 30.07.2008, 19:14, schrieb Oystein Eftevaag:
> I definately agree with this approach.
>
> The iPhone port is one of the #ifdef culprits (calling into the backend
> to return a path), something like this would be much nicer.

Aye.

>
> One (more or less) related suggestion though, for future consideration:
> What about support for multiple config files? Mainly for providing the
> possibility for additional config files containing individual game
> targets (to be installed by packages of the various free games we
> support). It would introduce a bit more complexity with regards to
> saving the config again later, but should be manageable.
>
> I'm sure this has been discussed already and I've missed it, just
> thought I'd throw it out there while the topic was up :)

Sure. And it hasn't been discussed here, though I did think about it, and
my view is this:

There is one and only one "default" config file, which can be in "special"
port specific locations (including being of a different kind that
"regular" data files). So that's why we need a special API for it.

All other config files will either be user specific custom files (and then
it'll be a regular file), or config files shipped with special game packs
(as in your example), and then again it'll be a (possibly read-only)
regular file.

But maybe I am too short sighted here. Maybe there are ports out there
which need to be able to write to multiple config files which are not
"normal" files (in the sense that they could be accessed via class File).
Right now I am not aware of that and my imagination is too limited to see
why it would be useful, but that's precisely why I posted this email: So
that all porters get a chance to speak up. *They* should know, after all
:-).

Cheers,
Max