Alex Tweedly wrote:
Paul McNett wrote:
Comments on this idea?
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.
Processes like this can be automated. Eventually (I know, promises
promises!) we'll have a project manager with a 'build' function that
will be smart enough to 'compile' the cdxml files into the throwaway .py
files, so that you have them in the right place at runtime. For now, we
could just tweak the CD to optionally convert them every time you save
the .cdxml.
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.
There's a lot of handwaving there, but I think it's not too hard,
especially borrowing chunks of code from ClassDesigner - give me a day
or two to see if bears fruit (or if I need to ask more questions.
I'm interested to see what you come up with, but conceptually I think my
idea is much more straightforward.
--
Paul McNett
http://paulmcnett.com
http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
