Christian Ridderström wrote:
>> 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 inherited 'Product' from Asger's original creation. (I'm merely tweaking
a super idea.)
> 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
Maybe. But I think Asger meant 'Product' as in 'The product of the bakery
is bread'. Here, 'The product of a a request to export to latex is a
snippet of latex code'.
> 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.
You are thinking in terms of LaTeX only. The template also has LinuxDoc,
DocBook and Ascii output formats. Maybe their definition of Requirement is
different.
Nonetheless, you are right to point out that the terminology isn't crystal
clear. I do think that lib/external_templates needs some introductory
comments to help explain the language.
> 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.
This is the job of a package manager, not of an inset. We do need a package
manager... (See
http://marc.theaimsgroup.com/?l=lyx-devel&m=102748093926086&w=2
plus ensuing thread for an try at one. If you're still interested in a pet
LyX project maybe you could resurrect it.)
--
Angus
