nanogui: Thread: nano-X 0.6

Hi Greg,

sorry for not keeping the thread, but here I have to use Lotus. It's good
for internal workflow management,
but not good for quickly hacking internet mails ... :-(

Where can I find your nano-X version 0.6 ? On Linuxhacker, there's only the
0.5pre3 version.
Does 0.6 have a GGI driver or other possibility to use it on X. Otherwise
it wont be usable for me, no 2.2 kernel ...

- alex

[1] I have to find a way to read me mails at home ...

On Thu, 17 Jun 1999, Alexander Peuchert wrote:
> Where can I find your nano-X version 0.6 ? On Linuxhacker, there's only the
> 0.5pre3 version.

There is no Nano-X 0.6 yet. 0.5pre3 is the latest development release.
Greg apparently has a large set of changes which for some reason he is
calling Nano-X-0.6, but he hasn't sent anything to me for inclusion for
several weeks.

> Does 0.6 have a GGI driver or other possibility to use it on X. Otherwise
> it wont be usable for me, no 2.2 kernel ...

I'll have a go at putting the one I was sent in and sending out a new
prerelease tonight, hopefully it shouldn't require many changes to fit
into the new code, but I don't know whether it'll be any more stable or
not.

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

: Where can I find your nano-X version 0.6 ? On Linuxhacker, there's only the
: 0.5pre3 version.
: Does 0.6 have a GGI driver or other possibility to use it on X. Otherwise
: it wont be usable for me, no 2.2 kernel ...
: 
: - alex
: 
: [1] I have to find a way to read me mails at home ...
: 
: 
	I can send you my version 0.6, which runs on linux 2.0 svgalib, 
as well as bare hardware.  I don't have a ggi driver, but it will run on your
kernel if you've got a VGA card.

Greg

Greg Haerr writes:
> 
> 
> : Where can I find your nano-X version 0.6 ? On Linuxhacker, there's only the
> : 0.5pre3 version.
> : Does 0.6 have a GGI driver or other possibility to use it on X. Otherwise
> : it wont be usable for me, no 2.2 kernel ...
> : 
> : - alex
> : 
> : [1] I have to find a way to read me mails at home ...
> : 
> : 
> 	I can send you my version 0.6, which runs on linux 2.0 svgalib, 
> as well as bare hardware.  I don't have a ggi driver, but it will run on your
> kernel if you've got a VGA card.
> 
> Greg
> 

Just a sugestion, but it would be really helpful if you annotate you
releases so there is less confusion about which version is which.

e.g.

Alex released nano-X-0.5, so subsequent releases by Greg based on this code
with Greg's additions could be released as nano-X-0.5gh1, nano-X-0.5gh2
etc.. in a similar way to Alan Cox's versions of the Linux kernel.

Al

: There is no Nano-X 0.6 yet. 0.5pre3 is the latest development release.
: Greg apparently has a large set of changes which for some reason he is
: calling Nano-X-0.6, but he hasn't sent anything to me for inclusion for
: several weeks.
: 

	I am sorry about all the name confusion that's taking place with nano.
Over a month ago, Alex said that he wanted more stable versions of nano.  So I stopped
sending in my changes.  I have kept my own log of changes since then.  I will release all
this when Alex's code is stable.  Following is my changelog, which are just my changes
to nano, *not* official releases, whatever that is.

Version 0.8 - 15th June 1999 - ####@####.####
	* added color bitmap support
	* wrote windows bmp file converter
	* drawing color bitmaps in 1, 4 and 8 bpp supported
	* added support for loading partial palettes
	* added MakePaletteConversionTable function
	* implemented optimized window redraw algorithms during window moves
	* added child window support
	* wrote button control
	* added more sophisticated focus routines on create/destroy
	* added support for type 1 and type 2 line drawing requests in GdLine
	* added multiple window color schemes
Version 0.7 - 8th June 1999 - ####@####.####
	* created new win32 api: Micro-Win
	* created window manager and overlapped window border drawcode
	* added software cursor structure to device layer
	* changed nano-x and micro-win color model to RGB for user programs
	* added setpalette driver entry point, 16 and 256 color std palettes
	* fixed console refresh bug for BOGL
	* fixed expose bug bad return;
	* fixed ELKS cols,rows bug in scr_bios.c
	* disallow console switching for ELKS while in graphics mode
	* added EGAMODE and CHARHEIGHT environment variables for ELKS/DOS
Version 0.6 - 23rd May 1999 - ####@####.####
	* Updated bugs from new mini-x distribution
	* Wrote int33 mouse driver for dos
	* Wrote a portable vga 4 plane driver for dos, elks
	* Updated dos driver to support XOR,AND,OR draw modes
	* Wrote routines for ELKS port, compiled with bcc
		uses new serial mouse driver, vga 4 plane driver and bios kbd
	* Added check for FRAMEBUFFER environment variable for /dev/fbX open
	* Added clipped text output routines, using bitmaps
	* Added GetCharBits device driver entry point, removed DrawText
	* Added new nano-X font format, wrote conversion programs to
		convert bdf fonts and PC ROM bios fonts.  There is no longer
		any dependency on the BOGL font structure.  Any number
		of fonts are supported.  Fonts use min 16 bits/scanline.
		Convbdf and convrom.exe are included.
	* Created rom 8x16, 8x16 fonts.
	* Entire nano-X can run on only drawpixel and readpixel if required
	* Documented scr_bogl.c (bogl), and scr_bios.c (bios) drivers.
	* Ported world program to 16 bit systems
	* Added pc, microsoft and logitech direct serial driver mouse support
	* Wrote SVGAlib screen driver, will now run on *any* linux system,
		not just v2.x framebuffer systems.  scr_svga.c.
	* Nano-X is now completely self contained, if desired, in that
		there are hw drivers for screen, mouse, and keyboard
		that don't require other software to be running
Version 0.5 - 18th May 1999 - ####@####.####
	* Rewrote cursor routines
	* Separated mouse from cursor routines
	* Removed DrawCursor from device driver
	* Added ReadPixel to device driver
	* Made demo programs work with cursor changes
	* Added polygon draw and fill routines
	* Added area pixel reading/writing, removed 8-bit limit for colors
	* Reworked color model
	* Added direct hardware 640x480x16 support for VGA real mode systems
	* Made api backwards compatible with mini-x
	* Ported mini-x world demo program to examples library

Greg

On Thu, 17 Jun 1999, Greg Haerr wrote:
> Over a month ago, Alex said that he wanted more stable versions of nano.  So I stopped
> sending in my changes.  I have kept my own log of changes since then.  I will release all

Whatever.

> this when Alex's code is stable.  Following is my changelog, which are just my changes
> to nano, *not* official releases, whatever that is.

Great, thanks a lot for the all the work you've put in. My position always
has been and still is: I'll integrate it when you send it to me.

> 	* created new win32 api: Micro-Win

Does that mean that the win32 API is integrated into Nano-X? How does it
work? Can you compile out Win32 support if you don't want it?

> 	* created window manager and overlapped window border drawcode

How does the window manager API work? Is it along the lines of the spec I
posted a few weeks ago or more like the way X11 does it?

> 	* fixed console refresh bug for BOGL

Are you still using the original Bogl version with only 8Bpp support?

> 	* Added check for FRAMEBUFFER environment variable for /dev/fbX open

I think that's in the latest development version... I definitely remember
writing it.

> 	* Added pc, microsoft and logitech direct serial driver mouse support

How does your mouse driver system work? Is it table based like GPM and
GII? I wonder whether it's worth me carrying on with the GII based one
I've been working on or not if you've written one too... 

> Version 0.5 - 18th May 1999 - ####@####.####

As I've said at least four times, the one you submitted as your 0.5
candidate got released almost exactly as 0.5pre1.

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

Alex Holden wrote:
> 
> On Thu, 17 Jun 1999, Greg Haerr wrote:
> > Over a month ago, Alex said that he wanted more stable versions of nano.  So I stopped
> > sending in my changes.  I have kept my own log of changes since then.  I will release all
> 
> Whatever.
> 
> > this when Alex's code is stable.  Following is my changelog, which are just my changes
> > to nano, *not* official releases, whatever that is.
> 
> Great, thanks a lot for the all the work you've put in. My position always
> has been and still is: I'll integrate it when you send it to me.
> 
> >       * created new win32 api: Micro-Win
> 
> Does that mean that the win32 API is integrated into Nano-X? How does it
> work? Can you compile out Win32 support if you don't want it?
> 
> >       * created window manager and overlapped window border drawcode
> 
> How does the window manager API work? Is it along the lines of the spec I
> posted a few weeks ago or more like the way X11 does it?

in all honesty i dont like the look of mini-windows if ti is a seperat
way of windowing stuff like gdk+gtk+ then thats fine buit if it's
integrated
into the tree then i think it's a tad bit silly - as it wont be the only
api.

Chris Ross
-- 
======================================================
| Chris Ross - Boris` on efnet, ####@####.#### |
|      Student, C Code Hacker, HTML,  and more...    | 
|           * Web server down - Back Soon *          |
`----------------------------------------------------'

On Thu, 17 Jun 1999, Chris Ross (Boris) wrote:
> in all honesty i dont like the look of mini-windows if ti is a seperat
> way of windowing stuff like gdk+gtk+ then thats fine buit if it's
> integrated into the tree then i think it's a tad bit silly - as it wont
> be the only api.

I thought Nano-win was going to be a widget set implemented on top of
Nano-X too. It at least wants to be optional.

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

: > 	* created new win32 api: Micro-Win
: 
: Does that mean that the win32 API is integrated into Nano-X? How does it
: work? Can you compile out Win32 support if you don't want it?

	There's two makefiles, one for nano-X, one for micro-windows.  Both
share the same dev*.c files, which is the nano-engine.  The nano-engine Gd*() api
runs is device-independent and runs on top of the device-dependent screen, kbd
and mouse drivers.

	The srv*.c code (4 files) implements the mini-x api.  The win*.c code
implements the win32 api.  You can build an executable that supports mini-x
or win32, but not both.  The demo programs are linked in to the exe as well,
using the public header for the api (nano-X.h for mini-x, windows.h for win32).

: 
: > 	* created window manager and overlapped window border drawcode
: 
: How does the window manager API work? Is it along the lines of the spec I
: posted a few weeks ago or more like the way X11 does it?

	The window manager is implemented underneath the win32 CreateWindow,
DestroyWindow, MoveWindow and BeginPaint routines.  In the win32 model,
window management is ever-present in the system.  the mini-x api
has no window manager as of yet.  I wrote the micro-windows implementation
first since I happen to know win32 inside and out, and wanted to test the underlying
windows engine, and found quite a few problems.

: 
: > 	* fixed console refresh bug for BOGL
: 
: Are you still using the original Bogl version with only 8Bpp support?

	Yes, but I moved all the upper-level bogl dependencies like
screen refresh and vt switching out of any common dev*.c code.  This can
be handled totally at the driver level, which is how svgalib does it. (we run
on that now, too)  I didn't do too much work with bogl because I knew
that you were working on it, and that nano uses less and less entry points
in bogl.  For instance, we don't use any text or cursor output routines anymore.
This changed when the decision was made to perform clipping at the mid level,
a big architectural change.

	Unfortunately, I can't get the damned 32 or 24 bpp framebuffers to work
on my mach64 card...  Any help here would be *greatly* appreciated. 

	I would love to integrate the truecolor bogl drivers.

	Another change is that I took the "VGA planar" stuff from the original
vga bogl driver and placed it into another file, since it really isn't framebuffer oriented,
but vga oriented.  As a result, we now have bare vga hardware drivers for DOS and ELKS.
The same thing needs to happen with the current bogl stuff, if we want to use the drivers
to run on bare hardware, which I think is a good idea.  Let me know if you want more info on
this idea.


: > 	* Added pc, microsoft and logitech direct serial driver mouse support
: 
: How does your mouse driver system work? Is it table based like GPM and
: GII? I wonder whether it's worth me carrying on with the GII based one
: I've been working on or not if you've written one too... 

	No - keep going with your work too.  Mine's not table based, but is a
quick put-together that implements PC, MS and logitech protocols, but doesn't 
require GPM or fifos, or any OS, for that matter.  It was written to run on 
almost bare hardware (it needs a serial port from the os, but I'm going to throw in
a serial driver for pc's as well, so that nano can boot from floppy and run without
an os...)

: 
: > Version 0.5 - 18th May 1999 - ####@####.####
: 
: As I've said at least four times, the one you submitted as your 0.5
: candidate got released almost exactly as 0.5pre1.
: 
	Thanks - I agree with everybody that it's hard to keep these versions straight!
My work doesn't include your directory and file renaming that occurred afterwards.

: in all honesty i dont like the look of mini-windows if ti is a seperat
: way of windowing stuff like gdk+gtk+ then thats fine buit if it's
: integrated
: into the tree then i think it's a tad bit silly - as it wont be the only
: api.
: 
	Micro-windows looks exactly like ms-windows.  Nano-X looks like
whatever the user programmer makes it look like, since everything
is done by the programmer and there is no window mgr.