* Blazing fast. Startup goes from 2.8s to 1.9s. Startup limitation is now in yelp code (which I can work on)
* API rocks. It's like a real gtk+ API. I can understand what's going on in it.
* People will expect the choice now.
* Frags apparently don't count as links, which means we'll have to deal with all events. Which sucks.
* WebCore apparently doesn't play nicely with libxslt. More on this in a minute.
* Scrollbars have gone AWOL.
Currently, the patch resides in bugzilla. It's ugly and disables lots of features. Once it's cleaned up a bit and more works, I'll consider (maybe!) landing it in SVN.
The problem with WebCore and libxslt. Any help most gratefully appreciated. The issue appears when trying to parse the next document after WebCore is initialised. The sequence goes something like:
Initialise and pages requested
Create window as well as html
(When user requests doc): Initialise new page.
When I do all this, it works beautifully up until the final step. Then, things go a bit squiffy:
Except the XML file definitely exists and is valid (I can display it normally). Things get even more fun for man and info pages, where the first step is to load the stylesheet using
"transform->stylesheet = xsltParseStylesheetFile (BAD_CAST stylesheet);"
This fails miserably and the entire program grinds to a horrible halt. So, anyone with experience of WebCore and / or libxslt want to comment and / or explain WTF is going on? There's a drink in it if you can solve it.