<font color="#333333"><font size="2"><font face="arial,helvetica,sans-serif">Fine by me :)<br clear="all"></font></font></font><div><strong><font face="arial, helvetica, sans-serif">----</font></strong></div><div><font face="arial, helvetica, sans-serif"><strong>Emil Uzelac</strong> | ThemeID | T: 224-444-0006 | Twitter: @EmilUzelac | E: <a href="mailto:emil@themeid.com" target="_blank">emil@themeid.com</a> | <a href="http://themeid.com/" target="_blank">http://themeid.com</a></font></div>
<div><font color="#999999" face="arial, helvetica, sans-serif">Make everything as simple as possible, but not simpler. - Albert Einstein</font></div><br>
<br><br><div class="gmail_quote">On Wed, May 11, 2011 at 5:46 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I don't think we should hold ourselves to the standard of having to write a rule for every conceivable thing that can possibly be done. On one hand, we want to ensure due diligence in establishing objective guidelines. On the other hand, we want to avoid regulatory overkill. We want the US Constitution, not the US tax code.<div>
<br></div><div>In this case, I think that it is safe to say, "we won't allow that", whether we add it to the Guidelines or not. The Theme preview needs to use the core/stock previewer, and NOT redirect to some arbitrary, uncontrolled, third-party URL. The previewer ensures that Themes can be previewed/compared using the same data set, allowing for a reasonably equal comparison. Besides that, the potential for abuse is just too great. </div>
<div><br></div><div>If the Theme previewer needs to be fixed/improved, then let's do that. If Theme developers want to provide an alternate demo for their Theme, that shows off all of the bells and whistles, they can provide a demo link in the Theme description, or in the Theme's admin page, etc.</div>
<div><br></div><div><font color="#888888">Chip<br><br></font><div class="gmail_quote"><div><div></div><div class="h5">On Wed, May 11, 2011 at 5:16 PM, Curtis McHale <span dir="ltr"><<a href="mailto:curtis@curtismchale.ca" target="_blank">curtis@curtismchale.ca</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div class="h5">
<div>
<div>
<span>So we should probably write a rule requiring the stock preview is used and then work to improve it rather then allowing it now and dealing with the possible bad fallout.<br>
</span><div>
<span><br>-- <br>Curtis McHale<div>SFNdesign<br><a href="tel:604.751.3482" value="+16047513482" target="_blank">604.751.3482</a><div><a href="http://curtismchale.ca" target="_blank">http://curtismchale.ca</a></div>
<div><a href="http://twitter.com/curtismchale" target="_blank">http://twitter.com/curtismchale</a></div></div></span>
</div></div>
</div><br></div></div><div class="im">_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></div></blockquote></div><br></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br>