Hi all,
first of all, thank you for your help about my problem on Device.java.
Secondy, I would like to try to make jcurses to work with JOS. To this
aim, I need two things:
1. how can I put a char with a back and fore color onto the screen (using
console or consoled class) ?
2. how can I read a *single* char ? (yes I have to use a KeyboardListener
I think, but in the host build any typed char is returned only after a
newline. I have designed a native class which, using a native method and
some ncurses system call, is able to read a single keystroke, but I think
it is better to integrate this inside JOS host core).
My objective is to write the *first* interactive JOS application.
Any suggestion ?
Cheers
Corrado
======================================================
Eng. Corrado Santoro - PhD Student
Unversity of Catania - Engineering Faculty
Institute of Computer Science and Telecommunications
Viale A. Doria, 6 - 95125 CATANIA (ITALY)
Tel: +39 095 7382365 Fax: +39 095 7382397
EMail: [EMAIL PROTECTED]
Personal Home Page:
http://www.cdc.unict.it/~csanto
ARCA Mobile Agent Framework Home Page:
http://netra.cdc.unict.it/ARCA
======================================================
On Wed, 5 Jan 2000, Todd L. Miller wrote:
> Along the way to hunting down a bug I've inserted in the i386
> build trying to to use Aviery's patch for a native #0 console, I made some
> changes to the host build's console handling. The summary is that I've
> adapted the host build to use the ncurses library. This allows
> char-by-char input easily, and simplifies the work in
> driver.KeyboardInterpreter. Things left to do for this style of
> build (from the text console i/o p.o.v.):
>
> (a) handle escape sequences (eg F1) and/or activate keypad() in
> ncurses() and adjust the handling in driver.KI to use its translations.
> (b) rewrite driver.console to use ncurses so that when the Fx keys are
> available, the Right Things will happen. (On update() and when visible,
> use native calls to addch(x,y,c) to draw.)
> (c) recognize and handle return correctly. (This might be something
> ncurses will handle automagically with the right settings.)
>
> None of these should be particularly difficult, though (a) will be
> time-consuming. This will allow us to test shells (when we're ready*,
> which should be soon) on the host build. (consoleVGA on the host build
> should be a simple re-write to pop up and use an X window.)
>
> I'll continue to hack away at figuring what I screwed up when
> inserting Aviery's code. (Which, btw, I did by hand so I could figure out
> what he was doing.)
>
> -_Quinn
>
> * See my prior email for options on shells. If you go with a shell that
> isn't its own program and doesn't use too much of the java libraries, it
> could start now. My short-term attention will be divided between
> processes and classpath; processes should be finished sooner.
>
>
>
> _______________________________________________
> Kernel maillist - [EMAIL PROTECTED]
> http://jos.org/mailman/listinfo/kernel
>
>
_______________________________________________
Kernel maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel
