Ticket #1580 (closed enhancement: fixed)

Opened 11 years ago

Last modified 11 years ago

Implement qtopia keyboard for ASU

Reported by: will Owned by: raster
Priority: low Milestone: Om2008.8
Component: E - Illume Version:
Severity: normal Keywords: must have
Cc: zecke@…, testing@… Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: PatchReviewResult:


current keyboard lists word selections underneath the qtopia bar with (options, cancel).
can we launch from that bar instead of underneath? Or at least on top of that bar.
this will give us more pixels for bigger letters in the keyboard.
for example:

  • while typing a word, selections show up in or on top of the qtopia menu bar, hiding (options, cancel)
  • when there is no typing, menu bar reappears.

Change History

comment:1 Changed 11 years ago by raster

  • Priority changed from normal to low

ugh painful, but can be done. nothing to do with qtopia's softmenu (its options/cancel thing). illume now needs special keyboard and layout policy to hide the softmenu while typing then timeout etc. etc.... a lot of little infra-changes

comment:2 Changed 11 years ago by roh

  • Owner changed from raster@… to raster

comment:3 Changed 11 years ago by will

raster, i really think we are better off using the qtopia keyboard as it is. You have put a lot of work into this, and lets not put that to waste. But our keyboard is not ready yet and you obviouly have your hands tied with more important issues. I know that.
We have the chance to provide a well developed keyboard (qtopia) and make users think, 'WOW!' or provide them with our keyboard that still needs work. No 'wow' factor included. Why wouldn't we want to give them a better experience in something as important as the keyboard? I will listen to every argument on this, but I firmly believe that using qtopia keyboard (now) is the right thing to do. My job is to help the average joe to enjoy our products. I know this will still take a while but we have to be realistic every step of the way.

comment:4 Changed 11 years ago by raster

if YOU REALLY want this (and mind u - there are a large set of devs that really would find this very bad), then zecke needs to enable this in qtopia, listen to the same x client messages on root (so non-qt apps work) and needs to change the key faking infra to match x which is going to be a air bit of work and beak several features of qtopia anyway as core x can't do it (generically) then there will be a chunk of integration work as the keyboard and all its window(s) need to be managed properly...

a qtopia keyboard will put blockers on other projects like zhone... so this has much further-reaching consequences than just ASU, but if you absolutely must have it, consequences or not...

zecke - your turn to have your say :)

comment:5 Changed 11 years ago by mickeyl

Will, this will be bad for everything except ASU. I'd rather have raster finish the keyboard, no matter whether ASU will include it or not. It has much broader use and is an investment in the future.

comment:6 Changed 11 years ago by will

There is no 'throwing away' anything here.
We need a good keyboard for the release, thats going to be qtopia(holger is working on it at least).
Raster will continue to work on the illume kbd, as we understand the value that it has for us in the near future.
Hope this clears things up :)

comment:7 Changed 11 years ago by will

  • Keywords must have added; keyboard removed
  • Summary changed from launch words from qtopia softmenu bar to Implement qtopia keyboard for ASU

comment:8 Changed 11 years ago by will

  • Status changed from new to in_testing

comment:9 Changed 11 years ago by regina_kim

  • Status changed from in_testing to closed
  • Resolution set to fixed

kernel : 20080723-asu.stable-uImage.bin
rootfs : 20080730-asu.stable-rootfs.jffs2

Implemented Qtopia keyboard


Note: See TracTickets for help on using tickets.