View Single Post
Old 08-29-2019, 02:20 PM   #55
Mavireck
Connoisseur
Mavireck might easily be mistaken for a TexanMavireck might easily be mistaken for a TexanMavireck might easily be mistaken for a TexanMavireck might easily be mistaken for a TexanMavireck might easily be mistaken for a TexanMavireck might easily be mistaken for a TexanMavireck might easily be mistaken for a TexanMavireck might easily be mistaken for a TexanMavireck might easily be mistaken for a TexanMavireck might easily be mistaken for a TexanMavireck might easily be mistaken for a Texan
 
Posts: 63
Karma: 18290
Join Date: Jul 2016
Location: France
Device: Kobo H2O (broken), Kobo H2O Edition 2 v1 (stolen), Kobo Clara 2E
Quote:
Originally Posted by sherman View Post
What a fascinating series of posts. I've been thinking about GUI toolkits on Kobo's for a while now, investigating different strategies.

Ideally, something like littlevgl, Dear Imgui, or nuklear could be quite nice to use, although they all have their pros and cons.

Littlevgl looks easily portable to different devices, but its event handling seems to be tied to a refresh rate/polling mechanism.

Dear Imgui looks nice, but it's C++ and designed for OpenGL, although there is a software rasterizer that has been developed for it.

Nuklear also looks quite nice. It too is OpenGL, with a software rasterizer that has been written. It's a single header library, which makes for easy deployment. Main issue is the font handling seems very convoluted to get started with.

Another thing I've been mulling is the idea of making my own toolkit, very much like KSSM here (although probably in Go).
These are some interesting links.
To be honest, I have no idea how to deal to make them work together with FBInk... That is way beyond my skills 😉
What stopped you from making your own toolkit? If you had already thought about it, what major changes would you do?
Mavireck is offline   Reply With Quote