On Jun 5, 2007, at 3:58 PM, Paul McNett wrote:
> Thanks to Dabo's modularity, I don't see any reason why I can't build
> out new features using cdxml while keeping my hand-coded classes
> around,
> too. Actually, Ed, would that work? Say I have a set of base classes
> done in raw Python/Dabo. Could I make subclasses/instances of those in
> the Class Designer, saved as cdxml, or is that a pipedream?
That's something that I'm working on now. So no, you can't do it
now, since the Class Designer only works with dabo.ui classes and
imported cdxml classes. But I'm adding support for designing Wizards
in the Class Designer, and these are not dabo.ui classes, so an
import mechanism is required. This should be done either later today
or tomorrow. After that, I planned on doing just what you suggest:
import a coded class into the Class Designer.
> What about the inverse (coded subclasses of cdxml classes)?
That would be tougher, since you're in Python-land, not Dabo-land
here. Think about it: the class definition statement requires:
class MySubclass(MySuperclass):
...and 'MySuperclass' needs to be in the namespace at that point. It
may certainly be possible to achieve this, but we'll need a home-
grown alternative to 'import' in order to add cdxml-defined classes
to the current namespace.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
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/dabo-dev/[EMAIL PROTECTED]
