On Dec 11, 2006, at 12:48 PM, Paul McNett wrote:
> Again, this sounds like a job for subclassing and/or mixins like you
> suggested. I really don't get it: If you are going to modify Dabo and
> not submit a patch for the improvement, then you shouldn't modify Dabo
> but modify your subclass.
Because it isn't an improvement per se; it might just be a
preference or a client requirement. A lame example might be if you
wanted all your apps to default to Helvetica Bold 24 for the
controls, because that's the corporate standard (lots of old folks,
y'know). Why would you submit that as an improvement?
> Why would people expect the framework to
> provide this layer when they can just do it themselves?
Because it isn't that simple. In the example above, how would I do
that for the dColumn class, so that every grid, both that I created
and that is created by the framework, uses that font? And still be
able to 'svn up' without worrying?
It is a perfectly valid design solution for these concerns. Lots of
Codebook developers took advantage of it during my years as librarian
of that framework. But while it was a great solution for VFP, it is
not at all ideal for Python. Mixins just work so much better, IMO.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
