On Jul 29, 2008, at 7:11 PM, Nate Lowrie wrote:
> That's not the point. I know I won't be able to instantiate an object
> until I run app.setup(). However, I expected to be able to create the
> class. I could manually define my own dOkCancelDialog and have it
> loaded at runtime. It seemed natural to be able to do the same with
> cdxml dialogs. If I have a library that creates a class for a cdxml
> on init and stores the class definition as package variable, does that
> grind so much with the framework that it absolutely makes no sense to
> implement it?
It would be nice if we could say "cdxml == Python class", but I tried
that route many times before settling on the current system.
In your case, it would be wiser to create a module-level method that
returns an instance of the dialog class; so instead of:
dlg = MyCdxmlDialog()
...you'd use:
dlg = module.getCdxmlDialog()
-- 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]
