Although I understand and can relate to the ideas being put forward by Chip, Emil's 2 cents make as much or more sense in the vein of the end-user should be responsible for their own content which includes letting them retain the option and responsibility of using shortcodes. As noted by Robert, there are benefits to having custom widgets in a theme as they will generally be properly tested for, or at least should be held accountable to, adhering to the theme's overall aesthetics.<br>
<br>I would only further this by saying to allow the custom widget functionality but also include sufficient (hello subjectivity *grin*) documentation so the end-user understands what may happen if the theme is changed to one that does not support these custom widgets.<br>
<br><br clear="all">Cais.<br>
<br><br><div class="gmail_quote">On Fri, Dec 30, 2011 at 10:44 PM, Emil Uzelac <span dir="ltr"><<a href="mailto:emil@themeid.com">emil@themeid.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<font color="#333333"><font><font face="arial,helvetica,sans-serif">I see what you mean Chip, I really do, however we're stepping over user's responsibilities here. Same thing will happen with i.e. "Specific Templates", not to mention widgets etc. In a perfect world yes, it would be nice to separate them, but we should not limited to that, or better yet "force" things into plugin. User's responsibility is to manage their sites and author's should keep their codes up to date, it can't get easier!</font></font></font><div>
<div><font face="arial, helvetica, sans-serif" color="#333333"><br></font></div><div><font color="#333333"><font face="arial, helvetica, sans-serif">Just my 2</font><span style="font-family:sans-serif;font-size:13px;line-height:19px;background-color:rgb(255,255,255)">˘ that's all,</span></font></div>
<div><font face="sans-serif"><span style="line-height:19px"><font color="#333333">Emil</font><br></span></font><div><font color="#333333"><font><font face="arial,helvetica,sans-serif"><br></font></font></font></div><div>
<div class="im">
<font color="#333333"><font><font face="arial,helvetica,sans-serif"><br clear="all">
</font></font></font><div><b><font face="arial, helvetica, sans-serif">----</font></b></div><div><font face="arial, helvetica, sans-serif"><b>Emil Uzelac</b> | ThemeID | T: <a href="tel:224-444-0006" value="+12244440006" target="_blank">224-444-0006</a> | 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 face="arial, helvetica, sans-serif" color="#999999">Make everything as simple as possible, but not simpler. - Albert Einstein</font></div><br>
<br><br></div><div><div class="h5"><div class="gmail_quote">On Fri, Dec 30, 2011 at 9:04 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">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">
What happens to that *content* when the user switches Themes? Buh-bye contact form, Google chart, etc.<div><br></div><div>Those shortcodes really belong in Plugins. They are content creation, not content presentation.</div>
<span><font color="#888888">
<div><br></div></font></span><div><span><font color="#888888">Chip</font></span><div><div><br><div><br><div class="gmail_quote">On Fri, Dec 30, 2011 at 8:48 PM, Emil Uzelac <span dir="ltr"><<a href="mailto:emil@themeid.com" target="_blank">emil@themeid.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<font face="arial, helvetica, sans-serif" color="#333333">Not sure, this was a quick scan-over that's all. I personally don't see anything wrong with the usage itself if they were error-free. </font><span><font color="#888888"><div>
<font face="arial, helvetica, sans-serif" color="#333333"><br>
</font></div></font></span><div><span><font color="#888888"><font face="arial, helvetica, sans-serif" color="#333333">Emil<br></font><div><font color="#333333"><font><font face="arial,helvetica,sans-serif"><br>
</font></font></font></div></font></span><div><div><font color="#333333"><font><font face="arial,helvetica,sans-serif"><br clear="all">
</font></font></font><div><b><font face="arial, helvetica, sans-serif">----</font></b></div><div><font face="arial, helvetica, sans-serif"><b>Emil Uzelac</b> | ThemeID | T: <a href="tel:224-444-0006" value="+12244440006" target="_blank">224-444-0006</a> | 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 face="arial, helvetica, sans-serif" color="#999999">Make everything as simple as possible, but not simpler. - Albert Einstein</font></div><br>
<br><br></div><div><div><div class="gmail_quote">On Fri, Dec 30, 2011 at 7:44 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">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">
Why is a Google Chart shortcode included in a *Theme*, rather than in a Plugin?<div><br></div><div>Chip<br><br><div class="gmail_quote"><div><div>On Fri, Dec 30, 2011 at 12:27 AM, Emil Uzelac <span dir="ltr"><<a href="mailto:emil@themeid.com" target="_blank">emil@themeid.com</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><font color="#333333"><font><font face="arial,helvetica,sans-serif">Reviewers,</font></font></font></div>
<font color="#333333"><font><font face="arial,helvetica,sans-serif"><div>
<font color="#333333"><font><font face="arial,helvetica,sans-serif"><br>
</font></font></font></div>In regards to: <a href="http://make.wordpress.org/themes/2011/12/15/getting-the-review-queue-back-on-track/" target="_blank">http://make.wordpress.org/themes/2011/12/15/getting-the-review-queue-back-on-track/</a> and <a href="http://codex.wordpress.org/Theme_Review#Code_Quality" target="_blank">http://codex.wordpress.org/Theme_Review#Code_Quality</a> as well, can we also make sure that <a href="http://codex.wordpress.org/Shortcode_API" target="_blank">Shortcodes</a> are checked as well? Shortcodes can produce <a href="http://php.net/manual/en/function.isset.php" target="_blank">undefined errors</a> and i.e. <a href="http://wordpress.org/extend/plugins/theme-check/" target="_blank">Theme Check</a> will find them, however only if you actually use the shortcodes on any given page/post. Good example is </font></font></font><font face="arial, helvetica, sans-serif" color="#333333"><a href="http://pastebin.com/FEGz56vu" target="_blank">http://pastebin.com/FEGz56vu</a> (Google Chart) all* Themes in repository using this or similar code will have undefined error(s). This is only an example. Some will say that this is harmless, however we still need error free Themes :)</font><div>
<font color="#333333"><font><font face="arial,helvetica,sans-serif"><br></font></font></font></div><div><font color="#333333"><font><font face="arial,helvetica,sans-serif">Thank you all for your help and Happy Holidays!</font></font></font></div>
<div><font color="#333333"><font><font face="arial,helvetica,sans-serif"><br></font></font></font></div><div><font color="#333333"><font><font face="arial,helvetica,sans-serif">Emil</font></font></font></div><div><font color="#333333"><font><font face="arial,helvetica,sans-serif"><br clear="all">
</font></font></font><div><b><font face="arial, helvetica, sans-serif">----</font></b></div><span><font color="#888888"><div><font face="arial, helvetica, sans-serif"><b>Emil Uzelac</b> | ThemeID | T: <a href="tel:224-444-0006" value="+12244440006" target="_blank">224-444-0006</a> | 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 face="arial, helvetica, sans-serif" color="#999999">Make everything as simple as possible, but not simpler. - Albert Einstein</font></div><br>
</font></span></div>
<br></div></div>_______________________________________________<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></blockquote></div><br></div>
<br>_______________________________________________<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></blockquote></div><br></div></div></div></div>
<br>_______________________________________________<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></blockquote></div><br></div></div></div></div>
<br>_______________________________________________<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></blockquote></div><br></div></div></div></div></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>