Lines: 72
References: <C58398B6-8915-458C-AF38-F3C82F9342B2@gmail.com>                   
            <4E4FF538.7070601@morningstar2.co.uk>
            <9788A2B7-3E8F-4D2C-A52E-10999BCB59FA@gmail.com>
            <4E516DF2.4040002@morningstar2.co.uk>
            <104nbkj0nr84x.dlg@nililand.de>
            <4E523217.2080408@morningstar2.co.uk>
            <cybpko27uiip.dlg@nililand.de>
            <4E52AA87.6090608@morningstar2.co.uk>
            <1i25hv8yiyx81$.dlg@nililand.de>
            <4E537C7A.5040605@morningstar2.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
User-Agent: 40tude_Dialog/2.0.15.41de
Message-ID:  <1konvzgb7ssyz.dlg@nililand.de>
Date:         Tue, 23 Aug 2011 13:03:38 +0200
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@listserv.uni-heidelberg.de>
Sender: Mailing list for the LaTeX3 project <LATEX-L@listserv.uni-heidelberg.de>
From: Ulrike Fischer <news3@NILILAND.DE>
Subject: Re: couple of l3keys notes
To: LATEX-L@listserv.uni-heidelberg.de
Precedence: list
Status: R

Am Tue, 23 Aug 2011 11:10:02 +0100 schrieb Joseph Wright:

> On 23/08/2011 09:32, Ulrike Fischer wrote:
>> I don't have enough practice with l3keys to decide this - just
>> starting. But from the language I would expect a \keys_set_known to
>> give an error if it encounters something unknown. Also a command to
>> set keys can set only known keys, so it sound like a pleonasm. 
> 
> Well no, as the special 'unknown' key allows behaviour for a key which
> is not defined to be set up.

Does keys_set_known makes a difference between modules with and
without such an unknown key?  

> 
>> Another question: pdfkeys has the notion of a "key tree" and
>> "pathes". And you can switch pathes with a command. (.cd I think).
>> Can/should one do something similar with l3keys? I see the
>> subgroups, but I'm not sure if they really are the same conzept.
> 
> Internally, l3keys uses the same storage approach as pgfkeys. The
> \keys_set:nn macro is rather more like \pgfqkeys than \pgfkeys, in the
> sense that it includes a root to search from. It is therefore possible
> to do something like
> 
>   \keys_set:nn { } { foo / key-a = value , bar / key-a = other-value }
> 
> So it would in principal be quite possible to implement
> 
>   \keys_set:n % No starting path
>     { / foo .cd: , key-a = value , bar .cd: , key-a = other-value }
> 
> However, at the moment there's not been a good use case for l3keys for
> such an approach. Explaining keys as a tree is not so easy as dealing
> with each modules keys separately.

I'm currently changing chessfss to keyval-syntax. I have to set
properties for board fonts, figurines fonts and other symbols. So I
have a structure like this:

all chess fonts
  family
  width
  series
  size
  
fig font
  encoding
  family
  width
  series
  size

board font
  encoding
  family
  width
  series
  size

...

So keys like "fig / encoding" look quite natural, but it would be
quite useful if a user could set keys also like this:

set-all, family=...

set-fig, family=...  , size= ...


-- 
Ulrike Fischer