On 3/20/11 9:16 AM, John Fabiani wrote: > On Sunday, March 20, 2011 08:57:53 am Paul McNett wrote: >> On 3/20/11 8:38 AM, John Fabiani wrote: >>> I noted that dPemMixin has several areas where code ties it to wxPython. >>> dMenuBar, dMenuItem, dMenu, dSlidePanelControl, DToggleButton come up. I >>> wonder why there are any strictly wx areas of code in property mixin? >>> Will it not make adding other GUI frameworks harder. >> >> dPemMixin is the main wx mixin. There are all kinds of ties to wx, because >> it is the main place where we wrap wx. >> >> Paul > > Ok and thanks. I'm not sure where I'm going with this. It's just I see dMenu, > etc.. are going to be called in every GUI framework and dPemMixinBase > (Abstract methods) don't really cover the issues. I guess I'm thinking it > should be more like dBizobj that calls back ends and all the methods are > Abstract.
I think you are touching on a major refactor I want to do to the ui layer. I've been thinking about it for years, and it would simplify much but put extra burden on developers to follow some extra rules when they change anything in the ui interface. Like my last response, it'll make sense to undertake this once we start working on another UI toolkit. It'll be worth it in the end but a big commitment to get there. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
