On 12/19/06, Carl Karsten <[EMAIL PROTECTED]> wrote: > Paul McNett wrote: > > Carl Karsten wrote: > >> Paul McNett wrote: > >>> Carl Karsten wrote: > >>>> I am also guessing I will enjoy coding new AZ code to create .cdxml > >>>> files that > >>>> look like the DataNav? stuff it currently creates. have you or started > >>>> down > >>>> that path and run into snags? > >>> Please try to get something working. It really shouldn't be *that* > >>> difficult. > >> What sort of somethings are you referring to? > > > > I believe you snipped out the context, but maybe I did. I meant tweaking > > your appwizard output to load in a CD-designed cdxml of a panel that > > contains the widgets for your edit page. > > > > > >> I have a functioning "Products Form" that should be just fine. I have a > >> "Events" Form that needs to be made pretty, and moving things around by > >> changing > >> py source code doesn't seem as efficient as using the Class Designer to > >> make an > >> cdxml. > >> > >> The cdxml concept seems like something worth investing time in. > > > > Yes, I agree, but it is still in active development and thus unstable. > > Those of us that need to get projects out *now* need to code the UI by > > hand, and will probably need to for the foreseeable future. And the > > truth is, I've always had a soft spot for coding by hand. > > > > With Python, it actually isn't as inefficient as one might think it > > would be to code the UI by hand (and you get a much better feel for what > > is going on).
Well said. When I came from C++, Python syntax and code looked remarkably like the psuedo code I wrote for C++. It really is high level and easy to do. And remember, Practice makes perfect........ > > I pretty much have no idea what is going on when I tried to edit by hand. It > was more of a "lets see what this does?" run, cringe, repeat. > > > The edit/test cycle is really very fast if you set up your > > environment properly: > > > > 3 terminal windows: 1 for interacting with Python directly, 1 for > > navigating the filesystem to locate the files to edit, 1 for running the > > module you are working on for testing. > > > > 1 editor window with multiple tabs for editing multiple source files. > > sounds like SPE, which I love in spite of its isms. :) SPE is nice, but I prefer to do something similar to what Paul does. 3 Bash windows and TextMate (Emacs, Vi, BBedit, etc.) is a lot more stable and faster than SPE. I find that it often would get bogged down with over a dozen tabs open. > > > > > > Alt+Tabbing back and forth, editing and running. Don't launch the entire > > app when you are working on the design of the edit page for your Events > > form. Write testing code in a 'if __name__=="__main__"' block to just > > instantiate the panel in a raw form. > > That is a good idea. > > > > > Less mousing, more keyboarding works the best for me. But I do concede > > that our "target" market is probably 99% against me here. > > I would have to disagree. I think that more people hand code Dabo UI stuff than you think. This should increase as more WxPython developers make the switch to Dabo. As far as I see it, you have VFP developers, which are visual developers, and you have people coming from other Python modules which generally prefer to hand code. > > We need to stop coding and do more market research. or maybe the other way > around. I get those two mixed up all the time. > > Carl K > > _______________________________________________ > Post Messages to: Dabo-users@leafe.com > Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users > _______________________________________________ Post Messages to: Dabo-users@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
