nanogui: Libraries, interfaces, X, Win32
Subject:
Libraries, interfaces, X, Win32
From:
Guan Yang ####@####.####
Date:
9 Sep 1999 10:18:28 -0000
Message-Id: <37D785A4.1311A414@softhome.net>
Here's my entry into the discussion of small-Xlib, MicroWindows, naming,
etc.
Half an hour ago, I proposed this naming model:
nanodevice <-> nanoserver <--nanoprotocol--> nanolib
\__________________________________________________/
NanoGUI
(I am a newbee to NanoGUI, but this is how I see the code is built up.
Correct my if I'm wrong.)
MicroWindows (I've played a little with it) would then be a library
which implements "nanoprotocol" with a different interface. The
client-side of Nano-X (which I call nanolib) then implements
"nanoprotocol" with an Xlib-like interface.
A real Xlib-clone implementation of "nanoprotocol" (which has been
proposed) would then be yet another library that implements
"nanoprotocol". That would be three libraries which implement that
"nanoprotocol", which isn't really that complicated.
Such a library should _really_ be named nano-X, and the "native" NanoGUI
library would then be "nanolib". This would also give us the opportunity
to refine our "own" library and make it suit use better, while having
the X-ness in a separate library. Or interface. Or whatever.
New model:
/--> MicroWindows
nanodevice <-> nanoserver <--nanoprotocol-----> Nano-Xlib
\--> "Native" NanoLib
Which isn't that hard to implement. Hasn't anyone attempted to merge the
MicroWindows and NanoGUI sources?
