Re: [Gnumed-devel] SOAP2.py questions from Richard

[Karsten Hilbert]

> This is certainly coming on well. Almost useable !
But it does not work on wxPython 2.4. Unless we don't want a
SOAP control in 0.1 this will not help us.

>  - the SOAP control will always be visible on the screen - it is akin to your 
> paper page you are writing on on your desk. The  OK.CLEAR buttons when 
> clicked needs to drop the contents of the SOAP control onto the progress 
> notes list underneath. 
Well, the SOAP control itself won't care what callers of it do
with the information it delivers. If the user clicks OK it
should just emit a dict keyed by section that contains the
information entered into it. Whether the caller drops that
into some list or writes it to the database or generates a
song from it is of no concern.

One thing I am wondering about is: How are we intended to deal
with data having been typed into a functional popup ? Eg.
imagine the user incantates the magic string that pops up the
vaccinations control. After completing that control the user
clicks OK. What happens next ? One thing is that we do want to
drop a quick note about the vaccination into the SOAP widget.
OTOH, we would also want to store the vaccination details into
the database. Do we do this immediately when OKing the
vaccinations popup ? If so how do we handle the case when the
user CANCELs the master SOAP control ? If not where do we keep
that information around and until when ?

Getting this right is just as important as making it visually
useful.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346