ryanhope / wterm Goto Github PK

I'm having an issue typing Control-A and Control-[ from my Bluetooth keyboard. All other useful control key combinations seem to work fine in my testing. I'm able to type these keys from the soft keyboard correctly. Control-A from the Bluetooth keyboard also works as expected in other parts of the OS.

I'm testing with 0.4.0-2 from Preware on webOS 3.0.5. The keyboard is a Think Outside Stowaway that I've been using with various devices for years.

The tab key is huge on first launching wTerm on a Pre3:

http://i.imgur.com/onWJT.png

Switching to landscape and back makes the button behave normally.

Support rotating and portrait mode. This will require a portrait friendly vkb as well as term resizing.

VTTEST 1.1 is the exact same as 1.2 except 1.1 is 80chars wide and 1.2 is full screen, for some reason the bottom line does not show up properly on test 1.1 but does 1.2.

Make touch events work as curses compatible mouse events.

The processing of non printable code is split between VTTerminalState::insertString() and TerminalState::processNonPrintableChar()

This should get consolidated.

characters that should be underlined appear as normal.

Should be straightforward to implement, I'd say rip out the italic stuff and replace it with font set to underline font style. I haven't checked if we track the underline mode like we do for bold.

Figure out why key repeating does not work.

Use TTF_SetFontStyle instead of multiple fonts, also, replace italics for underline.

In vttest menu 2 (screen features) the mouse shows up in the wrong spot sometimes.

VKB tap sounds in JS work fine except there is no way to make sounds for repeat presses. VKB tap sounds in C work for all presses including repeats but only for first card (which is often the exhibition mode card).

What can we do? Probably best idea is move repeat to JS or go back to tap sounds in JS and forget about repeat sounds.

Back-color and font color configurable in preferences

Hi,

cool app ! Thanks for your work
it would be great if you could support mc with all vkb key bindings.

Testcase:
ipkg-opt install mc
mc
no colors no fkeys ESC-0 works
export TERM=xterm
mc -a
looks better but no keybindings ESC-9 opens menu

sent from my TP

VZW Pre+ with webOS2.1.0 and wTerm 0.3.999-2. When typing into the terminal many of the keyboard characters show up as letters different than expected in the term and characters printed in the term are different.

For example trying to run ssh: it shows up as ssi in the term, but enter still runs the command and I see the default usage message. Many of the letters are switched making it look like gibberish.

We know how to build it, but a short guide that describes the setup would be useful.

Beyond build.git usage (the officially supported method), light documentation for BUILD_ROOT, DEVICE, and LOGLEVEL would be useful for new developers :).

I'm happy to tackle this when I get some time, but just wanted to track it as a known issue :).

If the plugin looses the focus keyboard events don't reach the plugin. "clicking" the plugin fixes it.

Control sequence parser only handles integer params. Need to extend CSP or implement something new for Operating System Controls.

When using font sizes of 8 or 11, the cursor seems to move right an extra pixel for each character typed.

cursor often doesn't show up in vi or in mcedit.

(via http://forums.webosnation.com/webos-internals/309714-wterm-webos-terminal-emulator-2.html#post3280072, but confirmed on my build)

See Puff's comment below for more detailed description of the issue.

When running color htop, the top line gets erased and doesn't render properly.

htop installed from ipkg-opt.

This only happens when TERM=xterm (htop runs in color mode); TERM=vt100 results in a uncolored but textually complete htop.

A fake keyboard noise (option) would be beneficial.

I'm finding the left-shifted numbers and bottom-right punctuation changes (to
accommodate the oh-so awesome cursor keys, thank you for not doing the
half-height up/down mishmosh) are the sources of most of my typos. The
following tweaks might improve accuracy for many folks:

~ to left of 1, shrink Bksp

to Up, ? to where > was
cursor cluster 2 positions to right, shrink Shift
perhaps use adt'l bottom-row space for 'Symbol' and/or other special hotkey(s)

Right now if there are multiple cards open and prefs are changed from one of the cards those changes are reflected on that term. If you then switch to a different card and open the prefs they will reflect the settings but the term will not. I am not sure what the proper behavior should be exactly but it seems like something needs to be done here.

It'd be great to have wterm avail on the phone platforms too. How to manage things like the vkb (replace full kbd with mini keyboard for control/esc/arrows/etc?) would need some work, but otherwise should "port" fairly easily.

Bluetooth keyboard seems to be working great with wterm (incl. Caps Lock).
But if a key on the VKB is pressed, bluetooth keys won't be processed until
the terminal area is tapped.

We need unicode/utf-8 support for rendering non ascii characters. This is needed for better support of box drawing characters as well as for internationalization.

Today I have found the wTerm 0.4 release in preware, I have been waiting for so long. Thanks for this great App!
Unfortunately the keyboard does not fully resize all keys when rotating the touchpad to landscape format.

When i change the rotation on my Pre- (webOS 2.1), it doesn't generate a SDL_VIDEORESIZE event, so the texture has the wrong dimension.

At least rotating back fixes it, and you can start with the rotation you need.

Hi,

on my Pre3 the dot (left of the spacebar) only produces a backspace. So I can't type cd .. (just an example). I don't think that is a feature, because the backspace key is fine, right?
Is this connected to my QWERTZ keyboard layout?

Cheers
Garfonso

Make the keys make noise

I didn't think this happened on the touchpad--regardless the rounded corners obscure characters in the top-left, etc.

Is this fixable?

Here are the remaining tests in vttest that wTerm still fails on.

VT220 Tests

1. Protected Areas (DECSCA)
2. 8-bit controls (S7C1T / S8C1T)

VT320 Tests

Pretty much everything

VT420 Tests

1. Back Index (DECBI) c3782fd
2. Forward Index (DECFI) c3782fd
3. Delete Column (DECDC) 453d4ad
4. Insert Column (DECIC) 453d4ad

VT520 Tests

1. Set Cursor Style (DECSCUSR) 2bd1ee0

ISO-6429 Cursor-Movement

1. Cursor-Horizonal-Index (CHT)
2. Next-Line (CNL)

ISO-6429 Color

1. BCE-style clear line/display (ECH, Indexing)
2. VT102-style features with BCE (Insert/Delete Char/Line) 924f4ec
3. Test of screen features with BCE 924f4ec
4. Test of screen features with ISO 6429 SGR 22-27 codes 924f4ec

Miscellaneous ISO-6429 (ECMA-48) Tests

1. Repeat (REP)
2. Scroll-Left (SL) aa3208b
3. Scroll-Right (SR) aa3208b

Known bugs

1. Funny scroll regions 1c2dad4

This used to work, at least on some commit I was playing with, so shouldn't be too far off.

Anyway, the bug can be seen if you use vim on a file that goes beyond the screen vertically. Scroll down, and then try scrolling back up. When scrolling up it appears we don't scroll at all (don't move the existing lines down I mean), and so instead just continually overwrite the top line.

Probably shows up in other applications too :).

After the font size is changed, the display is not updated until the user presses a printable character. Figure out how to do this automatically with out input.

Right now there are 2 main classes for vkb styling, 1 that is optimized for the TP and one that is for all the phones. This does not work well. The width of the Pre,Pre+,Pre2 and Veer screens is 320 but the Pre3 is 480. The pre3 needs different classes than the other phones.

echo -e "\033[10;10H\033[44mup\033[0;40;37;39;49m\033[10;30H\033[44myours\033[m"

This is an example of the bug for reference.

Although it is stated on Preware that wTerm supports UTF-8, it cannot display Asia characters in UTF-8 properly. I guess this is a font-related issue?

Support toggling the visibility of the vkb.

New Script Launcher would be an item in the program menu, next to where the New Terminal menu item. Dialog would pop up and user could input a command or path to an existing script, enter a name for the launcher, and a checkbox to run in background if they don't want it to open a terminal window on execution.

luncher icon could just be a variation of the current wterm icon, or give user options of different colors, etc when creating the launcher

nothing much to see here

when ssh'ed into an ubuntu system there's some weirdness with the ls command
(gnu ls, observed w/versions 7.4 & 8.5). whatever the font size / screen width,
sometimes the first char of a filename will be pushed out to the last column, eg:

ls /var
backups cache c
rash games l
ib local lock

term=vt100 and vim/joe/top/screen all look great.

Need to listen to the resize application event to account for when things like vkb and dashboards resize the app.

Scrolling is better for rxvt than xterm but still bad. Test with irssi and vttest.

Hey guys when I start up wterm I get the following error in term before I can use it:

login: can't chdir to home directory '/var/home/wterm'
mkdir cant't create directory '/var/luna...' permission denied
...ln : '/var/luna/preferences/localtime: permission denied

sorry about the '...' but unfortunatly these parts are cut away by the border

system:
veer 2.1.1

It would be great if you could scroll back through the terminal output using touch gestures.

echo -e -n "\e#8\e[20;20H\e[1;4;5;44mHello\e[J\e[m\n"

VKB toggles it visually, but alpha keys unaffected.

As mentioned in #21 - Bluetooth keyboards mostly work - but the arrow keys don't do anything
Tested on HP wireless keyboard and Freedom Pro keyboard.

The ESC key on the Freedom Pro doesn't work either

Is there an easy way to see what scancodes are being received?

When the font is set to 11pt shit gets weird (ex. double prompts). Make sure max rows/cols calculations are correct with non 12pt fonts.

Support terminal resizing. Screen rotations and toggling between vkb and no vkb will need this.