{"id":292,"date":"2007-03-11T15:54:16","date_gmt":"2007-03-11T22:54:16","guid":{"rendered":"http:\/\/www.red-sweater.com\/blog\/292\/marsedit-for-your-custom-blog"},"modified":"2012-04-25T07:47:40","modified_gmt":"2012-04-25T11:47:40","slug":"marsedit-for-your-custom-blog","status":"publish","type":"post","link":"https:\/\/redsweater.com\/blog\/292\/marsedit-for-your-custom-blog","title":{"rendered":"MarsEdit For Your Custom Blog"},"content":{"rendered":"

Although the vast majority of MarsEdit<\/a> users are using it to manage posts on one of the big publicly available blogging systems, there are a good number of users, especially in the tech community, who run their own custom blog or blog-like software. I’ve received several private inquiries and this public one<\/a>, all asking about the steps required to get MarsEdit working with a custom piece of hosting software.<\/p>\n

\nMany have suggested that it would help for MarsEdit to support some kind of plugin system whereby custom software authors could develop a script or piece of code to help MarsEdit interface with the site. This general line of thinking is the right one, but the plugin is probably more appropriate for the server<\/em> than for the client.\n<\/p>\n

\nSo how do you get MarsEdit working with your custom server software? You adopt a standard API and implement it for your site, in the form of a “xmlrpc.php” type file that accepts POST requests from MarsEdit and returns the appropriate responses. This isn’t as hard as it sounds, because there are really only a few calls involved. And after all, I assume if you’ve got a custom solution already, you know your way around a bit of web programming (or you know somebody who does!).\n<\/p>\n

\nThe best part is that by adopting a standard API, you’ll be prepared to work with other clients besides just MarsEdit. I mean, you’d be crazy to not use MarsEdit, but I’d rather keep you as a happy customer than a locked-in one!\n<\/p>\n

Pick An API<\/h3>\n<\/p>\n

\nThe first thing you’ll need to do is choose a publicly documented<\/a> API to implement. The choice is yours, but if you have no clue about which to adopt, I’d probably recommend the MetaWeblog API<\/a>. You’ll be in good company, since some major services such as WordPress<\/a> and Microsoft Spaces<\/a> use the API for their remote editing support.<\/p>\n

Observe A Working Case<\/h3>\n<\/p>\n

\nOnce you’ve settled no an API, I suggest setting up a working test blog that uses the API. That is, get a free blog somewhere, set it up and throw a few test posts up. Now you have a working case to compare your custom implementation against.\n<\/p>\n

\nMarsEdit makes it easy to examine the chit-chat that goes on between it and a given blog publishing system. From the Window menu select “RPC Console”, and you’ll see a verbose transcript of all the messages sent from and received by MarsEdit:\n<\/p>\n

\n\n<\/p>\n

\nNow you’ve got a working case to compare everything against as you iron out the details in yoru custom script.\n<\/p>\n

Write Your Custom Script<\/h3>\n

Start small. Very small. Just write a simple CGI script that accepts a HTTP POST request from MarsEdit and prints out the cargo of the request. You’ll see that it matches exactly what showed up in the RPC Console. From here I would start with a single API call, probably the “getRecentPosts” call, and build your way up from there. Once you’ve got getRecentPosts working you’ll be able to see your list of blog entries show up in MarsEdit, which will surely inspire you to finish the rest!\n<\/p>\n

\nIf you get completely stuck, the good news is there are lots of working code examples<\/em> out there as well. For instance, take a stroll down Google Code Search way on the MetaWeblog<\/a> term. Be mindful of the licensing of any code you find, as always.\n<\/p>\n

Configure MarsEdit For Your Blog<\/h3>\n

You’ll actually do this as soon as you’ve got your first very small test-case of a script finished. Just click the + button beneath MarsEdit’s list of blogs to add a new one, and specify the name and URL. Obviously MarsEdit will fail to obtain meaningful information about the blog, so you’ll have to edit the information manually. Assuming I set up a custom blog using MetaWeblog, the settings window might look like this:<\/p>\n

\n
(Note: The appearance of this dialog is slightly different in 1.1.3 and earlier. Look for this new layout in MarsEdit 1.1.4 and later)\n<\/p>\n

Extra Credit: Really Simple Discovery<\/h3>\n<\/p>\n

\nIf you want to spare yourself and future users of your software from the pain of manually entering the data into the settings dialog, you can describe your blog’s API support by embedding in the home page a “rel” tag identifying a specially-formatted file called an RSD<\/a> file. This stands for Really Simple Discovery, and is a format which MarsEdit can read to automatically determine which standard API your system uses.\n<\/p>\n

\nAny questions I didn’t cover? Feel free to ask in the comments.\n<\/p>\n

Update<\/h3>\n<\/p>\n

\nTom Insam posted this example<\/a> a couple weeks back, where he implemented the MetaWeblog API for his site’s custom software, Zimki<\/a>. Should serve as a good concrete example of the steps required.<\/p>\n","protected":false},"excerpt":{"rendered":"

Although the vast majority of MarsEdit users are using it to manage posts on one of the big publicly available blogging systems, there are a good number of users, especially in the tech community, who run their own custom blog or blog-like software. I’ve received several private inquiries and this public one, all asking about […]<\/p>\n","protected":false},"author":10,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[40,19,4],"tags":[],"class_list":["post-292","post","type-post","status-publish","format-standard","hentry","category-marsedit","category-technology","category-web"],"_links":{"self":[{"href":"https:\/\/redsweater.com\/blog\/wp-json\/wp\/v2\/posts\/292","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/redsweater.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/redsweater.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/redsweater.com\/blog\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/redsweater.com\/blog\/wp-json\/wp\/v2\/comments?post=292"}],"version-history":[{"count":2,"href":"https:\/\/redsweater.com\/blog\/wp-json\/wp\/v2\/posts\/292\/revisions"}],"predecessor-version":[{"id":2434,"href":"https:\/\/redsweater.com\/blog\/wp-json\/wp\/v2\/posts\/292\/revisions\/2434"}],"wp:attachment":[{"href":"https:\/\/redsweater.com\/blog\/wp-json\/wp\/v2\/media?parent=292"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/redsweater.com\/blog\/wp-json\/wp\/v2\/categories?post=292"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/redsweater.com\/blog\/wp-json\/wp\/v2\/tags?post=292"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}