| |
| |
On 12/1/22 21:20 Bill Spitzak wrote:
What I don't understand is why the included
libdecor is unable to load system-provided plugins.
Because there are no such plugins yet. I'm sure it could do that.
... If the system has it's own plugin it should be
loaded and used no matter how fltk is compiled.
Yes, *if* !
It does sound a lot like we need a better fallback plugin.
Take the code for the cairo plugin and fix the font sizes.
This can't be too hard.
I agree, this might be a better way than to rely on the GTK plugin
that needs the GTK dev headers (which is a *lot*) if we compile it
ourselves.
I would not add a dependency on GTK.
Currently it's optional (with the fallback to the Cairo plugin). But
I agree that I wouldn't want a hard dependency on GTK.
On
Thu, Dec 1, 2022 at 9:29 AM Manolo <manolo.gouy@gmail.com>
wrote:
The libdecor source code bundled in FLTK is unchanged
relatively to what it is at its
home repository. We don't want to change that.
Since the cairo plugin is apparently not acceptable, the
solution is to make the Wayland
FLTK platform require the libgtk-3-dev package, just like
it requires already libpango1.0-dev.
In the future, when the GTK libdecor plugin will have
become a Linux package, FLTK can be made
to require either libgtk-3-dev or libdecor.
--
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/5073f995-cfc3-deae-88ef-32aedb96b3f2%40online.de.
[ Direct Link to Message ] | |
|
| |
