-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Since my mail server went AFK for a couple of days, here are all my replies on
this thread again (stupid postfix :( ). I'll also have to resend some patches
later... :/
Uli
> Plan B: everyone has a titlebar
I like this idea, that way titlebars no longer an unused option that no one uses
because (implicitly) everyone has them.
But:
The wibox code updates wiboxes via XCopyRect() (I forgot the xcb name of that
and atm I'm too lazy to look it up). This would overdraw the child window AFAIK
which is a bad thing. I'm not sure this is correct, jd do you know more?
But this wibox would again need a lot of special case code. The lua code would
need a way to reserve a [X] pixel large area between parent wibox window and
the real client and then it needs something to put widgets there. Wiboxes with a
hole in their center sound complicated. :(
> Plan C
> ------
> Do nothing. Haha. I'd vote for that. :]
Given that I don't use titlebars myself....
Still, if I *would* use them, I'd prefer them to be implemented via 'real'
parent windows instead of a separate window which just happens to be above the
client (or not). This would also allow us to do way more fancy window borders.
Someone asked for some "pseudo 3D" look for window borders recently...
Anyway, nothing of this sounds perfectly easy and sensible to me. :(
Uli
> Plan A: client widget
Thinking about this, we could need something like this:
capi.client.new(wibox, client)
This should somehow associate the wibox with the client or create a new client
which refers to that wibox or something like this. (Call manage hook etc?)
This "wibox client" can then be managed normally by the existing code, but
requests for properties like c.class on that "wibox client" would be forwarded
to the real client. Only things like c.hide and c:geometry() would really affect
the wibox.
Then one can (if one wants) show the real client in there via the client widget.
For tabbing support, one would need to be able to "switch" the "wibox client" to
another client on the fly. However, I have no idea how to do frames this way
(frames with more than one client, that is. Which client's properties should be
passed on?)
Just a thought....
Uli
- --
"Do you know that books smell like nutmeg or some spice from a foreign land?"
-- Faber in Fahrenheit 451
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iQEcBAEBCAAGBQJKphM3AAoJECLkKOvLj8sGvPYH/RREvmah5aQVGwPgDZhhN0MA
D+vef6mzkwcOVvsAv6FqLgSaRTUKYzr+GLLOymvLjpCWAxaGsIEo8nqqR0mtMNww
0R4rkfJWr5mwvMn0yVpmd8TtmAqyI/EDaSc+5mATrBkjwW7Ee4VvMHZi1WUzAuKJ
V/SFF7XYNl6zsCD4Tked/Nrovb/U7Oh/ddQn+U9Mu/KDFhDqSN9G/llHRV2b9VS5
cM8r4AWOS+utnUVDNU9W8nlxp8gvlOg1kAIyIPWrrBNpAuWseOL31nATf22ZGX+0
sdEdYUISy/TcLdhwigcJObx9QkWCM8f6x98HohFl8k/UCbpEYc9w5hGg/s6UW+Y=
=bIff
-----END PGP SIGNATURE-----
--
To unsubscribe, send mail to [email protected].
