3D based desktop?
Moderator: Moderator Team
The hell over microsoft blocking direct rendering of opengl came from ATI and Nvidia. Only time they were not fighting with each other.
It was simple give us back Direct Opengl rendering. Or you get no 3d drivers from us at all. Biggest standard writers of Opengl these days is NVidia and ATI. Some one did not do there homework at Microsoft. Telling the creators of a standard that after all there hard work they have to bin it was never going to fly.
It was simple give us back Direct Opengl rendering. Or you get no 3d drivers from us at all. Biggest standard writers of Opengl these days is NVidia and ATI. Some one did not do there homework at Microsoft. Telling the creators of a standard that after all there hard work they have to bin it was never going to fly.
I never really got the idea behind a 3D desktop. always been more in favour of blackbox (and windows alternatives) for designing everything the way you want.
the only usefull 3d-ish feature i can imagine is using a Z-index (like div layers) and it would be an awesome feature at that. i always want my chat screens to be on top of multiple other windows. but certain things like image viewers should be able to go over THAT without too much effort.
imho that would be a VERY awesome feature to have, but im quite sure i stand alone in wanting that :p
the only usefull 3d-ish feature i can imagine is using a Z-index (like div layers) and it would be an awesome feature at that. i always want my chat screens to be on top of multiple other windows. but certain things like image viewers should be able to go over THAT without too much effort.
imho that would be a VERY awesome feature to have, but im quite sure i stand alone in wanting that :p
I'd love to have a 3D Desktop with React OS. But until its beta, and of course until nVidia drivers(Of course, ATi, Intel, and other drivers would be nice to have working, but react os never ran them at any point) work again, its not something to worry about.
I do think that React OS should be designed with 3D Desktops in mind. It would be cool if we had a layer between the hardware mouse driver and applications that would be ready to change, so we could make windows that were in different positions and rotations in the 3D world react correctly to the mouse. But i doubt it will be taken so overly serious - the most you can hope for is a basic 3D desktop, kind of minimalistic for a 3D desktop, that makes React OS more modern. I mean, making it so every window reads different mouse coordinates because of the distance and rotation of the window would be going way out of hand, but having a smoothly moving desktop with a decently neat minimize, maximize and close effects is just fine for me. Maybe a nice looking window border.
Now I'm just blabbing though, since this is so far ahead and I'm a terrible programmer.
Seriously though, this stuff would be nice for after alpha, but i think that it belongs somewhere after 1.0. I'm sure that the talented developers working on React OS will eventually do something related. Its just that in stages like this compatibility, optimization, and clean code are much much more important.
edit: And i would love to hear if you can still play UT on React OS and what graphics driver (If not Mesa) works to be doing so.
I do think that React OS should be designed with 3D Desktops in mind. It would be cool if we had a layer between the hardware mouse driver and applications that would be ready to change, so we could make windows that were in different positions and rotations in the 3D world react correctly to the mouse. But i doubt it will be taken so overly serious - the most you can hope for is a basic 3D desktop, kind of minimalistic for a 3D desktop, that makes React OS more modern. I mean, making it so every window reads different mouse coordinates because of the distance and rotation of the window would be going way out of hand, but having a smoothly moving desktop with a decently neat minimize, maximize and close effects is just fine for me. Maybe a nice looking window border.
Now I'm just blabbing though, since this is so far ahead and I'm a terrible programmer.
Seriously though, this stuff would be nice for after alpha, but i think that it belongs somewhere after 1.0. I'm sure that the talented developers working on React OS will eventually do something related. Its just that in stages like this compatibility, optimization, and clean code are much much more important.
edit: And i would love to hear if you can still play UT on React OS and what graphics driver (If not Mesa) works to be doing so.
kde is built on qt so i think there's no connection to reactos where we are basing on winapi, i meant aero's underlaying desktop window manager (not like gdi: making graph drawing directly to screen) as basis for compositing effects and functionality.
i know that we need something like stable reactos but branching? sh..t there's always the same problem: we have no enough devs..
i know that we need something like stable reactos but branching? sh..t there's always the same problem: we have no enough devs..
already been asked: http://www.reactos.org/forum/viewtopic.php?p=25300.
KDE 4 on windows draws directly to screen threw Opengl at this stage.
Aero goes threw Direct X only so if you have a card that perform better in opengl you are out of luck.
KDE 4 will take no work from Reactos developers. Other than fixing defects in reactos as need. Since the KDE 4 developers are doing the cross port.
KDE 4 requires a lot less memory than Aero. Min mode is still only a 64 meg overhead. So a operational system with KDE 4 with Reactos is still under 128 megs of ram. KDE 4 fully operational at 256 megs of ram even running applications.
KDE 4 on reactos is still not light weight as reactos is aiming at.
Aero goes threw Direct X only so if you have a card that perform better in opengl you are out of luck.
KDE 4 will take no work from Reactos developers. Other than fixing defects in reactos as need. Since the KDE 4 developers are doing the cross port.
KDE 4 requires a lot less memory than Aero. Min mode is still only a 64 meg overhead. So a operational system with KDE 4 with Reactos is still under 128 megs of ram. KDE 4 fully operational at 256 megs of ram even running applications.
KDE 4 on reactos is still not light weight as reactos is aiming at.
to quote PCPlus, a computer magazine here in the UK, windows and macOSX use a system that can be described as "2.5D", not 3D. This is because they don't do fancy threedimensional effects and whatnot, but instead every window is rendered seperately (including the root window - ie the desktop) and then composited onto the screen using the 3D graphics card. This has the advantage that you don't have to worry about damage and redrawing, as it is all handled by the GPU. I've been playing with vista since it's release, and can say that the 2.5D improves things for me. 3D does not necessarily mean having a desktop that you walk through like doom, but rather utilising the previously untapped power that lies dormant in your graphics hardware until you fire up a game.
Who is online
Users browsing this forum: No registered users and 1 guest