Re: [dev] A general approach to master-slave layouts

2011-11-13 Thread Anselm R Garbe
On 13 November 2011 01:10, Connor Lane Smith wrote: > On 10 November 2011 21:21, Anselm R Garbe wrote: >> I thought about this a while and I have to say I'm in favor to have a >> bold decision to apply it to hg tip in order to test this in a broader >> environment. This could lead to reducing the

Re: [dev] A general approach to master-slave layouts

2011-11-12 Thread Connor Lane Smith
Hi Anselm, On 10 November 2011 21:21, Anselm R Garbe wrote: > I thought about this a while and I have to say I'm in favor to have a > bold decision to apply it to hg tip in order to test this in a broader > environment. This could lead to reducing the "Wildwuchs" of the other > layout patches on

Re: [dev] A general approach to master-slave layouts

2011-11-10 Thread Anselm R Garbe
Hi Connor, On 6 November 2011 20:28, Connor Lane Smith wrote: > I've been thinking about this patch for a while, and I've knocked > together a patch which takes an alternative approach, which seems to > result in a simpler diff. > > In my patch each layout has three arrangement functions, one for

Re: [dev] A general approach to master-slave layouts

2011-11-06 Thread lolilolicon
On Mon, Nov 7, 2011 at 11:15 AM, lolilolicon wrote: > >  * Port my original spiral layout to play with this patch. I've simplified the spiral layout by rusing tile{h,v}. Nice. void spiral(Client *c, float fact, XRectangle *r, XRectangle *rp) { if(fact == 0) { rp->width = rp->height = 0; retu

Re: [dev] A general approach to master-slave layouts

2011-11-06 Thread lolilolicon
On Mon, Nov 7, 2011 at 3:28 AM, Connor Lane Smith wrote: > Hey, > > I've been thinking about this patch for a while, and I've knocked > together a patch which takes an alternative approach, which seems to > result in a simpler diff. > > In my patch each layout has three arrangement functions, one

Re: [dev] A general approach to master-slave layouts

2011-11-06 Thread Connor Lane Smith
Hey, I've been thinking about this patch for a while, and I've knocked together a patch which takes an alternative approach, which seems to result in a simpler diff. In my patch each layout has three arrangement functions, one for the master, one the slave, and one a 'meta-layout' which defines h

Re: [dev] A general approach to master-slave layouts

2011-10-31 Thread lolilolicon
On Tue, Nov 1, 2011 at 8:41 AM, Connor Lane Smith wrote: > Hey, > > On 31/10/2011, lolilolicon wrote: >> The idea of having more than one master windows is brilliant.  The `tile' >> layout in current hg tip basically splits the master and slave areas >> vertically, and tiles windows in each of th

Re: [dev] A general approach to master-slave layouts

2011-10-31 Thread Connor Lane Smith
Hey, On 31/10/2011, lolilolicon wrote: > The idea of having more than one master windows is brilliant. The `tile' > layout in current hg tip basically splits the master and slave areas > vertically, and tiles windows in each of the two areas using a vertical > stacking algorithm. I'll be intere

[dev] A general approach to master-slave layouts

2011-10-31 Thread lolilolicon
The idea of having more than one master windows is brilliant. The `tile' layout in current hg tip basically splits the master and slave areas vertically, and tiles windows in each of the two areas using a vertical stacking algorithm. The `ncol' layout does it slightly differently by tilling the m