Browser
Moderator: Moderator Team
-
- Posts: 167
- Joined: Sat Oct 01, 2005 1:48 am
- Location: United States
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).
In most areas, I would agree with using KHTML, however Gecko still has a few advantages (can't think of anything specific right now).
Mozilla ActiveX Control 1.7.7
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.
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.
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?GvG wrote: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)?Luke-Jr wrote:How does using a superior browser engine not suit ReactOS?
Feel free to contribute such a control based on KHTML then. I think the ReactOS project has enough code to write already....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?
Who is online
Users browsing this forum: DotBot [Crawler] and 74 guests