Re: scribble update

> From kerr_at_pa.dec.com Wed, 23 Aug 2000 13:20:34 -0700
> Date: Wed, 23 Aug 2000 13:20:34 -0700
> From: Deborah Wallach kerr_at_pa.dec.com
> Subject: [Handhelds] scribble update
>
> I checked in a new version of xscribble and updates to the classifier
> files to handhelds.org.
>
> The changes I made enabled: tab, capslock, '"', '\', '{', '}', '[', ']'.
> - tab is invoked by drawing the same symbol as is used for the letter 'f',
> but in punctuation mode, and starting from the bottom left instead of the
> top right.

A thousand thanks Debby! I can't live without TAB-completion when
using a full-size keyboard, and even more so when using something like
xscribble. (Incidentally, for the iPAQ folk, I haven't seen this new
version in the distribution yet...)

> The perl program that Russ Nelson posted to this list on August 9th will
> show you the stroke necessary to invoke each character.

For reference, this email, containing the stroke decoder can be found
at:

        http://www.handhelds.org/pipermail/handhelds/2000-August/000712.html

This is a great little utility. It would be nice if it could show up
on an FTP site somewhere, and in CVS under apps/xscribble, (I'd be
glad to add it if I could get CVS write access. How likely would that
be?).

Does anyone have a utility for editing/generating these classifier
files? As is obvious from the perl source mentioned above, the stroke
information is simply a list of X Y pairs. But what is all the
floating point data in the file before the list of X Y stroke data?
How did you generate more strokes, Debby?

My next immediate need from xscribble is a way to generate Escape, (vi
is pretty useless otherwise). I'd also like to make xscribble notice
if a modifier key was pressed while the stroke was entered and then
pass the appropriately modified key event on. (My idea is to map a
couple of the buttons on the iPAQ to CTRL and META and use them with a
single xscribble stroke rather than a two-stroke method where the
first stroke specifies the modifier. Modifiers seem like one of the
most useful mappings for buttons as applications will be able to
distinguish from plain mouse events and modified mouse events. This
can alleviate the problem of porting program that expect several mouse
buttons to work with a "1-button" stylus.)

-Carl
Received on Tue Sep 05 2000 - 08:54:54 EDT