<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Writing multi-threaded GUIs</title>
	<link>http://haskell.org/gtk2hs/archives/2005/07/24/writing-multi-threaded-guis/</link>
	<description>A GUI Library for Haskell based on Gtk</description>
	<pubDate>Fri, 29 Aug 2008 06:24:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Duncan</title>
		<link>http://haskell.org/gtk2hs/archives/2005/07/24/writing-multi-threaded-guis/#comment-27</link>
		<pubDate>Mon, 25 Jul 2005 16:48:44 +0000</pubDate>
		<guid>http://haskell.org/gtk2hs/archives/2005/07/24/writing-multi-threaded-guis/#comment-27</guid>
					<description>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. :-)</description>
		<content:encoded><![CDATA[<p>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.</p>
<p>Thank you for the idea. I&#8217;ll certainly investigate it. <img src='http://haskell.org/gtk2hs/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Antti-Juhani Kaijanaho</title>
		<link>http://haskell.org/gtk2hs/archives/2005/07/24/writing-multi-threaded-guis/#comment-26</link>
		<pubDate>Mon, 25 Jul 2005 16:21:56 +0000</pubDate>
		<guid>http://haskell.org/gtk2hs/archives/2005/07/24/writing-multi-threaded-guis/#comment-26</guid>
					<description>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?</description>
		<content:encoded><![CDATA[<p>Gtk+2 makes it possible to &#8220;deconstruct&#8221; its main loop and to drive it from outside of Gtk+.  Any reason that&#8217;s not used instead of this clever but a bit hackish solution?
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
