just thought I would throw this out there and plant the seed so to speak:
http://windowslivewriter.spaces.live.com/blog/cns!D85741BB5E0BE8AA!174.entry

It doesn't. About one and a half year ago I asked on the yahoo mailinglist if anyone was up for it, but I wasn't able to delegate the project. I've done a little bit of test coding, I know that Darren did some but nothing finished has been done yet.

I love the idea about supporting these apis, especially if it could be done in a generic way like my RSS package. The problem with the blogging api's is that they're meant for - hey blogging! A follows a non hierachical structure, and therefore these tree's doesn't support umbracos tree structure. This is why a generic approach would be cool.

Here's how I imagine it could work when you create a blog api instance:
1) Name your api and choose the user account(s) to be used. Note here that a user account could only be used for one blog (maybe the api's supports multiple blogs for one user, I'm not sure)
2) Select a root node in the tree structure where the api should be used
3) Select either "only subnodes below this level" or "all subnodes no matter level filtered by a document type)". This would allow all doc items to be edited no matter if they're in a tree structure (like blog or news items that are moved in date/category folders)
4) Select the document type that should be used for creating/editing and map the generic properties in umbraco to the api properties.

This way the api's could be used for both blogging, but also open up for editing normal pages or news items (at least parts of them due the limitations in the apis) in Word and other tools that supports the apis.

I'd be happy to do the UI coding including setting up these api mappings if someone would do the api support.

Let me know your thoughts :-)

/n

---

Jeeeez, did I really start this :-)