On Mon, Aug 07, 2006 at 11:54:58AM -0400, Ross Mohn wrote:
> On Mon, 2006-08-07 at 16:47 +0200, Anselm R. Garbe wrote:
>
> > On Mon, Aug 07, 2006 at 04:41:10PM +0200, Sander van Dijk wrote:
> > > On 8/7/06, Ross Mohn <rpmohn_AT_waxandwane.org> wrote:
> > > >
> > > >On Mon, 2006-08-07 at 16:31 +0200, Sander van Dijk wrote:
> > > ><snip>
> > > >(in fact, If it weren't for these classic-approach-only apps like the GIMP,
> > > >it would probably be a good idea to get rid of the per-client 'isfloat' as
> > > >well: using for instance three tiled and three floating clients in one tag
> > > >shows quite clearly how well these two paradigms mix; unfortunately, as
> > > >long
> > > >as there are paradigm-specific apps, we'll need the per-client 'isfloat').
> > > ><snip>
> > > >What about for transients / pop-ups?
> > > >-RPM
> > >
> > > Transients and pop-ups are probably the best examples of
> > > single-paradigm apps one can give ;-)
> >
> > And they are the only reason for Client->isfloat.
>
> For my usage pattern, there are some applications that I always want to
> be maxed. Fortunately, most are grouped together in one tag, hence my
> preference for a per tag-based max mode. Also, besides the apps that I
> make float with a rule, I sometimes want to float a specific window
> temporarily, hence my preference for a client-based float mode.
>
> I will scratch my own itches ;-)
I concentrate on st (simple terminal) already... ;)
Regards,
-- Anselm R. Garbe ><>< www.ebrag.de ><>< GPG key: 0D73F361Received on Mon Aug 07 2006 - 18:00:11 UTC
This archive was generated by hypermail 2.2.0 : Sun Jul 13 2008 - 14:30:01 UTC