7 Commits (ce624be8b83e880b1a81106a143e1440eeda4aab)

Author	SHA1	Message	Date
poire-z	f05e62c1fb	TextWidget: small refactoring, better handle max_width (#5503) ... Lots of code was doing some renderText calls to get the size of some text string, and truncate it to some width if needed, with or without an added ellipsis, before instantiating a TextWidget with that tweaked text string. This PR fixes/adds some properties and methods to TextWidget so all that can be done by it. It makes the calling code simpler, as they don't need to use RenderText directly. (Additionally, when we go at using Harfbuzz for text rendering, we'll just have to update or replace textwidget.lua without the need to update any higher level code.) Also: - RenderText: removed the space added by truncateTextByWidth after the ellipsis, as it doesn't feel needed, and break right alignment of the ellipsis with other texts. - KeyValuePage: fix some subtle size and alignment issues. - NumberPickerWidget: fix font size (provided font size was not used)	5 years ago
NiLuJe	b72a2000b1	A few minor fixes after #4847 (#4850) ... * Add a toggle to disable the C blitter in the Dev menu (depends on https://github.com/koreader/koreader-base/pull/882) (never shown if the JIT is disabled, grayed out if the C blitter is not installed) * Fix a few sizeUtf8Text call sites that were doing a nil check in order to account for the new return type. * Tweak statusbar handling to avoid spurious sizeUtf8Text warnings when it's hidden, and unify its behavior between being hidden via toggle, and hidden on book open (at least when all-at-once is not enabled). * c.f., https://github.com/koreader/koreader-base/pull/882 (Android, PB, RGB32 & Legacy Kindle regression fixes).	5 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
Hans-Werner Hilse	7b1777e095	adapt widgets and text rendering to new font rendering ... no background for text rendering anymore	10 years ago
chrox	92219a1f1e	cleanup: expand tab to 4 spaces	10 years ago
chrox	24ed02bbee	add bold property for text rendering	10 years ago
HW	ef111b99c6	Refactored to use strictly locals	11 years ago