lunch-meeting-over-maemo-blog.md (1689B)
1 # Lunch meeting over maemo-blog 2 3 <div class="p"> 4 We had a lunch meeting with [bergie](http://bergie.iki.fi/), [tigert](http://tigert.com/), [rambo](http://www.nemein.com/people/rambo/) and [mdk](http://www.mdk.org.pl/). Among other fun stuff, we talked about some ideas for maemo-blog: 5 6 * make the "engine" a dbus service and separate UI 7 * The DBus API should provide at least the following 8 9 * getting a list of configure blogs 10 * getting a list of posts in a blog 11 * getting a list of categories in a blog (preferably with post counts, if possible) 12 * creating categories (if supported by the blog API) 13 * creating posts to a defined blog 14 * creating posts to the default blog 15 * 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 16 17 * Open a "prepared" item in editor for posting 18 * Show a "choose blog" -dialog for posting* Finally implement the UI changes proposed by tigert 19 * Clean up the editor (preferably as a widget in it's own library) 20 * Replace category menu with tag cloud (needs tag cloud widget) 21 </div> 22 <div class="p"> 23 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: 24 <pre> 25 org.maemo_hackers.maemo_blog.get_posts(string:blog_id,string:field1[,string:field2...]); 26 org.maemo_hackers.maemo_blog.send_post(string:blog_id,string:field1,<type>:field1_value[,string:field2,<type>:field2_value...]); 27 </pre> 28 The latter would require fields "title" and "description". 29 </div> 30 31 Suggestions, comments etc welcome.