Re: tc1000 linux - the project (long)

on Sun, Jul 06, 2003 at 03:23:46AM +0700, Samphan Raruenrom wrote:
> Sorry if it sound like a stupid question cause I don't
> fully explore the problem yet and I don't know much about
> X/GNOME programming.
> But the i18n aspect make me worried a bit because current
> X implementations (xstroke, xscrible, xmerlin) convert stroke
> to character, then convert the character to 256 keycode, then send
> the keycode to X? (right?). Then normally, applications will get
> the keycode and ask X to convert the keycode to the (hopefully)
> same character. Am I right?
> This sounds very complicated. Isn't there any protocol
> that directly send a (16-bit) character/string to the active window?
> I don't think it is possible to implement, say, Chinese HWR this way?
>

X works with 'Keysym's , ( there converted to keycodes ) which are at
least 16bit. Xkbd can at least do most western language keyboard
layouts and send the associated events ok. I dont know about eastern
languages, but Id be surprised if this wasn't possible one way or
another.
 
> - Turn off the pointer all the time, like on PalmOS. Pen-based computing
> should get rid of the pointer, which existence is to remind you of the
> position of the pen. But the pen is in your hand, so having another
> marker on
>

You can do this already pretty trivially and effectively with X 4.3
and libxcursor. Just make a transparent cursor theme.
 
> The reason why kdrive support full Xrandr protocol should be easy.
> It's because Xrandr protocol and kdrive are written by the same
> person! :-)

I dont thinks its a simple as that ;-)

> The question is why the big X servers don't? I think
> I'd better ask this question in xwin.org mailling list.
>

Yep, good idea.

> >Though the problem is kdrive servers exist for most
> >cards except NVidia ones.
>
> The XFree86 nv driver don't do well on tc1000. It won't switch
> back to text mode (simply blank). DPMS won't work. No multiple-screen
> support. A lot of work need to be done on this free driver.
>

Hmm, still be better ( faster at least ) than the vesa driver.

> >Id hope using the Xvesa and big X nv sources it wouldn't be too hard
> >to make a rotation capable kdrive nv server.
>
> I still can't use the pen in Xvesa, actually,
> I'm guessing how your patch might work... It convert /dev/ttyS0 (FPI
> protocol) and
> send them to Xvesa as /dev/input/mice (IMPS/2 protocol) right?
>

Nope. It had an actual driver 'built' in for the touchscreen. The
keyboard mouse goes to /dev/input/mice.

Have you tried the Xvesa binary I mentioned ?

  -- Matthew
Received on Sun Jul 06 17:56:09 2003