Ed Leafe wrote:
On Jun 6, 2006, at 1:52 PM, Paul McNett wrote:
No, it wouldn't. You'd be saving your design in the cdxml file, but
importing from the equivilent of CLASSTEXT.py. So, you change your
design, re-run the cdxml->py conversion, and voila, your modified
design is live next time you run your app.
You're missing the main thing: editing the code! The whole point is
to be able to use Wing or emacs or vim or whatever is your favorite tool
to edit the code after the Class Designer visually creates the UI. Once
you've edited the code, re-generating a modified UI design will require
cut/paste of your modified code into the appropriate places.
You would edit a subclass of the CD-generated .py file. You would use CD
to edit the design, and Wing or vi or whatever to edit the subclass
which is where the bulk of your code would be.
1) Class Designer:
+ lay out your design, and save it as a .cdxml
2) Converter:
+ input is .cdxml, output is a throwaway .py file
3) Whatever editor you want:
+ create a .py file that imports the output from #2
We are at a point with Dabo that we could almost attract some of those
types of developers that 'do it all in code', but we are kind of far
away from attracting the VB-types still.
Agreed. That's why we need to keep focused on the overall goal, and
not be distracted by individual requests.
I don't think I'm being distracted by a request (as far as I see nobody
has requested that we do anything in particular). I'm proposing a
temporary solution that would allow more people to get running with Dabo
now. Indeed, if this works it could have the effect of getting *me*
using the Class Designer instead of laying out my designs by hand like
I'm doing now.
If we can make it so designs can be edited visually, but people can
still use whatever editor or IDE or debugger they like, then even if
that is a temporary solution it is better if it attracts people like
Alex and makes them want to invest more time into developing apps with
Dabo.
While having more people working with Dabo is always a good thing,
right now I would love to see more people interested in developing Dabo,
too. As you've pointed out, we have a lot of work to do, and it would be
great if we could get people to contribute towards that instead of
diverting efforts to tangential projects.
Having people using Dabo is almost a prerequisite for having people
developing Dabo.
--
Paul McNett
http://paulmcnett.com
http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
