104 Commits (d67d92bcab28c7f1ed0c07c2b2964db6ba6aa48c)

Author	SHA1	Message	Date
Hans-Werner Hilse	7da6dd28a5	handle Android app events in frontend/device code ... Events have been passed to the frontend/device (or /input) code before. Some of them have been handled in the FFI/input code, however. That seems to be highly critical with regard to timing, though, so we just let it enqueue the event for our code to process later. That way, a mutex that locks the input event queue can be freed faster.	10 years ago
Hans-Werner Hilse	2775ade5d6	fix device:init() bug on Android platform	10 years ago
Hans-Werner Hilse	63af71188a	refactor refresh ... Lots of the device-related distinction wandered into base/ffi/framebuffer_<driver>. This eases the refresh logic in UI manager, which basically only decides what kind of refresh to trigger. The device specific configuration in the framebuffer driver decides how to realize that whish. screen.lua is gone, in its place is now the framebuffer driver. The device abstraction decides what framebuffer driver to load.	10 years ago
Hans-Werner Hilse	3066c86e38	Refactoring hardware abstraction ... This is a major overhaul of the hardware abstraction layer. A few notes: General platform distinction happens in frontend/device.lua which will delegate everything else to frontend/device/<platform_name>/device.lua which should extend frontend/device/generic/device.lua Screen handling is implemented in frontend/device/screen.lua which includes the *functionality* to support device specifics. Actually setting up the device specific functionality, however, is done in the device specific setup code in the relevant device.lua file. The same goes for input handling.	10 years ago