<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: What Features do You Want to See?</title>
	<link>http://remstate.com/2007/04/21/what-features-do-you-want-to-see/</link>
	<description>Create the Internet of your Dreams</description>
	<pubDate>Sat, 11 Oct 2008 19:39:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Quandary</title>
		<link>http://remstate.com/2007/04/21/what-features-do-you-want-to-see/#comment-2548</link>
		<dc:creator>Quandary</dc:creator>
		<pubDate>Fri, 08 Jun 2007 15:12:55 +0000</pubDate>
		<guid>http://remstate.com/2007/04/21/what-features-do-you-want-to-see/#comment-2548</guid>
		<description>@Tomas Jablonskis

Oh, and with regard to the database collation -- I never touch that. I assume that the tables get created with whatever is the default for the database. I have no idea what the "right" collation should be, in any given scenario. But I can ask around and try to find out. I'll probably wind up following whatever WordPress does -- if it creates all its tables with UTF8, I'll do likewise; if it uses the database's default collation (which In Series does now), then I'll keep doing that.

Sorry for the inconvenience!</description>
		<content:encoded><![CDATA[<p>@Tomas Jablonskis</p>
<p>Oh, and with regard to the database collation &#8212; I never touch that. I assume that the tables get created with whatever is the default for the database. I have no idea what the &#8220;right&#8221; collation should be, in any given scenario. But I can ask around and try to find out. I&#8217;ll probably wind up following whatever WordPress does &#8212; if it creates all its tables with UTF8, I&#8217;ll do likewise; if it uses the database&#8217;s default collation (which In Series does now), then I&#8217;ll keep doing that.</p>
<p>Sorry for the inconvenience!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Quandary</title>
		<link>http://remstate.com/2007/04/21/what-features-do-you-want-to-see/#comment-2547</link>
		<dc:creator>Quandary</dc:creator>
		<pubDate>Fri, 08 Jun 2007 15:07:27 +0000</pubDate>
		<guid>http://remstate.com/2007/04/21/what-features-do-you-want-to-see/#comment-2547</guid>
		<description>@Tomas Jablonskis


Hey there; sorry for the delay in response. Slacking off is hard work, you know! :)

But seriously... you can get a list of all the posts in a series by using the &lt;code&gt;InSeries::adv_FirstInSeries&lt;/code&gt; and &lt;code&gt;InSeries::adv_NextInSeries&lt;/code&gt; calls. I tried to make sure that all the building blocks were available, so that folks can build up whatever custom things they like -- mostly because I can't write up, maintain and test a zillion different layouts. That said, if a lot of folks want to see a table-of-contents listing of each series, I could certainly code it up.


Hope that helps,</description>
		<content:encoded><![CDATA[<p>@Tomas Jablonskis</p>
<p>Hey there; sorry for the delay in response. Slacking off is hard work, you know! :)</p>
<p>But seriously&#8230; you can get a list of all the posts in a series by using the <code>InSeries::adv_FirstInSeries</code> and <code>InSeries::adv_NextInSeries</code> calls. I tried to make sure that all the building blocks were available, so that folks can build up whatever custom things they like &#8212; mostly because I can&#8217;t write up, maintain and test a zillion different layouts. That said, if a lot of folks want to see a table-of-contents listing of each series, I could certainly code it up.</p>
<p>Hope that helps,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomas Jablonskis &#124; wordpressinfo.lt</title>
		<link>http://remstate.com/2007/04/21/what-features-do-you-want-to-see/#comment-2517</link>
		<dc:creator>Tomas Jablonskis &#124; wordpressinfo.lt</dc:creator>
		<pubDate>Mon, 04 Jun 2007 16:11:16 +0000</pubDate>
		<guid>http://remstate.com/2007/04/21/what-features-do-you-want-to-see/#comment-2517</guid>
		<description>I corrected this problem:

In table wp_in_series_3_0_series, field series_name, Collation column I changed latin1_swedish_ci whith utf8_general_ci.

It woould be nice in the next release that plugin can automatticaly detect whitch collation to use.</description>
		<content:encoded><![CDATA[<p>I corrected this problem:</p>
<p>In table wp_in_series_3_0_series, field series_name, Collation column I changed latin1_swedish_ci whith utf8_general_ci.</p>
<p>It woould be nice in the next release that plugin can automatticaly detect whitch collation to use.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomas Jablonskis &#124; wordpressinfo.lt</title>
		<link>http://remstate.com/2007/04/21/what-features-do-you-want-to-see/#comment-2516</link>
		<dc:creator>Tomas Jablonskis &#124; wordpressinfo.lt</dc:creator>
		<pubDate>Mon, 04 Jun 2007 15:49:54 +0000</pubDate>
		<guid>http://remstate.com/2007/04/21/what-features-do-you-want-to-see/#comment-2516</guid>
		<description>I found one bug: plugin do not work with internetional UTF8 characters in serie name. I got this error:

WordPress database error: [Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '=']
SELECT series_id FROM wp_in_series_3_0_series WHERE series_name='Pluginų grupė: Feedai' AND owner_id='1'</description>
		<content:encoded><![CDATA[<p>I found one bug: plugin do not work with internetional UTF8 characters in serie name. I got this error:</p>
<p>WordPress database error: [Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation &#8216;=&#8217;]<br />
SELECT series_id FROM wp_in_series_3_0_series WHERE series_name=&#8217;Pluginų grupė: Feedai&#8217; AND owner_id=&#8217;1&#8242;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomas Jablonskis &#124; wordpressinfo.lt</title>
		<link>http://remstate.com/2007/04/21/what-features-do-you-want-to-see/#comment-2514</link>
		<dc:creator>Tomas Jablonskis &#124; wordpressinfo.lt</dc:creator>
		<pubDate>Mon, 04 Jun 2007 15:36:23 +0000</pubDate>
		<guid>http://remstate.com/2007/04/21/what-features-do-you-want-to-see/#comment-2514</guid>
		<description>Hello Quandary,

template tag InSeries::SeriesList() shows only series names. It would bee nice that it can show list of posts in that serie.

It is very nice plugin and I impatiently waiting for 3.1 version.</description>
		<content:encoded><![CDATA[<p>Hello Quandary,</p>
<p>template tag InSeries::SeriesList() shows only series names. It would bee nice that it can show list of posts in that serie.</p>
<p>It is very nice plugin and I impatiently waiting for 3.1 version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: REM State Blog Archive &#187; Automation Progress: It Posts!</title>
		<link>http://remstate.com/2007/04/21/what-features-do-you-want-to-see/#comment-2329</link>
		<dc:creator>REM State Blog Archive &#187; Automation Progress: It Posts!</dc:creator>
		<pubDate>Sun, 20 May 2007 23:43:39 +0000</pubDate>
		<guid>http://remstate.com/2007/04/21/what-features-do-you-want-to-see/#comment-2329</guid>
		<description>[...] and code up the tests. I can&#8217;t wait to spend more time goofing off (er&#8230; I mean, writing new features!) instead of testing. Hooray for constructive laziness! [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] and code up the tests. I can&#8217;t wait to spend more time goofing off (er&#8230; I mean, writing new features!) instead of testing. Hooray for constructive laziness! [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Owen</title>
		<link>http://remstate.com/2007/04/21/what-features-do-you-want-to-see/#comment-1903</link>
		<dc:creator>Owen</dc:creator>
		<pubDate>Thu, 03 May 2007 09:14:30 +0000</pubDate>
		<guid>http://remstate.com/2007/04/21/what-features-do-you-want-to-see/#comment-1903</guid>
		<description>Hi,

Thanks for the speedy reply - and the good news about the first/last links!

Yes, indeed the &lt;!--series-toc--&gt; approach would be PERFECT for what I have in mind. 

I completely agree with you. Allowing full, per-post customization would be a much better approach than my suggestion which would almost inevitably lead to configuration overload! 

Please head in that direction. I think it stands a good chance of including almost all the different features that different people want in one conceptually simple package.

Roll on 3.2 :)</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Thanks for the speedy reply - and the good news about the first/last links!</p>
<p>Yes, indeed the <!--series-toc--> approach would be PERFECT for what I have in mind. </p>
<p>I completely agree with you. Allowing full, per-post customization would be a much better approach than my suggestion which would almost inevitably lead to configuration overload! </p>
<p>Please head in that direction. I think it stands a good chance of including almost all the different features that different people want in one conceptually simple package.</p>
<p>Roll on 3.2 :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Quandary</title>
		<link>http://remstate.com/2007/04/21/what-features-do-you-want-to-see/#comment-1892</link>
		<dc:creator>Quandary</dc:creator>
		<pubDate>Thu, 03 May 2007 00:53:20 +0000</pubDate>
		<guid>http://remstate.com/2007/04/21/what-features-do-you-want-to-see/#comment-1892</guid>
		<description>@Owen

Glad to hear it!

Having things be different in the first (or last, for that matter) post is a good idea. It probably won't happen in 3.1, but it's certainly something I'd consider for 3.2. I've been toying with a more generic idea, to allow authors to indicate in the article that they want a series item &lt;em&gt;right here&lt;/em&gt; (e.g., &lt;code&gt;&#60;!--series-toc--&#62;&lt;/code&gt;) -- this would allow for full, per-post customization without having to have a million configuration options (first post [multi/single] layout, last post [multi/single] layout, etc.). Would that be good for you?

Finally, the first/last links for series are already slated (&lt;a href="/projects/in-series/bugzilla/show_bug.cgi?id=16" rel="nofollow"&gt;bug 16&lt;/a&gt;).

Thanks for the feedback. :)</description>
		<content:encoded><![CDATA[<p>@Owen</p>
<p>Glad to hear it!</p>
<p>Having things be different in the first (or last, for that matter) post is a good idea. It probably won&#8217;t happen in 3.1, but it&#8217;s certainly something I&#8217;d consider for 3.2. I&#8217;ve been toying with a more generic idea, to allow authors to indicate in the article that they want a series item <em>right here</em> (e.g., <code>&lt;!--series-toc--&gt;</code>) &#8212; this would allow for full, per-post customization without having to have a million configuration options (first post [multi/single] layout, last post [multi/single] layout, etc.). Would that be good for you?</p>
<p>Finally, the first/last links for series are already slated (<a href="/projects/in-series/bugzilla/show_bug.cgi?id=16&PHPSESSID=827e2a62e76ce1074935e9c2529d36cf" rel="nofollow">bug 16</a>).</p>
<p>Thanks for the feedback. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Owen</title>
		<link>http://remstate.com/2007/04/21/what-features-do-you-want-to-see/#comment-1884</link>
		<dc:creator>Owen</dc:creator>
		<pubDate>Wed, 02 May 2007 19:21:15 +0000</pubDate>
		<guid>http://remstate.com/2007/04/21/what-features-do-you-want-to-see/#comment-1884</guid>
		<description>Hi,

I am beginning to use this and I think I am going to find it one of the core plug-ins for what I am trying to do. I like it :)

I have two related features I would very much like to see in 3.1. I would like an option to have the TOC on the first post in a series only. I would also like the ability to have "previous post", "next post" AND "first post in series" in the navigation at the bottom of each entry.

This would then enable me to use the first post in a series as an introduction and overview (which includes a TOC) and then have the rest of the posts going back, forward, and rewind to the start.

Many many thanks!</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I am beginning to use this and I think I am going to find it one of the core plug-ins for what I am trying to do. I like it :)</p>
<p>I have two related features I would very much like to see in 3.1. I would like an option to have the TOC on the first post in a series only. I would also like the ability to have &#8220;previous post&#8221;, &#8220;next post&#8221; AND &#8220;first post in series&#8221; in the navigation at the bottom of each entry.</p>
<p>This would then enable me to use the first post in a series as an introduction and overview (which includes a TOC) and then have the rest of the posts going back, forward, and rewind to the start.</p>
<p>Many many thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henrik</title>
		<link>http://remstate.com/2007/04/21/what-features-do-you-want-to-see/#comment-1861</link>
		<dc:creator>Henrik</dc:creator>
		<pubDate>Tue, 01 May 2007 22:29:20 +0000</pubDate>
		<guid>http://remstate.com/2007/04/21/what-features-do-you-want-to-see/#comment-1861</guid>
		<description>Regarding the need to edit templates (Mosey). If you have a widget enabled theme, a simple way to do it is to use ie the &lt;a href="http://www.erik-rasmussen.com/blog/2006/11/30/widgetize-anything/" rel="nofollow"&gt;widgetize anything&lt;/a&gt; widget, which allows you to create widgets based on your own php code, then simply paste &lt;i&gt;InSeries::SeriesList();&lt;/i&gt; into the widget's code window. Voila, a series index!</description>
		<content:encoded><![CDATA[<p>Regarding the need to edit templates (Mosey). If you have a widget enabled theme, a simple way to do it is to use ie the <a href="http://www.erik-rasmussen.com/blog/2006/11/30/widgetize-anything/" rel="nofollow">widgetize anything</a> widget, which allows you to create widgets based on your own php code, then simply paste <i>InSeries::SeriesList();</i> into the widget&#8217;s code window. Voila, a series index!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
