On 2008-03-01, Per Ekström <[EMAIL PROTECTED]> wrote: > ------=_Part_14584_20378963.1204407188085 > Content-Type: text/plain; charset=ISO-8859-1 > Content-Transfer-Encoding: quoted-printable > Content-Disposition: inline > > Hi! > > I like the concept of Ion, though I have yet to try it "for real" (I've onl= > y > been playing around in it so far). Kudos for such a nice WM. :) > > There's just one thing I miss, that I haven't found in any of the tiling WM= > s > so far; There's no way to set up templates to tell your apps where they > should go. :(
As others have pointed out, there's "winprops" [1], that can be used to some extent. In particular the 'target' and 'new_group' properties are useful in this case. The former will specify an existing frame or so, and the latter the name of a stored layout for a new group to be created, if the 'target' didn't exist. You can copy-paste the configuration of a group you have created from the layout savefile (removing references to client windows), and pass it to ioncore.deflayout to give it a name. (Also see cfg_layout.lua for examples of layout definitions.) Give useful (unique) names to the frames within the layout, and you have a sort of template system. It's a bit clumsy, but then apps don't exactly help us here, and haven't found myself wanting an improved version of the feature. You could do something better with Lua scripting, perhaps. [1]: http://iki.fi/tuomov/ion-doc-3/ionconf/node4.html#SECTION00450000000000000000 -- Tuomo
