Future Start Menu
Moderator: Moderator Team
Except for windows 95 , it looks like 2003 wich is the latest Server OS from Microsoft.betaluva wrote:i think at some point in the future reactos should be released in two versions , one plain basic edition with the current explorer etc and a fulll multimedia gui version, i show screnshots of reactos to people and they just laugh and say im not using a os that looks like windows 95.
The people that choose an os by the appearance should learn that there are many other important things in an OS.
I think if ROS is stable to work with it than we can discuss about something like the GUI or other applcation, a Basic and a Multimedia Edition etc.
Programm all ideas, but make it so that its be removable ex. for the basic edition.
Yes do it, the it's a lot of Programmers who can't programming some heavy system things, but other things good.
I'm for the Idea from artguy10
With Greeting Ground0
PS:Sorry about my bad english.
Programm all ideas, but make it so that its be removable ex. for the basic edition.
Yes do it, the it's a lot of Programmers who can't programming some heavy system things, but other things good.
I'm for the Idea from artguy10
With Greeting Ground0
PS:Sorry about my bad english.
ReactOS SVN ... Firefox... OpenOffice...
-
- Posts: 52
- Joined: Tue Jul 04, 2006 1:39 pm
It's always funny when people forget that even slight and even beneficial stems from Windows design are gonna break compatibility...Speekix wrote:why we need only one type of the start menu????? why not to support natively different themes for the menu????
ReactOS has to run the same way Windows does. Any hacked-in custom start menu is a potential compatibility issue (and we currently got a LOT of them)
-
- Posts: 318
- Joined: Wed Jun 15, 2005 8:19 am
I think Speekix means support all types of Start Menus currently available from Classic to Vista?InFeRnODeMoN wrote:It's always funny when people forget that even slight and even beneficial stems from Windows design are gonna break compatibility...Speekix wrote:why we need only one type of the start menu????? why not to support natively different themes for the menu????
ReactOS has to run the same way Windows does. Any hacked-in custom start menu is a potential compatibility issue (and we currently got a LOT of them)
EDIT: used wrong name
-graey-
Lol.
That makes me laugh.
No, Using a custom start menu will not break compatibility. Ever. Only if you tried to change the layout of files, but thats not even smart. Other than that, its no different than XP having its own start menu or Vista having its own. See, you may or may not know that the only compatibility breaks are caused by API and file layouts, and occasionally a few other things (However, I've never saw the start menu cause a problem.) The way you speak, it sounds like having a Non-Microsoft Icon set would be problematic. That sounds just as redundant.
Hell, WindowBlinds can change the Start Menu - Sure, it can cause compatibility breaks, but thats completely unrelated from the custom start menu. (Notice: ReactOS can not yet use WindowBlinds. I believe there are a few hooking and GUI things that are currently unimplemented and/or broken, along with DirectX which would be a problem.)
That makes me laugh.
No, Using a custom start menu will not break compatibility. Ever. Only if you tried to change the layout of files, but thats not even smart. Other than that, its no different than XP having its own start menu or Vista having its own. See, you may or may not know that the only compatibility breaks are caused by API and file layouts, and occasionally a few other things (However, I've never saw the start menu cause a problem.) The way you speak, it sounds like having a Non-Microsoft Icon set would be problematic. That sounds just as redundant.
Hell, WindowBlinds can change the Start Menu - Sure, it can cause compatibility breaks, but thats completely unrelated from the custom start menu. (Notice: ReactOS can not yet use WindowBlinds. I believe there are a few hooking and GUI things that are currently unimplemented and/or broken, along with DirectX which would be a problem.)
Programmers: Help us put Vista graphics drivers on Linux! The WDOL Project Homepage
Hi,
Regards,
eXile.
I aggree with you. In OOP its called an "observer pattern". Even though ReactOS / the respective component is written in C, there is certainly a aquivalent approach used. Really ridiculous. However, theming would be a far better approach than "hacking the stuff into the code".No, Using a custom start menu will not break compatibility. Ever. Only if you tried to change the layout of files, but thats not even smart. Other than that, its no different than XP having its own start menu or Vista having its own. See, you may or may not know that the only compatibility breaks are caused by API and file layouts, and occasionally a few other things (However, I've never saw the start menu cause a problem.) The way you speak, it sounds like having a Non-Microsoft Icon set would be problematic. That sounds just as redundant.
Regards,
eXile.
-
- Posts: 475
- Joined: Sun Jun 10, 2007 3:56 am
I've gotten rather fed up with the classic interface, as I've used it for about 12-14 years (the number varies based on whether or not you count Win311's interface), and I believe I've seen enough grey for the rest of my life. On the other hand, functionality has a higher priority to me. I'd rather have a very powerful grey interface than a numbed down eyecandy interface (*cough* Mac OS X *cough*). Needless to say though, the two can be combined. As for ReactOS, I think it should be obvious that functionality will first be implemented, and that the candy can always be added later.
It compiles, let's ship it!
Who is online
Users browsing this forum: No registered users and 16 guests