Nate Lowrie wrote: > Paul McNett wrote: >> Nate Lowrie wrote: >>> Ed and Paul, is the TabPosition property not support right and left is >>> going to be a problem for inclusion into trunk as dPageFrame? If so, did >>> you just want to rename this class? >> -1 on replacing wx.NoteBook with FlatNotebook. FlatNotebook is >> owner-drawn, while wx.Notebook is platform-native. >> >> +1 on including it as a different class, though. > > So, +1 to include it as a different class? I need some of the > advanced functionality it offers so that's why I am doing the change. > Ideas for a name? dAdvancedPageFrame comes to mind. Not sure why > they call it FlatNotebook in the first place...
Here's an idea out of left field that I expect will get shot down, which is fine. It seems that in this case we have a native dPageFrame and an owner-drawn dPageFrame, that are basically serving the same need but there are pros and cons to each. So coming up with a completely different name is unfortunate. So I started thinking what we could do to indicate the difference but with the same fundamental name. And I came up with: dPageFrame : the native one based on wx.Notebook DPageFrame : the advanced non-native one based on FlatNotebook. This idea could be applied everywhere: lower 'd' when it is the default Dabo native implementation, and capital 'D' to denote advanced or non-native functionality. Okay, give me three seconds to duck before you start throwing out the pies... 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]
