On Aug 22, 2008, at 11:30 PM, Paul McNett wrote:
> The thing that got me thinking along these lines is that dPageFrame
> and
> DPageFrame exist for the same purpose. The main difference is that
> DPageFrame is more feature-rich, while dPageFrame is platform-
> native. So
> there's a tradeoff to choosing one or the other, but they are
> fundamentally the same thing.
Same is true for dPageList, dPageSelect, dPageFrameNoTabs
>> Imagine you are new to the framework, and see dPageFrame and
>> DPageFrame. How does that help you understand why you would use one
>> vs. the other?
>
> It would make me wonder, but hopefully the docstrings for each class
> would help me decide.
Why create the potential confusion in the first place?
My original objection was based on the fact that 'dPageFrameAdvanced'
or 'dStyledPageFrame' didn't indicate clearly enough the advantages in
selecting that class over other paged controls. I hardly think that
'DPageFrame' is an improvement.
>> I also think that if it is meant to be used by developers, then it
>> deserves the lower-case 'd' up front, just like dSlideControl and
>> dDockForm.
>
> 'd' and 'D' are the same letter.
<sarcasm> Really? I hadn't noticed! </sarcasm>
Of course they are, which is why I detest distinguishing radically
different classes by spelling them exactly the same but changing the
case of one letter, and in the meantime muddying our already unusual
naming conventions.
Hey, let's rename all our paged controls as follows:
dPageFrame
DPageFrame
dPageframe
dpageFrame
Don't worry if that looks confusing; the docstrings will clear it all
up!
My point was that both dSlideControl and dDockForm are both non-
native, "owner-drawn" classes, yet we expose them as regular Dabo base
classes and use the lower-case 'd'. I don't recall any objections to
including non-native controls at the time, nor do I recall any
suggestion that we need to name them so as to warn developers that
these are non-native controls.
> Do you have other suggestions?
Yes: just what I originally asked for. Find a name that better
describes what differentiates this class from the native paged control
than 'advanced'. 'Styled' is a step in the right direction, but IMO is
way too vague. I think we can do better.
-- Ed Leafe
_______________________________________________
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]
