From: Alex T. <al...@tw...> - 2005-07-05 22:10:38
|
kim...@ya... wrote: >I don't know whether this is true or not with other >Python GUI toolkits (I only know PythonCard) but I >find PythonCard extremely easy to handle situations >where you have a number of user interfaces that are >quite similar and yet each one has it's own subtleties >that needs its own code. > >For instance, with the application I am developing, I >have many situations like that. So, what I did was to >define a super-class for all of the similar GUIs. >Then I have one file (module) for each of the GUIs, >and subclass them from the super-class. This way, I >can have a resource file for each of them, and yet >share lots of the common action code as long as I >structured the code accordingly. > > > If you have an example of that you'd be willing to share, I'd love to see it (preferably the code etc. , not just a description, please). >I really like PythonCard. The only gripe I have is >the lack of more detailed documentations, like which >control supports which method and so forth - the >existing documentation needs a lot of improvement. I >had to spend a lot of time looking through code before >I can figure out how to do certain things. > > > Did you look at the html files created from the "widgets" sample ? Is there more detail that you need, or something missing from there ? (that's for the first part about details of which controls support which methods; I agree more documentation would be good - though I really like looking at the samples to see how things are done. Given a choice of a certain level of effort in writing docs vs. extending samples to give more coverage, I'd put the hours of effort into more examples ...) -- Alex Tweedly http://www.tweedly.net -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.8.8/37 - Release Date: 01/07/2005 |