<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body wsmode="reply" text="#000000" bgcolor="#FFFFFF">
    Yup thought it was familiar. I would think that a seamless extension
    of existing widgets and shortcodes would be preferable to a theme
    implementing custom widgets and shortcodes - which would break if
    the theme was switched.<br>
    <br>
    Theme authors would, of course, have to update these widgets when
    new versions of WordPress roll out, to accommodate changes in the
    core functionality.<br>
    <br>
    Paul Appleyard<br>
    <br>
    <div class="moz-cite-prefix">On 1/03/2013 11:06 AM, Emil Uzelac
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAEytdhfPXqKVfjKsyX1FgNa4Y2s8Cx1xoo5tUm7QD=ukxLNvRA@mail.gmail.com"
      type="cite">
      <div dir="ltr">Not really sure if this was decided or not, but we
        talked about this for sure.
        <div style="">Please see:&nbsp;<a moz-do-not-send="true"
href="http://lists.wordpress.org/pipermail/theme-reviewers/2012-June/009455.html">http://lists.wordpress.org/pipermail/theme-reviewers/2012-June/009455.html</a></div>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Thu, Feb 28, 2013 at 6:26 PM, Justin
          Tadlock <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:justin@justintadlock.com" target="_blank">justin@justintadlock.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">It is OK.
            &nbsp;This was decided by the theme review team last year:<br>
            <a moz-do-not-send="true"
href="http://lists.wordpress.org/pipermail/theme-reviewers/2012-June/009450.html"
              target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/2012-June/009450.html</a>
            <div class="HOEnZb">
              <div class="h5">
                <br>
                <br>
                On 2/28/2013 6:18 PM, Paul Appleyard wrote:<br>
                <blockquote class="gmail_quote" style="margin:0 0 0
                  .8ex;border-left:1px #ccc solid;padding-left:1ex">
                  I thought it was OK to extend core functionality - as
                  long as it RETAINED the original functionality; ie
                  didn't break when they switched themes. So, replacing
                  a widget with a custom one of the same name that had
                  the original functionality but with some added powers.<br>
                  <br>
                  Paul<br>
                  <br>
                  On 1/03/2013 9:34 AM, 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 5:14 PM, Justin Tadlock<br>
                    &lt;<a moz-do-not-send="true"
                      href="mailto:justin@justintadlock.com"
                      target="_blank">justin@justintadlock.com</a>&gt;
                    wrote:<br>
                    <blockquote class="gmail_quote" style="margin:0 0 0
                      .8ex;border-left:1px #ccc solid;padding-left:1ex">
                      I disagree. &nbsp;If we don't want developers ...<br>
                    </blockquote>
                    There is more than one type of developer.<br>
                    <br>
                    Removing widgets makes perfect sense to be available
                    for plugins<br>
                    territory. Doesn't make sense for themes. Yet
                    another form of<br>
                    vendor-lock-in.<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>
                  _______________________________________________<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>
                _______________________________________________<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>
      <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>