#7297 closed feature request (invalid)
Modularization
| Reported by: | SF/starfyre | Owned by: | fingolfin |
|---|---|---|---|
| Priority: | normal | Component: | --Other-- |
| Version: | Keywords: | ||
| Cc: | Game: |
Description
I submit that it would be less confusing to users if you split up the executable and just had it as an interface, with various modules for Scumm v.X games and another for the Simon games, another for BASS etc. This would also allow more people to contribute different engines, similar to how people are now contributing protocols to another of my favourite Sourceforge projects, Miranda IM, since it broke down the exe and modularized protocol handling.
I'm attempting to make contact with developers of the Kyrandia series so as to check their willingness to help preserve their masterpieces by developing a portable Kyrandia engine, standalone or as a module for ScummVM.
Ticket imported from: #773517. Ticket imported from: feature-requests/113.
Change History (5)
comment:1 by , 21 years ago
| Owner: | set to |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
comment:2 by , 21 years ago
comment:3 by , 21 years ago
I believe the intent is dynamic modules that can be loaded at run-time, rather than compile-time; something like a plugin interface.
comment:4 by , 21 years ago
Maybe we do that one day, as an optional thing. Not all our target systems support such a thing. And for development purposes, this has little to no impact anyway. We are not going to open ScummVM up for 3rd party modules at this point anyway. There would be nothing to be gained in this for us <shrug>.
comment:5 by , 6 years ago
| Component: | → --Other-- |
|---|
ScummVM *is* already modular.