![]() |
Re: [ANNOUNCE] Mauku 2.0 for Fremantle
Quote:
|
Re: [ANNOUNCE] Mauku 2.0 for Fremantle
Mauku 2.0 beta 3 is out now and is going to extras-testing today.
This version introduces ability to follow comments of a tweet (if known by the application; Twitter API is very limited with this aspect). Note that you have to remove cache directory manually before upgrading if you have used beta 1 or beta 2 previously. Type rm -Rf /home/user/.microfeed in the terminal before starting application manager. |
Re: [ANNOUNCE] Mauku 2.0 for Fremantle
Hi,
I was testing Mauku 2.0 this weekend, Widgets have changed quite a lot from the older version and it looks great :) Findings:
|
Re: [ANNOUNCE] Mauku 2.0 for Fremantle
Quote:
See the relevant thread: http://talk.maemo.org/showthread.php?t=29942 |
Re: [ANNOUNCE] Mauku 2.0 for Fremantle
Just a question here. I haven't used the new Mauku, but I heard that you're using yellow to denote that a tweet is the start of a thread, correct? Like the 3rd image in your first post?
I really don't think that the color is very intuitive to indicate that it's the start of a thread. If I see yellow on a tweet, it makes me immediately think "favorited". I think it's a lot more intuitive if you simply use tree view style triangles on the right side (not left as in the image below). Triangle pointing to the right to indicate that the tweet is the start of a thread. Upon click, the triangle spins downward exposing the rest of the thread. Having the rest of the thread be slightly indented from the left will further reenforce that those tweets are part of the same thread. Standard tree view behavior that everyone's familiar with. http://evolvedoo.sourceforge.net/abstract/tree.gif |
Re: [ANNOUNCE] Mauku 2.0 for Fremantle
Quote:
Quote:
Quote:
First, the depth of a such tree could be anything. There would be a single first tweet, but after that tweets could be nested very deeply, since replies may have replies also. (Jaiku prevents this and have actually a concept of a thread, but Twitter does not.) If every level were intended, let's say, 20 pixels, only after few levels, the message area would be very narrow. Secondly, Mauku is built on the concept of timeline. The latest tweets are always on the top of the window. If tweets were grouped into threads, it would be much harder to find latest tweets, since an user had to browse all active threads to read new comments. Thirdly, the Fremantle HIG does not encourage to use of nested tree style lists. :) I can see why. Instead, subwindows should be used. When an user clicks a tweet in Mauku 2.0, a dialog appears (third image in my first post). If a tweet has (known) comments or is a reply, there are options to open a new window with the whole thread of tweets related to the selected tweet (a refererred tweet with the selected comment and other comments or the selected tweet with comments). It is similar, but not the same, functionality than in old Mauku 0.x, and solves the issues listed above. However, thank you very much for the idea. :) Keep them coming! P.S. I have discussed about these things with a professional interaction designer also. Tree view was the first idea he had also. ;) However, after some discussion, he changed his opinion. |
Re: [ANNOUNCE] Mauku 2.0 for Fremantle
Quote:
Thanks for responding. |
Re: [ANNOUNCE] Mauku 2.0 for Fremantle
Having played with Mauku on an N900 and the SDK, some comments:
|
Re: [ANNOUNCE] Mauku 2.0 for Fremantle
Quote:
Quote:
Quote:
Quote:
Quote:
Thanks for your comments and ideas. |
Re: [ANNOUNCE] Mauku 2.0 for Fremantle
Quote:
Viewing linked images would be cool, even if they're only tiny thumbnails. |
All times are GMT. The time now is 09:52. |
vBulletin® Version 3.8.8