At this point in my project GUIX seems to do a lot of things I don't need, like handle input focus. I mainly need a way to draw screens and animate transitions (all simple swipes, between items and/or screens). Putting text and images on a screen (especially in monochrome) is, after all, not a big deal.
GUIX puts the focus on static screen design by virtue of having a graphical layout tool, so maybe it is simply the wrong model for my app. Nevertheless, is it possible to use GUIX as a (simple) drawing interface to the screen and not worry about input and focus? When I need input I could overlay an input box for editing, correct?
In other words, I'd like to have functions that do the drawing, realtime, instead of screens designed upfront. Dirty detection is not needed. Something that more resembles an immediate mode GUI, for those that are familiar with the term.
In this mode, using GUIX would still allow me to take advantage of for example clipping and perhaps functions to determine when to break a line to the next.
What in GUIX would argue against this approach? This is a rather important decision, maybe someone has experience to share doing things this way!
In summary:
- can I use plain GUIX functions to update the screen the way I'd like?
- in doing so, can I still overlay an input box and defer drawing and input handling to GUIX?
- is there anything in GUIX that argues against using it this way?
- should I perhaps throw out GUIX and its learning curve, and use something like the 2-file uGui (https://github.com/achimdoebler/UGUI)??