Ticket #161 (closed defect: fixed)

Opened 12 years ago

Last modified 12 years ago

Docked Keypad is too small

Reported by: sean_mosko@… Owned by: davewu01@…
Priority: high Milestone:
Component: Graphic Design Version: unspecified
Severity: normal Keywords:
Cc: songcw@…, buglog@… Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: PatchReviewResult:
Reproducible:

Description

Dave,

The keypad is too small. Can you please redraw this to make the hit areas of the
keys as large as possible?

We should split up the keys into different layouts to make for more room. For
example:

https://wiki.openmoko.org/wiki/Input_Method

is still a bit too complex. Let's try to go for a keypad more like maemo's. See
attached file.

-Sean

Attachments

n800_keypad.jpg (101.2 KB) - added by sean_mosko@… 12 years ago.
N800 Keypad

Change History

Changed 12 years ago by sean_mosko@…

N800 Keypad

comment:1 Changed 12 years ago by davewu01@…

  • Status changed from new to assigned

This is the bug same as #157.

comment:2 Changed 12 years ago by songcw@…

  • Cc songcw@… added

comment:3 Changed 12 years ago by songcw@…

* Bug 157 has been marked as a duplicate of this bug. *

comment:4 Changed 12 years ago by songcw@…

Dave,

I need you to redesign the input keypad. I made a sketch picture. It is:
https://wiki.openmoko.org/images/thumb/7/7d/Input_keypad_dock.PNG/450px-
Input_keypad_dock.PNG

In my mind, there is four different forms for the keypad. They are: capitals,
lowercases, numbers, and symbles. There are different numbers of keys in each
keypads. But I suggest the keypads use the same size.

At the functions, the keypad will display a picture for every key. So you'd
better give me the pictures for each keys.(There are two pictures for each
key, normal and push down. And the picture should contain the character.)

One suggestion, it is better that all keys have the same height. It will be
easy to write codes.

Chaowei

comment:5 Changed 12 years ago by davewu01@…

Chaowei-
I don't think it is good idea to slice each key as a single button object,
that would be has large amount of buttons on the keyboard, and will reduce the
performance seriously. as we has provided the PNG for the folat
keyboard, all the key present as one single PNG, when user tap on the key,
just show the hi-light border(PNG file with transparency, so you still can see
the character below) on that key, easy and efficiently.
I have explain that to Sean about month ago, and he agree with me. what do you
think? or if you have your programming concern, I still can follow your idea.

-Dave

comment:6 Changed 12 years ago by laforge@…

Please don't derive from the QUERTY layout of the keyboard. This is really
annoying and makes user input quite hard.

Motorola EZX phones (E680, A780, A1200) can do that on a 240x320 screen (240
pixel wide keyboard) that has way less physical size (2.4 inch).

So why should we not be able to do a similar good design?

comment:7 Changed 12 years ago by songcw@…

Dave,

I had talked with Sean at Monday, we didn't need a float keypad. The keypad is
a low level program, it is hard to write a float keypad.

Our system don't support the transparency, so I can't deal the keypad as a
whole picture, and add a transparent border on the push down key.

If each key is a separate section, when user push down a key, it only need
redraw the current key, I don't think it will reduce the performance.

The same as Harald said, it doesn't need a QUERTY layout of the keyboard. The
keypad should be muli-pages.

comment:8 Changed 12 years ago by sean_mosko@…

Dave,

The keypad on the iPhone looks really good. You can use a similar style layout.
Also, Matchbox (our window manager) needs to have each key a separate image. So
please ask Wanda to cut your keypads when you're finished.

-Sean

comment:9 Changed 12 years ago by davewu01@…

  • Status changed from assigned to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.