Re: [dev] dwm in a window

From: Anselm R Garbe <garbeam_AT_gmail.com>
Date: Wed, 8 Jul 2009 10:20:46 +0100

2009/7/8 yy <yiyu.jgl_AT_gmail.com>:
> 2009/7/5 Alexander Polakov <polachok_AT_gmail.com>:
>>  Well, explaining is not my best (and english too), so better take a
>> look at a picture
>>  http://rootshell.be/~polachok/trash/dwm-in-a-win.png
>
> Well, I think this is awesome, it is sad to see how quickly this
> thread turned into another dead-end discussion about how much X sucks.
>
> There are so many possibilities with nested dwm instances that I think
> some ideas would be worth trying. I can see its application to web
> browsers like surf or uzbl, or how a "master dwm" with a nested dwm
> per tag could be used as a workspaces on top of dwm solution. I can
> think of better examples, but I have some questions:
>
> I had a quick glance at the code and I guess what you are doing is
> getting control of the windows given in the command line with scan. Is
> there any reason windows cannot be moved between dwm's on the fly? how
> difficult would it be to communicate the different dwm instances?
> (moving clients between them  based on rules and user actions would be
> enough for me, more elaborated interfaces could be possible). Also, I
> would really like to know where is dwm on a window situated with
> respect to xephyr and rio, whatever you think about Plan9, running rio
> inside rio is a great feature, if I can have that with dwm I think is
> one of the most killer features you could have in a window manager.
>
> Don't you think the integration of this feature into dwm could be well
> worth? Maybe not, maybe it is just a hack or not a good idea at all,
> but I would like to see some discussion about that.

dwm just manages windows which are owned by X, so dwm is just an X
client -- with one exception to others: only one X client can select
for specific event masks such as SubstructureRedirectMask on the
display, by convention that is usually the window manager client
(singleton). So dwm is not a window system.

The idea behind dws is to form a window system API on top of X in the
beginning, to achieve all this, so basically dwm could be written on
top of dws, which itself could run on top of X, but then such dwm
would only manage native dws clients -- which will enable us to do
exactly what you require in the dws world.

So it's quite likely that there will be dwm running on X and some dws
in a window running dwm on dws in the interim, until there is an X
layer on top of dws and native graphics support for dws later on.

Kind regards,
Anselm
Received on Wed Jul 08 2009 - 09:20:46 UTC

This archive was generated by hypermail 2.2.0 : Wed Jul 08 2009 - 09:24:01 UTC