Talk:Modular Backends

From ScummVM :: Wiki
Revision as of 07:07, 6 May 2006 by Ender (talk | contribs) (and equally unhelpful comment)
Jump to navigation Jump to search
  • Another candidate for modularization would be the DYNAMIC_MODULES. Right now the dynamic loading is handled by base/plugins.cpp, with #ifdefs galore.
Fully agreed, Marcus. I am not yet 100% how that would look, but it's indeed a natural candidate. Another one probably is the config file save/load code... considering that on some targets (like DC, I believe), you can't just save a file like that... :-) Fingolfin 23:31, 2 May 2006 (UTC)
  • It's outside my own personal sphere of interest - it won't make much, if any, difference to the game engines themselves, right? - but it seems like a sensible idea. And if it eventually makes it easier to put a new backend together, so much the better!
  • I like the idea, particularly for the ease of reusing components for the Small Devices Backend. The only question is the balance between 'file bloat' and sensible organisation. As far as my comments on this, I suggest combining the Audio/Sound directories into one AV directory under backends. Eg, backends/av/sdl (/audio.cpp | video.cpp), /x11/video.cpp, /oss/audio.cpp). Going by purpose, '/backends/saves' could be moved to /backends/fs/saves in this nested hierarchy. I don't really think too many extra subdirectories under /backends/ will be needed if the files are linked by the platform build system, since the purpose of the modularised files should be clear. Ender 07:07, 6 May 2006 (UTC)