On Thu, 2006-11-16 at 19:08 +0000, Mike Dransfield
wrote:> Looking through the code for the plugins, it seems
> like there is a need to apply options to individual
> windows and window types.
>
> As far as I can see there are 2 basic needs for the
> plugin developer.
>
> 1. Run time tagging of windows similar to XHints.
> I do not think plugin developers should resort to
> xlib coding for this and I think there is a genuine
> need for it. Beryl has added an ipcs system which
> I think handles this sort of thing for the plugins.
> These hints should be available to all plugins,
> window privates are only available to the individual
> plugin.
hm, I think it still might make sense to use X properties for this. We
can add some utility functions for setting and getting properties to
make life easier for plugins and we can always short-circuit these set
and get functions if performance is important.
>
> 2. Individual window settings. A lot of the plugins
> are starting to have window specific settings, these
> are normally set based on the class, title etc.
> So far they have been using a string like this to
> configure an individual window class.
>
> c:Kopete:80
>
> Maybe something could be standardized in the
> core to accommodate these requirements?
Yes, some kind of general window matching option that could contain
type, class and other constrains would be useful. Lets add that.
-David