<?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: So we need a new term to describe widgets</title>
	<atom:link href="http://ptahdunbar.com/wordpress/so-we-need-a-new-term-to-describe-widgets/feed/" rel="self" type="application/rss+xml" />
	<link>http://ptahdunbar.com/wordpress/so-we-need-a-new-term-to-describe-widgets/</link>
	<description>Web Craftsman, WordPress hacker and Entrepreneur.</description>
	<lastBuildDate>Tue, 16 Feb 2010 19:17:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Justin Tadlock</title>
		<link>http://ptahdunbar.com/wordpress/so-we-need-a-new-term-to-describe-widgets/#comment-3107</link>
		<dc:creator>Justin Tadlock</dc:creator>
		<pubDate>Thu, 26 Feb 2009 00:43:32 +0000</pubDate>
		<guid isPermaLink="false">http://ptahdunbar.com/?p=580#comment-3107</guid>
		<description>Ryan, I definitely agree that &lt;code&gt;get_sidebar()&lt;/code&gt; should stay.  It&#039;s perfect for including sidebars.

I think the biggest issue is just breaking out of the mindset that widgets only go in sidebars.</description>
		<content:encoded><![CDATA[<p>Ryan, I definitely agree that <code>get_sidebar()</code> should stay.  It&#8217;s perfect for including sidebars.</p>
<p>I think the biggest issue is just breaking out of the mindset that widgets only go in sidebars.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Tadlock</title>
		<link>http://ptahdunbar.com/wordpress/so-we-need-a-new-term-to-describe-widgets/#comment-3106</link>
		<dc:creator>Justin Tadlock</dc:creator>
		<pubDate>Thu, 26 Feb 2009 00:39:41 +0000</pubDate>
		<guid isPermaLink="false">http://ptahdunbar.com/?p=580#comment-3106</guid>
		<description>No, we actually have the same idea here from what I can see.  I agree that all that would be needed is a new function like you&#039;ve shown.  But, &lt;code&gt;get_widget()&lt;/code&gt; just sounds like you&#039;re only grabbing a single widget.  When, in fact, we would be loading an entire widget area (i.e. container, section, etc.).

I think &lt;code&gt;get_widget_area()&lt;/code&gt; would make more sense here.

I did notice that in the title of your post, you said we need a new &quot;term to describe widgets.&quot;  I&#039;d like to keep the current terminology for widgets.  What I want is a new term to describe the thing that contains widgets, which we&#039;ve been calling sidebars.</description>
		<content:encoded><![CDATA[<p>No, we actually have the same idea here from what I can see.  I agree that all that would be needed is a new function like you&#8217;ve shown.  But, <code>get_widget()</code> just sounds like you&#8217;re only grabbing a single widget.  When, in fact, we would be loading an entire widget area (i.e. container, section, etc.).</p>
<p>I think <code>get_widget_area()</code> would make more sense here.</p>
<p>I did notice that in the title of your post, you said we need a new &#8220;term to describe widgets.&#8221;  I&#8217;d like to keep the current terminology for widgets.  What I want is a new term to describe the thing that contains widgets, which we&#8217;ve been calling sidebars.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://ptahdunbar.com/wordpress/so-we-need-a-new-term-to-describe-widgets/#comment-3105</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Wed, 25 Feb 2009 23:12:12 +0000</pubDate>
		<guid isPermaLink="false">http://ptahdunbar.com/?p=580#comment-3105</guid>
		<description>The term get_sidebar should definitely stay. They function calls up a particular template, which is intended for sidebars. It has nothing to do with the issue over widgets, it just coincidentally happens to often be used for displaying widgets.</description>
		<content:encoded><![CDATA[<p>The term get_sidebar should definitely stay. They function calls up a particular template, which is intended for sidebars. It has nothing to do with the issue over widgets, it just coincidentally happens to often be used for displaying widgets.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ptah Dunbar</title>
		<link>http://ptahdunbar.com/wordpress/so-we-need-a-new-term-to-describe-widgets/#comment-3104</link>
		<dc:creator>Ptah Dunbar</dc:creator>
		<pubDate>Wed, 25 Feb 2009 09:32:39 +0000</pubDate>
		<guid isPermaLink="false">http://ptahdunbar.com/?p=580#comment-3104</guid>
		<description>Seems like we have different ways of calling widgets. You mind explaining your way for how you&#039;d like widgets to work?

Updated the article for &lt;code&gt;locate_template&lt;/code&gt; instead of &lt;code&gt;load_template&lt;/code&gt;. Didn&#039;t know about that neat function.</description>
		<content:encoded><![CDATA[<p>Seems like we have different ways of calling widgets. You mind explaining your way for how you&#8217;d like widgets to work?</p>
<p>Updated the article for <code>locate_template</code> instead of <code>load_template</code>. Didn&#8217;t know about that neat function.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Tadlock</title>
		<link>http://ptahdunbar.com/wordpress/so-we-need-a-new-term-to-describe-widgets/#comment-3103</link>
		<dc:creator>Justin Tadlock</dc:creator>
		<pubDate>Wed, 25 Feb 2009 08:13:49 +0000</pubDate>
		<guid isPermaLink="false">http://ptahdunbar.com/?p=580#comment-3103</guid>
		<description>I haven&#039;t made up my mind just yet.  I was hoping to hear something from someone a bit more &quot;official,&quot; but none of the WP.org developers chimed in.

Personally, I wouldn&#039;t name a function that gets a widget area &lt;code&gt;get_widget&lt;/code&gt;.  It sounds like you&#039;re only grabbing one widget instead of an entire set of widgets.  Maybe just append an &quot;s&quot; on the end, at least.

While it would be neat to get some new terminology, maybe we don&#039;t even need it.  WP 2.7 introduced the &lt;code&gt;locate_template&lt;/code&gt; function, which gives plenty of control over templates.  Maybe it&#039;s best if theme developers are left to come up with their own terminology.</description>
		<content:encoded><![CDATA[<p>I haven&#8217;t made up my mind just yet.  I was hoping to hear something from someone a bit more &#8220;official,&#8221; but none of the WP.org developers chimed in.</p>
<p>Personally, I wouldn&#8217;t name a function that gets a widget area <code>get_widget</code>.  It sounds like you&#8217;re only grabbing one widget instead of an entire set of widgets.  Maybe just append an &#8220;s&#8221; on the end, at least.</p>
<p>While it would be neat to get some new terminology, maybe we don&#8217;t even need it.  WP 2.7 introduced the <code>locate_template</code> function, which gives plenty of control over templates.  Maybe it&#8217;s best if theme developers are left to come up with their own terminology.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
