On Tue, 23 Sep 2003, Angus Leeming wrote:
> Example of modifier options in action:
>
> Template RasterImage
> GuiName "Image: $$FName"
> InputFormat "*"
> AutomaticProduction true
> Modifiers Rotate, Resize, Clip, Extra
> Format LaTeX
> ModifierOption Rotate RotationLatexOption
> ModifierOption Resize ResizeLatexOption
> ModifierOption Clip ClipLatexOption
> ModifierOption Extra ExtraLatexOption
> Options "$$Extra$$Rotate$$Resize$$Clip"
> Product "\\includegraphics$$Options{$$Basename}"
> UpdateFormat eps
> UpdateResult "$$Basename.eps"
> Requirement "graphicx"
> FormatEnd
> TemplateEnd
>
> Needless to say, I'd like suggestions on how to improve any of this...
About the syntax: I find it mostly understandable, but I'm not sure about
'Product'... isn't this more like a composition/concatenation rather than
a multiplication?
I assume 'Product' represents an expression that after evaluation
(substitution?) result in a snip of Latex code, so I'd suggest using one
of the following keywords rather than 'Product':
Code
Output
Result
Expression
And just a minor thing... 'Requirement' means what packages that needes to
be included using \usepackage, right? If so, why not use something like:
Packages
UsePackage
RequiredPackages
RequirePackage
to make the connection to packages clearer.
Finally a loose thought... sometimes you can get undesired results if you
include packages in the wrong order (I remember something about a bug
related to rotating a figure). I don't know if it's worth the effort
to specify when a package should (preferably) be included, I guess you can
always manually add your \requirepackage{}-statements to the preamble.
/Christian
--
Christian Ridderström http://www.md.kth.se/~chr
