5 Commits (dacb59f6b20d5775bc2e7bb725637a14d6718c80)

Author	SHA1	Message	Date
Hans-Werner Hilse	dacb59f6b2	move debug function handover, set viewport for Kobo Mini ... in order to have debugging facilities in framebuffer:init(), we hand over the debug function as soon as we can. Also, set a viewport for Kobo Mini. Hopefully, it fits most people - I can only test on my unit.	10 years ago
Hans-Werner Hilse	677871cbf7	allow emulator to specify a viewport ... This allows for Viewport debugging. It is configured via an environment variable, EMULATE_READER_VIEWPORT. It works with Lua table syntax, e.g.: EMULATE_READER_VIEWPORT="{x=10,w=550,y=5,h=790}"	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	3eae0cdcb7	Bugfixes: test leftovers, wrong paths	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