<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments for Coherent Graphics Ltd</title>
	<atom:link href="http://coherentpdf.com/blog/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://coherentpdf.com/blog</link>
	<description>Ocaml and PDF and suchlike</description>
	<pubDate>Sat, 25 May 2013 21:29:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>Comment on A Proper GUI for OCaml (Part One) by Paolo</title>
		<link>http://coherentpdf.com/blog/?p=4#comment-2</link>
		<dc:creator>Paolo</dc:creator>
		<pubDate>Wed, 19 Mar 2008 21:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://coherentpdf.com/blog/?p=4#comment-2</guid>
		<description>Very interesting! I think OCaml is a wonderful language, but it still lacks in a decent GUI toolkit, something as complete as QT, for example.&lt;br/&gt;&lt;br/&gt;Some time ago I had the idea to link two executables together via socket communication, but I had no more spare time to develop it. I'm glad someone successfully realized a similar project.&lt;br/&gt;&lt;br/&gt;At what level the communication takes place? In my original design a GUI entirely written using QT (C++, Python) talks with an underling OCaml process using DBus. QT actually wraps DBus messages into its signal/slot paradigm, so it should be not too difficult to create the link, since a binding for DBus is available for OCaml.&lt;br/&gt;&lt;br/&gt;In this design no "mouse event" are passed between the two processes, but only high level "signals" have to be passed. In my idea this should simplify the design a lot.</description>
		<content:encoded><![CDATA[<p>Very interesting! I think OCaml is a wonderful language, but it still lacks in a decent GUI toolkit, something as complete as QT, for example.</p>
<p>Some time ago I had the idea to link two executables together via socket communication, but I had no more spare time to develop it. I&#8217;m glad someone successfully realized a similar project.</p>
<p>At what level the communication takes place? In my original design a GUI entirely written using QT (C++, Python) talks with an underling OCaml process using DBus. QT actually wraps DBus messages into its signal/slot paradigm, so it should be not too difficult to create the link, since a binding for DBus is available for OCaml.</p>
<p>In this design no &#8220;mouse event&#8221; are passed between the two processes, but only high level &#8220;signals&#8221; have to be passed. In my idea this should simplify the design a lot.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
