<?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"
	>
<channel>
	<title>Comments on: Ranting on Wordpress Plugin Development</title>
	<atom:link href="http://www.bloggingpro.com/archives/2006/11/29/ranting-on-wordpress-plugin-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bloggingpro.com/archives/2006/11/29/ranting-on-wordpress-plugin-development/</link>
	<description>News, plugins and themes for blogging applications</description>
	<pubDate>Mon, 13 Oct 2008 16:42:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: aydin-aydin</title>
		<link>http://www.bloggingpro.com/archives/2006/11/29/ranting-on-wordpress-plugin-development/#comment-215214</link>
		<dc:creator>aydin-aydin</dc:creator>
		<pubDate>Thu, 18 Sep 2008 08:16:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2006/11/29/ranting-on-wordpress-plugin-development/#comment-215214</guid>
		<description>Patent, Marka Patent, Patent Ofisi, Patent Dirsek, Patent Office, Patent Tescil, Patent Burosu, www patent, Patent com, Patent Ofisim, Patent Tescili, marka patent tescil, patent alma, turk patent, tasarim tescili, tescil belgesi, tasarim tescil, marka tescil, marka tescil belgesi, marka tescili</description>
		<content:encoded><![CDATA[<p>Patent, Marka Patent, Patent Ofisi, Patent Dirsek, Patent Office, Patent Tescil, Patent Burosu, www patent, Patent com, Patent Ofisim, Patent Tescili, marka patent tescil, patent alma, turk patent, tasarim tescili, tescil belgesi, tasarim tescil, marka tescil, marka tescil belgesi, marka tescili</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anne Helmond</title>
		<link>http://www.bloggingpro.com/archives/2006/11/29/ranting-on-wordpress-plugin-development/#comment-96213</link>
		<dc:creator>Anne Helmond</dc:creator>
		<pubDate>Fri, 01 Dec 2006 10:41:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2006/11/29/ranting-on-wordpress-plugin-development/#comment-96213</guid>
		<description>I have been using widgets and plugins for a little while now and I love them.
I have been experiencing some problems with configuring some though. I am currently documenting my problems for my thesis which will deal with software constraints in Wordpress http://www.annehelmond.nl/tag/wordpress

I don’t mind a wide array of options as long as the documentation is good. I am semi tech-savvy and I strongly dislike documentation such as “adjust the php on the correct page”. Which page did you say? I think there is a strong correlation with the development of the themes. Some plugins seem to mess up the theme or the other way round, some themes don’t adjust well to plugins.
Isn’t it possible to come up with a solution that automatically adjust the plugin to your page’s CSS?</description>
		<content:encoded><![CDATA[<p>I have been using widgets and plugins for a little while now and I love them.<br />
I have been experiencing some problems with configuring some though. I am currently documenting my problems for my thesis which will deal with software constraints in Wordpress <a href="http://www.annehelmond.nl/tag/wordpress" rel="nofollow">http://www.annehelmond.nl/tag/wordpress</a></p>
<p>I don’t mind a wide array of options as long as the documentation is good. I am semi tech-savvy and I strongly dislike documentation such as “adjust the php on the correct page”. Which page did you say? I think there is a strong correlation with the development of the themes. Some plugins seem to mess up the theme or the other way round, some themes don’t adjust well to plugins.<br />
Isn’t it possible to come up with a solution that automatically adjust the plugin to your page’s CSS?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anne Helmond &#187; Software constraints in blogging software</title>
		<link>http://www.bloggingpro.com/archives/2006/11/29/ranting-on-wordpress-plugin-development/#comment-96211</link>
		<dc:creator>Anne Helmond &#187; Software constraints in blogging software</dc:creator>
		<pubDate>Fri, 01 Dec 2006 10:38:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2006/11/29/ranting-on-wordpress-plugin-development/#comment-96211</guid>
		<description>[...] The framework itself feels restrictive and I have been looking for tools to accomplish what I want. In the case of Wordpress I have been looking for Widgets and Plug ins that can achieve what I want. Or rather, the backend tools that shape and form my blog. Plugins and widgets are solutions to the restrictions in the Wordpress software, but are restrictions being reproduced on another level? What kind of constraints are built into the internet on the content level? How does software control meaning (content). These are several questions I am planning to ask myself in my MA thesis. I recently came across two related posts: Ranting on Wordpress Plugin Development by Justin Shattuck and Ranting on Wordpress Plugin Development by David at Blogger Pro  Bookmark to: [...]</description>
		<content:encoded><![CDATA[<p>[...] The framework itself feels restrictive and I have been looking for tools to accomplish what I want. In the case of Wordpress I have been looking for Widgets and Plug ins that can achieve what I want. Or rather, the backend tools that shape and form my blog. Plugins and widgets are solutions to the restrictions in the Wordpress software, but are restrictions being reproduced on another level? What kind of constraints are built into the internet on the content level? How does software control meaning (content). These are several questions I am planning to ask myself in my MA thesis. I recently came across two related posts: Ranting on Wordpress Plugin Development by Justin Shattuck and Ranting on Wordpress Plugin Development by David at Blogger Pro  Bookmark to: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Choco</title>
		<link>http://www.bloggingpro.com/archives/2006/11/29/ranting-on-wordpress-plugin-development/#comment-95254</link>
		<dc:creator>Choco</dc:creator>
		<pubDate>Thu, 30 Nov 2006 10:05:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2006/11/29/ranting-on-wordpress-plugin-development/#comment-95254</guid>
		<description>&lt;blockquote&gt;Makes me wonder if there should be some sort of limitation on the amount of option menus or sub-options and whatnot that WordPress allows plug-ins. , I still think simplicity is key for 99% of the bloggers out there.&lt;/blockquote&gt;

Plugins are not part of Wordpress itself. They are "OPTIONAL" extentions made by everyone who feels like it. Thus the &lt;i&gt;"As much as I love to see WordPress extended beyond its original intention"&lt;/i&gt; argument is a void point.

However, if you meant that Wordpress should start limiting its "extention" options your asking for a less flexible and lesser open Wordpress. Especially since its optional and you could choose not to take plugins (!) this is really a bad idea. 

If probloggers can take the advantage of a lesser well developed plugin while awaiting improvement of that plugin its pure gain! Problogger aren't part of the 99% and want specific extra tools. It makes much business sense to not start acting like an emperor on these issues. Or to put it in Richards words, build an plugin who does what you want here yourself :)

I do support simpel and effective plugins though (don't get me wrong on that one), but I think true good developers make the extra effort for documentation and simplicity anyway. You simply can't force bad developers to act like good ones, its free development remember..</description>
		<content:encoded><![CDATA[<blockquote><p>Makes me wonder if there should be some sort of limitation on the amount of option menus or sub-options and whatnot that WordPress allows plug-ins. , I still think simplicity is key for 99% of the bloggers out there.</p></blockquote>
<p>Plugins are not part of Wordpress itself. They are &#8220;OPTIONAL&#8221; extentions made by everyone who feels like it. Thus the <i>&#8220;As much as I love to see WordPress extended beyond its original intention&#8221;</i> argument is a void point.</p>
<p>However, if you meant that Wordpress should start limiting its &#8220;extention&#8221; options your asking for a less flexible and lesser open Wordpress. Especially since its optional and you could choose not to take plugins (!) this is really a bad idea. </p>
<p>If probloggers can take the advantage of a lesser well developed plugin while awaiting improvement of that plugin its pure gain! Problogger aren&#8217;t part of the 99% and want specific extra tools. It makes much business sense to not start acting like an emperor on these issues. Or to put it in Richards words, build an plugin who does what you want here yourself <img src='http://www.bloggingpro.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>I do support simpel and effective plugins though (don&#8217;t get me wrong on that one), but I think true good developers make the extra effort for documentation and simplicity anyway. You simply can&#8217;t force bad developers to act like good ones, its free development remember..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glenn</title>
		<link>http://www.bloggingpro.com/archives/2006/11/29/ranting-on-wordpress-plugin-development/#comment-94826</link>
		<dc:creator>Glenn</dc:creator>
		<pubDate>Thu, 30 Nov 2006 00:00:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2006/11/29/ranting-on-wordpress-plugin-development/#comment-94826</guid>
		<description>For my two cents I think the less file editing needed the better.  Put the options into an option page, it's not too difficult to do, although as you say, menu clutter becomes a problem.

What I'd like to see is a sort of plugin framework.  Maybe a base class to extend off with some standard functions (add filter, show option page, etc)  I've been working on something like that for my plugins, but it would be nice to have some kind of standard.</description>
		<content:encoded><![CDATA[<p>For my two cents I think the less file editing needed the better.  Put the options into an option page, it&#8217;s not too difficult to do, although as you say, menu clutter becomes a problem.</p>
<p>What I&#8217;d like to see is a sort of plugin framework.  Maybe a base class to extend off with some standard functions (add filter, show option page, etc)  I&#8217;ve been working on something like that for my plugins, but it would be nice to have some kind of standard.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://www.bloggingpro.com/archives/2006/11/29/ranting-on-wordpress-plugin-development/#comment-94665</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Wed, 29 Nov 2006 19:33:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2006/11/29/ranting-on-wordpress-plugin-development/#comment-94665</guid>
		<description>The plug-in which I have developed has remained as simple as possible.  I think ease of use is the main reason for plug-ins in the first place anyway!

I'd rather see less complaining about the state of plug-ins and more action instead!</description>
		<content:encoded><![CDATA[<p>The plug-in which I have developed has remained as simple as possible.  I think ease of use is the main reason for plug-ins in the first place anyway!</p>
<p>I&#8217;d rather see less complaining about the state of plug-ins and more action instead!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajay D'Souza</title>
		<link>http://www.bloggingpro.com/archives/2006/11/29/ranting-on-wordpress-plugin-development/#comment-94617</link>
		<dc:creator>Ajay D'Souza</dc:creator>
		<pubDate>Wed, 29 Nov 2006 18:26:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2006/11/29/ranting-on-wordpress-plugin-development/#comment-94617</guid>
		<description>I've always tried to ensure that my plugins are as easy to use as possible.

Most of them are easily configurable from within WP-Admin itself.

One problem I face is documentation.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve always tried to ensure that my plugins are as easy to use as possible.</p>
<p>Most of them are easily configurable from within WP-Admin itself.</p>
<p>One problem I face is documentation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
