[Gnumed-devel] How GNUmed handles form templates

[Jim Busser]

On 2010-01-07, at 5:11 PM, Jim Busser wrote

        (on gnumed-bugs as

        Re: [Gnumed-bugs] <bug>: 0.6.rc3 still no luck printing meds

> after I tried to correct this by instead setting the master dat (form) to
> 
>       
> /home/jbusser/gm/cvs/gnumed/gnumed/server/sql/v11-v12/data/GNUmed-default_medication_list_template.tex

when a user would make a change to a master data (for example as I did above on 
the public db) I am having trouble understanding why --- if the above is a 
master change that would affect all users, from all workplaces --- it is any 
good idea since the gnumed middleware or backend would have to be permissioned 
at the OS level to read this file if an attempt were made to print from any 
other machine system level user

also, as soon as I would disconnect my drive from the system, other users would 
be unable to access the file, and would get an error

unless...

1) the above changes affect only the gnumed account of the logged in user (in 
this case Leonard McCoy any-doc)
… however there would still come a problem anytime this user would do GNUmed 
login and try to print from any other machine at a time that the hosting 
machine (machine that hosts the form template) would be disconnected or asleep

or

2) the above file reference simply records the *origin* of a file which -- as 
part of the Save -- get also *copied* into the GNUmed postgres database

??