On Sunday, March 20, 2011 09:01:01 am Ed Leafe wrote: > On Mar 20, 2011, at 11:57 AM, Paul McNett 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. > > Also, dabo.ui.dPemMixinBase is where base mixin properties that are not > ui-toolkit-specific are handled. If we ever undertake wrapping another > toolkit, those properties that are not wx-specific will probably be > refactored up into this base class. > > > -- Ed Leafe
As I said earlier I'm not real sure where I going with this - But I think you are expressing what I was trying to say. The fact is we have defined many GUI properties as Dabo properties means at some point they will have to go into dPemMixinBase and later call the GUI dPemMixin. Right? Johnf _______________________________________________ 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]
