<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I would be on board with that too (enhancing but not combining
widgets). <br>
<br>
We should nail out a guideline for this for the 3.6 guideline
updates. Here's the text from our original guideline for this that
was never added to the theme review page:<br>
<pre style="color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">Themes may OPTIONALLY unregister core Widgets
If unregistered, Themes are REQUIRED to replace these Widgets with their own (extended) version</pre>
I think that should cover it.<br>
<br>
<div class="moz-cite-prefix">On 3/1/2013 8:14 AM, Chip Bennett
wrote:<br>
</div>
<blockquote
cite="mid:CAPdLKqfoY7h48W82aXqxqOf7Sou8Ns-oEAqJMuiya1FTMohTLg@mail.gmail.com"
type="cite">
<div dir="ltr">I agree with Cais that *enhancing* core Widgets is
one matter, and inherently acceptable, and that *combining" core
Widgets is a separate matter, and not acceptable.
<div><br>
</div>
<div style="">From the end user's perspective: changing the
active Theme should not change the list of default core
Widgets. If the user sees core "Archives" and "Recent Posts"
Widgets listed with Theme A active, the user should still see
"Archives" and "Recent Posts" Widgets listed with Theme B
active.</div>
<div style=""><br>
</div>
<div style="">This conversation has motivated me to push my
Category and Tag Widget improvements back upstream, along with
Oenology's "Post Formats" widget. If they are accepted into
core, I'd love to be able to remove them from the Theme. (Less
code to maintain FTW.)</div>
<div style=""><br>
</div>
<div style="">As for cluttering up the Widgets screen: well,
IMHO it's already a huge mess. What would a few extra Widgets
matter? :)</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">
On Fri, Mar 1, 2013 at 8:49 AM, Edward Caissie <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div>
<div>Although I did agree with the idea of replacing
default core widgets with "enhanced" versions of the
same widget, given this conversation I believe this
can be expanded upon.<br>
<br>
</div>
First, I do not agree with multiple "default" widgets
being replaced with a single "enhanced" widget. As far
as I am concerned this is not acceptable.<br>
<br>
</div>
Second, if the default widget is going to be "replaced"
it should be in the sense the new "enhanced" widget is
simply extending the default widget.<br>
Lets take the default "Categories" widget as an example,
an extended version should provide exactly the same
functionality as the default version when it is
initiated.<br>
The enhanced version then may add on top of that
functionality additional options such as an include or
exclude option, again just as an example using the
Categories widget, there are much better enhancements
that could be implemented, such as RSS feeds (h/t Chip)<br>
<br>
</div>
That being said, I also happen to agree with Otto on why
lose out on the opportunity to self-promote with a custom
widget that may be exclusive to the theme ... even adding
in three or four theme widgets will not really clutter up
the widget window that much; and, if they are prefaced
with the theme name (IIRC this is not covered in the
guidelines) they will also naturally be grouped together
as well.<span class="HOEnZb"><font color="#888888"><br>
</font></span></div>
<div class="gmail_extra"><span class="HOEnZb"><font
color="#888888"><br clear="all">
<div>Edward Caissie<br>
aka Cais.</div>
</font></span>
<div>
<div class="h5">
<br>
<br>
<div class="gmail_quote">On Fri, Mar 1, 2013 at 5:58
AM, Dane Morgan <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:dane@danemorganmedia.com"
target="_blank">dane@danemorganmedia.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div>On 2013-02-28 22:50, Otto wrote:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
On Thu, Feb 28, 2013 at 10:45 PM, Justin
Tadlock<br>
<<a moz-do-not-send="true"
href="mailto:justin@justintadlock.com"
target="_blank">justin@justintadlock.com</a>>
wrote:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
It can be an archive widget, posts widget,
or something like that. Another<br>
good example is a combination of the tags
and categories widgets into a<br>
super-cool taxonomy/terms widget. That'd
be neat to see.<br>
</blockquote>
Those should be *entirely new widgets*,
labeled with the name of the<br>
theme in front of them..<br>
<br>
Why would you be intentionally incompatible
*and* ignore freebie<br>
branding opportunities? I just don't get it
at all.<br>
<br>
-Otto<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a moz-do-not-send="true"
href="mailto:theme-reviewers@lists.wordpress.org"
target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a moz-do-not-send="true"
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</blockquote>
<br>
</div>
</div>
+1<br>
<br>
I think Otto has this one right. Maybe some users
don't agree that your enhancement is an
enhancement. Give them the option and let them try
you out, don't confuse them and take away default
choices.
<div>
<div><br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a moz-do-not-send="true"
href="mailto:theme-reviewers@lists.wordpress.org"
target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a moz-do-not-send="true"
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a moz-do-not-send="true"
href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a moz-do-not-send="true"
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>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
theme-reviewers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a>
<a class="moz-txt-link-freetext" href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</pre>
</blockquote>
<br>
</body>
</html>