HTML Help and IWebBrowser status

2002-12-03 Thread Ender
Hi all, I'm just posting a quick update on my various WINE work for those intrested. I currently have a working HTML Help viewer, which seems to work pretty well on everything I've tested so far. It does however need some more work to conform to the way the real HTML Help system works in

Re: HTML Help and IWebBrowser status

2002-12-03 Thread Roderick Colenbrander
Hi, Why not use Mozilla instead of KHTML? There exists an opensource activex control based on mozilla which is fully compatible with IWebBrowser. The only difference is that the name is MozillaBrowser. There's even a little tool that can convert a IWebBrowser app to a MozillaBrowser app by

Re: HTML Help and IWebBrowser status

2002-12-03 Thread Mike Hearn
Hi Roderick, This was discussed about a month ago, so see the archives for more info. Basically there was a Gecko vs KHTML debate, with Ender (who is writing the code) eventually settling on KHTML for the following reasons: - Simple - No XPCOM dependancies - Could be more easily hacked to add IE

Re: HTML Help and IWebBrowser status

2002-12-03 Thread Joerg Mayer
On Tue, Dec 03, 2002 at 04:46:00AM -0600, Ender wrote: That brings me to my other WIP, de-QT'ing KHTML and turning it into a working browser implementation for WINE. So far this is actually coming along quite well, and besides a few points it definatly makes an effective browser and IE

Re: HTML Help and IWebBrowser status

2002-12-03 Thread Greg Turner
On Tuesday 03 December 2002 06:59 am, Mike Hearn wrote: Hi Roderick, This was discussed about a month ago, so see the archives for more info. Basically there was a Gecko vs KHTML debate, with Ender (who is writing the code) eventually settling on KHTML for the following reasons: This is