[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] Workaround for prescriptions

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Workaround for prescriptions
Date: Sun, 23 Sep 2012 19:47:00 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

On Sun, Sep 23, 2012 at 04:57:58PM +0000, Jim Busser wrote:

> > Attached find a better example for a text/generic form
> > template. It can be tested this way:
> > 
> > - save as ~/text-form.conf
> > - update git tree from gitorious
> > - cd ...gnumed/client/business/
> > - run "python test ~/text-form.conf"

> 1) By what method ( a placeholder ??) will such text templates be "called" 
> from within GNUmed?

They are form templates, as with any other form template
(AbiWord, LaTeX, LO, PDF, XeTeX, Gnuplot), and are used with
the (new) TextForm engine.

> 2) When (within the text of the attachment, text-form.conf) you wrote
>       Eventually, the file will be passed to what is defined
>       as "editor" and "post processor" above which can
>       be *arbitrary* pieces of code, doing whatever.
> does "above which can be arbitrary code" mean
>       within this template file, below the top line containing
>               [form]
>       and above the line containing
>               editor =

Above means <within the group [form] in the form of values
of the options "editor" and "post processor">.

Those options can be placed *below* the "template =
$template$", too, that doesn't matter, as long as they are
inside the group [form].

Think of text-form.conf as a config file just like

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

[Prev in Thread] Current Thread [Next in Thread]