nanogui: Thread: DJGPP/Allegro port?

Hello Everyone,

I am new here and I am looking for a gui to port to DJGPP/Allegro.  I though I would try porting Nanogui and/or Microwindows, but I am still a bit confused as to which files belong to what and what I should start with.

Let us take the example of the Nanogui demo.  I seem to be able to build a lot of the files, but I am unsure which files are platform dependant.  Can anyone tell me which files I have to port to get a simple nanogui or microwindows demo working so I can begin to get a grasp on how things work.

Thank you,

Doug Eleveld


--== Sent via Deja.com http://www.deja.com/ ==--
Share what you know. Learn what you don't.

On Tue, 21 Dec 1999, Doug Eleveld wrote:
> I am new here and I am looking for a gui to port to DJGPP/Allegro.

Rebuilding the Nano-X server with DJGPP probably won't be too difficult,
but porting Allegro to Nano-X may not be very easy (you'll probably want
to start with the X11 port, as the Nano-X API is quite similar to X).

> Let us take the example of the Nanogui demo.  I seem to be able to
> build a lot of the files, but I am unsure which files are platform
> dependant.  Can anyone tell me which files I have to port to get a
> simple nanogui or microwindows demo working so I can begin to get a
> grasp on how things work.

Since DJGPP is single tasking, you want to use the "App built into the
server model".

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

: Let us take the example of the Nanogui demo.  I seem to be able to build a
lot of the files, but I am unsure which files are platform dependant.  Can
anyone tell me which files I have to port to get a simple nanogui or
microwindows demo working so I can begin to get a grasp on how things work.

Doug,
	The 0.87pre3 release has the files sorted into appropriate
directories.
You might start by reading the architecture document on the web site
http://microwindows.censoft.com/

Following is a brief description of the pre3 directory structure.  All files
are device and platform independent, with the exception of the drivers
directory.
Microwindows supports two APIs, a win32 feel, known as Microwindows,
and an Xlib feel, known as Nano-X.

	microwin/src		- main source directory
		src/engine	- shared graphics drawing engine
		src/drivers	- screen, mouse, kbd drivers (platform
dependent)
		src/nanox	- Nano-X api and server
		src/mwin	- Microwindows api and server
		fonts		- in core proportional fonts
		demos/nanox	- Nano-X demos
		demos/mwin	- Microwin demos

Microwindows performs it's own clipping and low level drawing, so it really
isn't designed to run on top of another graphics system, but rather to be
one.  Nonetheless, there is an X11 screen driver, for instance, that
allows Microwindows to run on X.  Perhaps you might want to build
a driver that interfaces to Allegro's screen drivers, bypassing the clipping
layer, since that's contained in the src/engine level.

Regards,

Greg