berry wrote:

> > > Another question:
> > >
> > > With Swing classes, at what point is native code actually
> > > called to do drwing .  If you could tell me, I am wondering what classes
> it
> > > happens in and what is specifically happening. In 1.1 it would be
> > > the peer classes.
> >
> > I know that one : )
> > swing uses
> > Canvas
> > Frame
> > Dialog
> > Window
> > The native peers are called there.
> >
>
> I thought that the whole point of swing was that there were not any peers.

Well you have to get access  to the screen some where.
Sun's swing implementation is integrated with the native system in  the
above AWT classes and through that there native peers.
You have to access the native display or Windowing system somewhere.

There are  of course other ways to do it here was my approach.

First I redid the AWT peers to use swing.
After this I wrote several  types of drivers one on the hardware one using a
java Xlib client.
And one running on top of the original AWT for access to Frame's and windows.
For hardwareI got  the native code down to a  two hundred lines of c and
assembler to allow java video drivers to work. For the mouse and keyboard  you
need irq support and would have to have a jvm running in kernel mode : (
I did write pseudo java drivers  using  kernel message queues. Works fine for
slow devices.
Linux tty drivers used to be butt ugly but I think there better now.
I haven't done any work to port the low level stuff to the new driver api's in
Linux 2.2.
I'll hopefully do that before Christmas. But I want to get my vi  in java
project done first before I
go full screen java agian. I just doing  command line and vi key bindings for
jEdit ad running it without  the fancy menu bars as a shell.
I did not like having to telnet  to run the native vi.   You would think Bill
Joy would get vi going in java I think he wrote it originally : )


Mike






----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to