No subject
Wed Oct 24 21:06:28 UTC 2012
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.
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.)
As for cluttering up the Widgets screen: well, IMHO it's already a huge
mess. What would a few extra Widgets matter? :)
On Fri, Mar 1, 2013 at 8:49 AM, Edward Caissie <edward.caissie at gmail.com>wrote:
> 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.
>
> 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.
>
> 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.
> 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.
> 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)
>
> 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.
>
> Edward Caissie
> aka Cais.
>
>
> On Fri, Mar 1, 2013 at 5:58 AM, Dane Morgan <dane at danemorganmedia.com>wrote:
>
>> On 2013-02-28 22:50, Otto wrote:
>>
>>> On Thu, Feb 28, 2013 at 10:45 PM, Justin Tadlock
>>> <justin at justintadlock.com> wrote:
>>>
>>>> It can be an archive widget, posts widget, or something like that.
>>>> Another
>>>> good example is a combination of the tags and categories widgets into a
>>>> super-cool taxonomy/terms widget. That'd be neat to see.
>>>>
>>> Those should be *entirely new widgets*, labeled with the name of the
>>> theme in front of them..
>>>
>>> Why would you be intentionally incompatible *and* ignore freebie
>>> branding opportunities? I just don't get it at all.
>>>
>>> -Otto
>>> ______________________________**_________________
>>> theme-reviewers mailing list
>>> theme-reviewers at lists.**wordpress.org<theme-reviewers at lists.wordpress.org>
>>> http://lists.wordpress.org/**mailman/listinfo/theme-**reviewers<http://lists.wordpress.org/mailman/listinfo/theme-reviewers>
>>>
>>
>> +1
>>
>> 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.
>>
>> ______________________________**_________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.**wordpress.org<theme-reviewers at lists.wordpress.org>
>> http://lists.wordpress.org/**mailman/listinfo/theme-**reviewers<http://lists.wordpress.org/mailman/listinfo/theme-reviewers>
>>
>
>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
--e89a8f22c38112933904d6dd9fe3
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">I agree with Cais that *enhancing* core Widgets is one mat=
ter, 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 li=
st of default core Widgets. If the user sees core "Archives" and =
"Recent Posts" Widgets listed with Theme A active, the user shoul=
d still see "Archives" and "Recent Posts" Widgets liste=
d 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&=
#39;s "Post Formats" widget. If they are accepted into core, I=
9;d love to be able to remove them from the Theme. (Less code to maintain F=
TW.)</div>
<div style><br></div><div style>As for cluttering up the Widgets screen: we=
ll, IMHO it's already a huge mess. What would a few extra Widgets matte=
r? :)</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quo=
te">
On Fri, Mar 1, 2013 at 8:49 AM, Edward Caissie <span dir=3D"ltr"><<a hre=
f=3D"mailto:edward.caissie at gmail.com" target=3D"_blank">edward.caissie at gmai=
l.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><div><div><div>Although I did agree with the idea of repla=
cing default core widgets with "enhanced" versions of the same wi=
dget, 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 concern=
ed this is not acceptable.<br><br></div>Second, if the default widget is go=
ing to be "replaced" it should be in the sense the new "enha=
nced" widget is simply extending the default widget.<br>
Lets take the default "Categories" widget as an example, an exten=
ded version should provide exactly the same functionality as the default ve=
rsion 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 bette=
r 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 exclus=
ive to the theme ... even adding in three or four theme widgets will not re=
ally 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=3D"HOEnZb"><font color=
=3D"#888888"><br>
</font></span></div><div class=3D"gmail_extra"><span class=3D"HOEnZb"><font=
color=3D"#888888"><br clear=3D"all"><div>Edward Caissie<br>aka Cais.</div>=
</font></span><div><div class=3D"h5">
<br><br><div class=3D"gmail_quote">On Fri, Mar 1, 2013 at 5:58 AM, Dane Mor=
gan <span dir=3D"ltr"><<a href=3D"mailto:dane at danemorganmedia.com" targe=
t=3D"_blank">dane at danemorganmedia.com</a>></span> wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"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=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On Thu, Feb 28, 2013 at 10:45 PM, Justin Tadlock<br>
<<a href=3D"mailto:justin at justintadlock.com" target=3D"_blank">justin at ju=
stintadlock.com</a>> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
It can be an archive widget, posts widget, or something like that. =A0Anoth=
er<br>
good example is a combination of the tags and categories widgets into a<br>
super-cool taxonomy/terms widget. =A0That'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>
______________________________<u></u>_________________<br>
theme-reviewers mailing list<br>
<a href=3D"mailto:theme-reviewers at lists.wordpress.org" target=3D"_blank">th=
eme-reviewers at lists.<u></u>wordpress.org</a><br>
<a href=3D"http://lists.wordpress.org/mailman/listinfo/theme-reviewers" tar=
get=3D"_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u>=
</u>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 o=
ut, don't confuse them and take away default choices.<div>
<div><br>
______________________________<u></u>_________________<br>
theme-reviewers mailing list<br>
<a href=3D"mailto:theme-reviewers at lists.wordpress.org" target=3D"_blank">th=
eme-reviewers at lists.<u></u>wordpress.org</a><br>
<a href=3D"http://lists.wordpress.org/mailman/listinfo/theme-reviewers" tar=
get=3D"_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u>=
</u>reviewers</a><br>
</div></div></blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href=3D"mailto:theme-reviewers at lists.wordpress.org">theme-reviewers at list=
s.wordpress.org</a><br>
<a href=3D"http://lists.wordpress.org/mailman/listinfo/theme-reviewers" tar=
get=3D"_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers<=
/a><br>
<br></blockquote></div><br></div>
--e89a8f22c38112933904d6dd9fe3--
More information about the theme-reviewers
mailing list