LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Kelly Smith <[log in to unmask]>
Reply To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Date:
Mon, 22 Oct 2018 07:08:26 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines)
Hello,

The class is coming along nicely. The class options are fully-functional
and no longer crash TeX (thanks to Joseph Wright for the info on option
processing in 2e).

I have found templates very useful for managing document components. However,
this means that some templates are woven into the class internals,
necessitating that there only ever be a single template for a given object
type. Of course, instances of that single template can be declared and used
freely. As such, it seems prudent to provide a more limited interface to
document designers.

An example of such a limited interface is font sizes. I provide the commands

`\DeclareFontSize {<name>} {<attributes>}`
`\EditFontSize {<name>} {<attributes>}`
`\UseFontSize {<name>}`

as wrappers around the `\DeclareInstance`, &c. set of commands. The idea is
that these commands should be the only means by which one interact will with
the class' font size template. I am making a similar system for page layout.

Is this an appropriate approach to abstraction, or is it an abuse of xtemplate?

-Kelly

ATOM RSS1 RSS2