Peter Damoc wrote:
It's not just you, GUI designers can be a true pain in the ass sometimes and indeed for simple things can really slow you down BUT
for complex layouts they can prove to be a very good thing.
Actually, I think complex layouts are where they break down. I've never
seen a GUI designer that did not discourage the user from creating and
using custom controls. You are hard pressed to have a complex design
that does not group controls in a way that they could best joined into
a single class, and used that way.
Or a better example, the doctor comes and tells me that he wants a
tooltip on all the textfields, doing that from a GUI designer was a
very very easy BUT if I would have had to do it by hand...
You're kidding, right? You'd rather point and click at 50 text fields
than do a search and replace in a text editor? Bulk changes are EXACTLY
why you want code, rather than a point and clicky thing.
Sure you can do it by hand, sure is cleaner than a generated code,
sure it can even be optimised and if you are an expert you could be
faster, more efficient NOT using a GUI designer BUT for a begginer,
a GUI designer means discoverable features and that is something I
think should be the norm.
A good ide should have integrated help, etc, to help with this. However, I think you're seeing the classic conflict between "usability" and what I like to call "learn-to-usability". Marketing needs require focus on learn-to-usability, but if you sacrifice true, long-term productivity for easy of learning to use, you'll end up with a toy.
By the way, Peter, why start from scratch? I fail to see how your goals differ substantially from those of Dabo, Pythoncard, and Wax (or PyGUI, if you're really going to start from scratch)
-Chris