Scripting and Gnome and KDE

[ben at co.and.co]

Boudewijn Rempt <boud at rempt.xs4all.nl> wrote:
>>> Absolutely, but I don't know that an essay on the problems is exactly
>>> the right way of introducing the toolkit.
> 
>> That's probably true.  Given the goal of showing how to do non-obvious
>> things with a toolkit, what changes would you recommend?
> 
> Well, I'm not sure I saw any really non-obvious things - a treeview
> isn't that spectacular nowadays, and neither is layout management.

Layout managment was a relief after some MFC experience, and when I made
the mistake of choosing a 22pt default font in licq (Qt plugin), I
started seeing the merits of it. But then again, I'm not a seasoned Qt
developper.

>> it tells the reader how to solve a specific problem, but
>> doesn't provide a general method for discovering how to use other
>> parts of the toolkit.

After reading the tutorial on http://wwww.valdyas.org (hope I get it
right), I wondered how much PyQt and PyGtk resembled each other.
IMVVHO, a general purpose signal/slot-mechanism would be nice addition
to pyton.
 
> Besides, toolkits are different enough that migrating from one to
> another often demands a complete new way of thinking: that's something
> the article in Dr Dobbs did show: tkInter is one way of working,
> PyQt another, but PyGTK is completely different once again. That's
> an important insight, I feel.

There's still a huge problem with the various licences, as they don't
really match Python's license.

Greetings,
-- 
ben . de . rydt at pandora . be ------------------ your comments
http://users.pandora.be/bdr/ ------- inl. IPv6, Linux en Pandora