Linked by Thom Holwerda on Wed 13th Jul 2005 14:00 UTC, submitted by Timothy R. Butler
Permalink for comment 3795
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
Linked by Thom Holwerda on 05/15/13 23:03 UTC
More News »
Sponsored Links



Member since:
2005-07-06
> PyQT/PyKDE exist, but don't have ample documentation.
Err... PyQt/PyKDE only need a few pages of documentation because for the most parts, they work just like the C++ equivalents and developers can just refer to the official Qt doc. C++ is OO, Python is OO, so what do you expect?
Of course, if you are going to write an OO language binding for a non-OO toolkit that pretends to be OO, then you will need a lot of documentation.