Mime-Version: |
1.0 |
Content-Type: |
text/plain; charset="UTF-8" |
Date: |
Mon, 22 Oct 2018 07:08:26 +0200 |
Reply-To: |
|
Subject: |
|
Content-Transfer-Encoding: |
quoted-printable |
Message-ID: |
|
Sender: |
|
From: |
|
Parts/Attachments: |
|
|
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
|
|
|