Is there any easy way to get information developed in the wiki transferred to Word? Could content even be synchronized?

I think it shouldn't be really difficult to write a vbs macro on a word that would call the "GETages/{pageid}/export" api call and write the output to the word document...

First, you must export the page you want to convert to html. For example, if we want to export http://wiki.opengarden.org/Deki_Wiki:

curl -b cookies.txt "http://wiki.opengarden.org/@api/deki/pages/=DekiWiki/export?format=html" > c:\dekiwiki.html

And the we will use vbscript to convert the html output to a word document:

Set Word = CreateObject("Word.Application")
Set Doc = Word.Documents.Open("c:\dekiwiki.html")
Doc.SaveAs "c:\dekiwiki.doc",wdFormatDocument
Word.Quit

I'm using Office 2007 and it works without problem, I suppose older Office version will work too.
This is just a quick hack, but maybe you can start with this...

Sweet. I would think that with a bit more effort you could even bypass the curl command and directly load the HTML directly from within word.

The problem you WILL run into is that Word (even Word 2007) does not produce standards compliant html output, even if you use the clean html file save option. I found that when cutting and pasting html coding from Word docs that Deki Wiki will not translate everything correctly when making a conversion to xhtml. You can read a lot about MS html standards compliance issues if you search google.

With the latest release, it's easy to include any PHP application without adding overhead to Deki Wiki by using our /@gui/ URL. It could be feasible to add a feature here which would accept data, run it through a Word HTML cleaning PHP application (I've seen many), then pass it to the API. If somebody can provide the knowledge on the Word side to POST/PUT documents to a location, I'd be willing to volunteer my resources on adding the PHP side to accept the data.

royk,
what's the /@gui/ URL? I don't find info of it...

It's lightly documented. It's a second entry point into the PHP application which doesn't load up the whole Deki Wiki application when you hit it. This is primarily being used right now for our new link and image dialogs - it allows us to execute quick API calls and do transformations on the data while keeping server load to a minimum.

We'll document it shortly.

So, if I'm understading it, I could put there my own php files and execute them from there?
This could be useful when writing php extensions...

Hey doop,

I've written up some documentation on /@gui/. It's grown organically for a specific purpose, so it might require some tweaking to get it to work exactly as users want it.

I'm not sure if it'll work with extensions, as it was designed to remix data from the API in a speedy way to allow us to develop rich interfaces (the new dialogs make heavy use of /@gui/).

Let me know if you have any thoughts about modifying this for other uses.