Bruce there is some internal discussion going on already about clarification of the verbiage of the plugin in light of the fact that you are a longer term developer, thus the issue has more weight than someone just starting out. Not sure what will come of it but there is some already going on.<div>
<br></div><div>Further thoughts on how it could be clarified would be welcome by myself at least.<br clear="all"><br>Curtis McHale<br>PH: 604.751.3482<br><a href="http://www.curtismchale.ca">http://www.curtismchale.ca</a><br>
Linkedin: <a href="http://www.linkedin.com/in/curtismchale">http://www.linkedin.com/in/curtismchale</a><br>Twitter: <a href="http://twitter.com/curtismchale">twitter.com/curtismchale</a><br><br>
<br><br><div class="gmail_quote">On Sat, Jun 25, 2011 at 10:48 AM, Bruce Wampler <span dir="ltr"><<a href="mailto:brucewampler@gmail.com">brucewampler@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Sorry, Otto, I can't help myself here - I'm sure I'm going to piss you off, you you<br>
really need an attitude change when it comes to understanding how to write<br>
user interfaces, and to interact with users.<br>
<br>
WordPress lives because of the contributions of its user base, including both<br>
main line developers, and theme writers. I am a very long time software developer.<br>
I may sometimes stick to tried and true methods, but I seldom do it without<br>
consulting current examples of code.<br>
<br>
But to dismiss my claims that the interface to Theme Check is confusing is<br>
really insulting, and ignoring the input of someone who has learned a lot<br>
over the years about dealing with users.<br>
<br>
First of all, I've been submitting versions of Weaver for over a year. Probably<br>
at least 10 versions in that time. Just a year. And I know for a fact, that at<br>
least 5 or 6 of those times, the theme requirements have changed in such a<br>
fashion to require me to change the theme to meet them. So don't tell me that<br>
the requirements don't change that often. I have personally seen that they do.<br>
Well I consider 5 or 6 significant changes in a year a lot.<br>
<br>
And don't tell me that tracking the changes at some obscure URL:<br>
<br>
<a href="http://plugins.trac.wordpress.org/log/theme-check" target="_blank">http://plugins.trac.wordpress.<u></u>org/log/theme-check</a><br>
<br>
is a obvious place to find all the new theme requirement changes. That's<br>
obvious. What would constitute obscure?<br>
<br>
And maybe the INTENT was to always have WARNING block themes, but<br>
when I submitted the last version, which only in March this year, WARNINGS<br>
did NOT cause a theme to be rejected. March is not that long ago.<br>
<br>
And why does red make anything special? In all my years of programming,<br>
a WARNING has never been considered fatal for anything. It is a WARNING, no<br>
matter what the color. It is not obvious at all that it is a fail, even if it is red.<br>
<br>
And if the Theme Check is the same for the plugin (which I use constantly,<br>
by the way) as the upload site, why does the upload site so clearly use the<br>
word FAIL, and that never appears in the plugin version.<br>
<br>
I imagine you are an experience programmer, but I'm afraid you've not learned<br>
a very fundamental lesson when dealing with people who use your software:<br>
<br>
There are no dumb questions, and when a user gives a sincere and serious<br>
comment about your software's user interface, you don't insult them and<br>
dismiss their comment with "IT WAS RED".<br>
<br>
<br>
Sorry if I've pissed you off, Otto, but you need to take some of these questions<br>
a little more seriously, and stop dismissing them with your so-called<br>
superior knowledge.<br>
<br>
<br>
-- <br>
-----------<br>
Bruce Wampler, Ph.D.<br>
<br>
Software developer<br>
Creator of first spelling checker for a PC<br>
Creator of Grammatik(tm), first true grammar checker<br>
e-mail: bw at <a href="http://brucewampler.com" target="_blank">brucewampler.com</a><br>
blog: <a href="http://brucewampler.wordpress.com" target="_blank">brucewampler.wordpress.com</a><br>
<br>
______________________________<u></u>_________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u></u>reviewers</a><br>
</blockquote></div><br></div>