ReactX - Wrapper or not?
Moderator: Moderator Team
ReactX - Wrapper or not?
Hi,
I got a pretty general question (thus I posted it in the general discussion forum ):
Will ReactX be a wrapper around OpenGL (like WineD3D), or will it be a own implementation communicating with the graphics driver?
Cheers,
eXile.
I got a pretty general question (thus I posted it in the general discussion forum ):
Will ReactX be a wrapper around OpenGL (like WineD3D), or will it be a own implementation communicating with the graphics driver?
Cheers,
eXile.
-
- Posts: 52
- Joined: Tue Jul 04, 2006 1:39 pm
- EmuandCo
- Developer
- Posts: 4723
- Joined: Sun Nov 28, 2004 7:52 pm
- Location: Germany, Bavaria, Steinfeld
- Contact:
It will be a REAL DirectX, no Wrapper to OGL. But first some GDI and win32k Stuff needs work.
ReactOS is still in alpha stage, meaning it is not feature-complete and is recommended only for evaluation and testing purposes.
If my post/reply offends or insults you, be sure that you know what sarcasm is...
If my post/reply offends or insults you, be sure that you know what sarcasm is...
AFAIK Current windows design would make it difficult to have 2 Dx implementations installed.
As the system get mature we should really have some kinda mechanism for installing/removing/switching components that would otherwise be just defaulted with windows (explorer, directx, .net, various libraries etc)
As the system get mature we should really have some kinda mechanism for installing/removing/switching components that would otherwise be just defaulted with windows (explorer, directx, .net, various libraries etc)
Wined3d works with windows just by swapping dlls.
Of course you cannot use both at once. You have to select what one you wish to use.
Only main reason for wined3d is testing and inside vm's. Please note wined3d development is currently being assisted in places by Parallels vm to use with XP 2000 2003 so Direct X can be past back to the opengl of the host os. They were also the ones that proved the port was possible. Of course wined3d might disappear from usefulness if React X has a driver that can talk back to opengl if needed.
So a install option would be enough. Because I guess in time React X will have direct 10 native without needing wined3d to boost. Other reason why wined3d is being ported.
Of course you cannot use both at once. You have to select what one you wish to use.
Only main reason for wined3d is testing and inside vm's. Please note wined3d development is currently being assisted in places by Parallels vm to use with XP 2000 2003 so Direct X can be past back to the opengl of the host os. They were also the ones that proved the port was possible. Of course wined3d might disappear from usefulness if React X has a driver that can talk back to opengl if needed.
So a install option would be enough. Because I guess in time React X will have direct 10 native without needing wined3d to boost. Other reason why wined3d is being ported.
Now here's a question, is it really reactos's place to prescribe a Dx implementation?wined3d are only a tempary solvtions until our own native dx are ready.
as Z98 say. he is inform why wined3d was imported and it still have some issue it does not work in ReactOS for ReactOS or mesa3d bugs.
Or for that matter any of the other higher user components?
I mean isn't the MS monoculture part of what's wrong with windows?
For example i was surprised to find that ReactOS is coming up with it's own .net implementation, when Mono is out there already...
YES. A true Direct X can use Direct X drivers.
Wined3d cannot. Note not all cards have Opengl drivers. Some have Opengl to direct X wrappers. Wine would be completely useless with them.
Pnet and Mono are both options for .net. Please note Mono directly supports different versions. If it was found ros's .net would perform better with alterations to make it more correct I see no reason why not do it.
Please note Reactos Direct X last time I asked GreatLord is being based on Windows 2000 design. This one program running cannot crash OS by calling it wrong. XP you can crash the OS by calling it wrong. It is not a major speed difference either.
Microsoft problem is not only a mono culture problem. It is that OS stability and security are put second at times traded for user ability and speed.
Wined3d cannot. Note not all cards have Opengl drivers. Some have Opengl to direct X wrappers. Wine would be completely useless with them.
Pnet and Mono are both options for .net. Please note Mono directly supports different versions. If it was found ros's .net would perform better with alterations to make it more correct I see no reason why not do it.
Please note Reactos Direct X last time I asked GreatLord is being based on Windows 2000 design. This one program running cannot crash OS by calling it wrong. XP you can crash the OS by calling it wrong. It is not a major speed difference either.
Microsoft problem is not only a mono culture problem. It is that OS stability and security are put second at times traded for user ability and speed.
Who is online
Users browsing this forum: No registered users and 37 guests