{
"attachments": [],
"comments_archived": true,
"date": "2003-11-19T01:36:31.000Z",
"layout": "post",
"title": "VoodooPad gets an XML-RPC wiki API",
"wordpress_id": 507,
"wordpress_slug": "voodoo-pad-wiki-api",
"wordpress_url": "http://www.decafbad.com/blog/?p=507",
"year": "2003",
"month": "11",
"day": "18",
"isDir": false,
"slug": "voodoo-pad-wiki-api",
"type": "entry",
"postName": "2003-11-18-voodoo-pad-wiki-api",
"html": "You wanted to share the same documents with your coworkers and friends. Now you can.\n\nWith VoodooPad 1.1, you can view, edit, and save to any wiki that supports the 'vpwiki api'.
\n\n\n\n\n<p>Funny, I’ve been tinkering with <a href=\"http://www.decafbad.com/twiki/bin/view/Main/XmlRpcToWiki\">a wiki <span class=\"caps\">API</span></a> along with a <a href=\"http://www.jspwiki.org/Wiki.jsp?page=WikiRPCInterface\">few others tinkerers</a> for a year or so now. I wonder if we could get these APIs merged or synched and give VoodooPad access to a slew of wikiware?</p>\n
\n\n\n\nshortname=voodoo_pad_wiki_api
\n\n\n\n",
"body": "You wanted to share the same documents with your coworkers and friends. Now you can.\r\n\r\nWith VoodooPad 1.1, you can view, edit, and save to any wiki that supports the 'vpwiki api'.
\r\n\r\n\r\n\tFunny, I’ve been tinkering with a wiki API along with a few others tinkerers for a year or so now. I wonder if we could get these APIs merged or synched and give VoodooPad access to a slew of wikiware?
\r\n\r\nshortname=voodoo_pad_wiki_api\r\n\r\n\r\n ",
"parentPath": "./content/posts/archives/2003",
"path": "2003/11/18/voodoo-pad-wiki-api",
"summary": "You wanted to share the same documents with your coworkers and friends. Now you can.\n\nWith VoodooPad 1.1, you can view, edit, and save to any wiki that supports the 'vpwiki api'.\nSource:Flying Meat Software\n\n\n\n\n\nFunny, I’ve been tinkering with a wiki API along with a few others tinkerers for a year or so now. I wonder if we could get these APIs merged or synched and give VoodooPad access to a slew of wikiware?
",
"needsBuild": true,
"prevPostPath": "2003/11/16/the-recipe-web-2",
"prevPostTitle": "Building the Recipe Web II",
"nextPostPath": "2003/11/20/recipe-web-3",
"nextPostTitle": "Building the Recipe Web III"
} ![](\"http://www.gravatar.com/avatar.php?gravatar_id=6492f173a7059ece309f7d670ff44e95&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\"/)
\r\n nf0\r\n Its pretty cool a few weeks ago I loaded there wiki on my powerbook and was editing it from my Win2k laptop in a browser. It was pretty cool, now if Twiki would support that API It would make it all even better, I'm sure the power of perl can make it happen.\r\n \r\n \r\n \r\n ![](\"http://www.gravatar.com/avatar.php?gravatar_id=2e83224d92ed7f1148f4dd3cdb0e4548&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\"/)
\r\n Bill Seitz\r\n Kinda assumes that all wikis use the same SmartAscii format, eh?\r\n\r\nhttp://webseitz.fluxent.com/wiki/SmartAscii\r\nhttp://webseitz.fluxent.com/wiki/WikiStandards\r\n \r\n \r\n \r\n ![](\"http://www.gravatar.com/avatar.php?gravatar_id=2ac2cffd36ada8c734b90e02a1e5c1ac&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\"/)
\r\n l.m.orchard\r\n It's worse than that: VoodooPad uses RTF for its internal wiki format and plaintext for export to wiki. Though, I think when pairing up VoodooPad with some specific wiki, it wouldn't be too annoying to use that wiki's SmartAscii in VoodooPad. I doubt that converting between RTF and a particular implementation of SmartAscii would be a very enjoyable endeavor.\r\n \r\n \r\n \r\n ![](\"http://www.gravatar.com/avatar.php?gravatar_id=8f688c7919a6645352e1bb59b2f45ae4&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\"/)
\r\n Janne Jalkanen\r\n Yeah, we discussed the original wiki API with the author of VoodooPad, but his requirements were sufficiently different so that we couldn't agree on a common API.\r\n\r\nI think the key issues were around using HTTP authentication and the format of the wiki.\r\n\r\nThe divergence of the Wiki APIs is emblematic to the divergence of the entire Wiki community. Not that it's necessarily a bad thing.\r\n \r\n \r\n \r\n ![](\"http://www.gravatar.com/avatar.php?gravatar_id=ffca18b21e33769cc792a9f73d0b5a75&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\"/)
\r\n Harald Scheirich\r\n Hi, I am the author of PersonalWiki (for OS X) I am looking into implementing the wiki XMLRPC interface into my product, I am open for suggestions. PersonalWiki is based on ASCII input formats. Currently Supported are StructuredText (ZWiki) and Wikipedia. I also did my own implementation for communicating with ZWiki but a more \"standard\" solution would be nice.\r\n\r\nThe difference between different Wiki's input formatting is a pain I think it is not really a good thing\r\n \r\n \r\n \r\n
Archived Comments
\n\n- \n
\n\n![](\"http://www.gravatar.com/avatar.php?gravatar_id=6492f173a7059ece309f7d670ff44e95&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\")
\nnf0\n \n\n\n \n\n\nIts pretty cool a few weeks ago I loaded there wiki on my powerbook and was editing it from my Win2k laptop in a browser. It was pretty cool, now if Twiki would support that API It would make it all even better, I'm sure the power of perl can make it happen. \n\n\n \n- \n
\n\n![](\"http://www.gravatar.com/avatar.php?gravatar_id=2e83224d92ed7f1148f4dd3cdb0e4548&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\")
\nBill Seitz\n \n\n\n \n\n\nKinda assumes that all wikis use the same SmartAscii format, eh?\nhttp://webseitz.fluxent.com/wiki/SmartAscii\nhttp://webseitz.fluxent.com/wiki/WikiStandards \n\n\n \n- \n
\n\n![](\"http://www.gravatar.com/avatar.php?gravatar_id=2ac2cffd36ada8c734b90e02a1e5c1ac&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\")
\nl.m.orchard\n \n\n\n \n\n\nIt's worse than that: VoodooPad uses RTF for its internal wiki format and plaintext for export to wiki. Though, I think when pairing up VoodooPad with some specific wiki, it wouldn't be too annoying to use that wiki's SmartAscii in VoodooPad. I doubt that converting between RTF and a particular implementation of SmartAscii would be a very enjoyable endeavor. \n\n\n \n- \n
\n\n![](\"http://www.gravatar.com/avatar.php?gravatar_id=8f688c7919a6645352e1bb59b2f45ae4&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\")
\nJanne Jalkanen\n \n\n\n \n\n\nYeah, we discussed the original wiki API with the author of VoodooPad, but his requirements were sufficiently different so that we couldn't agree on a common API.\nI think the key issues were around using HTTP authentication and the format of the wiki.\nThe divergence of the Wiki APIs is emblematic to the divergence of the entire Wiki community. Not that it's necessarily a bad thing. \n\n\n \n- \n
\n\n![](\"http://www.gravatar.com/avatar.php?gravatar_id=ffca18b21e33769cc792a9f73d0b5a75&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\")
\nHarald Scheirich\n \n\n\n \n\n\nHi, I am the author of PersonalWiki (for OS X) I am looking into implementing the wiki XMLRPC interface into my product, I am open for suggestions. PersonalWiki is based on ASCII input formats. Currently Supported are StructuredText (ZWiki) and Wikipedia. I also did my own implementation for communicating with ZWiki but a more \"standard\" solution would be nice.\nThe difference between different Wiki's input formatting is a pain I think it is not really a good thing \n\n\n \n
\n\n\n\n
\n
\n
\n
\n