[compiz] window matching interface and the new match option

[David Reveman]

On Tue, 2007-02-27 at 16:39 +0000, Mike Dransfield wrote:
> David Reveman wrote:
> >
> > PID can be in the core. Process name, host name.. and everything else
> > you can think of that are strings should be in the regex plugin.
> >
> > Window dimensions would be useful. '>', '<', '=' can be used without any
> > changes to match interface as those things are up to the expression
> > handler to parse and there's nothing that prevents that right now.
> >
> > If you or anyone else feel like implementing a few of these please do
> > so.
> >   
> 
> I will have a look at PID and window size matching using greater
> than and less than, the others are not so important now.
> 
> Also do you think it would be OK to add an override redirect match?
> It would make it possible to work around a few toolkit bugs (ie. the 
> mozilla
> menu problem)
> 
> 
> >> It would also be very useful if the match string could include a
> >> value as well.  This would mean that plugins like blur could
> >> have a list of matches with values and it could apply different
> >> types of blur to different types of windows.  eg.  It could use
> >> 4xBilinear for any window which is wider than 500 px like this
> >>
> >> min_width=500 =4xBilinear
> >>     
> >
> > I don't think we want this in the match option. What you want is a list
> > of (match, int) pairs and that can be created right now by having two
> > list options. However, I've been waiting for a good reason to add a pair
> > option type and this seems like the perfect case.
> 
> It sounds good :)

I had a look at this and I'd like to wait with adding a pair option type
until we've moved the ini plugin and dbus plugin updates into master.

I've added general window opacity matching as two list options for now.

- David