It's because it will give time for Help and the docs to be written.Pi_User5 wrote:I read your report. I see that you don't want it implemented right away. Is there a reason or is this because this will give time for it to be written?
Blog: The TODO list, collaborative edition
Moderator: Moderator Team
-
- Posts: 101
- Joined: Sun Oct 21, 2012 11:57 pm
- Location: Melbourne, Victoria, Australia
- Contact:
Re: Blog: The TODO list, collaborative edition
Just think of ReactOS as the XP beta, Whistler.
Re: Blog: The TODO list, collaborative edition
Got it!
I use ReactOS on real hardware. Will you? My Computers: https://www.reactos.org/wiki/PC_ROS_Rigs Go all the way to the bottom.
[ external image ]
[ external image ]
Re: Blog: The TODO list, collaborative edition
A useful set of help documents is a big undertaking. The original XP help docs are frankly close to worthless: They never solved a single issue over all my years using it. I hope that any ROS doesn't dumb down their help docs like Microsoft. Updateable files would be great. There are already thousands of pages on the web with XP issues and their solutions that could be ported as needed when users come across them (though hopefully ROS actually avoids a lot of the buggyness in the first place).
For a beta release you're not going to get a flood of noob's with no idea what they are doing: Most of the people interested in an XP clone will be experienced XP users. It's been out for 13 years which is a long time to get used to its setup and quirks.
Please don't get into the microsoft/mozilla/google mindset of "don't touch this part its too complicated for you and you might break somethihng". The registry is a classic example: I could not count all the times (probably hundreds) I've had to manually change settings in the registry to fix a bug. A good guide to what's where in the registry and a fairly detailed description of shell operations would set ROS apart from all the other operating systems out there. Just because a person is inexperienced in such matters does not mean they are stupid and giving users "a peak under the hood" so to speak would be a good way to encourage more people to get into coding.
For a beta release you're not going to get a flood of noob's with no idea what they are doing: Most of the people interested in an XP clone will be experienced XP users. It's been out for 13 years which is a long time to get used to its setup and quirks.
Please don't get into the microsoft/mozilla/google mindset of "don't touch this part its too complicated for you and you might break somethihng". The registry is a classic example: I could not count all the times (probably hundreds) I've had to manually change settings in the registry to fix a bug. A good guide to what's where in the registry and a fairly detailed description of shell operations would set ROS apart from all the other operating systems out there. Just because a person is inexperienced in such matters does not mean they are stupid and giving users "a peak under the hood" so to speak would be a good way to encourage more people to get into coding.
Re: Blog: The TODO list, collaborative edition
It would be better if the docs were actually "ReactOS Internals" xD
Re: Blog: The TODO list, collaborative edition
If you want to mention Alex's Book here, there was AFAIK a Chinese guy who wrote a book about the ReactOS internals.hbelusca wrote:It would be better if the docs were actually "ReactOS Internals" xD
Re: Blog: The TODO list, collaborative edition
The book Alex mentioned in his talk in Toronto last year is Windows core scenario analysis - the use of open source ReactOS-(Chinese Edition) by MAO DE CAO.
Another book that mentions ReactOS is Build Your Own Security Lab: A Field Guide for Network Testing by Michael Gregg.
Both are on the big on-line book seller's web site.
Another book that mentions ReactOS is Build Your Own Security Lab: A Field Guide for Network Testing by Michael Gregg.
Both are on the big on-line book seller's web site.
Re: Blog: The TODO list, collaborative edition
BTW, isn't the weekly report/update overdue?
Re: Blog: The TODO list, collaborative edition
Indeed.... my F5 key is getting worn out....Webunny wrote:BTW, isn't the weekly report/update overdue?
-
- Posts: 441
- Joined: Sat Nov 15, 2008 4:13 pm
Re: Blog: The TODO list, collaborative edition
If you use Firefox you can make it check every so often and tell you when a page changes using an addon called update scanner
https://addons.mozilla.org/en-US/firefo ... e-scanner/
https://addons.mozilla.org/en-US/firefo ... e-scanner/
I reserve the right to ignore any portion of any post if I deem it not constructive or likely to cause the discussion to degenerate.
Re: Blog: The TODO list, collaborative edition
Maybe they should add an RSS feed instead, so you can keep track of updates without any addons.justincase wrote:If you use Firefox you can make it check every so often and tell you when a page changes using an addon called update scanner
https://addons.mozilla.org/en-US/firefo ... e-scanner/
-
- Posts: 441
- Joined: Sat Nov 15, 2008 4:13 pm
Re: Blog: The TODO list, collaborative edition
An RSS feed would also save on bandwidth as compared to refreshing the page (manually or with update scanner).
I reserve the right to ignore any portion of any post if I deem it not constructive or likely to cause the discussion to degenerate.
Who is online
Users browsing this forum: Bing [Bot], DotBot [Crawler], Semrush [Bot] and 67 guests