Re: [Mono-dev] Managed DirectX

2006-10-26 Thread Stefan Dösinger
Am Donnerstag 26 Oktober 2006 17:46 schrieben Sie: > > At the moment wined3d calls glx directly, but we want to change it to use > > our opengl32.dll instead and fix some opengl issues(windowed gl, > > glx<->agl abstraction) in opngl32.dll. > > I think I don't understand what you're looking for. Ma

Re: [Mono-dev] Managed DirectX

2006-10-26 Thread Brian Crowell
Jon Chambers wrote: all currently. A brief benchmark showed COM Interop on mono running at about 5x slower than on .Net. I'm sure that will get better if I spend some time working on that (but I'd rather get some other features working first). I don't know how this compares to the icall example

Re: [Mono-dev] Managed DirectX

2006-10-26 Thread Jon Chambers
If you're asking about the performance of the current COM Interop implementation, I don't have many answers. It has not been optimized at all currently. A brief benchmark showed COM Interop on mono running at about 5x slower than on .Net. I'm sure that will get better if I spend some time working o

Re: [Mono-dev] Managed DirectX

2006-10-26 Thread Brian Crowell
Jon Chambers wrote: > interop assemblies. If you want to try anything out on mono, you will > need to build you interop assemblies with .Net (either by hand or via > tlbimp). If you need any other help let me know. All right, I went back and found the COM import examples in the .NET documentati

Re: [Mono-dev] Managed DirectX

2006-10-26 Thread Brian Crowell
> Unfortunately this dll depends on Wine. The dependency is not too big, but > needed for certain functionality, namely IWineD3DSurface::GetDC. This method > allows applications to do normal gdi operations on d3d surfaces and the > framebuffer. I don't know if managed dx still supports that, bec

Re: [Mono-dev] Managed DirectX

2006-10-26 Thread Stefan Dösinger
Hi, > Does the library depend on the rest of Wine to run? > > Am curious if it is possible to write a C program that can just call > into these libraries directly? > > I mention this because Mono would be accessing the libraries by > dlopening them, looking up the addresses of methods with dlsym a

Re: [Mono-dev] Managed DirectX

2006-10-25 Thread Miguel de Icaza
Hello, > I am one of the programmers of the Wine Direct3D implementation, and I > wondered if there are any plans to implement Managed DirectX in Mono, and if > it is possible to share efforts between wine and mono? This would be fantastic. > This is basically what the wine direct3d code looks

Re: [Mono-dev] Managed DirectX

2006-10-25 Thread Brian Crowell
Stefan Dösinger wrote: > So from the other replies it sounds like you can use wine for dx, but mono > needs some preparation work first. If you need any help just contact me or > the wine-devel list :-) Well, one option is to use a library written in C++/CLI, compile it with Microsoft's C++ com

Re: [Mono-dev] Managed DirectX

2006-10-25 Thread Stefan Dösinger
Am Mittwoch 25 Oktober 2006 19:02 schrieben Sie: > A practical example of building a wrapper by hand would be most helpful. > Late binding is not an option, and I haven't ever found interface > definition files for DirectX9. As far as I know idl files for dx9 do not exist, only the d3d9.h, d3d9type

Re: [Mono-dev] Managed DirectX

2006-10-25 Thread Brian Crowell
Michael Schurter wrote: > Careful what you do with ILDASM Brian, at least if you plan on > contributing code to the mono project: Yes, I know. I mostly just wanted to figure out how they made calls; everything else in my own managed implementation is written from scratch using documentation. Be

Re: [Mono-dev] Managed DirectX

2006-10-25 Thread Michael Schurter
Brian Crowell wrote: > Richard Matthias wrote: >> It's worth mentioning that Microsoft's Managed DirectX doesn't use COM >> interop. They have a library with a simpler C interface that talks to >> the kernel portion of DirectX that the drivers plug into and the MDX >> library uses that - it's almos

Re: [Mono-dev] Managed DirectX

2006-10-25 Thread Brian Crowell
Richard Matthias wrote: > It's worth mentioning that Microsoft's Managed DirectX doesn't use COM > interop. They have a library with a simpler C interface that talks to > the kernel portion of DirectX that the drivers plug into and the MDX > library uses that - it's almost completely seperate from

Re: [Mono-dev] Managed DirectX

2006-10-25 Thread Richard Matthias
It's worth mentioning that Microsoft's Managed DirectX doesn't use COM interop. They have a library with a simpler C interface that talks to the kernel portion of DirectX that the drivers plug into and the MDX library uses that - it's almost completely seperate from the DirectX that C++ developers

Re: [Mono-dev] Managed DirectX

2006-10-25 Thread Brian Crowell
Jon Chambers wrote: > I am working on COM Interop support in mono. ... > ... If you want to try anything out on mono, you will need to > build you interop assemblies with .Net (either by hand or via tlbimp). If you > need any other help let me know. A practical example of buildin

Re: [Mono-dev] Managed DirectX

2006-10-25 Thread Jon Chambers
I am working on COM Interop support in mono. Alot of functionality is currently available for calling unmanaged COM objects from managed code (Runtime Callable Wrappers) in mono. I am working on COM Callable Wrappers right now and should have something in svn in the near future. Some details may ne

Re: [Mono-dev] Managed DirectX

2006-10-25 Thread Brian Crowell
Stefan Dösinger wrote: > I am one of the programmers of the Wine Direct3D implementation, and I > wondered if there are any plans to implement Managed DirectX in Mono, and if > it is possible to share efforts between wine and mono? Hello. I started on an open implementation of the XNA libraries

[Mono-dev] Managed DirectX

2006-10-25 Thread Stefan Dösinger
Hi, I am one of the programmers of the Wine Direct3D implementation, and I wondered if there are any plans to implement Managed DirectX in Mono, and if it is possible to share efforts between wine and mono? I googled around a bit, but couldn't find anything substancial, except that this was dis