I think LibGalloc is for you, if it is possible at all to persuade
you to come back.
On Mon, 12 Mar 2001, Jos Hulzink wrote:
(about problems with LibGGI extensions)
> 1) No documentation.
LibGalloc Documentation is synced with source before each release. If
it is not documented, it is because we are still deciding how it will
be implemented. As long as I have anything to do with it, this
will always be the case.
> 2) Many libs that do many things, but the core GGI / KGI is forgotten.
>
> I know, GGI has beautiful "everything is a target" capabilities. It is
> cool to see a cube rotating with six visuals on it. But the practical use
> is none. What I still don;t see is a 3D hw accellerated application
> running, neigther in X nor Windows nor KGI. Okay, 3D isn't also the core
> activity of GGI, but without it, what is the use of yet another graphics
> library.
LibGalloc is the answer to this, though we are still a way away from
accessing 3D features. If you want to stay out from underneath the car
and maybe just hand us a wrench once and a while, then just give us some
time and it will become useful for apps development. If you like getting
a face full of motor oil, then bring your floor jack :-)
> 3) GGI and GII seem rather obsolete thanks to SDL. KGI has lost value due
> to the improving XFree (3d accel available, colour depth switching is
> coming). I know, XFree can't be compared with KGI, but at the moment,
> the only use of KGI for me would be getting my PPC into real textmode
> instead of Framebuffer, which would speed things up very much.
Well, as far as that is, you are right in the same way that people
who say Asyncronous Transfer Mode is obselete, now that there is
IP diffserv. But in both cases of course the latter is inferior
to the former, and it is just a matter of time before the former
exceeds the latter in some way that is critical enough to make it
"not obselete anymore" :-)
--
Brian
