[Gnumed-devel] disentangling gmDemographics.py-guidelines for future modules

[Horst Herb]

I am just in the process of hooking gmDemographics.py up to the backend.
I fail to understand the philosophy behind it.

The gmDemographics plugin extends the top line of the tool bar - so far so 
good. Would have been nicer to implement it as an independent panel which is 
the added to the toolbar as a whole, but that can still be done. 

But then - how dare the "PatientPanel" grab hold of the plugin and set up 
event handlers for it? Never! This is akin with using global variables.

Each GUI panel must be a self sufficient black box, communicating with other 
panels ONLY via messages or with the main process via the broker objects. 
Always.

In the current example the plugin must set up wx event handlers for the 
"search" event, and the post a message "gmSignals.PatientSelected()" via the 
dispatcher. How else should other GUI elements get notice that something that 
they are concerned with has changed?

Please read the relevant online documentation at 
http://gnumed.net/whitepapers/messenging.html
and
http://gnumed.net/whitepapers/signals.html

Horst
---
[This E-mail scanned for viruses by SURFSIDE INTERNET]