Designed for ReactOS logo. The development of its own specif

Here you can discuss ReactOS related topics.

Moderator: Moderator Team

Post Reply
towerr
Posts: 258
Joined: Wed Jun 20, 2007 3:01 am

Designed for ReactOS logo. The development of its own specif

Post by towerr »

Designed for ReactOS logo. The development of its own specification.
originally posted by bz00mmer (on russian part) http://www.reactos.org/forum/viewtopic.php?t=5874
translated by criso

It is no secret that Windows possesses the number of deficiencies, which are largely not inherent to it's design but rather to (1) the organization of its security (2) the large number of poorly designed applications, which require Administrator privilege to function, and (3) the haphazard directory structure layout, what can lead to significant reduction in productivity? and the formation of garbage in the filesystem and registry after numerous program installs/uninstalls.

I considered the issue of security in the context of ReactOS and consider that we are capable of making new security policies, such as will prevent viruses from damaging the system, and hackers from seizing control of the computer. ReactOS itself can forge ahead with the necessary security policies, but what can be done with thousands of poorly designed applications? A large number of them will cease to work.

One outcome is that developers or end users will be forced to decrease security policy, and in consequence the planned level of security will never be implemented; the alternative is an unwavering position on security: over time, the number of users will grow, and software developers will be forced to correct their applications.

Besides security - what can be done with the accumulated garbage in the file system and registry?
In this respect ReactOS can follow a similar path to Linux - a directory for each file type:
applications, libraries, control panels, temporary files and the user's documents.

I will give a simple example - application configuration:

Method A will preserve them in HKEY_CURRENT_USER\software\a_company\a_app\
?? Method B will preserve them already in HKEY_LOCAL_MACHINE\software\b_company\b_app\
Method C will store settings relative to the program directory: .\C.exe and .\config\c.ini
Method D will preserve them in C:\WINDOWS\D_app.ini
Method E will preserve them in C:\WINDOWS\E_company\e_app.ini
Method F will hide the configuration files in C:\Documents and Settings\User_Name\local settings\application data\f_company\f_app\
Method H will store them in C:\Documents and Settings\All Users\application data\H_app
?? - not found!
And there are still more possibilities! And this only for config files: for libraries, ??

There are two scenarios: to lay this task on the developers of ReactOS or on the developers of user software.
What can the OS developers do? Can we specify which method should be native for any one application and, re-route it's files into the appropriate places? Practically - realized, logically - it is irrational. ??
The developers of user ON will make this much better, only by them to know as!

Proposed solution:
To create an analog of the Certified for Windows logo, with a list of requirements for any application which must be strictly adhered to in order to obtain the honorable designation of Designed for ReactOS.

Now I am not proposing a list of requirements here, as it is first necessary to agree on idea itself.


Topical references:
Windows Server "Longhorn" Logo for Software
Download details: Designed for Windows XP Application Specification
hto
Developer
Posts: 2193
Joined: Sun Oct 01, 2006 3:43 pm

Re: Designed for ReactOS logo. The development of its own specif

Post by hto »

I think moderators may delete this duplicate topic.
Post Reply

Who is online

Users browsing this forum: Alexisgarcia, Google [Bot], Semrush [Bot] and 2 guests