<?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: Form over Function? Never thought about it&#8230;</title>
	<atom:link href="http://www.joedolson.com/articles/2010/04/form-over-function-never-thought-about-it/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.joedolson.com/articles/2010/04/form-over-function-never-thought-about-it/</link>
	<description>Tips and Commentary on Web Accessibility, Usability, and Search Marketing best practices.</description>
	<lastBuildDate>Tue, 07 Feb 2012 10:51:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Noel Proulx</title>
		<link>http://www.joedolson.com/articles/2010/04/form-over-function-never-thought-about-it/comment-page-1/#comment-34330</link>
		<dc:creator>Noel Proulx</dc:creator>
		<pubDate>Sat, 29 May 2010 09:11:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=779#comment-34330</guid>
		<description>Now I would fall into the layman category when it comes to tweaking a WP plug in. But I will say I like the method Scorpion suggests (or perhaps I am reading it wrong). If you set up a few easy to recognize tags/variables with a few comments that state something like &quot;this is a highlighted dates color&quot; etc, it should make it easy enough to get a fair amount of customization for the WP challenged like myself. 

When it comes to almost anything I use on the web I far prefer function over eye candy, solid functional design, to me, is just far more important than the aesthetics.</description>
		<content:encoded><![CDATA[<p>Now I would fall into the layman category when it comes to tweaking a WP plug in. But I will say I like the method Scorpion suggests (or perhaps I am reading it wrong). If you set up a few easy to recognize tags/variables with a few comments that state something like &#8220;this is a highlighted dates color&#8221; etc, it should make it easy enough to get a fair amount of customization for the WP challenged like&nbsp;myself. </p>
<p>When it comes to almost anything I use on the web I far prefer function over eye candy, solid functional design, to me, is just far more important than the&nbsp;aesthetics.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scorpion</title>
		<link>http://www.joedolson.com/articles/2010/04/form-over-function-never-thought-about-it/comment-page-1/#comment-34127</link>
		<dc:creator>Scorpion</dc:creator>
		<pubDate>Tue, 11 May 2010 08:33:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=779#comment-34127</guid>
		<description>Hi there,
well it seems that you will keep the plugin up to date, first of all I would use this opportunity to thank you here!

..next I really like your plugin so I just support you with it :) A good compromise would be to have some general css tags which can be set with predefined values (e.g. clickable color-hex-code-jscript-popup-thing) for the main areas.

On the other hand you are completely right with your point that its hard to develop a plugin in good quality but also solve some stupid-style problems.

Think about some priorities! How hard is it to implement the named predefined values? What about other big issues? How many users use your plugin? And how many are contacting you in a month? Are these ones the advanced user? 
I don&#039;t know... I just can say that I really welcome the disable / reset possibility of the style and I&#039;m using my own style on 2 uses right now.</description>
		<content:encoded><![CDATA[<p>Hi there,<br />
well it seems that you will keep the plugin up to date, first of all I would use this opportunity to thank you&nbsp;here!</p>
<p>..next I really like your plugin so I just support you with it <img src='http://www.joedolson.com/articles/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  A good compromise would be to have some general css tags which can be set with predefined values (e.g. clickable color-hex-code-jscript-popup-thing) for the main&nbsp;areas.</p>
<p>On the other hand you are completely right with your point that its hard to develop a plugin in good quality but also solve some stupid-style&nbsp;problems.</p>
<p>Think about some priorities! How hard is it to implement the named predefined values? What about other big issues? How many users use your plugin? And how many are contacting you in a month? Are these ones the advanced user?<br />
I don&#8217;t know&#8230; I just can say that I really welcome the disable / reset possibility of the style and I&#8217;m using my own style on 2 uses right&nbsp;now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gaz</title>
		<link>http://www.joedolson.com/articles/2010/04/form-over-function-never-thought-about-it/comment-page-1/#comment-34096</link>
		<dc:creator>Gaz</dc:creator>
		<pubDate>Fri, 07 May 2010 06:31:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=779#comment-34096</guid>
		<description>The &quot;design test&quot; for me is quite a simple one .... if I just install the plugin and start using it, will it look out of place on screen, or can I just leave it at default for a month or two until I get time to revisit it and tweak the styling?

Often when I&#039;m building WP sites, there are so many plugins to embed, all coming from disparate sources, that the priority is to &quot;get them in and working&quot; then come back and do all the styling as a contiguous run.

Sometimes I see one pludin or theme stylesheet completely over-riding another plugin&#039;s styling.  When this happens, I shrug and mentally warn it that &quot;I&#039;ll sort you out later&quot; - sometimes it&#039;s just too timeline destructive to jump on it immediately.

When it comes to beginners though, as you say, they have little idea of where or how to fix the styling, so an admin-side option to at least set background and border colours has to be a must have item for them (there&#039;s plenty of GPL code for that which you could &quot;borrow&quot; and tweak).  Similarly, an overall height and width setting, or a widget, is probably essential for beginners nowadays - the entry level of &quot;numpty-ism&quot; seems to fall daily (yeah I know, we were all numpties at one time).

If I had to summarise, I&#039;d say design the design side for numpties, aim the features and functions at mid to upper level users, with a &quot;works out of the box&quot; default for numpties.

Gaz</description>
		<content:encoded><![CDATA[<p>The &#8220;design test&#8221; for me is quite a simple one &#8230;. if I just install the plugin and start using it, will it look out of place on screen, or can I just leave it at default for a month or two until I get time to revisit it and tweak the&nbsp;styling?</p>
<p>Often when I&#8217;m building WP sites, there are so many plugins to embed, all coming from disparate sources, that the priority is to &#8220;get them in and working&#8221; then come back and do all the styling as a contiguous&nbsp;run.</p>
<p>Sometimes I see one pludin or theme stylesheet completely over-riding another plugin&#8217;s styling.  When this happens, I shrug and mentally warn it that &#8220;I&#8217;ll sort you out later&#8221; - sometimes it&#8217;s just too timeline destructive to jump on it&nbsp;immediately.</p>
<p>When it comes to beginners though, as you say, they have little idea of where or how to fix the styling, so an admin-side option to at least set background and border colours has to be a must have item for them (there&#8217;s plenty of <abbr title="GNU General Public License">GPL</abbr> code for that which you could &#8220;borrow&#8221; and tweak).  Similarly, an overall height and width setting, or a widget, is probably essential for beginners nowadays - the entry level of &#8220;numpty-ism&#8221; seems to fall daily (yeah I know, we were all numpties at one&nbsp;time).</p>
<p>If I had to summarise, I&#8217;d say design the design side for numpties, aim the features and functions at mid to upper level users, with a &#8220;works out of the box&#8221; default for&nbsp;numpties.</p>
<p>Gaz</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Flo - Gold Coast Web Design</title>
		<link>http://www.joedolson.com/articles/2010/04/form-over-function-never-thought-about-it/comment-page-1/#comment-34023</link>
		<dc:creator>Flo - Gold Coast Web Design</dc:creator>
		<pubDate>Sun, 02 May 2010 12:18:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=779#comment-34023</guid>
		<description>I think looks are important to get you over the line. It&#039;s just like in real life...If you are selling a house and give it a new coat of paint you will have a higher chance of selling it although the core is the same. I guess the same applies to almost anything now a days. Just funcitonality doesn&#039;t count any more ... sad but true. I&#039;d be happy to style your calendar for you if you like ...</description>
		<content:encoded><![CDATA[<p>I think looks are important to get you over the line. It&#8217;s just like in real life&#8230;If you are selling a house and give it a new coat of paint you will have a higher chance of selling it although the core is the same. I guess the same applies to almost anything now a days. Just funcitonality doesn&#8217;t count any more &#8230; sad but true. I&#8217;d be happy to style your calendar for you if you like&nbsp;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JLeuze</title>
		<link>http://www.joedolson.com/articles/2010/04/form-over-function-never-thought-about-it/comment-page-1/#comment-33919</link>
		<dc:creator>JLeuze</dc:creator>
		<pubDate>Sat, 24 Apr 2010 15:28:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=779#comment-33919</guid>
		<description>There&#039;s definitely a balance to be struck. No design at all can leave mom-technical users frustrated, and too much design can leave technical users just as frustrated.

I&#039;m always pleased when I install a plugin and it has a decent minimalist design that fits in OK with that majority of themes. But some plugins take it too far and heavily over-designed. These kind of themes can be tough to integrate into a theme when you have to override all of the plugin&#039;s CSS to get it to match.

Keep up the great work on your calendar plugin Joe, this is a weak area of WordPress that I think could use some real improvement!</description>
		<content:encoded><![CDATA[<p>There&#8217;s definitely a balance to be struck. No design at all can leave mom-technical users frustrated, and too much design can leave technical users just as&nbsp;frustrated.</p>
<p>I&#8217;m always pleased when I install a plugin and it has a decent minimalist design that fits in OK with that majority of themes. But some plugins take it too far and heavily over-designed. These kind of themes can be tough to integrate into a theme when you have to override all of the plugin&#8217;s <abbr title="Cascading Style Sheets">CSS</abbr> to get it to&nbsp;match.</p>
<p>Keep up the great work on your calendar plugin Joe, this is a weak area of WordPress that I think could use some real&nbsp;improvement!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

