Re: Improving API for lists, or wildcarded schemas

[Tony Houghton <lists realh co uk>]

In <1075345730 27392 73 camel localhost localdomain>, Havoc Pennington wrote:

> On Mon, 2004-01-26 at 20:04, Tony Houghton wrote:
> > 
> > ALternatively, instead of using lists I could use options called
> > "sensor1", "sensor2" etc all the way up to 16, but defining them all
> > properly in the schemas file would bloat it. Is it possible to make one
> > schema apply to multiple options eg "sensor*"? If not, would it be
> > reasonable to add such a capability?
> 
> You can have multiple <applyto>, I think there's an example in
> metacity.schemas - not sure if this helps or not?

Yes, I think that tips the balance in favour of discrete keys instead of
lists for this application.

> The problem with wildcarding is there's nothing to match against at
> schemas install time, so it would need to be a runtime match - unclear
> how to implement that in gconfd.

OK, sounds like it could be a bit of a headache.

I take it you're not keen on my other idea about making it easier to
access individual items in a list?

-- 
TH * http://www.realh.co.uk