well here is the brief concept:

it is a markup language for APP (NOT WEB) GUI’s, for Linux

but:

1: it does not have to depend on a single GUI Toolkit (GTK Or QT)

2: it depends on external Programs called “Translators” which translate the Markup language calls and whatever onto something your GUI Toolkit understands

3: it does not manage any form of functionality whatsoever, you have to depend on a another language to do that

what it aims to do:

sometimes a GTK app on a QT Desktop Environment

just does not match the theme

which that idea aims to solve

how would you fix it

  • balsoft@lemmy.ml
    link
    fedilink
    arrow-up
    2
    ·
    1 day ago

    Wayland just gives you a buffer to write to, it doesn’t give you drawing primitives in the way XCB does. It’s kinda the point, and makes implementing display servers/compositors a lot simpler and easier, and most apps will be using some kind of non-XCB toolkit anyways.

    So if you’re making an app you do kinda need a toolkit, but it can be a very simple and lightweight one.

    • TootSweet@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 day ago

      most apps will be using some kind of non-XCB toolkit anyways.

      Not my favorites. I’m mostly thinking of the Suckless sort of tools. dmenu, st, dwm, etc.

      But yeah. If a toolkit is necessary for Wayland, then I’d love some extremely minimal options. Or better yet, exactly one minimal option so good that nobody ever feels the need for an alternative. (But that’s not going to happen. Heh.)

      I’ve poked a little bit at the Go GUI toolkit “Fyne”. It appears to use OpenGL/GLFW, which is kinda neat, I think. Looks like GLFW’s dependencies are indeed quite minimal.