Michael Palmer wrote:
So far, development of PyGUI seems to be a one-man effort, and it may be slowed down by the attempt to develop the API and the implementations concurrently. Could it be useful to uncouple the two, such that the API would be specified ahead of the implementation?
I'm not sure that would work very well. I don't think it's possible to invent a good API for something as complex as a GUI toolkit in the absence of experience using it, so the API has to evolve in parallel with at least one implementation, and with real applications that actually use the features concerned. Also, the features that go into the PyGUI API are partly determined by what is available in the underlying target libraries. I don't want to end up with things in the API specification that are too difficult or unwieldy to implement on some of the target platforms. I also don't want one implementation to get too far ahead of the others, for the same reason. If anyone wants to help, what's needed most right now is a good native Windows implementation. One or two people claimed to be working on that some time ago, but I haven't heard from them recently. For the reasons I mentioned above, I'm reluctant to forge ahead with too many new features until a native Windows version exists. -- Greg -- http://mail.python.org/mailman/listinfo/python-list
