Hi everyone, as already mentioned on irc I'd like to see a static layout in awesome and perhaps I'll give it a try myself... The idea and working mechanism is shamelessly stolen from ion.
*skip this block if you know ion* The basic building block of a static layout is the area. Areas are a sort of frame/container which can hold windows, preferably only one window at a time (except tabs). Areas do not automatically resize/appear/disappear, they reserve a fixed space. A static layout should always contain at least one area. Areas can be split both vertical and horizontal resulting in an additional area. Areas can be manually resized. An area can be tabbed, so that an area holds several windows of which only one is visible. Static layouts should be configurable via a configuration file, so that a layout can be defined once and is set up on startup or when a specific client is started. It should be possible to give areas names in this configuration file. With this name it should be possible to automatically add clients to specific areas in a static layout. There should be a mechanism to mark a specific client and later on paste the marked client into the currently active area. There could be one or more floating area in addition to the fixed ones. When a client is moved to a static layout it could be added as floating first, or added in a floating area. I am not entirely sure how this should play together with the tagging system of awesome, since displaying two tags of which at least one uses static layout is hard. So it might be a good idea to simply forbid displaying a static layout tag together with another one. I heard that AStorm is already working on this, I don't know about the progress and any codewise plans though. I am not familiar with the code except for 10 minutes looking through it. Now my question is what you think about it, how it should be implemented best and (@AStorm) what has already been done? Greetings, Patrick
signature.asc
Description: PGP signature
