Re: [Gnumed-devel] plugin framework

[Karsten Hilbert]

self-replying, but here goes:

> That would be good. But the question was why there is
> *plugin* code in *wxpython/gmDemographics.py* ?
> 
> > IMHO it should be moved back and wxpython/gmDemographics.py should be 
> > retired.
> IMHO, no. Most of the time IMO it makes sense to split
> plugins like this:
However, if people prefer it'd be useful to first consolidate
wxpython/gmDemographics.py and wxpython/gui/gmDemographics.py
into *one* file, let it settle down, and then split again as
described.

> >  (the original intention was that plugins be fairly self-contained)
> They would still be, in a way. The self-containedness need not be
> physically but semantically, eg. loading gmLabJournal.py
> shouldn't require any other plugin to be loaded.
And for the record: gmLabJournal.py doesn't, even now.

> > It references the clinical window manager as our [Richard's and my] 
> > intention was that all
> > patient-related stuff (including demographics) went into this super-plugin.
> Aha but is there any *use* of the connection right now ?
Eg, can we break it ? Also, I'd like to break the ugly direct
connection between the top panel and "the demographic plugin".

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