wow! <br><br>I like the settings button on screen (I don't like more the use of the AUX Button, I think that is not much intuitive). <br><br>According to me another good thing is possibility to switch to the illume desktop by sliding the "time bar" from right to left.<br>
<br>great work!<br><br><div class="gmail_quote">On Wed, Jun 10, 2009 at 1:37 AM, pike <span dir="ltr"><<a href="mailto:pike-openmoko@kw.nl">pike-openmoko@kw.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi<br>
<div class="im"><br>
> Hey great! All 'design guidelines' and things like that are great! I'd<br>
> like you to explain more of what's happening in the screenshots. Tell<br>
> what is new, why have you done it, what's the thinking behind it etc.<br>
<br>
</div>I find it more easier to explain using pictures :-)<br>
Got a graphic mind I guess.<br>
<br>
Take a look at<br>
<a href="http://wiki.openmoko.org/wiki/Image:Bab-1.2-3screens.png" target="_blank">http://wiki.openmoko.org/wiki/Image:Bab-1.2-3screens.png</a><br>
<br>
Any good interface has it's on "Rythm & Rhyme". On<br>
a single screen, your eye will catch the hidden grid<br>
and swerve around primary and secondary options in<br>
a split second. This works subliminally - you wouldn't<br>
even notice, but this is what makes an interface<br>
'feel good'. This is even more true for phones, small<br>
screen, use it with one eye and one finger in a busy<br>
environment .. and between screens, your memory will<br>
recognize changes in that "Rythm and Rhyme", too. Yes,<br>
a good interface is much like a poem, or a piece of<br>
music :-)<br>
<br>
.. so I was trying to find a grid, a basic layout,<br>
that fits all purposes. At the same time, this grid<br>
should be numberfriendly, as it has to be programmed<br>
in edje. You need "a few classes" of fonts, not a<br>
new font on every page. Same with colors, shades, etc.<br>
<br>
So that's basicly what this was<br>
<a href="http://wiki.openmoko.org/wiki/Image:BAB-List-default-1.0-grid.png" target="_blank">http://wiki.openmoko.org/wiki/Image:BAB-List-default-1.0-grid.png</a><br>
.. but it's already outdated :-)<br>
<br>
Such a grid should include whatever options<br>
you might think of in the future - dialogs, extra<br>
buttons, etc .. so that's basicly this<br>
<a href="http://wiki.openmoko.org/wiki/Image:BAB-List-default-1.0.png" target="_blank">http://wiki.openmoko.org/wiki/Image:BAB-List-default-1.0.png</a><br>
<br>
For example, this "big blocker bar" (a modal dialog) is not<br>
actually used anywhere, but if it *would* be, it should be<br>
there (there is a modal dialog in the "dial" and<br>
when "sending" an sms, btw). Same for the "informational<br>
bar" - a thing that should hide itself once you touch the<br>
screen imho - its not used anywhere - but if it would<br>
be, it should be right there. And hey, it could say<br>
"52 messages, 4 unread", for an instance, couldnt it ? :-)<br>
<br>
> what is new<br>
<br>
As little as possible :-D<br>
But, as I'm sketching and using the phone, a few things<br>
are indeed new and needed imho.<br>
<br>
- The "next", "back" paradigm doesnt really work for<br>
me. I want to know *what* "next" is. "back" is not<br>
always where I came from. And above that, I don't<br>
always know where I am (this happens particularly<br>
in the settings, currently). So I've changed "back"<br>
and "next" to a virtual "path" and an "action".<br>
There could be more actions, actually (eg in sms|read,<br>
you can "delete" and "reply" a message). If you<br>
click on an action, that should become part of<br>
your path in the next screen. For example, if<br>
you are in "Setting | Wifi", the main action is<br>
"Scan". In the next screen, the path should be<br>
"Settings | Wifi | Scan". Action and Paths are<br>
CamelCased.<br>
<br>
<br>
- the "panel" (the top bar) should be removed in all<br>
screens if we are in windowed mode imho, because you now<br>
get two rows of similar icons. Ergo, there can be<br>
nothing essential in Paroli's panel that's not in the<br>
Illume panel. And hence, you need a different button<br>
to "close" a paroli app (like "msgs") when you are<br>
not in full screen - because the clock should not be here.<br>
In fact, it should look like a "close" button: if you tap<br>
around Illume, you will find the "chooser" is still<br>
hanging around and not responding until you "close"<br>
the other screen.<br>
So that's what the funny circle is in the 3rd image at<br>
<a href="http://wiki.openmoko.org/wiki/Image:BAB-List-default-1.0.png" target="_blank">http://wiki.openmoko.org/wiki/Image:BAB-List-default-1.0.png</a><br>
, a 'close button'.<br>
I also think the main screen, the launcher, should<br>
indicate it's waiting for the other app to quit. It<br>
would not harm if you are in fullscreen (since you won't see<br>
it) and it would be very beneficial in windowed mode.<br>
I have a screenshot of that, here ..<br>
<br>
- If you look at<br>
<a href="http://wiki.openmoko.org/wiki/Image:Bab-1.2-3screens.png" target="_blank">http://wiki.openmoko.org/wiki/Image:Bab-1.2-3screens.png</a><br>
you'll see there are more ideas - and I have still more<br>
on paper. Most of them are optional. But I understand,<br>
doing something like what I sketched in the Launcher<br>
requires changing the whole way it works (in Python),<br>
not just changing edje files :-|<br>
<br>
The most important thing is, I think, I differentiate<br>
between "primary" and "secondary" options:<br>
<br>
The screen is divided in lines.<br>
<br>
Each line can only have one primary, big, white, option.<br>
If you click it, the background color of the whole line<br>
quickly hilites before the screen changes.<br>
<br>
A line can have several secondary (small, grey, lowercased)<br>
options. If you click it, only the font color quickly<br>
switches before the screen changes.<br>
<br>
I think this differentation is usefull, as it gives a user<br>
an idea about the "default" action - go forward - and several<br>
sideoptions - "delete that thing, go back" - without visually<br>
cluttering the screen.<br>
<br>
Anyway .. that's a lot of text. Maybe I should get<br>
into edje. Or maybe I should get XULRunner to work<br>
on my phone :-D<br>
<br>
$2c,<br>
<font color="#888888">*-pike<br>
</font><div><div></div><div class="h5"><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Openmoko community mailing list<br>
<a href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a><br>
<a href="http://lists.openmoko.org/mailman/listinfo/community" target="_blank">http://lists.openmoko.org/mailman/listinfo/community</a><br>
</div></div></blockquote></div><br>