nanogui: Thread: Announcing Micro-Win

This list has been conspicuously quiet for the last while, so I thought
I'd try to wake it up a bit.

Following my last major work to nano-X version 0.6, which basically
got all the mini-x feature set running, along with device drivers for keyboard,
mouse and screen for linux framebuffer, linux 1.x svgalib, elks, msdos,
and bare hardware,  I decided that it would be time to see whether the basic 
"Gd" device middleware layer was ready for another "upper-level api."

So, without further ado, I announce Micro-Win.  Micro-Win is a replacement
user api running on top of my nano device independent layer that implements
the Win32 user and gdi modules.  Well, implements some of the *huge* api, at least.
The following is currently implemented:

	CreateWindow
	DestroyWindow
	RegisterClass
	GetDC
	GetWindowDC
	ReleaseDC
	BeginPaint
	EndPaint
	FillRect
	LineTo, MoveTo
	GetClientRect
	GetWindowRect
	ScreenToClient, ClientToScreen
	DefWindowProc
	MoveWindow
	ShowWindow
	GetMessage
	DispatchMessage
	WinMain
	WM_* messages for the above api
	Client and non-client painting (only WS_BORDER NC painting currently)
	Replacement <windows.h>

The client and window rect, along with full clipping and window control are supported.
All this of course runs in about 50K of memory.  This allows small windows
programs to be run, without re-writing them.

The idea here is that the now, there is a small nano system that can run X api
and Win32 api, all in a small space.  In fact, although I haven't done this yet,
I could make it run them both at the same time, because the api's are implemented
on top of a portable device layer.  Anybody with some custom controls or cool
win32 draw code can now run on linux, elks, dos, etc.

My next plan is to port some controls, button, checkbox, radio button, listbox,
and scrollbar, as well as complete some cool 3d window caption and border
draw code.

Greg

On Wed, 2 Jun 1999, Greg Haerr wrote:
> This list has been conspicuously quiet for the last while, so I thought
> I'd try to wake it up a bit.

I've mostly been working on 7110-Linux for the past few days, though I
have done part of an MDA driver for Bogl as well. Hopefully I'll find the
time to get Nano-X-0.5 out of the door next week some time.

> Following my last major work to nano-X version 0.6, which basically
> got all the mini-x feature set running, along with device drivers for keyboard,
> mouse and screen for linux framebuffer, linux 1.x svgalib, elks, msdos,

You never sent me your latest patches against 0.4- did you put them up
somewhere else? It'd be nice to get your changes integrated before I make
the 0.5 release if possible.

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

As windowing toolkits such as GTK+ and V now exist in some form on many
unices and win32 wouldn't it be more useful to port one of those (i reckon
GTK+) to nano-X ?


Cheers

Paul
------
Paul Roberts ####@####.####
 Caffeine for Mind
    Pizza for Body
    Sushi for Soul  -  Pitr

>From: Greg Haerr ####@####.####
>Sent: 03 June 1999 01:53
>To: ####@####.####
>Cc: ####@####.####
>Subject: Announcing Micro-Win
>
>This list has been conspicuously quiet for the last while, so I thought
>I'd try to wake it up a bit.
>
>Following my last major work to nano-X version 0.6, which basically
>got all the mini-x feature set running, along with device 
>drivers for keyboard,
>mouse and screen for linux framebuffer, linux 1.x svgalib, elks, msdos,
>and bare hardware,  I decided that it would be time to see 
>whether the basic 
>"Gd" device middleware layer was ready for another "upper-level api."
>
>So, without further ado, I announce Micro-Win.  Micro-Win is a 
>replacement
>user api running on top of my nano device independent layer 
>that implements
>the Win32 user and gdi modules.  Well, implements some of the 
>*huge* api, at least.

On Wed, 2 Jun 1999, Greg Haerr wrote:

> This list has been conspicuously quiet for the last while, so I thought
> I'd try to wake it up a bit.
> 
> Following my last major work to nano-X version 0.6, which basically
> got all the mini-x feature set running, along with device drivers for keyboard,
> mouse and screen for linux framebuffer, linux 1.x svgalib, elks, msdos,
> and bare hardware,  I decided that it would be time to see whether the basic 
> "Gd" device middleware layer was ready for another "upper-level api."
> 
Can I have a copy of nano-X for elks? I think it would go real nice on my
hard disk machine....

BTW: Why is it that on some machines (286/8086) elks boots, and freezes
after displaying login:

Any clues?

Luke(Boo) Farrar.

On Thursday, June 03, 1999 3:15 AM, Paul Roberts ####@####.#### wrote:
: As windowing toolkits such as GTK+ and V now exist in some form on many
: unices and win32 wouldn't it be more useful to port one of those (i reckon
: GTK+) to nano-X ?
: 
: 
: Cheers
: 
: Paul
: 

Please go right ahead.  I've only got so much spare time...


gh

On Thursday, June 03, 1999 3:02 AM, Alex Holden ####@####.#### wrote:
: On Wed, 2 Jun 1999, Greg Haerr wrote:
: > This list has been conspicuously quiet for the last while, so I thought
: > I'd try to wake it up a bit.
: 
: I've mostly been working on 7110-Linux for the past few days, though I
: have done part of an MDA driver for Bogl as well. Hopefully I'll find the
: time to get Nano-X-0.5 out of the door next week some time.
: 
: > Following my last major work to nano-X version 0.6, which basically
: > got all the mini-x feature set running, along with device drivers for keyboard,
: > mouse and screen for linux framebuffer, linux 1.x svgalib, elks, msdos,
: 
: You never sent me your latest patches against 0.4- did you put them up
: somewhere else? It'd be nice to get your changes integrated before I make
: the 0.5 release if possible.
: 

	My changes since your pre-release minor changes are massive.
I'd just release your 0.5.  I'm in the middle of the Micro-Win changes, and will
make this stuff available after that, and see what's changed since my 0.4.  If I
remember correctly, you didn't like my directory names and changed all them as
well.  I haven't integrated any of that stuff.  In addition, now, many of the srv*.c file
names have changed again to accomodate the device-independent middle
layer and the two api's on top.


Have you met your stated goals for the 0.5 release?


greg

>BTW: Why is it that on some machines (286/8086) elks boots, and freezes
>after displaying login:


This one has been bugging me since ELKS *.67.  I cannot for the life of me
figure out why I can't login using this setup.  Luke: get curious like I
did - try to use your ELKS boot disks to boot a +386 machine.  I found that
I still couldn't login there either, but it had a different problem.  In
case your problem is different than mine, it has been suggested to me, on
this list, that init is spawning consoles and this somwhow hammers the
hardware.  Changing that didn't help me at all, but you might want to try.
Anyhow, I'm still working on the problem, I'll let ya know if I find
anything cool...

Ross
--
Do to a fauly operating system, a witty signiture is unable to be provided.
Apologies are offered.

On Thu, 3 Jun 1999, Greg Haerr wrote:
> 	My changes since your pre-release minor changes are massive.

Okay, it'd have been preferrable to have merged it in a patch at a time,
but I did volunteer to do the full merge myself anyway once you sent it to
me.

> I'd just release your 0.5.

Why? I said I'd make sure it was pretty stable before 0.5, including
the networking code, and I'm sticking to that.

> I'm in the middle of the Micro-Win changes, and will make this stuff
> available after that, and see what's changed since my 0.4.  If I

Okay, that just means even more work at one go for me to merge it though.

> remember correctly, you didn't like my directory names and changed all them as
> well.  I haven't integrated any of that stuff.  In addition, now, many
> of the srv*.c file names have changed again to accomodate the
> device-independent middle layer and the two api's on top.

Doesn't matter. File names are a trivial thing to change, though as I
said you'll have to fix the DOS Microsoft C makefile stuff yourself as I
don't have (and don't want) any machines with a setup like that.

> Have you met your stated goals for the 0.5 release?

Not yet. That's why I haven't released it yet.

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