am I missing something? I tried it as keyboard-wide.xml and keyboard.xml.
will check lines endings didnt get mangled or something really stupid by me

Thank you, sorry. I thought maybe with 5.3.2 it would work. Baf has the same error message - or had before. Something about qlib? Maybe all it needs is the right lib it builds against and the Touch's lib is too old?

I will make a version of it with images - but then the one baf made looks good on Touch. And it still would not work one for all. It will always be images too small on PW or too big on Touch. I prefer the nice big symbols as in the screenshots over even the keyboard-wide.xml that cubemike99 made.

Here's a proof-of-concept example of using kterm's -e and -l options to launch a terminal program from KUAL with a custom interface using matchbox-keyboard's layout config, in this case a media player with basic controls (play/pause, forward, back, next, previous, volume +/-, off).

This is just an example and not of much practical use since it just plays *.mp3 in a folder, but the concept can be adapted to other things (or a media player with a better frontend, at least). Hopefully it'll give someone an idea to play with.

No screenshots since I apparently can't do that when kterm's running a program. Just imagine an ugly text-based media player with hastily drawn media buttons under it.

There's a bug of sorts with kterm (and xterm before it) where some programs won't execute right if just run with the -e command (e.g. "kterm -e foo" will open kterm but then immediately exit without running foo). I don't know why this is but you can get around this by putting the command in a shell script and using -e on that instead (e.g. "kterm -e foo.sh" where foo.sh contains only "#!/bin/sh [linefeed] foo" -- see attached example for example).

Here's a proof-of-concept example of using kterm's -e and -l options to launch a terminal program from KUAL with a custom interface using matchbox-keyboard's layout config, in this case a media player with basic controls (play/pause, forward, back, next, previous, volume +/-, off).

That is an interesting concept. Great idea.

Quote:

No screenshots since I apparently can't do that when kterm's running a program. Just imagine an ugly text-based media player with hastily drawn media buttons under it.

Workaround to make screenshots: use a different terminal window. Does not matter which terminal you issue the screenshot command from. Open program with -e and -l, then ssh into the Kindle via USBNetworking, and issue screenshot command. My earlier version of doing it only in kterm is good when you are on the go, and the PW is the only thing with you. You gotta think outside the box.

Here's a proof-of-concept example of using kterm's -e and -l options to launch a terminal program from KUAL with a custom interface using matchbox-keyboard's layout config, in this case a media player with basic controls (play/pause, forward, back, next, previous, volume +/-, off).

This is just an example and not of much practical use since it just plays *.mp3 in a folder, but the concept can be adapted to other things (or a media player with a better frontend, at least). Hopefully it'll give someone an idea to play with.

No screenshots since I apparently can't do that when kterm's running a program. Just imagine an ugly text-based media player with hastily drawn media buttons under it.

There's a bug of sorts with kterm (and xterm before it) where some programs won't execute right if just run with the -e command (e.g. "kterm -e foo" will open kterm but then immediately exit without running foo). I don't know why this is but you can get around this by putting the command in a shell script and using -e on that instead (e.g. "kterm -e foo.sh" where foo.sh contains only "#!/bin/sh [linefeed] foo" -- see attached example for example).

Fixed it all up. Made a few beautifying adjustments to key sizes. One liberty I took, well 2 actually. I moved the arrow keys back to inverted T, and added the missing esc key left of the left shift key. This *should* now work on Touch as well (any takers?). It does look good on PW. If this one works on Touch and PW equally well (and shows the buttons the same) it could be a one-fits-all solution.

Note: I removed all the unnecessary extended="false" statements. Matchbox keyboard assumes it is false by default. The normal sized keys I removed all the width="****" statements. Matchbox keyboard considers 1000 as the standard size for a key. Theoretically it should matter not if implicitly specifying width. Unfortunately the calculations of the relative keysizes only works correct if width="1000" is omitted for standard sized keys. Relative sizes are also adjusted - so specifying a width="1500" will make the key 1.5 times as wide as a standard key. Much better to work with to create a layout based on relative position rather than providing hard numbers.

Attached a screenie from PW, and the modified keyboard-wide.xml file. Again, someone please test this on Touch, it is supposed to work on both PW and Touch, and look about the same.

P.S.: If this one works, I will make a us-dvorak layout by simply editing this xml.

P.P.S.: This one is revoked now too. See post #129 for a improved version by baf.

Works and looks the same. I can finally type "ls" without it ending up being "la"!

Thank you for testing, that does look nice. Actually it looks better on the Touch than it does on the PW, as the images are a bit bigger. What matters is rather the size of the buttons to hit, and they look the same now. The writing is still easy to read on PW. Do you mean you hit la by accident, because the buttons were too small before? If that is better now, that is a nice side-effect.

The one thing that I am worried about is the keys that got cut out: pageup/down, home/end, delete, ......

If those are necessary, then maybe they should get their own modifier - similar to the buttons left and right of space. The matchbox keyboard that comes with kterm does support a third modifier.That modifier can work to provide all those keys that got lost from baf's original implementation - plus a way to also add a number key block.

The one thing that I am worried about is the keys that got cut out: pageup/down, home/end, delete, ......

If those are necessary, then maybe they should get their own modifier - similar to the buttons left and right of space. The matchbox keyboard that comes with kterm does support a third modifier.That modifier can work to provide all those keys that got lost from baf's original implementation - plus a way to also add a number key block.

There's a bug of sorts with kterm (and xterm before it) where some programs won't execute right if just run with the -e command (e.g. "kterm -e foo" will open kterm but then immediately exit without running foo). I don't know why this is but you can get around this by putting the command in a shell script and using -e on that instead (e.g. "kterm -e foo.sh" where foo.sh contains only "#!/bin/sh [linefeed] foo" -- see attached example for example).

This is not a bug. It just runs commands without shell, as xterm. Command kterm -e "/bin/sh -c /bin/ls" should also work, but shell script might be easier to use.

Oh I like that. That is a good use of the shift key. And the esc-key on top left looks better. And since there is no more keys missing (far as I can tell), it should be good now to replace keyboard-wide.xml and keyboard.xml both with the one you attached. And get rid of the special case handling in bin/kterm.sh. No more need to pick the wide for Paperwhite.

Oh I like that. That is a good use of the shift key. And the esc-key on top left looks better. And since there is no more keys missing (far as I can tell), it should be good now to replace keyboard-wide.xml and keyboard.xml both with the one you attached. And get rid of the special case handling in bin/kterm.sh. No more need to pick the wide for Paperwhite.

Great! There is one more thing. For PW, do you use original or enlarged images? If you use enlarged ones we would still have to use two config files, I think.

Great! There is one more thing. For PW, do you use original or enlarged images? If you use enlarged ones we would still have to use two config files, I think.

No, I never messed with the images. My screenshot is with the default ones, since I was striking to remove all the PW this, TOUCH that hassle. If you want a layout for PW that is seperate, then get rid of the images where you can. That will always look better than trying to fight with images. Make them too big, and all goes real crazy.

Ok, so I leave one config for both devices. Updated kterm-0.6 package on my page with your file. Thanks a lot!

OMG. I am surprised nobody jumped me for it yet. When I posted my layout, it had a typo in the esc-key. You copied that key to a different location (top left) without looking. Now your layout has a non-functioning esc-key.

I put as action: "escpape" and it should be "escape". Did not notice until just now. My apologies.