3 ms·

So many questions OP. I dove into the source and couldn't answer... 1. Does this use native rendering of the local OS? I.e. On Linux it uses GTK or QT? 2. Is

So many questions OP. I dove into the source and couldn't answer... 1. Does this use native rendering of the local OS? I.e. On Linux it uses GTK or QT? 2. Is this meant to be entirely OS Agnostic? Are you going to support Linux, Windows, Kitchen Sink, Etc? 3. Are you planning on seeing this through to the end and completing the library 100% or is this a proof on concept?

helge5 7y ago
In the current state it draws into a pixel buffer array which you can then display on for example an epaper display connected to a Raspi or other embedded device. 1. No. Neither. It does all the drawing on its own. Right now even fonts. 2. I think he would like to make it platform agnostic that way (i.e. provide reusable parts), but no, not right now. 3. His primary goal is/was driving UIs on embedded devices and AFAIK wants to complete it at least for this task. Disclaimer: In contact with @cosmo in some Slack, due to my SwiftWebUI project (which offloads a load of things to the browser, so his stuff is quite different / more complex in many ways).
- bobajeff 7y ago
  I will be watching this. We can always use more better tools for making GUI on embedded. Especially ones that do their own rendering. One of my plans is to play around with using and/or creating a custom flutter engine embedder like flutter-pi.
- digi59404 7y ago
  Interesting! I'm curious about this because I didn't see anything rendering to the pixel buffer array. Do you know where that code is? I tried looking for it.
artonge 7y ago
I think this is just an API that must be connected to a graphical backend for each platform. > The project's goal is to provide a platform-agnostic interface — without the generation of the graphical user interface. > The rendering of graphical user interfaces can be implemented in platform specific (Linux, Windows, Embedded, …) projects.

helge5 7y ago

In the current state it draws into a pixel buffer array which you can then display on for example an epaper display connected to a Raspi or other embedded device. 1. No. Neither. It does all the drawing on its own. Right now even fonts. 2. I think he would like to make it platform agnostic that way (i.e. provide reusable parts), but no, not right now. 3. His primary goal is/was driving UIs on embedded devices and AFAIK wants to complete it at least for this task. Disclaimer: In contact with @cosmo in some Slack, due to my SwiftWebUI project (which offloads a load of things to the browser, so his stuff is quite different / more complex in many ways).

bobajeff 7y ago
I will be watching this. We can always use more better tools for making GUI on embedded. Especially ones that do their own rendering. One of my plans is to play around with using and/or creating a custom flutter engine embedder like flutter-pi.
digi59404 7y ago
Interesting! I'm curious about this because I didn't see anything rendering to the pixel buffer array. Do you know where that code is? I tried looking for it.

artonge 7y ago

I think this is just an API that must be connected to a graphical backend for each platform. > The project's goal is to provide a platform-agnostic interface — without the generation of the graphical user interface. > The rendering of graphical user interfaces can be implemented in platform specific (Linux, Windows, Embedded, …) projects.