1,079
edits
Difference between revisions of "Modular Backends"
Jump to navigation
Jump to search
→Potential modules
| Line 37: | Line 37: | ||
* Graphics | * Graphics | ||
* Input (events) -> possibly have graphics, input & event code all in a single type of module, just like SDL does -- after all they are usually tightly tied together anyway. | * Input (events) -> possibly have graphics, input & event code all in a single type of module, just like SDL does -- after all they are usually tightly tied together anyway. | ||
* Sound (possibly allow for custom mixer implementations. Maybe even make it possible to use | * Sound (possibly allow for custom mixer implementations. Maybe even make it possible to use custom MP3 playback implementations and such things, for platforms that offere optimized implementations. Of course, this is tricky, and may not be possible at all) | ||
* Timers (the current code would be left as default implementation, but e.g. Morphos port could override it easily) | * Timers (the current code would be left as default implementation, but e.g. Morphos port could override it easily) | ||
* Mutexes (only used when timers & threads are involved, so could be part of that) | * Mutexes (only used when timers & threads are involved, so could be part of that) | ||
| Line 45: | Line 45: | ||
* Native MIDI drivers (already modular, backends/midi/) | * Native MIDI drivers (already modular, backends/midi/) | ||
* Scaler code (see common/scaler*) -> we already share some scaler code, but that could probably be done in a better way, and maybe some more generic scalers could be added (e.g. a good & fast downscaler). | * Scaler code (see common/scaler*) -> we already share some scaler code, but that could probably be done in a better way, and maybe some more generic scalers could be added (e.g. a good & fast downscaler). | ||
== Source layout == | == Source layout == | ||