eafton
eafton
@slouken Wouldnt it be easier to draw and handle the menus ourselves atleast on X11?
> ```diff > +#ifndef DBUS_ERROR_UNKNOWN_PROPERTY > +#define DBUS_ERROR_UNKNOWN_PROPERTY "org.freedesktop.DBus.Error.UnknownProperty" > +#endif > ``` Implemented.
Menu export works now, I just gotta wire it up.
> Will this implementation count with being able to use scroll events? > > Currently we use it to set volume up/down based on scroll up/down over the tray (albeit...
> Two more things that I can't seem to find in the current source, is it planned to: > > 1. Be able to hide/show the icon without destroying it...
> Can someone run down the use cases for this "toolkit"? > > Right now we use zenity if available for X11 and Wayland, and I think this is reasonable...
> Just some random thoughts from me: > > * Having to dip down into X11 for any functionality beyond basic window management _sucks_, so anything that makes this suck...
@Kontrabant @icculus Do we pick SDL_ttf (at some point in the future when system font lookup gets added) or fcft for font rendering on Wayland and maybe X11? slouken said...
Also here is an idea on how to solve the "backend seperation" problem. Notice the seperate drawing and text drivers. They are there to make the toolkit work better on...
Idea on how to handle GTK/Qt/GNOME/KDE/etc integration...