: How about if you put that and other things like it in some directory on
: your server, and I'll set up a cron job to mirror it every night to
: ftp.linuxhacker.org/pub/microwindows/ ? I'm going to stay late tonight,
: get the CVS set up, and start integrating it.
Sure, if you want to mirrow the Micro-Windows download area,
use microwindows.censoft.com/pub/microwindows.
:
: > uses, and we need to think about whether we want that or not. The RGB
: > color model mods are included in the version that I've posted with the
: > micro-windows project, however.
:
: Yes, I'm not really sure what to do about the colours. There seem to be
: two main possible ways:
: * The clients ask the server how many bits of colour depth the display has
: and thenceforth simply supply the relevant sized colour words.
: * The clients always talk RGB and the server converts it to whatever it is
: using at the time.
: The first one makes the server more lightweight, and slightly reduces the
: network bandwidth if you're running the server in a low bit depth, but the
: client or widget set has to be more complex. X seems to use a much more
: complex model where an application can request different colour maps and
: things, but I don't think we want to support that level of complexity.
I think that the RGB model is the way to go. Check it out in Micro-windows.
It doesn't care about how many bits the display has, as I have developed
separate 4bpp and 8pp standard palettes, and a color selection algorithm
based on weighted distance squares, so an application can ask for any RGB color.
So, the client always talks RFB. In addition, I built an api that allows the
client to reload the system palette at any partial point, or continue
aggregating colors into the system palette. Try using Micro-windows, with
256 color bitmaps in the demo windows, and a 256 color desktop wallpaper image.
You'll quickly see where the problems are.
I didn't include the RGB model in your nano-X distribution because of
tons of changes, on top of other changes. In addition, I've been thinking that nano-X
probably should become completely X-compliant in the api's that it provides,
much like micro-windows does for win32. In this way, It's actually a mini-replacement
for X.
Greg
