Don't worry; I've got other code to finish writing first (Theme activation/deactivation hooks, for one thing). But, I'd like to get an idea of what, with respect to core code, such a pitch will involve. (I've always understood the biggest changes to be in the API rather than core.)<div>
<br></div><div>Chip<br><br><div class="gmail_quote">On Tue, Jul 5, 2011 at 10:10 AM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com">otto@ottodestruct.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I wouldn't start writing code just yet. It needs to be pitched first.<br>
<br>
It's probably not all that difficult to add, actually. But because of<br>
the need for API support (not to mention adding readme.txt parsing in<br>
the theme directory), it's one of those "large" features that needs<br>
core dev buy-in first.<br>
<font color="#888888"><br>
-Otto<br>
</font><div><div></div><div class="h5"><br>
<br>
<br>
On Tue, Jul 5, 2011 at 9:56 AM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br>
> Otto,<br>
> If you can point me in the right direction in core for the Plugin-related<br>
> functionality, I'll try to get the ball rolling.<br>
> I assume there's an update.php or upgrade.php or somesuch, but I've never<br>
> delved into that part of core...<br>
> Chip<br>
><br>
> On Tue, Jul 5, 2011 at 9:51 AM, Otto <<a href="mailto:otto@ottodestruct.com">otto@ottodestruct.com</a>> wrote:<br>
>><br>
>> On Tue, Jul 5, 2011 at 2:08 AM, Syahir Hakim <<a href="mailto:khairulsyahir@gmail.com">khairulsyahir@gmail.com</a>><br>
>> wrote:<br>
>> > Hi everyone,<br>
>> ><br>
>> > Is there a way to add a little note on the WordPress Updates admin<br>
>> > screen<br>
>> > under the updates notification for themes listed on the repository?<br>
>> > Something like this: <a href="http://tinypic.com/r/ir6r7b/7" target="_blank">http://tinypic.com/r/ir6r7b/7</a><br>
>><br>
>> No. However something like this would be a core modification to<br>
>> support it, as well as work on the backend <a href="http://wordpress.org" target="_blank">wordpress.org</a> api code and<br>
>> themes directory to allow for readme.txt files and parsing and such.<br>
>><br>
>> Discussion is about to begin surrounding 3.3 features. This would be a<br>
>> good time to pitch such an idea for 3.3 development.<br>
>><br>
>> -Otto<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>
><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>
><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>
</div></div></blockquote></div><br></div>