Alex Tweedly wrote:
I'd be unhappy about the extra step of cdxml -> py conversion - I'd be
bound to forget it, or find it annoying enough that I was less likely
to change the UI when I should.
It could certainly be automatic; if the tool generates both, it could
keep them in sync.
What I was thinking of (and I repeat this is a stop-gap until CD
becomes a fully-capable IDE) was something like
write my code just as I would today as "pure api" - but omitting the
part that would create and layout out the API
add a call to a new lib function read and layout the cdxml file
- it creates the controls and sizers as needed
and the rest of the code then works just like today.
That's exactly what XRC gives you, with the ability to load all or part
of an XRC file. Very roughly: XRCed = CD, .xrc = .cdxml. I'm not
promoting XRC here, but pointing to it as a proof of existence and
usability. I use XRCed in this fashion today, and look forward to using
the Dabo tools when I can afford the learning curve. (And with Eli
Golovinsky's additions, as I mentioned in another message, the common
"idioms" to load the XML file and connect to its components disappear
under the covers.)
--
Don Dwiggins
Advanced Publishing Technology
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
