Page 1 of 1

graphical shell plans

Posted: Tue Feb 27, 2007 12:13 am
by herorev
What are the plans concerning the graphical shell?

Will ReactOS eventually switch to a more mature shell like LiteStep, or will ROS Explorer be kept and improved? Or will something even more established like KDE be used?

It would seem like reinventing-the-wheel to create a whole new shell/environment when there are so many mature ones out there.

Posted: Tue Feb 27, 2007 12:45 am
by Z98
There is a plan to rewrite ROS Explorer. The devs have already rejected integrating shells like KDE or for that matter any other shell that does not look and feel just like the Windows shell. And while KDE is similar, it's no where close enough. The basic reasoning behind this is that this has to look and feel like Windows, not just have similar underlying technologies.

Posted: Tue Feb 27, 2007 7:15 am
by GreyGhost
Hello,
As Z98 said the ROS explorer will be under going a rewrite to remove some of the many bugs and improve it in the whole...
I think stickin to ROS explorer is better as it will be more or less similar to what u see on Windows so a user who wants to migrate to ROS will fin it much easier and for other shells (IMO) u need a bit getting used to ...

But once ROS is stable enough u can happily use any other shell u wish to use just like u would in windows .. :)

Posted: Tue Feb 27, 2007 9:44 am
by groganm
Hello,
Is there any point in trying to become familiar with the existing explorer code to try to resolve the many outstanding bugs? Or is a complete (C based) rewrite more likely? I read somewhere that there was going to be some consultation with people that have good user interface experience?
Thanks,

Posted: Tue Feb 27, 2007 11:04 am
by Ged
it would probably be best to concentrate your efforts elsewhere.

aero

Posted: Fri Mar 02, 2007 5:07 am
by Floyd
i would personally like to see a beryl type project in the future for react ...
not to replace reactos explorer, but rather to offer an alternative to aero ...
directx10 is going to a big hurdle for react i think, anyway.

Posted: Fri Mar 02, 2007 11:23 am
by GreatLord
dx10 is small problem.
I am only working on dx 1-7 graphice part, but before I can coninue my work I often land by I need fixing bug x,y,z then I can go back doing test and write code for 1-2 days until I run into next x,y,z bug. so on.

either it is something does not working or the test apps I am using 3d party close source are missing a api or triger some bugs I need take care of before I can continue.

Posted: Fri Mar 02, 2007 1:01 pm
by Radhad
And what about DirectX 8 & 9? Will it be implemented after DirectX 1 to 7 or is someone else working on it?

Posted: Fri Mar 02, 2007 3:20 pm
by GreatLord
8 & 9 is using same kernel interface and user mode interface, it is question of user mode dll we are missing for it. that are need it be writen
when dx graphice gdi32/win32k works to 100%

dx graphice
1-7 ddraw.dll
8 d3d8.dll
9 d9d9.dll

if u we talking simple graphice interface for dx to getting some games working

Posted: Fri Mar 02, 2007 3:49 pm
by Radhad
GreatLord wrote:8 & 9 is using same kernel interface and user mode interface, it is question of user mode dll we are missing for it. that are need it be writen
when dx graphice gdi32/win32k works to 100%

dx graphice
1-7 ddraw.dll
8 d3d8.dll
9 d9d9.dll

if u we talking simple graphice interface for dx to getting some games working
You said some games may work then. As far as I know there were a lot of DirectX9 updates in the past, the latest was in february 2007. So these changes & updates have to be added later on?

Posted: Fri Mar 02, 2007 5:22 pm
by GreatLord
directx are over 100 diffent dll and not everyone are being in use,
games most using
ddraw.dll <- we need write thuse self
d3d8.dll <- we need write thuse self
d3d9.dll <- we need write thuse self
dinput.dll <- ported from wine with allot bugfix and implement some api
dsound.dll <- ported from wine with a warper I wrote works in windows

then we got whole gdi32.dll and win32k.sys
I am working basic only on gdi32.dll and win32k.sys at moment
make sure all api works as they should
(windows xp/2003 model)
d3d9.dll -> d3d8thk.dll->gdi32.dll->win32k.sys->the drv
d3d8.dll -> d3d8thk.dll->gdi32.dll->win32k.sys->the drv
ddraw.dll -> gdi32.dll->win32k.sys->the drv

Posted: Sat Mar 03, 2007 12:00 am
by Phalanx
GL, with vista has the gui been moved into user space? If it is place through DirectX, is that just an effect on what is drawn in gdi, or is it done in DirectX?

Posted: Mon Mar 12, 2007 4:50 pm
by jason.b.c
can this work in Ros...?


http://ozonegui.net/

Posted: Mon Mar 12, 2007 5:15 pm
by GreyGhost
Best thing is to try.. but it *may* need porting as the windows version needs DX 5 ++ or we need to wait till DX work gets well ahead ..

Posted: Tue Mar 13, 2007 2:48 am
by jeff.sadowski
Z98 wrote:There is a plan to rewrite ROS Explorer. The devs have already rejected integrating shells like KDE or for that matter any other shell that does not look and feel just like the Windows shell. And while KDE is similar, it's no where close enough. The basic reasoning behind this is that this has to look and feel like Windows, not just have similar underlying technologies.
Oh great that means your going to change it every four years :lol: