Code reviewers sought for Lilith emulator.

[der Mouse]

>> [...coding in Xlib...wheel reinvention...]
> It's already been done, and now there are standard wheels (GTK, QT,
> etc.).

Yeah, and I've yet to find one that supports interfaces I can actually
stand (as user and programmer).  (Of lower but still moderate
importance, most of them require half of hell's back acre to build.)

I've actually been thinking for a while now that I should go through my
X programs and put together some kind of toolkit, even if only for my
own use.

> Using an existing system allows your application to function well,
> and allows you to think about more important things than "Gee, this
> thing would look better if I moved it 3 pixels to the left and
> changed the color a bit.  Oh well, I'll have edit the code some more
> because I didn't make a facility to do that."

Where do you get this delusion that using Xlib directly means a lack of
configurability?  Or constant macdinking?

> Then, you have the disadvantage (some would say advantage, but I'd
> say that's misguided) of having your app look and behave completely
> different from everything else the end user runs.

You mean, like, if you use one toolkit and most of the stuff the user
runs uses a different one?

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		mouse at rodents-montreal.org
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B