On Dec 19, 2006, at 9:02 AM, Carl Karsten wrote:
> ok, I have an idea. I don't like the idea, but it somehow seems it
> might be
> better, given the amount of functionality that is *only*? in the
> datanav
> classes: make a copy of the code that instantiates classes based
> on the .cdxml,
> and instead of instantiate, write out some py source code that
> could be injected
> into a datanav form.
IMO that's a band-aid approach. The whole datanav/appwiz design
needs to be overhauled, similar to what we did when we moved from
field specs to py code. And I don't recommend doing that until the
Class Designer and related programs are mature enough to handle
anything we can throw at it. I've spent the last few days trying to
get the DesignerXMLConverter class to be able to handle individual
page classes and making them work in a pageframe transparently at
both design time and run time. This and a mess of other such issues
need to be addressed and solved before we start dicking around with
integrating datanav and cdxml.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
