search

DevHossamHassan / hackerskeyboard

Automatically exported from code.google.com/p/hackerskeyboard
0 stars 0 forks source link

RFE: light skin more friendly for e-ink display #140

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Hi,
I am using android 2.1 compatible version of hacker's keyboard on my Nook 
Simple Touch, seems to be the best keyboard for nook, thank you for that.
You can find a related thread here 
http://forum.xda-developers.com/showthread.php?t=1339199

Would it be possible/easy to change keyboard colors so it would look similar to 
nook standard keyboard?
http://www.droiddog.com/wp-content/uploads/2011/06/keyboard.jpg
It seems that hacker's keyboard doesn't support skins and the current look is 
too dark on e-ink display. Also selection of particular key is causing 
flickering on e-ink display, it would be great to have an option to disable 
that.

I would like these features in the 2.1 compatible version (only option for Nook 
STR).

Thank you.

Original issue reported on code.google.com by srot.ka...@gmail.com on 4 Jan 2012 at 8:38

GoogleCodeExporter commented 9 years ago 
The current prereleases have basic theming support, the built-in "Stone (bold)" 
theme uses black text on white keys. Can you try 1.28rc21 (or later) from 
http://code.google.com/p/hackerskeyboard/downloads/list and let me know if that 
improves things?

For the flickering, make sure you turn off feedback popups, but it still uses 
some animations and screen feedback without them. It wasn't really designed for 
e-ink, but much of this should be fixable through a theme. For example, 
removing the "pressed" state from 
http://code.google.com/p/hackerskeyboard/source/browse/java/res/drawable/btn_key
board_key_stone.xml would reduce redraws.

The keyboard still redraws itself when shifting, I guess this could be disabled 
through an option if people want to use static hints drawn on the keys instead.

Original comment by Klaus.We...@gmail.com on 8 Jan 2012 at 3:52

GoogleCodeExporter commented 9 years ago 
Ah, just realized you can't use the unpatched builds due to the compatibility 
requirements. It may take a bit of time before I can integrate the patch from 
issue 57, but I'll try to get a test build out sooner.

Original comment by Klaus.We...@gmail.com on 8 Jan 2012 at 3:54

GoogleCodeExporter commented 9 years ago 
Great news, thank you for fast response. I will happily test it once the 
compatibility patch is applied.

Original comment by srot.ka...@gmail.com on 8 Jan 2012 at 8:35