<font color="#333333"><font><font face="arial,helvetica,sans-serif">How about keeping all functionalities (features) intact and just extending them? User will still have all default options as well as any other "extended" stuff too. This will not "kill" what comes as standard from the core. </font></font></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">Another question: Is there a way to extend them without unregistering anything at all or this isn't possible? Justin, Chip or Otto will know this better I'm sure :)</font></font></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">Thanks,</font></font></font></div><div><font color="#333333"><font><font face="arial,helvetica,sans-serif">Emil<br>
</font></font></font><br><div class="gmail_quote">On Sat, Jun 2, 2012 at 1:30 AM, Philip M. Hofer (Frumph) <span dir="ltr"><<a href="mailto:philip@frumph.net" target="_blank">philip@frumph.net</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" dir="ltr">
<div dir="ltr">
<div style="font-size:12pt;font-family:'Calibri'">
<div>That still retains the utilization and features of the original widget as
well as the customizations of the new widget.</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> </div>
<div style="BACKGROUND:#f5f5f5">
<div><b>From:</b> <a title="konstantin@obenland.it" href="mailto:konstantin@obenland.it" target="_blank">Konstantin Obenland</a> </div>
<div><b>Sent:</b> Friday, June 01, 2012 11:19 PM</div><div class="im">
<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>
<div style="font-size:small;font-style:normal;text-decoration:none;font-family:'Calibri';display:inline;font-weight:normal"><div><div class="h5">Yeah,
I can live with that! How would you phrase that for the Theme Review Codex page?
<div> </div>
<div>
<ul>
<li>Themes may OPTIONALLY unregister core Widgets
<ul>
<li>If unregistered, Themes are REQUIRED to replace these Widgets with their
own (extended) version</li></ul></li></ul>
<div> </div>
<div>Something like that?</div>
<div>Konstantin</div>
<div> </div>
<div>
<div> </div>
<div>
<div>On 02.06.2012, at 05:20, Emil Uzelac wrote:</div><br>
<blockquote type="cite"><font color="#333333"><font face="arial,helvetica,sans-serif">So custom widget to replace a default widget
while keeping default functionalities and extending them should be good and
"removing" the core widgets without any replacement is not? If so that sounds
good to me.</font></font>
<div><font color="#333333"><font face="arial,helvetica,sans-serif"><br></font></font></div>
<div><font color="#333333"><font face="arial,helvetica,sans-serif">Emil<br></font></font><br>
<div class="gmail_quote">On Fri, Jun 1, 2012 at 9:33 PM, Merci Javier <span dir="ltr"><<a href="mailto:mercijavier@gmail.com" target="_blank">mercijavier@gmail.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote"><br>
<div class="gmail_quote">
<div>On Fri, Jun 1, 2012 at 7:35 AM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@gmail.com</a>></span> wrote:<br></div>
<div>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote"><br>Deregistering core widgets should only be done if an
enhanced version of that exact widget is registered that includes *all* of
the original widget's functionality; otherwise just register a new
*required theme-specific* widget.<br></blockquote></div></div><br>+1 on
this. I recall reviewing a theme where the Recent Posts widget was
deregistered and replaced with an "enhanced" widget with images and excerpts
but didn't include option for the basic Recent Post functionality for just
plain links.
<br><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>_______________________________________________<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><p>
</p><hr><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>
</div><p></p></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></div>