At 1252334475 time_t, Cedric GESTES wrote: > - empty clientwidget : this will allow to create tag with a fixed > layout, and could allow to focus empty tag on another screen. > (handling two screen without mouse is not trivial atm and require > tweak and tricks here and there)
Well, Pierre made a proposal which has some sense regarding this issue, i.e. implemeting a special module/function defining what focus is. > - real tab: with the current version of awesome it's impossible to > make tab work properly. I know it's not the philosophy of awesome to > use tab, but as a framework window manager I think it make sens. In > fact I will really like to mix both fixed layout+tab and current > awesome windows handling. > > For the empty clientwidget think, the proposition A seems better. > For tab I can think of plural solution. > One can be to allow sublayout, using a suit.max layout in a frame > would just create tabs. I don't think titlebar and tabs are related. Titlebar can show informations about tab, that certain, but your organization of tab is dependant on you. There's probably a lead to follow in what you say about sublayouts. Making 2 clients tabbed is just arranging them with suit.max (or something else, why not?) were the area is not the full screen but probably the coordinates of ones of the 2 clients. Another plan (let's call it Plan D) I forgot to mention is to remove titlebar from C code and let Lua handle it with wiboxes following clients. But that's also has drawbacks IMHO, like getting client width/height does not count the titlebar following it. Cheers, -- Julien Danjou // ᐰ <[email protected]> http://julien.danjou.info // 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD // Trust me.
signature.asc
Description: Digital signature
