<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">For what it's worth:<div>By extending the core widget and registering the extending class, you can overwrite methods of the core widget class: <a href="https://gist.github.com/2851784">https://gist.github.com/2851784</a></div><div>But honestly, I think that's even worse, because now they <i>look</i> like a core widget but behave differently :)</div><div><br></div><div>Sorry, but I still don't buy in. :) Aren't we here on the functionality side of Presentation vs. Functionality? Where is the line between deregistering a core widget and removing an image size (for the lack of a better example)?</div><div>Core worked so hard on providing the ability to retain Widgets on Theme switch - and then the widgets themselves are gone...</div><div><br></div><div>Konstantin</div><div><br></div><div><br></div><div><div>On 01.06.2012, at 14:25, Chip Bennett wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Because having two Widgets with equivalent functionality is redundant and confusing, and adds to the already crowded/poor UX of the Appearance -> Widgets screen. :)<div><br></div><div>Chip<br><br><div class="gmail_quote">
On Fri, Jun 1, 2012 at 7:08 AM, Konstantin Obenland <span dir="ltr"><<a href="mailto:konstantin@obenland.it" target="_blank">konstantin@obenland.it</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">@chipbennett:<div><div>You're referring to Oenology, right?<div>Why are you deregistering the core Widgets, rather than just adding your custom ones? :)</div><div><br></div><div>@Frumph</div>
<div>What benefit does it have? Why not just <i>add</i> custom widgets to the existing ones?</div><div>I think it would affect user experience, as they might expect certain core widgets to be there, and all over sudden they're gone or their behavior changed.</div>
<span class="HOEnZb"><font color="#888888"><div><br></div><div>Konstantin</div></font></span><div><div class="h5"><div><br></div><div><br></div><div><div>On 01.06.2012, at 14:00, Philip M. Hofer (Frumph) wrote:</div><br><blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div style="font-size:12pt;font-family:'Calibri'">
<div>Q. Does it affect any plugins or other stripends if someone did deregister
and reregister their custom widgets? </div>
<div>A. No? (can’t think of any)</div>
<div> </div>
<div> </div>
<div style="font-size:small;font-style:normal;text-decoration:none;font-family:'Calibri';display:inline;font-weight:normal">
<div style="FONT:10pt tahoma">
<div><font size="3" face="Calibri"></font> </div>
<div style="BACKGROUND:#f5f5f5">
<div><b>From:</b> <a title="chip@chipbennett.net" href="mailto:chip@chipbennett.net" target="_blank">Chip Bennett</a> </div>
<div><b>Sent:</b> Friday, June 01, 2012 4:43 AM</div>
<div><b>To:</b> <a title="theme-reviewers@lists.wordpress.org" href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>
</div>
<div><b>Subject:</b> Re: [theme-reviewers] Unregistering default
widgets</div></div></div>
<div> </div></div>
<div style="font-size:small;font-style:normal;text-decoration:none;font-family:'Calibri';display:inline;font-weight:normal">Actually,
I use this. Mainly due to a lack of a better work-around (though I'm open to
ideas). I needed to modify the container markup slightly, to implement the
"show/hide" links for the Widgets. Rather than simply forking the core Widgets
as *new* Widgets, I deregister the core Widgets, and then re-register my
modified versions.
<div> </div>
<div>I don't mind using a different approach, if anyone has a good suggestion. I
mainly just don't want to load jQuery just for such a simple effect.</div>
<div> </div>
<div>Chip<br>
<div>
<div> </div>
<div class="gmail_quote">On Fri, Jun 1, 2012 at 3:19 AM, Emil Uzelac <span dir="ltr"><<a href="mailto:emil@themeid.com" target="_blank">emil@themeid.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote"><font color="#333333"><font face="arial,helvetica,sans-serif">I
am pretty sure that this would be considered as "locking" the core
functionalities and not really sure what would be the reason and scenario when
author would unregister default widget and replace them with Theme-specific.
If this is not in review and I can't find it either, well it should be for
sure. Good eye Konstantin!</font></font>
<div><font color="#333333" face="arial, helvetica, sans-serif"><br></font></div>
<div><font color="#333333" face="arial, helvetica, sans-serif">My 2c!<span><font color="#888888"><br></font></span></font><span><font color="#888888">
<div><font color="#333333"><font face="arial,helvetica,sans-serif"><br></font></font></div></font></span>
<div><span><font color="#888888"><font color="#333333"><font face="arial,helvetica,sans-serif">Emil <br></font></font></font></span>
<div>
<div>
<div> </div>
<div class="gmail_quote">On Fri, Jun 1, 2012 at 3:08 AM, Konstantin Obenland
<span dir="ltr"><<a href="mailto:konstantin@obenland.it" target="_blank">konstantin@obenland.it</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">Hi all,<br><br>I didn't find documentation on whether it
is allowed for Theme authors to unregister default widgets.<br>Is
it?<br><br>Thanks,<br>Konstantin<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>
</blockquote></div>
<div> </div></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>
<div> </div></div></div><div>
<br></div><hr>
_______________________________________________<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>
</div></div></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>
</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></div>
_______________________________________________<br>theme-reviewers mailing list<br><a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>http://lists.wordpress.org/mailman/listinfo/theme-reviewers<br></blockquote></div><br></body></html>