<?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: Adii on Frameworks: No Love</title>
	<atom:link href="http://www.bloggingpro.com/archives/2009/03/03/adii-on-frameworks-no-love/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bloggingpro.com/archives/2009/03/03/adii-on-frameworks-no-love/</link>
	<description>News, plugins and themes for blogging applications</description>
	<lastBuildDate>Fri, 10 Feb 2012 01:07:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: æ€§å¼€æ”¾å¥³å­</title>
		<link>http://www.bloggingpro.com/archives/2009/03/03/adii-on-frameworks-no-love/#comment-218207</link>
		<dc:creator>æ€§å¼€æ”¾å¥³å­</dc:creator>
		<pubDate>Tue, 10 Mar 2009 02:35:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/?p=2734#comment-218207</guid>
		<description>Thank you!</description>
		<content:encoded><![CDATA[<p>Thank you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajay</title>
		<link>http://www.bloggingpro.com/archives/2009/03/03/adii-on-frameworks-no-love/#comment-218091</link>
		<dc:creator>Ajay</dc:creator>
		<pubDate>Wed, 04 Mar 2009 19:00:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/?p=2734#comment-218091</guid>
		<description>I believe there should be a balance of features. A simple theme which satisfies most of the users needs, while providing the user the ability to customize as much as possible by editing the code.

Again, options for basic color schemes and all are fine, but at one point the theme would get super-bloated and result in really slow loading website</description>
		<content:encoded><![CDATA[<p>I believe there should be a balance of features. A simple theme which satisfies most of the users needs, while providing the user the ability to customize as much as possible by editing the code.</p>
<p>Again, options for basic color schemes and all are fine, but at one point the theme would get super-bloated and result in really slow loading website</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.bloggingpro.com/archives/2009/03/03/adii-on-frameworks-no-love/#comment-218077</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Tue, 03 Mar 2009 22:24:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/?p=2734#comment-218077</guid>
		<description>What I think is interesting is the expectations of users, and of themers.

Not too long ago, as a WordPress user who wanted to tweak their own stuff, you were expected to learn the fundamentals. Now there seems to be a consensus that you shouldn&#039;t have to learn in order to make decisions about your site.

Frameworks are the in-between. They offer non-developers the chance to add all the point-and-click stuff for the &#039;users&#039; without needing to understand it yourself.

This is how many other industries have worked for a long time, televisions have long been badged up, many cars are built on the same chasis, and I am sure we have all had cable modems badged by the ISP. They make themes into a commodity to buy, brand, and sell, and will meet a need just a certainly as a mid-range Ford.

There will still be Bentley and there will still be Skoda.

I also agree that frameworks make it more difficult for users who can modify things themselves. The question is, if they want to do that why are they using a framework?</description>
		<content:encoded><![CDATA[<p>What I think is interesting is the expectations of users, and of themers.</p>
<p>Not too long ago, as a WordPress user who wanted to tweak their own stuff, you were expected to learn the fundamentals. Now there seems to be a consensus that you shouldn&#8217;t have to learn in order to make decisions about your site.</p>
<p>Frameworks are the in-between. They offer non-developers the chance to add all the point-and-click stuff for the &#8216;users&#8217; without needing to understand it yourself.</p>
<p>This is how many other industries have worked for a long time, televisions have long been badged up, many cars are built on the same chasis, and I am sure we have all had cable modems badged by the ISP. They make themes into a commodity to buy, brand, and sell, and will meet a need just a certainly as a mid-range Ford.</p>
<p>There will still be Bentley and there will still be Skoda.</p>
<p>I also agree that frameworks make it more difficult for users who can modify things themselves. The question is, if they want to do that why are they using a framework?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan Rice</title>
		<link>http://www.bloggingpro.com/archives/2009/03/03/adii-on-frameworks-no-love/#comment-218075</link>
		<dc:creator>Nathan Rice</dc:creator>
		<pubDate>Tue, 03 Mar 2009 20:02:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/?p=2734#comment-218075</guid>
		<description>Unless you make literally EVERY single aspect of the theme editable from the backend, then Adii is right in his characterization of my statements: framework themes, themes like Flexx and WPUnlimited, and other &quot;advanced&quot; themes are way to hard for a user to modify, especially if the user wants to modify the theme heavily.

Take WPUnlimited for instance ... if an advanced user wanted to start hacking up the core files, moving stuff around, removing things, etc., there&#039;s a good chance most of the features you built into the theme will be broken and/or obsolete in his final creation.

We&#039;re at an impass -- there are 3 types of themes out there, as far as I can see:

1. The framework
2. The traditional theme
3. The Point-and-Click

Each one appeals to a different kind of person.  I think, however, there is probably room for all 3, though I do believe one will eventually come out as dominant in the market.</description>
		<content:encoded><![CDATA[<p>Unless you make literally EVERY single aspect of the theme editable from the backend, then Adii is right in his characterization of my statements: framework themes, themes like Flexx and WPUnlimited, and other &#8220;advanced&#8221; themes are way to hard for a user to modify, especially if the user wants to modify the theme heavily.</p>
<p>Take WPUnlimited for instance &#8230; if an advanced user wanted to start hacking up the core files, moving stuff around, removing things, etc., there&#8217;s a good chance most of the features you built into the theme will be broken and/or obsolete in his final creation.</p>
<p>We&#8217;re at an impass &#8212; there are 3 types of themes out there, as far as I can see:</p>
<p>1. The framework<br />
2. The traditional theme<br />
3. The Point-and-Click</p>
<p>Each one appeals to a different kind of person.  I think, however, there is probably room for all 3, though I do believe one will eventually come out as dominant in the market.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adii Rockstar</title>
		<link>http://www.bloggingpro.com/archives/2009/03/03/adii-on-frameworks-no-love/#comment-218072</link>
		<dc:creator>Adii Rockstar</dc:creator>
		<pubDate>Tue, 03 Mar 2009 19:33:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/?p=2734#comment-218072</guid>
		<description>As Nathan Rice has pointed out on that post; it is actually helluva more difficult for the average user (with no CSS / HTML / PHP knowledge). So with regards to the end-user, I still maintain that my argument has quite a bit of truth.</description>
		<content:encoded><![CDATA[<p>As Nathan Rice has pointed out on that post; it is actually helluva more difficult for the average user (with no CSS / HTML / PHP knowledge). So with regards to the end-user, I still maintain that my argument has quite a bit of truth.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

