gnumed-devel
[Top][All Lists]
Advanced

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

Re: [Gnumed-devel] How to contribute templates


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] How to contribute templates
Date: Wed, 23 Nov 2011 01:38:59 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

On Fri, Nov 18, 2011 at 05:38:41PM +0000, Jim Busser wrote:

> On the wiki
> 
>       http://wiki.gnumed.de/bin/view/Gnumed/TemplateRepository
> 
> under
> 
>       How to contribute templates
> 
> it asks
> 
>       Please provide:
> 
>       • filename: e.g. medication_list.tex
>       • description: e.g. a list of past and prestent medications taken by 
> the patient
>       • version: e.g. 0.1 please increase the version when you update the 
> template
>       • date: when was it you created the template
>       • targeted GNUmed version: e.g. 0.8.x
>       • license: GPL , FDL or anything you would like
>       • source: either your name or 'VCS' when it gets incorporated into the 
> main GNUmed repository
> 
> Just thinking… the dialog in gmFormWidgets.py asks for
> 
>       Name
>       Alias
>       Version
>       Template type
>       Document type
>       Filename
>       Processed by (OpenOffice, LaTex, Image editor, Gnuplot, PDF form editor)
> 
> and maybe if the author/contributor would embed in their template a version 
> and a 'processed by' these values could "auto-load" into the template?
> 
> The values would have to be commented, for example in a Tex template:
> 
>       % Version = '1.1'
>       % Processed_by = 'LaTex'
> 
> or if such words might (within a template) be ambiguously used, then
> 
>       % gm_read_version =
>       % gm_read_processed_by =
> 
> and
> 
>       % gm_target_version = 1.1
> 
> could evoke a warning in the dialog, if the user was using 0.8 for example 
> 'Template intended for GNUmed 1.1 and higher. Use at your own risk.'

Two thoughts:

- not all template types will easily embed (or emit upon request) such strings
- while technically fairly sound this to me seems too elaborate a
  scheme to implement for a so-far-non-problem

Karsten
-- 
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346



reply via email to

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