cubicweb-blog #1337569 Implement the Metaweblog API [open]
http://www.xmlrpc.com/metaWeblogApi http://en.wikipedia.org/wiki/MetaWeblog This is an API which works with a bunch of blog authoring tools. This could be a way of making it easier to include images in posts without having to upload them first then copy the URL etc... Firefox extensions scribefire : http://www.scribefire.com/ works well with it and is really usable. | |
| priority | normal |
|---|---|
| type | enhancement |
| done in | <not specified> |
| closed by | <not specified> |
similar entities
- cubicweb-tracker #1484254 visual distinction between bug / enhancement
- cubicweb-tracker #636937 clear visual difference between open and closed ticket
- cubicweb #2363313 _cw gets hosed after a .commit()
- 1 to 1 relationships and subresources in REST APIs | Technology on Heels with Lyst Engineering (http://developers.lyst.com/2015/02/20/1-to-1-relationships-and-subresources-in-rest-apis/)
- cubicweb #5414757 [dataimport] more api specification
[see all]
Comments
-
2010/10/19 13:16, written by nchauvat
-
2010/10/25 11:58, written by alutz
-
2010/10/25 17:02, written by nchauvat
add commentIn general, I will vote -1 on implementing API. we need to export/import more data, not to conform to more APIs.
using API help us benefit from the ecosystem of applications that use web services. For example implementing RSS feeds makes cubicweb usable with all RSS feed readers.
This is an input API, facilitating the addition of content to a cubicweb instance.
RSS is not an API. It is a data format. +1 for RSS and in general, -1 for APIs. The universal API of the Web is the set of HTTP verbs. Think REST.