Re: [Gnumed-devel] GNUmed plugin development - part 7

[Karsten Hilbert]

On Thu, Apr 09, 2009 at 04:02:01PM +0200, Hilbert, Sebastian wrote:

> in gmCardiacDevicePlugin.py tells me that in the case of the Document archive 
> plugin we borrowed from the class cSelectablySortedDocTreePnl is located in 
> the file gmMedDocWidgets. The name implies that this is a collection of 
> classes of medical document widgets. The device parameters are essentially 
> measurements.
> 
> There is a file called gmMeasurementWidgets available and I am going to 
> extend 
> that one.
That reasoning makes sense.

> I added a class cCardiacDeviceMeasurementsPnl to the file 
It is usually helpful to name the GNUmed class extending the
wxg Class the same except for the wxg -> c prefix, so
"cCardiacDevicePluginPnl" would be more consistent.

One reason being that you might later want to have a class
cCardiacDeviceMeasurementsPnl which really only holds the
measurements and not concern itself with other things also
related to cardiac devices. Then you are in a quagmire.

> If you followed the above steps you might notice that the plugin throws many 
> errors in the file gnumed.log. This file can be viewed directly from within 
> GNUmed. It does not show up. The reason is simple. I use a complex set of 
> widgets that are scattered across the files gmMeasurementWidgets and 
> gmNarrativeWidgets.
> 
> The errors are that widgets found in gmNarrativeWidgets are not found, most 
> likely because I put the class cCardiacDeviceMeasurementsPnl(parent, -1) in 
> gmMeasurementWidgets. It could help to move the class into narrative widgets 
> but that is not what I want. I could as well start another file called 
> gmDeviceWidgets.
> 
> Any help is appreciated.
You need to

a) think about which classes you really need from gmNarrativeWidgets.py
b) then add relevant import statements

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