Quote:
Originally Posted by baf
That's clever idea, but the gain will be minimal. Average images folder size is 9 KB plus 10 KB of xml config. Removing two layouts you will save 40 KB.
Neither will it solve flashing problem. As we specify keyboard layout on command line kterm will just start with given config instead of default one. It won't be switched later.
I don't quite get what problems it could solve, but if there is need for kterm.sh script to accept the arguments that will be passed to kterm, the patch is trivial.
Code:
#!/bin/sh
EXTENSION=/mnt/us/extensions/kterm
DPI=`cat /var/log/Xorg.0.log | grep DPI | sed -n 's/.*(\([0-9]\+\), [0-9]\+).*/\1/p'`
#use different layouts for high resolution devices
if [ ${DPI} -gt 290 ]; then
PARAM="-l ${EXTENSION}/layouts/keyboard-300dpi.xml"
elif [ ${DPI} -gt 200 ]; then
PARAM="-l ${EXTENSION}/layouts/keyboard-200dpi.xml"
fi
${EXTENSION}/bin/kterm ${PARAM} "$@"
|
Instead of an update_*.bin, we could also have a "install" script. This would check the dpi and extract the appropriate image files. But again, won't be as user friendly as just extracting the kterm folder into /mnt/us/extensions.
baf is right in questioning the gains from removing the unused image files. Maybe just some perfectionism!
The "$@" solution is a simple way to make kterm.sh pass on parameters to the kterm executable.
As regards flashing - maybe i've been seeing too many versions on too many kindles..
but now i'm observing a distinct transition when the shift or function modifier key is pressed. In the case of pressing the shift key, only the labels change. The key borders remain constant. But when the function modifier key is pressed, I see not only the transition between the labels, but also the borders of
all the keys change. And the height of the F1, F2... keys seems to be less than the height of the corresponding 1,2,3... keys!