[Gnumed-devel] disappointing

[syan tan]

with respect to bugs , they usually get debugged over time. At the 
moment, usability bugs might be off a concern, but the
logic is pretty simple ( just store names and cross references, and use 
the cursor description, and move back and forth between
names for widgets vs names for tables, fields and references. The only 
naming dependency is that table have a non-composite
primary key called id, references are named id_xxxxx where xxx is the 
referenced table, and the single named target table is at
the top of the reference tree. one-to-many relationships aren't handled 
yet .  If you try it , it is logical and simple ( and probably
has been done many times before , but IT people would like you to 
believe it is more complicated than that).

e.g ironing out bugs -  gmPG lost connections upto a few months ago.

I probably didn't expect the edit area to  be accepted; but you can 
knock up a quick prototype for a
ehr with it , and it stores and retrieves data. 

Wrt to a pretty interface, that wouldn't be hard if you store the  
widget construction requests in a list, and place them in
a good template container for the original edit area.  I give all credit 
to Richard for the simplicity of the design, which is
why you can write a simple tool for its generation.