Open main menu

Difference between revisions of "Small Devices Backend"

added headings, fixed typo
(added Variable upscaler)
(added headings, fixed typo)
Line 1: Line 1:
A backend used for smaller devices with limited functionality. I.e. small screen, no keyboard, low memory, low processor etc.
A backend used for smaller devices with limited functionality. I.e. small screen, no keyboard, low memory, low processor etc.


Targets are:
=== Possible Targets ===


* WinCE -- small screen, no keyboard
* WinCE -- small screen, no keyboard
Line 11: Line 11:
* GP32 -- small screen, no keyboard, low resources, low memory
* GP32 -- small screen, no keyboard, low resources, low memory


=== Structure ===
All above devices will subclass this backend and possibliy override system-specific methods, i.e.:
All above devices will subclass this backend and possibliy override system-specific methods, i.e.:


Line 22: Line 23:
* It should add another level of abstraction and should let lowest level functions like input and screen blitting to be overriden. For example, PalmOS and GP32 backends do not use SDL. That shouldn't be really hard, as most functionality is in place and current SDL backend performs blitting only from 2 functions.
* It should add another level of abstraction and should let lowest level functions like input and screen blitting to be overriden. For example, PalmOS and GP32 backends do not use SDL. That shouldn't be really hard, as most functionality is in place and current SDL backend performs blitting only from 2 functions.


* It should be written with extensive use of #ifdefs, so if I, say, don't need a virtual keyboard or downscalers for paltform Foo, I don't bloat my code.
* It should be written with extensive use of #ifdefs, so if I, say, don't need a virtual keyboard or downscalers for platform Foo, I don't bloat my code.


List of common subsystems:
=== Common Subsystems ===


* Virtual keyboard
* Virtual keyboard
152

edits