Difference between revisions of "Small Devices Backend"
(Add another common item) |
(Mention screen blit) |
||
Line 19: | Line 19: | ||
Small Devices backend should be based on SDL backend, but should have most functions as virtual, so functionality could be overriden. An example is PSP which has hardware scalers, and PS2 where Lavos wants to implement 3D virtual keyboard. | Small Devices backend should be based on SDL backend, but should have most functions as virtual, so functionality could be overriden. An example is PSP which has hardware scalers, and PS2 where Lavos wants to implement 3D virtual keyboard. | ||
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. | |||
List of common subsystems: | List of common subsystems: |
Revision as of 22:13, 10 December 2005
A backend used for smaller devices with limited functionality. I.e. small screen, no keyboard, low memory, low processor etc.
Targets are:
- WinCE -- small screen, no keyboard
- PalmOS -- small screen, no keyboard, low resources, low memory
- SymbianOS -- small screen, no keyboard, low resources, low memory
- PSP -- no keyboard
- PS2 -- no keyboard
- DC (?)
- GP32 -- small screen, no keyboard, low resources, low memory
All above devices will subclass this backend and possibliy override system-specific methods, i.e.:
SDL --> SmallDevices --> WinCE --> PalmOS --> PSP --> SymbianOS
Small Devices backend should be based on SDL backend, but should have most functions as virtual, so functionality could be overriden. An example is PSP which has hardware scalers, and PS2 where Lavos wants to implement 3D virtual keyboard.
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.
List of common subsystems:
- Virtual keyboard
- Splash screen (most of ports have it, so it could be unified)
- Downscalers, used for <320x200 screens
- No scalers, but that should be under #ifdef as PSP and PS2 have enough power
- Low-res sound
- Zoning, like used in WinCE and SymbianOS
- It should hide unneeded options from GUI like MT-32, MIDI device, i.e. those which either don't make sense or too fat for small devices