Comments on: Writing multi-threaded GUIs http://projects.haskell.org/gtk2hs/archives/2005/07/24/writing-multi-threaded-guis/ A GUI Library for Haskell based on Gtk Wed, 22 May 2013 01:36:59 +0000 http://wordpress.org/?v=2.5.1 By: Duncan http://projects.haskell.org/gtk2hs/archives/2005/07/24/writing-multi-threaded-guis/#comment-27 Duncan Mon, 25 Jul 2005 16:48:44 +0000 http://haskell.org/gtk2hs/?p=38#comment-27 That is true, we could drive the Gtk+ main loop from within Haskell. I was about to say that this would still mean having to use polling, however by breaking the Gtk+ main loop into phases it would allow us to get at the set of file descriptors that Gtk+ is waiting on. In which case we might be able to do the blocking in Haskell rather than in the Gtk+ loop which would mean the Haskell runtime system would have a complete view of the programs event sources. Thank you for the idea. I'll certainly investigate it. :-) That is true, we could drive the Gtk+ main loop from within Haskell. I was about to say that this would still mean having to use polling, however by breaking the Gtk+ main loop into phases it would allow us to get at the set of file descriptors that Gtk+ is waiting on. In which case we might be able to do the blocking in Haskell rather than in the Gtk+ loop which would mean the Haskell runtime system would have a complete view of the programs event sources.

Thank you for the idea. I’ll certainly investigate it. :-)

]]> By: Antti-Juhani Kaijanaho http://projects.haskell.org/gtk2hs/archives/2005/07/24/writing-multi-threaded-guis/#comment-26 Antti-Juhani Kaijanaho Mon, 25 Jul 2005 16:21:56 +0000 http://haskell.org/gtk2hs/?p=38#comment-26 Gtk+2 makes it possible to "deconstruct" its main loop and to drive it from outside of Gtk+. Any reason that's not used instead of this clever but a bit hackish solution? Gtk+2 makes it possible to “deconstruct” its main loop and to drive it from outside of Gtk+. Any reason that’s not used instead of this clever but a bit hackish solution?

]]>