<?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: Qdig-WP Kubrick Integration</title>
	<atom:link href="http://randomfrequency.net/blog/2006/03/16/qdig-wp-kubrick-integration/feed/" rel="self" type="application/rss+xml" />
	<link>http://randomfrequency.net/blog/2006/03/16/qdig-wp-kubrick-integration/</link>
	<description>where the signal to noise ratio always varies</description>
	<lastBuildDate>Sun, 18 Jul 2010 11:54:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Hagan Fox</title>
		<link>http://randomfrequency.net/blog/2006/03/16/qdig-wp-kubrick-integration/comment-page-1/#comment-1773</link>
		<dc:creator>Hagan Fox</dc:creator>
		<pubDate>Thu, 06 Apr 2006 22:02:25 +0000</pubDate>
		<guid isPermaLink="false">http://randomfrequency.net/blog/2006/03/16/qdig-wp-kubrick-integration/#comment-1773</guid>
		<description>Oops.  I just posted transposed letters in the Qdig site&#039;s URL.

Hagan</description>
		<content:encoded><![CDATA[<p>Oops.  I just posted transposed letters in the Qdig site&#8217;s URL.</p>
<p>Hagan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hagan Fox</title>
		<link>http://randomfrequency.net/blog/2006/03/16/qdig-wp-kubrick-integration/comment-page-1/#comment-1772</link>
		<dc:creator>Hagan Fox</dc:creator>
		<pubDate>Thu, 06 Apr 2006 21:58:16 +0000</pubDate>
		<guid isPermaLink="false">http://randomfrequency.net/blog/2006/03/16/qdig-wp-kubrick-integration/#comment-1772</guid>
		<description>Heya David,

During the past week I completely reworked how Qdig deals with URL and filesystem paths to the gallery directory, so now making a plugin for Qdig 1.3 (currently still qdig-devel) should be easier, but I don&#039;t know how it will affect the existing plugin.  Embedding galleries in general should be dramatically simpler with the new path-related code.

There&#039;s a remote possibility I could do some more with paths before 1.3 is released, but any significant changes will almost certainly be postponed for Qdig 1.4.

Anyhow, I wanted to at least warn you that the link to Qdig tarball and .zip files will point to a significantly different version soon.

I also think Qdig-WP users will like the new version&#039;s $cnvrt_alt[&#039;by_height&#039;] setting, which causes Qdig to convert all resampled images to the same height rather than letting portrait-oriented images be a bit taller than landscape-oriented ones.  You can also link the displayed image to an all-thumbnails page (similar to Pbase galleries) and some other new stuff...

Hagan</description>
		<content:encoded><![CDATA[<p>Heya David,</p>
<p>During the past week I completely reworked how Qdig deals with URL and filesystem paths to the gallery directory, so now making a plugin for Qdig 1.3 (currently still qdig-devel) should be easier, but I don&#8217;t know how it will affect the existing plugin.  Embedding galleries in general should be dramatically simpler with the new path-related code.</p>
<p>There&#8217;s a remote possibility I could do some more with paths before 1.3 is released, but any significant changes will almost certainly be postponed for Qdig 1.4.</p>
<p>Anyhow, I wanted to at least warn you that the link to Qdig tarball and .zip files will point to a significantly different version soon.</p>
<p>I also think Qdig-WP users will like the new version&#8217;s $cnvrt_alt['by_height'] setting, which causes Qdig to convert all resampled images to the same height rather than letting portrait-oriented images be a bit taller than landscape-oriented ones.  You can also link the displayed image to an all-thumbnails page (similar to Pbase galleries) and some other new stuff&#8230;</p>
<p>Hagan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Cheung</title>
		<link>http://randomfrequency.net/blog/2006/03/16/qdig-wp-kubrick-integration/comment-page-1/#comment-1684</link>
		<dc:creator>Ian Cheung</dc:creator>
		<pubDate>Mon, 20 Mar 2006 12:11:33 +0000</pubDate>
		<guid isPermaLink="false">http://randomfrequency.net/blog/2006/03/16/qdig-wp-kubrick-integration/#comment-1684</guid>
		<description>Hi David,

Thanks for posting those links.  Actually the guide should be helpful for not just Kubrick, I just used Kubrick because it is a standard of sorts.  Once people get it working with Kubrick they can use what they learnt to apply it to other themes.  For instance I integrated it with my own site theme by just changing some of the width numbers.  

And great news for people wondering if it works under WP2.0, yes it does!  Someone had problems with it (see comments on the guide post) but I suspect that they were not WP2.0 related.  And later he got it working fine.  

Thanks again for your great work and hope everything is well.  I was a bit worried about your absence.</description>
		<content:encoded><![CDATA[<p>Hi David,</p>
<p>Thanks for posting those links.  Actually the guide should be helpful for not just Kubrick, I just used Kubrick because it is a standard of sorts.  Once people get it working with Kubrick they can use what they learnt to apply it to other themes.  For instance I integrated it with my own site theme by just changing some of the width numbers.  </p>
<p>And great news for people wondering if it works under WP2.0, yes it does!  Someone had problems with it (see comments on the guide post) but I suspect that they were not WP2.0 related.  And later he got it working fine.  </p>
<p>Thanks again for your great work and hope everything is well.  I was a bit worried about your absence.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

