Comments for page "Wikidot Development" http://squark.wikidot.com/blog:wikidot-development/comments/show http://squark.wikidot.com/blog:wikidot-development/comments/show#post-542516 Re: API http://squark.wikidot.com/blog:wikidot-development/comments/show#post-542516 Thu, 23 Jul 2009 19:08:19 +0000 David Marseilles 29608 If you strive for compatibility with some major current API, it's more likely you could use some existing software, at least for things like blogging.

I'm more into Windows Mobile (why would you want to use an iPhone when the Touch Pro2 exists?), but I have the mobile urge as well.

]]> http://squark.wikidot.com/blog:wikidot-development/comments/show#post-477859 Re: API http://squark.wikidot.com/blog:wikidot-development/comments/show#post-477859 Wed, 13 May 2009 08:10:49 +0000 Gabrys 2462 Pacam komcia testowego

]]> http://squark.wikidot.com/blog:wikidot-development/comments/show#post-476947 Re: API http://squark.wikidot.com/blog:wikidot-development/comments/show#post-476947 Tue, 12 May 2009 13:05:32 +0000 Gabrys 2462

By the way, drafts will be implemented soon in the web version of WD, so it could be connected with API backend.

This is nice.

Also editing tags and uploading files while editing a page is planned.

The API's not-yet-public page.save method already lets you save tags and new source at one shot, so waiting for this feature on Wikidot is not needed :).

Nevertheless synchronization of the local drafts with those online could be not so trivial if draft model will include revisions. What to do then, create another revision, overwrite existing, combine them?

I though about really simple drafts, i.e. only update what's on Wikidot to the saved version. What's on disk is only a "cache" before actually writing the draft to Wikidot. If you want another "revision" of draft (which for blog and notes are not very likely), you just create a new other draft.

Other possible API application would be wiki-photoblog. Choose a file (or a few files), write short description, select tags and "upload to Wikidot". The application could choose proper name for page, examine photos metadata (defined EXIF tags) and upload everything to Wikidot in two steps probably:

  • saving page source (including EXIF) and tags in one step
  • attaching the photo in second step

but all this "complexness" would be hidden from user.

]]> http://squark.wikidot.com/blog:wikidot-development/comments/show#post-476939 Re: API http://squark.wikidot.com/blog:wikidot-development/comments/show#post-476939 Tue, 12 May 2009 12:56:00 +0000 Squark 160264 Exactly, API is crucial. The faster the better.

By the way, drafts will be implemented soon in the web version of WD, so it could be connected with API backend. Also editing tags and uploading files while editing a page is planned.

Nevertheless synchronization of the local drafts with those online could be not so trivial if draft model will include revisions. What to do then, create another revision, overwrite existing, combine them?

]]> http://squark.wikidot.com/blog:wikidot-development/comments/show#post-476932 API http://squark.wikidot.com/blog:wikidot-development/comments/show#post-476932 Tue, 12 May 2009 12:47:30 +0000 Gabrys 2462 Every piece of software you're dreaming about requires Wikidot API. This shows how very very very important it is.

BTW I'm also dreaming about blog application, that uses GTK or Qt as the GUI, let's me

  • write my blog/notes offline
  • tag them while writing (even before saving)
  • save drafts:
    • offline: save them to disk
    • online: save them to a draft category on some wiki (maybe other than the public one)
  • synchronize offline drafts with the draft category when getting online (or by clicking a button)
  • publish draft posts/notes
]]>