On 2008-09-07, Carlos Pita <[EMAIL PROTECTED]> wrote:
>> Can you explain me how to achieve the frame-->wgroupcw-->clientwin setup
>> instead?
>
> I've been messing a little more with this and discovered that the
> difference is more subtle that I had thought. In both cases the parent
> is the frame, but reg:attach(cwin) will make the frame also the manager
> while customary ion handling of new windows will put them under a new wc
> group management, which is itself ultimately managed by the frame. Could
> you clarify this please? Which is the rationale behind this slightly
> complex setup? A snippet of lua (?) code showing the creation and/or
> connection of the different collaborators (the wc group, the frame, the
> window) will be very enlightening.
The layout savefiles (~/.ion3/SESSIONNAME/saved_layout.lua) can be
englightening. It's exactly the same data that can be passed to
the attach functions.
The template for the WGroupCW container attach is. For details,
see the documentation and the savefiles.
reg:attach{
type = "WGroupCW",
...,
managed = {
{
type = "WClientWin",
...
}
},
}
---
As for rationale.. client windows within frames are managed
in groups just like workspaces (and FS client windows) are
groups within the screen. Also, both WFrames and WScreens
(incl. WRootWins) are WMPlexes; a frame is just a decorated
one, but the bulk of the code for the functionality is the
same.
--
Tuomo
