Terminal emulator for Touch (and Paperwhite?)

[encol]

It works fine on my PW3
Thank you!

[nasser]

Kterm v2.2 working OK on PW1, PW3 & KT3.

Only.. If you have a script which calls the kterm executable directly with parameters (usually -e), bypassing kterm.sh, then your'e stuck with the default keyboard images.

To avoid that, you have to pass parameters to the kterm.sh script. But it looks like it has to be re-written to accept parameters. Or am I missing something?

[baf]

Originally Posted by nasser

Only.. If you have a script which calls the kterm executable directly with parameters (usually -e), bypassing kterm.sh, then your'e stuck with the default keyboard images.

Include layout selecting option in your custom script. kterm.sh is just meant to start kterm from kual.

[knc1]

Originally Posted by nasser

Kterm v2.2 working OK on PW1, PW3 & KT3.

Only.. If you have a script which calls the kterm executable directly with parameters (usually -e), bypassing kterm.sh, then your'e stuck with the default keyboard images.

To avoid that, you have to pass parameters to the kterm.sh script. But it looks like it has to be re-written to accept parameters. Or am I missing something?

Originally Posted by baf

Include layout selecting option in your custom script. kterm.sh is just meant to start kterm from kual.

KUAL can pass parameters.
or
as baf suggests, use a custom script.

As (now) written:
https://github.com/bfabiszewski/kter...g/bin/kterm.sh
It does not expect parameters.

To submit changes, fixes or whatever: use the features of git/github.

I.E (in general - full directions on github and a zillion places on the 'net):
Clone the repo.
Make a local branch.
Add / Modify as desired.
Issue a pull request. (the author can review in context)

For individuals with open source code, github is free (one of the reasons we use it often).

[JimmyR]

Works great on my K5 and PW2. Thank you.

[nasser]

Originally Posted by baf

Include layout selecting option in your custom script. kterm.sh is just meant to start kterm from kual.

Originally Posted by knc1

KUAL can pass parameters.
or
as baf suggests, use a custom script.
....

I'm too lazy..
I'll just stick to using a single img/ folder and keyboard.xml.
... and copy the appropriate image files to each kindle..
... and of course, comment out the if then logic of kterm.sh.

EDIT:
But, this isn't an option for everybody.. especially plug-and-play users.. so, baf's package with 3 sets of image files and the layout selection logic in the startup script is the ideal solution..

[knc1]

Originally Posted by nasser

- - - -
But, this isn't an option for everybody.. especially plug-and-play users.. so, baf's package with 3 sets of image files and the layout selection logic in the startup script is the ideal solution..

A good point.

Also, if it is made too Kindle specific, it loses its ability to run on any device with GTK+ support.
I.E: It should, and probably still does, run on your PC or Laptop.

[nasser]

Originally Posted by knc1

A good point.

Also, if it is made too Kindle specific, it loses its ability to run on any device with GTK+ support.
I.E: It should, and probably still does, run on your PC or Laptop.

No dice..

bash: ./kterm: cannot execute binary file: Exec format error

Maybe needs an ARM emulator?

[knc1]

Originally Posted by nasser

No dice..

bash: ./kterm: cannot execute binary file: Exec format error

Maybe needs an ARM emulator?

Enable qemu emulation or re-build for your pc's cpu type.

[knc1]

Originally Posted by nasser

I'll just stick to using a single img/ folder and keyboard.xml.
... and copy the appropriate image files to each kindle..
... and of course, comment out the if then logic of kterm.sh.
- - - -

MrDCorn has a better idea.

When this version is considered stable (as in no code changes for xxyy time) -

We can wrap it in an update_*.bin package.
The install script of the package can selectively install the file(s) that match the Kindle model on which the updater is running.

This will also probably get rid of the keyboard flashing during application start-up when the code has to switch from the default keyboard.

[baf]

Originally Posted by knc1

MrDCorn has a better idea.

When this version is considered stable (as in no code changes for xxyy time) -

We can wrap it in an update_*.bin package.
The install script of the package can selectively install the file(s) that match the Kindle model on which the updater is running.

This will also probably get rid of the keyboard flashing during application start-up when the code has to switch from the default keyboard.

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.

#!/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} "$@"

[encol]

Can i suggest a new feature for the next version(s)?

It would be great some way (menu?, shortcut?, ..?) to show/hide the keyboard from inside kterm (once is started) or to rotate the screen

[baf]

Originally Posted by encol

Can i suggest a new feature for the next version(s)?

It would be great some way (menu?, shortcut?, ..?) to show/hide the keyboard from inside kterm (once is started) or to rotate the screen

Hmm, there is a menu. It opens on two finger touch in the terminal window. Doesn't it work for you?

[encol]

Ehm... Sorry I haven't seen it before

[baf]

Originally Posted by encol

Ehm... Sorry I haven't seen it before

You ask for a feature and you have it.