<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Playing with Sheeple-based GUI atop CL-OpenGL</title>
	<atom:link href="http://nklein.com/2009/11/playing-with-sheeple-based-gui-atop-cl-opengl/feed/" rel="self" type="application/rss+xml" />
	<link>http://nklein.com/2009/11/playing-with-sheeple-based-gui-atop-cl-opengl/</link>
	<description>software development and consulting</description>
	<lastBuildDate>Tue, 02 Mar 2010 01:40:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: sykopomp</title>
		<link>http://nklein.com/2009/11/playing-with-sheeple-based-gui-atop-cl-opengl/comment-page-1/#comment-463</link>
		<dc:creator>sykopomp</dc:creator>
		<pubDate>Fri, 20 Nov 2009 07:56:05 +0000</pubDate>
		<guid isPermaLink="false">http://nklein.com/?p=1007#comment-463</guid>
		<description>You might want to look at what I&#039;ve been doing with &lt;a href=&quot;http://github.com/sykopomp/until-it-dies&quot; rel=&quot;nofollow&quot;&gt;Until It Dies&lt;/a&gt;. It&#039;s meant to be more of a 2d game engine, but I wrap a bunch of stuff to make this kind of OpenGL drawing relatively simple (at least as far as I know how to). For fonts, I&#039;m just hooking up to ftgl, which made the process pretty painless, although I&#039;m not sure how great a decision that is in the long run...

You can check out a (right now, extremely bloated) example of how it works &lt;a href=&quot;http://github.com/sykopomp/until-it-dies/blob/master/demo/testgame.lisp&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;.

Anyways, anything having to do with easy-to-use GUIs in lisp sounds like a great idea. I&#039;ve been tempted now and then to try and write something like &lt;a href=&quot;http://www.mike-austin.com/inertia/&quot; rel=&quot;nofollow&quot;&gt;Inertia&lt;/a&gt;, too, which would be quite nice for development in general...</description>
		<content:encoded><![CDATA[<p>You might want to look at what I&#8217;ve been doing with <a href="http://github.com/sykopomp/until-it-dies" rel="nofollow">Until It Dies</a>. It&#8217;s meant to be more of a 2d game engine, but I wrap a bunch of stuff to make this kind of OpenGL drawing relatively simple (at least as far as I know how to). For fonts, I&#8217;m just hooking up to ftgl, which made the process pretty painless, although I&#8217;m not sure how great a decision that is in the long run&#8230;</p>
<p>You can check out a (right now, extremely bloated) example of how it works <a href="http://github.com/sykopomp/until-it-dies/blob/master/demo/testgame.lisp" rel="nofollow">here</a>.</p>
<p>Anyways, anything having to do with easy-to-use GUIs in lisp sounds like a great idea. I&#8217;ve been tempted now and then to try and write something like <a href="http://www.mike-austin.com/inertia/" rel="nofollow">Inertia</a>, too, which would be quite nice for development in general&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pat</title>
		<link>http://nklein.com/2009/11/playing-with-sheeple-based-gui-atop-cl-opengl/comment-page-1/#comment-462</link>
		<dc:creator>pat</dc:creator>
		<pubDate>Thu, 19 Nov 2009 17:13:49 +0000</pubDate>
		<guid isPermaLink="false">http://nklein.com/?p=1007#comment-462</guid>
		<description>I probably should have added this somewhere before the call to &lt;q&gt;woolly:main-loop&lt;/q&gt; as an example of how to catch when the button was pressed.
[cc lang=&quot;lisp&quot; first_line=&quot;25&quot;]
(sheeple:defreply woolly:mouseup :around ((bb but) mouse-button xx yy)
   (when (sheeple:call-next-reply)
     (format t &quot;BUTTON CLICKED!~%&quot;)
     t))
[/cc]
I will probably make a separate Sheeple message for &lt;q&gt;mouseclicked&lt;/q&gt; so this could be a one-line method instead of a funky &lt;q&gt;:around&lt;/q&gt; thing.

And, before release, I promise to make those names more lispy: e.g. &lt;q&gt;mouse-up&lt;/q&gt; and &lt;q&gt;mouse-clicked&lt;/q&gt;.</description>
		<content:encoded><![CDATA[<p>I probably should have added this somewhere before the call to <q>woolly:main-loop</q> as an example of how to catch when the button was pressed.</p>
<div class="codecolorer-container lisp blackboard" style="overflow:auto;white-space:nowrap;border: 1px solid #9F9F9F;width:435px;"><div class="lisp codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap"><span style="color: #66cc66;">&#40;</span>sheeple<span style="color: #66cc66;">:</span><span style="color: #555;">defreply</span> woolly<span style="color: #66cc66;">:</span><span style="color: #555;">mouseup</span> <span style="color: #66cc66;">:</span><span style="color: #555;">around</span> <span style="color: #66cc66;">&#40;</span><span style="color: #66cc66;">&#40;</span>bb but<span style="color: #66cc66;">&#41;</span> mouse-button xx yy<span style="color: #66cc66;">&#41;</span><br />
&nbsp; &nbsp;<span style="color: #66cc66;">&#40;</span><span style="color: #b1b100;">when</span> <span style="color: #66cc66;">&#40;</span>sheeple<span style="color: #66cc66;">:</span><span style="color: #555;">call-next-reply</span><span style="color: #66cc66;">&#41;</span><br />
&nbsp; &nbsp; &nbsp;<span style="color: #66cc66;">&#40;</span>format t <span style="color: #ff0000;">&quot;BUTTON CLICKED!~%&quot;</span><span style="color: #66cc66;">&#41;</span><br />
&nbsp; &nbsp; &nbsp;t<span style="color: #66cc66;">&#41;</span><span style="color: #66cc66;">&#41;</span></div></div>
<p>I will probably make a separate Sheeple message for <q>mouseclicked</q> so this could be a one-line method instead of a funky <q>:around</q> thing.</p>
<p>And, before release, I promise to make those names more lispy: e.g. <q>mouse-up</q> and <q>mouse-clicked</q>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
