Nate Lowrie wrote:
> On Wed, Aug 13, 2008 at 2:20 PM, Paul McNett <[EMAIL PROTECTED]> wrote:
>> 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.
> 
> It is unfortunate.  This wouldn't be an issue if FlatNotebook
> supported left and right tab positions...

It would still be an issue, because of the non-platform-nativeness of 
FlatNotebook. One of the major reasons we chose wxPython over say PyQt 
was that wxPython instantiates platform-native widgets on each target 
platform.


>> 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.
> 
> You know, one could argue that FlatNotebook is native since it is
> included in the WxPython distro...

ui-toolkit native, yes. Platform-native, no.

>> 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.
> 
> This is fine and dandy, but you will have to rename a bunch of
> controls to use the new scheme...dLed, dHtmlBox, dSpinner, dHyperLink,
> dLinePlot, and dEditor come to mind, as well as the Dock classes.
> They are all non-native.

I realize that we'd end up renaming some stuff, which is messy.


>> Okay, give me three seconds to duck before you start throwing out the
>> pies...
> 
> I like to eat my pies...

Cool.

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]

Reply via email to