gnumed-devel
[Top][All Lists]
Advanced

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

Re: [Gnumed-devel] switchable layout managers


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] switchable layout managers
Date: Mon, 19 Jul 2004 12:41:52 +0200
User-agent: Mutt/1.3.22.1i

> We (Karsten and I) have accepted that layout should be done with 
> a dedicated layout class ("inner frame") loaded from gmGuiMain (which still 
> controls the outer
> frame and the top toolbars) ]
ACK.

> Well, do we really need plugin wrappers at all?
> All the layout managers need is a list of widget classes to load.
But the various layout managers may have different ways to
access/signal the plugins. That is where the wrappers come
in, they mediate between what the layout manager thinks it
wants to do and what the non-plugin widget code (in wxpython/)
does.

> The tab label can be inferred from __class__.__name__
> so if asked to load  Gnumed.wxpython.gmContactsWidget.Contacts
> we know to call it "Contacts". "_" should be mapped to space,
> so we have Gnumed.wxpython.gmDemographics.Patient_Details
Sure, if "your" layout manager wants to do it that way, fine.
That shouldn't affect "my" layout manager, however. Else we'd
not need to try and separate them.

> These still behave as "plugins" in that someone can write a single file which 
> can be 
> dropped into the tree and will work as a loadable module.
If you do that you forego the ability to reuse the functional
GUI part in custom clients by hardcoding the assumption that
this functional part of the GUI is a layout manager plugin, or
even a notebook plugin. Again, the *functional* part couldn't
care less whether it's instantiated in a plugin wrapper or in
a simple standalone frame or whatever.

> The Terry layout would look under client/bitmaps to see if an icon exists
> of the same name, if it does, fine, if not use the label as above.
>
> For placement the Terry widget may have two lists on the configuration 
> backend (one for the notebook,
> one for the sidebar) or it could examine the widgets ancestry (if it descends 
> from gmSidebarWidget, it goes in the 
> sidebar)
Sure, see above. "Your" layout manager may do as it pleases.

One thing, can you post a screenshot ? I am not convinced that
I understand the look of "your" layout manager. Are we sure
Richard agrees that that is what he intended ?

> This would end the practice of loading every widget in the directory,
Huh ? How ?

> instead a default list (for the locale) would be preloaded in the backend
This makes a lot of sense, we just haven't gotten around to it.

> This is good as we can purposely leave broken widgets off the list,
> until they get fixed.
As they are now automatically. I agree, however, that the
get_plugin_load_list tries to be overly smart (my fault). I
will fix that.

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]