On Tue, 19 Mar 2002, Eric Faurot wrote: > We could enforce this by taking the whole display/input dir out of > the libs tree and create a separate 'modules' repository, with one > subdir for each lib/extension. Then we could provide separate releases > for driver updates.
Hmmm... maybe later. I could see moving the .h files back, but then we need to deal with relative paths when one .h includes another, so there are arguments for the way it is now. Whatever we do we need to avoid the kind of mess like what is seen in the DirectFB source code (see libggi/default/fbdev/directfb/core/). > BTW, I'm not sure I understand the 'default/' in libgii. > AFAIK, it's for generic code that can be shared by different > targets. So it's ok for linear_*, but why fbdev is not in display? It is historically known as "default" because it used to only have the generic* stuff which was a default implementation for unaccelerated targets. Really, the directory should be called "renderer" but I'm not sure a rename is worth it. The stuff in there contains code for drawing (or color) primitives which can be used separately by display targets -- i.e. it does not contain the visual management stuff like setmode/etc. > And there are lots of kgi stuff too... KGI directories other than libkgi should be moved to an attic, IMO, Since they cannot drive the current KGI. libkgi is the playground. -- Brian
