On Thu, 21 Jun 2001, Christoph Egger wrote:
> There is no doubt, that libggi supports some targets, which are only
> on some OS's available. So we shouldn't try to open the target, when
> it isn't available on the OS at all. We should fail instead.
> Here is a list of targets, libggi has. Please correct the list.
>
> We should enable/disable the targets by checking #defines.
I think the reason this hasn't been done is that folks were
trying to decide between this, and building a display-auto-linux
(or display-auto-win32 or whatever), which we map to display-auto
in the config file. This would mean a lot less #ifdefs and cleaner code
all around. Basically, that would make ggiOpen(NULL) the same thing as
ggiOpen("display-auto").
> directX Win32
+ WINE (man, would that be a mess :-)
> glide depends, if glide is installed or not
If glide is not installed, then we should open anyway and let
it fail and move to the next.
> ipc *unknown by me*
Any UNIX.
> kgi *unknown by me*
Well eventually, Any OS, but the current kgi should be deleted
from the tree and return when libkgi is ready for primetime.
> monotext *unknown by me*
Any OS, it uses a parent textmode visual.
> suidkgi *unknown by me*
Should be removed.
> tele *unknown by me*
Any OS. Opens a visual on a remote host running ggiteleserver.
> terminfo *unknown by me*
Any UNIX.
> vcsa Linux, any OS else?
NTIKO. vcsa always struck me as a linux invention.
--
Brian
