Page 1 of 3

Browser

Posted: Wed Oct 05, 2005 11:40 am
by Express
What is "Reactos Internet Browser"?

Is it Gecko? Khtml? or new engine...?

Posted: Wed Oct 05, 2005 3:49 pm
by zoken
I think you must install the Mozilla Active X Control to be able to use it.
So it should be Gecko.

Posted: Wed Oct 05, 2005 5:53 pm
by Dr. Fred
correct

Posted: Thu Oct 06, 2005 6:59 am
by mikedep333
Why isn't the mozilla activeX control included with ReactOS?

Posted: Thu Oct 06, 2005 1:30 pm
by Phalanx
Cause it is harder to build it as well. Maybe it will be in there soon (I hope).

Posted: Thu Oct 06, 2005 6:54 pm
by Harteex
It will be included in future releases afaik.

Posted: Sun Oct 09, 2005 6:47 am
by Luke-Jr
Why not use the superior KHTML?

Posted: Sun Oct 09, 2005 7:49 am
by Phalanx
Luke-Jr wrote:Why not use the superior KHTML?
In what ways that suit ReactOS?

Posted: Sun Oct 09, 2005 7:58 am
by Luke-Jr
Phalanx wrote:
Luke-Jr wrote:Why not use the superior KHTML?
In what ways that suit ReactOS?
How does using a superior browser engine not suit ReactOS?

Posted: Sun Oct 09, 2005 9:58 am
by GvG
Luke-Jr wrote:How does using a superior browser engine not suit ReactOS?
Is it available as a control for Windows (i.e. not as a stand-alone application but as a control that can be embedded by other apps)?

Posted: Sun Oct 09, 2005 10:20 am
by Mike
Well, you'll probably have to port KHTML to be a native Windows library... I know that the KDE-Cygwin project has Konqueror working, but that requires Cygwin (and that's probably something ReactOS won't want to integrate -_-).

In most areas, I would agree with using KHTML, however Gecko still has a few advantages (can't think of anything specific right now).

Posted: Sun Oct 09, 2005 12:24 pm
by dj50
Mike wrote:In most areas, I would agree with using KHTML, however Gecko still has a few advantages (can't think of anything specific right now).
It renders better, especially sites designed with only IE in mind.

Mozilla ActiveX Control 1.7.7

Posted: Sun Oct 09, 2005 1:32 pm
by oiaohm
I know the major difference.

Mozilla ActiveX Control 1.7.7.

http://www.iol.ie/~locka/mozilla/control.htm

This is Part of the Firefox/Mozilla project. The IE Active X control replacement.

By relinking most progams will work with the mozilla replacement. Some hard ones still need work. The program IE Patcher.

This is already half done. All that is have to be done is intergation and fixing of faults.

KHTML will require working from scratch without support. It will take a lot longer. KHTML might have a tech advantage. Mozilla has a support advantage the Control is a older project.

Time cost is not worth it at this point.

Posted: Sun Oct 09, 2005 9:05 pm
by Luke-Jr
GvG wrote:
Luke-Jr wrote:How does using a superior browser engine not suit ReactOS?
Is it available as a control for Windows (i.e. not as a stand-alone application but as a control that can be embedded by other apps)?
Nope, but such would make a good part of the ReactOS project, IMHO... If people want Gecko, they can use Firefox-- why build a new interface when the problems are in the engine?

Posted: Sun Oct 09, 2005 10:07 pm
by GvG
Luke-Jr wrote:Nope, but such would make a good part of the ReactOS project, IMHO... If people want Gecko, they can use Firefox-- why build a new interface when the problems are in the engine?
Feel free to contribute such a control based on KHTML then. I think the ReactOS project has enough code to write already....