<?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: Python and pigment</title>
	<atom:link href="http://macslow.net/?feed=rss2&#038;p=115" rel="self" type="application/rss+xml" />
	<link>http://macslow.net/?p=115</link>
	<description>stuff happening on macslow.net</description>
	<pubDate>Sat, 31 Jul 2010 23:02:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: karim</title>
		<link>http://macslow.net/?p=115&#038;cpage=1#comment-176847</link>
		<dc:creator>karim</dc:creator>
		<pubDate>Tue, 28 Jul 2009 15:03:28 +0000</pubDate>
		<guid isPermaLink="false">http://macslow.thepimp.net/?p=115#comment-176847</guid>
		<description>thanks ,any way</description>
		<content:encoded><![CDATA[<p>thanks ,any way</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MacSlow</title>
		<link>http://macslow.net/?p=115&#038;cpage=1#comment-176846</link>
		<dc:creator>MacSlow</dc:creator>
		<pubDate>Tue, 28 Jul 2009 11:59:15 +0000</pubDate>
		<guid isPermaLink="false">http://macslow.thepimp.net/?p=115#comment-176846</guid>
		<description>@ karim: I'm not involved in pigment and elisa (now called moovida) in over two years now. You are much better off trying to contact the upstream developers on the official pigment- and moovida-mailing-lists (https://lists.moovida.com/mailman/listinfo)</description>
		<content:encoded><![CDATA[<p>@ karim: I&#8217;m not involved in pigment and elisa (now called moovida) in over two years now. You are much better off trying to contact the upstream developers on the official pigment- and moovida-mailing-lists (https://lists.moovida.com/mailman/listinfo)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: karim</title>
		<link>http://macslow.net/?p=115&#038;cpage=1#comment-176845</link>
		<dc:creator>karim</dc:creator>
		<pubDate>Tue, 28 Jul 2009 11:35:13 +0000</pubDate>
		<guid isPermaLink="false">http://macslow.thepimp.net/?p=115#comment-176845</guid>
		<description>Hey,
I am a new pigment user and I am developing a plug in for Elisa media centre and I am having problems in writing widgets code ,
I have wrote a code that creates only a SectionMenuControl and a decorator that draw a link in it ,that's all

I want to use the widgets in the pigment toolkit but i don't seem to get can any one help me ,i have searched for a tutorials on how to do it and nothing came on.</description>
		<content:encoded><![CDATA[<p>Hey,<br />
I am a new pigment user and I am developing a plug in for Elisa media centre and I am having problems in writing widgets code ,<br />
I have wrote a code that creates only a SectionMenuControl and a decorator that draw a link in it ,that&#8217;s all</p>
<p>I want to use the widgets in the pigment toolkit but i don&#8217;t seem to get can any one help me ,i have searched for a tutorials on how to do it and nothing came on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: philn</title>
		<link>http://macslow.net/?p=115&#038;cpage=1#comment-29744</link>
		<dc:creator>philn</dc:creator>
		<pubDate>Thu, 01 Nov 2007 10:29:52 +0000</pubDate>
		<guid isPermaLink="false">http://macslow.thepimp.net/?p=115#comment-29744</guid>
		<description>For the record Pigment is now under LGPL (since last summer).</description>
		<content:encoded><![CDATA[<p>For the record Pigment is now under LGPL (since last summer).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MacSlow</title>
		<link>http://macslow.net/?p=115&#038;cpage=1#comment-21961</link>
		<dc:creator>MacSlow</dc:creator>
		<pubDate>Thu, 21 Jun 2007 00:00:37 +0000</pubDate>
		<guid isPermaLink="false">http://macslow.thepimp.net/?p=115#comment-21961</guid>
		<description>@ mallum: Yeah, that licence-issue is a big one. I forgot that in my comparison-list. And that's why I would currently not consider using pigment for my own personal stuff or stuff that's meant to be used &#34;outside&#34; of a Fluendo-project. I told that a few people at Fluendo. We'll see if they reconsider it. I hope so. The 3D-capabilites of pigment and clutter don't really satisfy my needs (or better... wishes). But I know that both libraries are work-in-progress so that's ok. The bindings I don't care for that much personally (I really still don't like Python :). I just stated them for people who might be interested in something different than C or C++. Since I will meet you at GUADEC (hopefully) anyway we should continue talking about these kind of things - and clutter in particular - there. There's a lot of topics I would like to bring up.</description>
		<content:encoded><![CDATA[<p>@ mallum: Yeah, that licence-issue is a big one. I forgot that in my comparison-list. And that&#8217;s why I would currently not consider using pigment for my own personal stuff or stuff that&#8217;s meant to be used &quot;outside&quot; of a Fluendo-project. I told that a few people at Fluendo. We&#8217;ll see if they reconsider it. I hope so. The 3D-capabilites of pigment and clutter don&#8217;t really satisfy my needs (or better&#8230; wishes). But I know that both libraries are work-in-progress so that&#8217;s ok. The bindings I don&#8217;t care for that much personally (I really still don&#8217;t like Python :). I just stated them for people who might be interested in something different than C or C++. Since I will meet you at GUADEC (hopefully) anyway we should continue talking about these kind of things - and clutter in particular - there. There&#8217;s a lot of topics I would like to bring up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mallum</title>
		<link>http://macslow.net/?p=115&#038;cpage=1#comment-21938</link>
		<dc:creator>mallum</dc:creator>
		<pubDate>Wed, 20 Jun 2007 22:36:02 +0000</pubDate>
		<guid isPermaLink="false">http://macslow.thepimp.net/?p=115#comment-21938</guid>
		<description>Arg, I just stumbled on this post and comments, and theres actually a few things wrong and important things missing from your feature by feature comment. Namely;

 - Both are O/S but Clutter is LGPL and Pigment is GPL (https://core.fluendo.com/pigment/trac/browser/trunk/LICENSE.GPL?)
 - Clutter is in no way strict 2D, its always done 3D!!
 - Clutter also has Perl and Mono bindings (as well as python)

I could go on but I wont :)</description>
		<content:encoded><![CDATA[<p>Arg, I just stumbled on this post and comments, and theres actually a few things wrong and important things missing from your feature by feature comment. Namely;</p>
<p> - Both are O/S but Clutter is LGPL and Pigment is GPL (https://core.fluendo.com/pigment/trac/browser/trunk/LICENSE.GPL?)<br />
 - Clutter is in no way strict 2D, its always done 3D!!<br />
 - Clutter also has Perl and Mono bindings (as well as python)</p>
<p>I could go on but I wont <img src='http://macslow.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MacSlow</title>
		<link>http://macslow.net/?p=115&#038;cpage=1#comment-17485</link>
		<dc:creator>MacSlow</dc:creator>
		<pubDate>Sun, 15 Apr 2007 20:38:37 +0000</pubDate>
		<guid isPermaLink="false">http://macslow.thepimp.net/?p=115#comment-17485</guid>
		<description>@ Stojance: Most of my stuff is available. Check &lt;a href="http://macslow.thepimp.net/?page_id=8"&gt;Projects&lt;/a&gt; or &lt;a href="http://people.freedesktop.org/~macslow"&gt;my page at fdo&lt;/a&gt;. The sources of my python/pigment learning-exercises are everything but helpful. They are mostly embarrassing, because I'm still learning python and know nothing of python's best practices yet. If you want to get into python-coding with pigment just go and grab a recent pigment-release from &lt;a href="https://core.fluendo.com/pigment/trac/"&gt;here&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>@ Stojance: Most of my stuff is available. Check <a href="http://macslow.thepimp.net/?page_id=8">Projects</a> or <a href="http://people.freedesktop.org/~macslow">my page at fdo</a>. The sources of my python/pigment learning-exercises are everything but helpful. They are mostly embarrassing, because I&#8217;m still learning python and know nothing of python&#8217;s best practices yet. If you want to get into python-coding with pigment just go and grab a recent pigment-release from <a href="https://core.fluendo.com/pigment/trac/">here</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stojance</title>
		<link>http://macslow.net/?p=115&#038;cpage=1#comment-17484</link>
		<dc:creator>Stojance</dc:creator>
		<pubDate>Sun, 15 Apr 2007 19:28:55 +0000</pubDate>
		<guid isPermaLink="false">http://macslow.thepimp.net/?p=115#comment-17484</guid>
		<description>Hey MacSlow!

It wouldn't be a bad idea to release the code on these programs that you make. I really like to learn how these things go, OpenGL, Cairo and stuff. There aren't much examples laying around, you know.</description>
		<content:encoded><![CDATA[<p>Hey MacSlow!</p>
<p>It wouldn&#8217;t be a bad idea to release the code on these programs that you make. I really like to learn how these things go, OpenGL, Cairo and stuff. There aren&#8217;t much examples laying around, you know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: obi</title>
		<link>http://macslow.net/?p=115&#038;cpage=1#comment-17463</link>
		<dc:creator>obi</dc:creator>
		<pubDate>Sat, 14 Apr 2007 17:18:49 +0000</pubDate>
		<guid isPermaLink="false">http://macslow.thepimp.net/?p=115#comment-17463</guid>
		<description>@Macslow: That's quite interesting, actually - I didn't realize they were even more similar than I imagined. Guess I now have to take a closer look at pigment too. I echo your sentiments that it would be nice if they'd join forces, but I do realize this takes a lot of effort from both projects - I'll be the last to judge them for it.

Thank you for the comparison.</description>
		<content:encoded><![CDATA[<p>@Macslow: That&#8217;s quite interesting, actually - I didn&#8217;t realize they were even more similar than I imagined. Guess I now have to take a closer look at pigment too. I echo your sentiments that it would be nice if they&#8217;d join forces, but I do realize this takes a lot of effort from both projects - I&#8217;ll be the last to judge them for it.</p>
<p>Thank you for the comparison.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MacSlow</title>
		<link>http://macslow.net/?p=115&#038;cpage=1#comment-17458</link>
		<dc:creator>MacSlow</dc:creator>
		<pubDate>Sat, 14 Apr 2007 01:24:08 +0000</pubDate>
		<guid isPermaLink="false">http://macslow.thepimp.net/?p=115#comment-17458</guid>
		<description>@ obi: That's true. clutter and pigment kind of cover the same use-cases for such a library of that kind. Also feature-wise they are very similar. But I'm not very experienced yet with clutter. Also my experience with pigment is still very young. pigment is actually written in ANSI C using gobject. Furthermore it provides a python-binding, which is used by Elisa, as does clutter. Here's a rough feature-by-feature comparison:

- both implemented in C
- both leverage gobject, gstreamer, OpenGL
- both offer bindings for Python
- clutter already interfaces with cairo/pango, pigment will also start to do so in the next weeks
- placement/rotation-wise clutter is strict 2D only at the moment (that might change), pigment is 3D
- both heavily developed, commercially funded and OpenSource
- clutter there's already a gtk-widget, for pigment this is planned
- both will be able to support gtk-widgets on surfaces/drawables once gtk offers offscreen-rendering
- both have a pluggable rendering-backend (e.g. OpenGL, OpenGL&#124;ES, directfb...)
- both offer keyframed animation
- clutter offers path-based animation, pigment will soon too
- elisa (not pigment) will offer integration of backends like Ogre3D, OpenSceneGraph or the like
- pigment will offer fragment/vertex-shader and GLSL support, clutter will perhaps too

To my current knowledge this list is quite complete. But I'm always glad for corrections/additions.

It's a bit sad to see these two efforts pulling in the same direction, but not joining forces. Maybe this will change in the future... please note that this is pure speculation/wishing from my side.</description>
		<content:encoded><![CDATA[<p>@ obi: That&#8217;s true. clutter and pigment kind of cover the same use-cases for such a library of that kind. Also feature-wise they are very similar. But I&#8217;m not very experienced yet with clutter. Also my experience with pigment is still very young. pigment is actually written in ANSI C using gobject. Furthermore it provides a python-binding, which is used by Elisa, as does clutter. Here&#8217;s a rough feature-by-feature comparison:</p>
<p>- both implemented in C<br />
- both leverage gobject, gstreamer, OpenGL<br />
- both offer bindings for Python<br />
- clutter already interfaces with cairo/pango, pigment will also start to do so in the next weeks<br />
- placement/rotation-wise clutter is strict 2D only at the moment (that might change), pigment is 3D<br />
- both heavily developed, commercially funded and OpenSource<br />
- clutter there&#8217;s already a gtk-widget, for pigment this is planned<br />
- both will be able to support gtk-widgets on surfaces/drawables once gtk offers offscreen-rendering<br />
- both have a pluggable rendering-backend (e.g. OpenGL, OpenGL|ES, directfb&#8230;)<br />
- both offer keyframed animation<br />
- clutter offers path-based animation, pigment will soon too<br />
- elisa (not pigment) will offer integration of backends like Ogre3D, OpenSceneGraph or the like<br />
- pigment will offer fragment/vertex-shader and GLSL support, clutter will perhaps too</p>
<p>To my current knowledge this list is quite complete. But I&#8217;m always glad for corrections/additions.</p>
<p>It&#8217;s a bit sad to see these two efforts pulling in the same direction, but not joining forces. Maybe this will change in the future&#8230; please note that this is pure speculation/wishing from my side.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
