[wp-xmlrpc] GSOC Proposal - Extending WordPress Remote API
n.prasath.002 at gmail.com
Wed Mar 23 11:25:40 UTC 2011
I did'nt understand what your saying
wp.editCategory is missing and i have added a patch for that.
wp.newCategory, wp.deleteCategory is already there.
wp.getCategories is replaced by mw_getCategories
wp.getCategory is an option but normally there a few categories in a blog
and mw_getCategories can do the job
On Wed, Mar 23, 2011 at 4:14 PM, Baptiste Bernard <
baptiste.bernard at utopiaweb.fr> wrote:
> Hi all,
> CRUD of categories could be great too !
> No way to edit a category atm :'( so We can edit the "default" category
> through api :/ (was forgotten by developpers a priori)
> - wp.newCategory
> - wp.editCategory
> - wp.deleteCategory
> - wp.getCategory
> - wp.getCategories
> 2011/3/23 prasath nadarajah <n.prasath.002 at gmail.com>
>> Hi Jorge
>> Thanks for the feedback!!!
>> I would really love to see what the mobile team is expecting in XMLRPC
>> I will include these idea in my proposal.
>> I posted a draft proposal with the new API in my blog.
>> check it there and drop comments.
>> On Tue, Mar 22, 2011 at 7:53 PM, Jorge Bernal <jorge at automattic.com>wrote:
>>> Sounds great, XMLRPC could use some love ;)
>>> I plan to gather some ideas for improvements from the mobile team in
>>> the following weeks.
>>> Besides adding missing features, my main concern right now is trying
>>> to reduce redundant calls and minimize traffic: I'd bet nobody was
>>> thinking of 3G when the api was invented.
>>> Some ideas for now:
>>> * Add a "since" attribute to methods like wp.getRecentPosts,
>>> wp.getComments, so we can check for new stuff without downloading
>>> everything again. Started at
>>> * wp.getLatestActivity - get posts/comments since a given date. Maybe
>>> even add categories or anything that changed, so syncing would involve
>>> one call only
>>> * wp.quickPost - merge newPost and newMediaObject, so publishing a
>>> picture can be done with just one call. Maybe quickPost is not the
>>> best name for it, but roughly that's the idea
>>> As for obsolete APIs, many of the wp.* methods use the mw, mt, or
>>> blogger implementations. Nothing should be removed to maintain
>>> compatibility, but the wp.* API should be able to leave those
>>> implementations behind
>>> On Sat, Mar 19, 2011 at 7:01 PM, prasath nadarajah
>>> <n.prasath.002 at gmail.com> wrote:
>>> > Hi hackers,
>>> > I,m interested in working on extending WordPress xmlrpc capabilities
>>> > this years GSOC. I came up with some ideas for improving the current
>>> > Please let me know what you think of these ideas and possible additions
>>> > this project. Thank You.
>>> Jorge Bernal | jbernal at gmail.com | jorge at automattic.com
>>> Mobile Engineer @ Automattic | http://automattic.com/
>>> http://jorgebernal.info/ | http://jorgebernal.es/ |
>>> wp-xmlrpc mailing list
>>> wp-xmlrpc at lists.automattic.com
>> wp-xmlrpc mailing list
>> wp-xmlrpc at lists.automattic.com
> wp-xmlrpc mailing list
> wp-xmlrpc at lists.automattic.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the wp-xmlrpc