[Top][All Lists]

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

Re: [Gnumed-devel] Busy Cursor Thanks + Q re missing GUI elements

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Busy Cursor Thanks + Q re missing GUI elements
Date: Tue, 3 Aug 2004 19:55:17 +0200
User-agent: Mutt/

> > 2)Note that when gnumed boots up that the clinical sections such as 
> > vaccinations/allergies now have own tabs on the bottom, wheras design wise 
> > they shouldn't appear until the clinical tab is clicked on, and then be 
> > linked to buttons on the top tool bar, not tabs on the bottom.
> I really disagree here, as this slows down navigating the interface
> (click at the bottom on "clinical", then click again up top to select
> the clinical widget -- 2 clicks too many)
The "clinical" tab is likely to go away and/or be replaced by
a "patient summary" tab. Reason being that it is the widget
encapsulating the Richard space design ideas. Those will be
factored out into the Richard space layout manager - which is
XOR to the Horst space layout manager.

> Also we are unable to formulate or enforce any rule about where
> (clinical/toplevel) widgets should go: result total confusion, new
> users will have to memorise an arbitrary system for where widgets go.
No. In Horst space tabs will encapsulate some meaningful
snippet of clinical relevance. The label should clearly
express what sort of things to expect on that tab.

> Remember the list of modules loaded is user dependent: so a secretary
> logging in will get demographics, billing, recalls etc., a doctor
> will get all the clinical ones, and the adminstrator will
> (in the fullness of time) modules for user account management etc,
> so we already have separate clients in that sense.
Right on ! And they can even have fairly arbitrary inner-frame
layouts due to the current refactoring (which should IMO be
the last big thing before finishing the more boring parts of

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]