1,079
edits
Difference between revisions of "Modular Backends"
→Potential modules
| Line 39: | Line 39: | ||
* 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 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) | * 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) | ||
* Audio CD (could be mixed with Audio/Sound, but then again the code overlap is probably non-existent, at least in the current backends) | |||
* 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) | ||