nanogui: Thread: Antwort: Micro-Windows version 0.82

Hi Greg,

Yesterday, Alex (Holden) sent me a copy of the GGI driver. I'll try to get
it working
with nano-X.

One other thing. From your mail I get the impression that nano-X and
microwindows
seem to be connected together without nano-X being able to live alone. Is
this correct ?
Or can I still use your nano-X tree to develop my nano-Toolkit ?

- alex

On Tuesday, June 29, 1999 1:54 AM, Alexander Peuchert ####@####.#### wrote:
: Hi Greg,
: 
: Yesterday, Alex (Holden) sent me a copy of the GGI driver. I'll try to get
: it working
: with nano-X.

	That would be great.  If you get it working with nano-X, it'll
work with Micro-Windows too.


: 
: One other thing. From your mail I get the impression that nano-X and
: microwindows
: seem to be connected together without nano-X being able to live alone. Is
: this correct ?

	No.  Nano-X can absolutely live alone, as can Micro-Windows.  
They both share the same driver interface and mid-level graphics engine.
The design idea was to allow different upper level api's on the same 
engine, while allowing all of it to run on various hardware and OSs,
like Linux 2.2, 2.0, ELKS, MSDOS and bare hardware.



: Or can I still use your nano-X tree to develop my nano-Toolkit ?
: 
	I would suggest that you use my tree, because Alex says his
is not compiling at the moment.  I'll send Alex anything I add for nano-X.
In addition, the Micro-Windows engine in microwindows-0.81 fully supports
a palettized RGB scheme.  This is upwardly implemented into the nano-X
api.  (e.g. GR_COLOR is an unsigned long).  There is a setpalette entry
point in the low level driver that's required to maximize the color scheme.
(This can be left out, but then we compile in a default color palette that
is 16 colors long...)

Greg

On Tue, 29 Jun 1999, Greg Haerr wrote:
> : Or can I still use your nano-X tree to develop my nano-Toolkit ?
> 	I would suggest that you use my tree, because Alex says his
> is not compiling at the moment.  I'll send Alex anything I add for nano-X.

I think the user API is currently the same in mine and Greg's, so a 
user space toolkit should work with both. The only problem I can see is
that you'll have to compile the toolkit into the server along with the
application and can still only use one application at a time (my code
doesn't solve that yet either), plus you'll only have an 8bpp framebuffer 
driver (I think my code solves that problem). If you're porting it to GGI
that doesn't really matter anyway though. I don't think things have 
changed that much internally that porting the driver back to my code after
getting it working on Greg's should be much more than changing the name of
the file and the headers it references.

--------------- Linux- the choice of a GNU generation. --------------
: Alex Holden (M1CJD)- Caver, Programmer, Land Rover nut, Radio Ham :
-------------------- http://www.linuxhacker.org/ --------------------

: I think the user API is currently the same in mine and Greg's, so a 
: user space toolkit should work with both.

	Yup.  The color model is slightly different, but if you use
the "standard" colors (16 VGA) they have different values, but will compile
and run.  For the real world, though, I think buttons etc will want
to be RGB.



 I don't think things have 
: changed that much internally that porting the driver back to my code after
: getting it working on Greg's should be much more than changing the name of
: the file and the headers it references.
: 
	There is a setpalette entry point change as well.