LISTSERV mailing list manager LISTSERV 16.0

Help for LATEX-L Archives


LATEX-L Archives

LATEX-L Archives


LATEX-L@LISTSERV.UNI-HEIDELBERG.DE


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

LATEX-L Home

LATEX-L Home

LATEX-L  November 2009

LATEX-L November 2009

Subject:

xtemplate

From:

Joseph Wright <[log in to unmask]>

Reply-To:

Mailing list for the LaTeX3 project <[log in to unmask]>

Date:

Sun, 8 Nov 2009 17:07:24 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (93 lines)

Hello everyone,

There has been some work going on within the team to get ideas (and 
code) into better shape with template. The result of the work is the 
xtemplate package. There are still open questions that we are working 
on, and also some where more input would be very helpful. I'll try to 
outline what we have done and what remains to be decided.

 =======================================================================

The ideas are laid out in the dtx: Will has done a good job of setting 
them out there, and I'm not going to repeat it! For people familiar with 
template, you'll see that we've renamed \DeclareTemplateType to 
\DeclareObjectType, as the old name was downright misleading.

The keyval system has been completely revised in xtemplate. This is 
because it became clear we wanted some "self-documentation" in the keys. 
The idea now is to divide things into two:

  - \DeclareTemplateInterface. This sets up the names of keys in a 
template and the type of argument they expect (skips, functions, etc.). 
It also includes default values.
  - \DeclareTemplateCode. Sets up the implementation of the keys.

The reason for this is that the interface should be understandable 
without needing to know about the code. So the aim is that you can look 
at the arguments to \DeclareTemplateInterface and know what you might 
want to change, without looking at \DeclareTemplateCode at all.

Most of the ideas for instances and collections have not changed (at the 
moment).

 =======================================================================

There are a number of things that still need sorting out. In no 
particular order, I'll list the ones I remember.

The key types are in the main pretty easy to follow. One that I'm not 
sure about is "tokenlist". In the context of designing templates, "text" 
would seem to make sense here, as this is really what is intended. If 
the interface is supposed to help designers, the TeX token concept is 
not necessarily helping much.

\MultiSelection has not been moved to xtemplate from template. That is 
because it'd not clear quite what to do yet. The general question is how 
to make one key depend in some way on another. Frank suggested some 
"stories":

  - set the vertical space between items of a list depending on the list
    context (i.e., the list depth) -> that is an index like spec

  - set the vertical space before a heading to X except when the heading
    is immediately preceded by another heading (in which case use Y) but
    use Z if the heading falls on the top of a new page -> that is not an
    index like spec

  - set some length to the max of X and the current value of variable V
    taken from the context of the instance

So something that uses an index is one possibility, but only covers some 
scenarios. The question is therefore what situations need support at the 
level of xtemplate (as opposed to being handled in the code part of a 
template).

The collections idea is currently probably not quite right. A while ago, 
Frank said:

'What exactly should collection instances be used for? I'm starting to 
question how much use they actually provide as they offer exactly one 
level of variance and often you would have several layers, e.g., would 
"frontmatter", "mainmatter", "backmatter" be good candidates for 
collections? So that, for example, pagestyles behave differently in 
those places? But then this should also influence the way headings are 
set (would be possible) and in the way page numbers are displayed (more 
difficult perhaps). And what happens if somebody else come up with a 
different type of collection, e.g., making "minipage" a collection to 
change behaviour or stuff inside. Then who wins? And why?'

and that still applies. As collections are about design, I can't myself 
see how more than one can be in force at any time, but can see the 
problem of keeping things in sync. The code currently sticks close to 
the original template concept, but this probably needs to change.

The argument order of some of the functions probably needs rethinking. 
This will probably have to be decided after other stuff is sorted out!

 =======================================================================

Thoughts on any part of (x)template very welcome. It's clear that some 
problems will have to be revisited as more use is made of templates: we 
can't hope to know everything now!
--
Joseph Wright

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

September 2019
July 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
June 2018
May 2018
April 2018
February 2018
January 2018
December 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
July 2016
April 2016
March 2016
February 2016
January 2016
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
September 2012
August 2012
July 2012
June 2012
May 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
September 2007
August 2007
June 2007
May 2007
March 2007
December 2006
November 2006
October 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
November 2005
October 2005
September 2005
August 2005
May 2005
April 2005
March 2005
November 2004
October 2004
August 2004
July 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
October 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
October 2002
September 2002
August 2002
July 2002
June 2002
March 2002
December 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
January 1998
December 1997
November 1997
October 1997
September 1997
August 1997
July 1997
June 1997
May 1997
April 1997
March 1997
February 1997
January 1997
December 1996

ATOM RSS1 RSS2



LISTSERV.UNI-HEIDELBERG.DE

Universität Heidelberg | Impressum | Datenschutzerklärung

CataList Email List Search Powered by the LISTSERV Email List Manager