On Mon, 13 Dec 1999, John Fortin wrote:
>
>
> Marcus Sundberg wrote:
> >
> > James Simmons <[EMAIL PROTECTED]> writes:
> >
> > > I had a interesting discussion on the possiblility of having a Direct X
> > > on linux with John Carmack. Well it appears Mircosoft will sue anyone that
> > > tries that. So I talked to him about Mesa-GGI and how Direct X support was
> > > added to libGGI. So to the person that wrote the Direct X interface. Do
> > > you think you have a enough of a bridge between Direct X and GGI to allow
> > > Mesa-GGI programs to run on top of Direct X completely?
> >
> > Mesa-GGI requires nothing more than a DirectBuffer, which I assume
> > the DirectX target will have. Mesa-GGI needs to be fixed to use
> > the LibGGI API correctly before it will work on targets where you
> > must acquire DirectBuffers though, something which I assume the
> > DirectX target will require. Right John?
>
> I'm torn here. The current version I am using does not need to acquire
> the
> direct buffer. However, it uses features available only on win
> 95/98/W2K.
> It will not work on NT4, as NT4 only supports directx v3.
>
> I think that I will end up with a separate NT4 version which will not be
> as
> flexible as the Win 95/98/2K version. Eventually, the NT4 version would
> go away
> as it is replaces by Win2K.
Seems to me that a LibGGI helperlib for the DirectX target is what
is needed here. That is, you have one generic core DirectX target, which
exports some simple APIs to which you can attach special-case helper
libraries for DX3, DX7, buffer mapping, etc. This type of situation is
exactly what helperlibs are made for. Take a look at the vgagl helper
which is used with the svgalib target for a good example of how to use a
helperlib. The mansync and linvtsw helperlibs are also good examples.
Jon
---
'Cloning and the reprogramming of DNA is the first serious step in
becoming one with God.'
- Scientist G. Richard Seed
