On Wed, 2011-07-20 at 11:59 +0200, Thomas Jollans wrote: > On 20/07/11 04:12, sturlamolden wrote: > > 5. No particular GUI thread synchronization is needed -- Python has a > > GIL. > That's where you're wrong: the GIL is not a feature of Python. It is an > unfortunate implementation detail of current versions of CPython. (and > PyPy, apparently)
And this GIL is certainly *not* a synchronization solution. Even with a GIL you can hang yourself with threads - I've verified this. :) > > 6. Expose the event loop to Python. > You can tap into the Gtk/GLib event loop. +1 > What do you propose? We know what happens when you write a fresh GUI > toolkit: Swing and Tkinter show us. > The only reasonable option to create a toolkit that actually looks good > is to base it on the "usual" GUI libraries. +1 > It is perfectly reasonable to be required to manually call some sort of > > Is it worth the hassle to start a new GUI toolkit project? > No. +1, or -1, errr.. which ever one means I agree with "no". > > Or should modern deskop apps be written with something completely > > different, such as HTML5 > NO!! Barf. Of course, Gtk [at least experimentally] supports an HTML5 canvas. A good UI library provides a lot beyond painting-the-screen (there are events, and packing/geometry, etc...). So even if you use HTML5 you are then going to lay something on top of that [JavaScript + JQuery...]. > Don't be silly. Even using a crappy windowing toolkit is a lot simpler > than doing the HTML/JavaScript/HTTP/etc dance. +1 -- http://mail.python.org/mailman/listinfo/python-list