-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Legacy: text-based interface #3
Comments
Started work in prettier_ui branch, moving UI element views into UI elements themselves. |
Work moved further, I split BaseListUIElement into logic and view objects and added a sample view for BaseListUIElement which has fonts and will likely get some more graphical elements. There now needs some kind of design decision - pick fonts, decide on what's going to be the default view and whether there'll be adjustability of menu views per each menu (and what level of adjustability there will be). Also, the "scrolling" part might need to be split into another View object, to act as a mixin of sorts. Not to mention that the scrolling won't work that well with non-monospaced fonts, and there's no automatic character size determination yet, so font sizes are hardcoded for now - not that good for adjustability. I'm thinking about "pre-define some character size/screen line count combos and maybe let the user pick a font". |
prettier_ui branch seems to be usable now, merged it into the master branch. |
#76 has brought us close to the goal, with BaseListUIElements (Menus, Checkboxes etc.) now sporting a new cursor, and DialogBox being more readable. Also, CharArrowKeysInput elements now have graphical rendering, too - it doesn't look any different from character-based rendering, but that's only until somebody figures out how to make it better. |
Now there's |
As pyLCI was character display-based, it mainly operated with text. Right now, ZeroPhone uses a display which actually allows setting individual pixels, and there's much more screen real estate - but this fork of pyLCI still uses text in UI elements, using the display_data function which is limited to text. The goal of this issue is teaching UI elements to work with PIL canvas (used by luma.oled) and making simple canvas-based screen output functions for currently available UI elements.
As a bonus, it would be nice to be able to use a fallback to text-based interface in most used and least ZeroPhone-specific UI elements, for backwards compatibility.
BaseListUIElement
-based elementsDialogBox
CharArrowKeyInput
NumpadCharInput
IntegerAdjustInput
BaseListUIElement
-based elementsDialogBox
CharArrowKeyInput
NumpadCharInput
IntegerAdjustInput
The text was updated successfully, but these errors were encountered: