>Like all frameworks there are issues. Mostly, stuff that I don't use. There is a WYSISWYG designer that I haven't used in many years. Don't use the command line debugger very often. Then there is the issue of keeping up with the changes in python and wxPython. There are other issues but I'll say that I am more productive with Dabo than I ever was with FoxPro.
>Johnf

It's exactly the wizzy wig designers that need to be redesigned to keep up the changes in python and wx (and wxPython). I once managed to use one of them and concluded that I don't need them. That was three years ago. I don't need that kind of thing with the proportional method of assigning space to controls, that wx uses. It doesn't care about any damn pixels, it just calculates the proportion of space to give them, and you can just set the proportion at will for any group of controls at some level (and yup, it's nested, it's all containers in containers, under different names). Never looked back.

Actually I was disappointed (weird, I wasn't appointed first) when I saw that everybody went the M$ way and denounced foxels in favor of pixels. And since then we had to invent various resizing acrobatics and whatnot. Had there been the decision to go with foxels and generally the vector graphics way, we could have saved ourselves months of work over the years. But no, M$ loves pixels, so redo all the graphic stuff every few years, because monitors have grown.