[Scummvm-devel] Evolution of Scummvm-tools

[Einar Johan Trøan Sømåen]

2016-01-05 10:40 GMT+01:00 Eugene Sandulenko <sev.mail at gmail.com>:
>
>
> Moreover, you cannot use our common/ code directly, as that one is tied to
> backends/, the thing scummvm-tools completely lacks.
>

As it stands now, yes, although stubbing out the stuff that isn't
neccessary isn't horribly hard,

I did a quick and dirty attempt at that a while ago (technically based of
ResidualVM, but the common/backend stuff is the same there,
apart from stuff I stripped out anyhow) at
https://github.com/somaen/osystemio

Such a fork is useful for putting together code that might eventually run
in an engine (and thus preferably should use Common::-stuff).

Now, that repository never got much farther (and mostly serves a a very
quick proof of concept, but I can see a pretty decent value in having
functions with at least the same interface as the most common
Common::-stuff available outside of the complete ScummVM-environment (even
if we don't add forbidden.h implicitly).

Come to think of it, it's even more useful when one can combine it with
something like STL (i.e. for refactoring complete game engines,
without having to break them early, so that you can get stuff like
file-loading converted prior to replacing the audio/video presentation
parts).

So, perhaps we shouldn't include tools in scummvm/scummvm, but I'd be much
in favour of having a suitably large (sub)set of
Common:: available in tools.

Regards

Einar Johan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scummvm.org/pipermail/scummvm-devel/attachments/20160105/6bcffea7/attachment.html>