Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Mime-Version: 1.0 (Apple Message framework v936)
References: <19189.17593.814557.704925@morse.mittelbach-online.de>           
            <4AF5A79B.9040003@residenset.net>
            <19189.49743.74826.581704@morse.mittelbach-online.de>
            <4AF6DC52.2030401@residenset.net>
Content-Transfer-Encoding: 8bit
Message-ID:  <0DF959B5-ED1B-497A-A1D5-C2DF49FC064E@gmail.com>
Date:         Tue, 10 Nov 2009 20:50:54 +1030
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: Will Robertson <wspr81@GMAIL.COM>
Subject: Re: an object type for heading commands
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <4AF6DC52.2030401@residenset.net>
Precedence: list
Status: R

Branching off on a comment by Lars.

On 09/11/2009, at 1:27 AM, Lars Hellström wrote:

> My first gut reaction is that decisions of whether to put a heading  
> in the TOC or not should be controlled by the choice of instance (or  
> are they named "objects" now?).

No, instances are still instances :)

"Objects" are what you used to declare when you wrote in the template  
package \DeclareTemplateType. That command has now changed to  
\DeclareObjectType. Why? Because even more importantly than templates,  
objects are linked to *instances* -- it's possible to even create an  
instance that satisfies an object without using a template.

So where before we had this implicit idea of templates and instances  
being collected together to fulfil some sort of role in the document,  
we can now explicit talking about, say, "heading objects", "float  
objects", "vulgar fraction objects", and so on.

I'd like to improve the documentation on this, so if you have any  
comments on how xtemplate can be made clearer I'm all ears.

-- Will