But it will be good to support drivers from NT6 too, to improve the hardware compatibility and fix some problem with NT6 softwares.
Aspects of Vista/7/8/10 (and sometimes 5.2) that should NOT be ported to React
Moderator: Moderator Team
-
- Posts: 227
- Joined: Wed Feb 21, 2018 3:46 pm
- Location: Somewhere in France
Re: Aspects of Vista/7/8/10 that should NOT be ported to React
Re: Aspects of Vista/7/8/10 that should NOT be ported to React
Obviously!
Skillset: VMS,DOS,Windows Sysadmin from 1985, fault-tolerance, VaxCluster, Alpha,Sparc. DCL,QB,VBDOS- VB6,.NET, PHP,NODE.JS, Graphic Design, Project Manager, CMS, Quad Electronics. classic cars & m'bikes. Artist in water & oils. Historian.
Re: Aspects of Vista/7/8/10 that should NOT be ported to React
windows Photo Viewer is good enough to do the job but there are better image viewers
that is more of a edge case scenario
you are partially wrong you can edit content of folders in "Program Files" & "Program Files (x86)" you need to take ownership of the program folder there is a tweak to add take ownership to the right click but if i know that i am going to add mods to a game then i create a folder on the root of my c: and name it games and any games that i install to that folder inherit the permissions so i can edit the game fileswdstudios wrote: ↑Tue Aug 21, 2018 11:59 pm In NT 5.x, users could edit the contents of the "Program Files" and "Program Files (x86)" directories. In NT 6.x, this is not authorized, even for administrators, which is a huge pain in the ass when developing game mods, or really just for anyone who wants to be treated like an adult and like the owner of their own f**king computer.
i have never had this issue but most of the time i use teracopy when copying/moving files
imho the Vista + searches is garbage
windows 8
ribbon bar in windows explorer file manager and WordPad and Paint
the start screen
right click Jump lists
forcing user to use the settings metro app / the settings metro app
metro apps
there are a lot more Aspects of windows 10 that should NOT be ported to React that bug me
-
- Posts: 64
- Joined: Tue Mar 13, 2018 4:28 am
- Location: Dixon, California
- Contact:
Re: Aspects of Vista/7/8/10 that should NOT be ported to React
Well call me stupid but I liked the metro apps idea. Compatibility would be cool, just... don't implement the actual metro crap and just only have metro compatibility.
Also, I liked Windows 10's multi-desktop system... but that's just me.
"We are going to have to act, if we want to live in a different world."
Proud owner of one semi-modern ROS compatible computer. I hope to make an industry out of selling ROS compatibles the moment 0.5.0 releases.
Proud owner of one semi-modern ROS compatible computer. I hope to make an industry out of selling ROS compatibles the moment 0.5.0 releases.
-
- Posts: 531
- Joined: Thu Jan 10, 2013 6:17 pm
- Contact:
Re: Aspects of Vista/7/8/10 that should NOT be ported to React
Interesting trivia: Earlier versions of ROS did have multiple desktops.Missingno50 wrote: ↑Wed Sep 05, 2018 7:59 pm Also, I liked Windows 10's multi-desktop system... but that's just me.
Re: Aspects of Vista/7/8/10 that should NOT be ported to React
That's how it was theoretically pretend supposed to work. In reality, it didn't work.MadWolf wrote: ↑Wed Sep 05, 2018 6:19 pmyou are partially wrong you can edit content of folders in "Program Files" & "Program Files (x86)" you need to take ownership of the program folderwdstudios wrote: ↑Tue Aug 21, 2018 11:59 pm In NT 5.x, users could edit the contents of the "Program Files" and "Program Files (x86)" directories. In NT 6.x, this is not authorized, even for administrators, which is a huge pain in the ass when developing game mods, or really just for anyone who wants to be treated like an adult and like the owner of their own f**king computer.
-
- Posts: 1790
- Joined: Fri Aug 07, 2009 5:11 am
- Location: USA
Re: Aspects of Vista/7/8/10 that should NOT be ported to React
Yes, until Gigaherz made the new explorer work. I remember those days.karlexceed wrote: ↑Wed Sep 05, 2018 8:33 pm trivia: Earlier versions of ROS did have multiple desktops.
Last edited by PurpleGurl on Sat Sep 08, 2018 1:56 am, edited 1 time in total.
- EmuandCo
- Developer
- Posts: 4787
- Joined: Sun Nov 28, 2004 7:52 pm
- Location: Germany, Bavaria, Steinfeld
- Contact:
Re: Aspects of Vista/7/8/10 that should NOT be ported to React
Gigaherz
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...
Re: Aspects of Vista/7/8/10 that should NOT be ported to React
Gigaherz is at least a thousand times better coder than megaherz.
Skillset: VMS,DOS,Windows Sysadmin from 1985, fault-tolerance, VaxCluster, Alpha,Sparc. DCL,QB,VBDOS- VB6,.NET, PHP,NODE.JS, Graphic Design, Project Manager, CMS, Quad Electronics. classic cars & m'bikes. Artist in water & oils. Historian.
-
- Posts: 531
- Joined: Thu Jan 10, 2013 6:17 pm
- Contact:
Re: Aspects of Vista/7/8/10 that should NOT be ported to React
Hidden APIs known only to Microsoft - that sort of feature will NEVER be ported to ReactOS - obviously, I am assuming that in the process of coding and reverse engineering Windows the devs could actually discover some of these? Could this have happened already?
Skillset: VMS,DOS,Windows Sysadmin from 1985, fault-tolerance, VaxCluster, Alpha,Sparc. DCL,QB,VBDOS- VB6,.NET, PHP,NODE.JS, Graphic Design, Project Manager, CMS, Quad Electronics. classic cars & m'bikes. Artist in water & oils. Historian.
- EmuandCo
- Developer
- Posts: 4787
- Joined: Sun Nov 28, 2004 7:52 pm
- Location: Germany, Bavaria, Steinfeld
- Contact:
Re: Aspects of Vista/7/8/10 that should NOT be ported to React
There are many APIs MS does not make public and does not recommend to tinker with. And we already have many of these. Same goes for Wine btw. We HAVE to add these to be able to run any WIndows app out there.
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...
Re: Aspects of Vista/7/8/10 that should NOT be ported to React
Thankyou for that. I understand that we port them as we find them but in the process they then become public and not hidden I assume? So, what I am saying is, we have no hidden APIs...
Skillset: VMS,DOS,Windows Sysadmin from 1985, fault-tolerance, VaxCluster, Alpha,Sparc. DCL,QB,VBDOS- VB6,.NET, PHP,NODE.JS, Graphic Design, Project Manager, CMS, Quad Electronics. classic cars & m'bikes. Artist in water & oils. Historian.
-
- Posts: 1790
- Joined: Fri Aug 07, 2009 5:11 am
- Location: USA
Re: Aspects of Vista/7/8/10 that should NOT be ported to React
Yes, you have a point. If we find them or they are revealed to us, then they are not "hidden." Plus our documentation is more likely to be accurate, and it probably isn't best for me to fully elaborate why that is the case here. I will just say that the court ordered that the APIs be documented publicly, but did not stipulate who was to prepare it or how accurate it had to be.
Now more to the topic, if we change targets, then there are things we'd have to port, even if we don't like them. Those would be changes related to graphics and sound. Hardware sound acceleration would likely not be usable, and getting a compositing engine (DWM) would likely be necessary.
Now more to the topic, if we change targets, then there are things we'd have to port, even if we don't like them. Those would be changes related to graphics and sound. Hardware sound acceleration would likely not be usable, and getting a compositing engine (DWM) would likely be necessary.
-
- Posts: 119
- Joined: Fri Jun 27, 2014 9:01 am
Re: Aspects of Vista/7/8/10 that should NOT be ported to React
I don't know about a compositing engine being required, in windows the DWM can be stopped and the gui still works just no transparent effects are available. That being said i'm sure most users would want a compositing engine if ReactOS ever gets NT6+ driver compatibilityPurpleGurl wrote: ↑Sat Sep 22, 2018 9:11 pm Now more to the topic, if we change targets, then there are things we'd have to port, even if we don't like them. Those would be changes related to graphics and sound. Hardware sound acceleration would likely not be usable, and getting a compositing engine (DWM) would likely be necessary.
Who is online
Users browsing this forum: Bing [Bot] and 13 guests