[Compcomm] So what's going on code-wise? Or what we're working on.

[Danny Baumann]

Hi,

> > I know it does, and I have a patch for multiscreen waiting for that.
> > It was fixed in beryl quite some time ago.
> >
> > Also, most people don't choose decorator by typing in the command for
> > it in the command section, most people don't even fully understand
> > what it's for. And since there isn't much of a reason NOT to support
> > this in a startup script, I added it.
> >   
> 
> This is probably something we should look at changing, users
> do not need to know about that OR starting a decorator as well
> as compiz.  They should just start compiz and it will take care
> of the decorators.  Its possible that one day there might be another
> decorator plugin and that would take care of its decorator.
> 
> If we had a library that could read and write settings using their
> plugins then you could write a script which sets that value and
> then starts compiz.  It would be virtually the same as far as you are
> concerned but things would work as designed.

If libbs (and the bset plugin) was used by everyone, we actually had
such a library already ;-)

The problem here is that you don't really know what storage backend is
used by the user. That's why you have a problem even if you created an
application that uses the storage backend to save the decorator command
option. Besides that, I agree that this would be the most elegant
solution.

Regards,

Danny