Html user interface
Moderator: Moderator Team
-
- Posts: 18
- Joined: Fri Dec 03, 2004 1:12 am
- Contact:
Html user interface
I was windering if it was possible to have an html user interface in ReactOS. It don't have to be all of it but maybe front ends for user accounts and stuff like XP....
If at all posible...
If at all posible...
We need a react OS Update. How would we get by wih out it.
i don't like the point that it is html, but a similar (FAST) interface, coded in pure C would be nice for normal users.
Wir sind die Borg. Widerstand ist Spannung durch Stromstärke.
www.wakka.de
www.wakka.de
-
- Posts: 107
- Joined: Fri Nov 26, 2004 10:12 pm
- Location: España (perdido en el atlantico)
Could you explain me why you dont want html and prefer C?nothin2g wrote:i don't like the point that it is html, but a similar (FAST) interface, coded in pure C would be nice for normal users.
I see HTML better for the following reasons:
1) HTML is easy to code.
2) It is as standard (even more) as C
3) It is very easy to mantain.
4) Not being "executable" code (only links to executable code) and interpreted by an engine (browser) it is less prone to bugs and exploits, you only have to worry of the browser and the executable code not being faulty, and not all the thousands of posible HTML files.
4) You will still use HTML files for many things, help files, information files to the user... so, why two ways?, one to handle the FAST interface and the other the html files if 1 can make both.
5) Using only one you can concentrate your eforts in that alone.
6) It has to be that way for windows compatibility.
Well those are my points for suporting HTML.
Best regards,
Lucio Diaz.
But it isn't easy to code an HTML engine.Lucio Diaz wrote: Could you explain me why you dont want html and prefer C?
I see HTML better for the following reasons:
1) HTML is easy to code.
Have you ever heard the term "tag soup?"2) It is as standard (even more) as C
HTML standards are still evolving. Much maintenence would be needed of the HTML and whatever HTML engine.3) It is very easy to mantain.
The dialog resources in Windows/ReactOS are also not "executable" and are not prone to exploits. And dialog resource processing only has to worry about processing well behaved dialogs designed for the OS and can be kept simple. A web browser has to worry about every single web page on the Internet and browsers can be extended almost infinatly and to the point where they are unmanageable.4) Not being "executable" code (only links to executable code) and interpreted by an engine (browser) it is less prone to bugs and exploits, you only have to worry of the browser and the executable code not being faulty, and not all the thousands of posible HTML files.
Help files should use a dedicated, minimal hypertext (not necessarily HTML) renderer that is separate from the users web browser (and should not be networkable to avoid exploits). That way when the browser is upgraded you don't have to worry about breaking help files.4) You will still use HTML files for many things, help files, information files to the user... so, why two ways?, one to handle the FAST interface and the other the html files if 1 can make both.
HTML and a rendering engine is a very large effort.5) Using only one you can concentrate your efforts in that alone.
Not for software compatibility. Window can use other shells besides Microsoft's explorer and software still run properly. User compatibility might be another issue, (imagine a windows user trying to verbally guide a ReactOS user over the phone telling them what to click). *BUT* Microsoft has already made a mess of all that because all of that web stuff can be turned off. I use Windows XP at work and I don't see ANY web stuff, not in the control panel, not in the file windows, not in the start menu, not anywhere. It is easy enough for people to turn off these options that it is hard to walk them through anything without knowing what options they turned on or off.6) It has to be that way for windows compatibility.
[/quote]Well those are my points for supporting HTML.
Best regards,
Lucio Diaz.
Well, those are my points for not supporting an HTML UI
imagine a settings dialog with the gecko first start loading time
Wir sind die Borg. Widerstand ist Spannung durch Stromstärke.
www.wakka.de
www.wakka.de
-
- Developer
- Posts: 66
- Joined: Tue Jan 11, 2005 1:42 am
Who is online
Users browsing this forum: Ahrefs [Bot] and 32 guests