1,510
edits
Difference between revisions of "Small Devices Backend"
Small Devices Backend (view source)
Revision as of 22:15, 10 December 2005
, 22:15, 10 December 2005no edit summary
(Mention screen blit) |
|||
| Line 20: | Line 20: | ||
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. | * 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. | |||
List of common subsystems: | List of common subsystems: | ||