Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs

commit e0f0b02bedd17621d813e314ae0aeb71cf7b3b62
parent 72c2c769388a753ee6988e4a7f9d7d264dbe8dff
Author: Santtu Lakkala <>
Date:   Tue, 27 Feb 2007 11:47:18 +0000

Lunch meeting over maemo-blog

Aposts/ | 32++++++++++++++++++++++++++++++++
1 file changed, 32 insertions(+), 0 deletions(-)

diff --git a/posts/ b/posts/ @@ -0,0 +1,31 @@ +# Lunch meeting over maemo-blog + +<div class="p"> + We had a lunch meeting with [bergie](, [tigert](, [rambo]( and [mdk]( Among other fun stuff, we talked about some ideas for maemo-blog: + +* make the "engine" a dbus service and separate UI +* The DBus API should provide at least the following + +* getting a list of configure blogs +* getting a list of posts in a blog +* getting a list of categories in a blog (preferably with post counts, if possible) +* creating categories (if supported by the blog API) +* creating posts to a defined blog +* creating posts to the default blog +* upload media (preferably through gnome-vfs URI's in the post content to keep us indenpendent of network, cache network/bluetooth files locally?)* The UI should also have a DBus API for the following + +* Open a "prepared" item in editor for posting +* Show a "choose blog" -dialog for posting* Finally implement the UI changes proposed by tigert +* Clean up the editor (preferably as a widget in it's own library) +* Replace category menu with tag cloud (needs tag cloud widget) +</div> +<div class="p"> + I was planning on making the post query/sending functions quite generic, so the user would list the fields they're insterested, something like this: + <pre> +org.maemo_hackers.maemo_blog.get_posts(string:blog_id,string:field1[,string:field2...]); +org.maemo_hackers.maemo_blog.send_post(string:blog_id,string:field1,<type>:field1_value[,string:field2,<type>:field2_value...]); + </pre> + The latter would require fields "title" and "description". +</div> + + Suggestions, comments etc welcome. +\ No newline at end of file