OmniWeb with -current webkit

[Cryo]

Is there a way to tell the sneaky peeks version to load a currently build WebKit framework (ala Safari in the WebKit.app test application)?

[Forrest]

No .

[troyb]

This isn't possible because OmniWeb still requires a few customizations that aren't part of the Apple WebKit. These differences may go away in 10.5 and beyond but for the time being you're stuck with the webkit we provide :)

[Handycam]

Is there any thought to using a more recent WebKit in 5.5, since 13302 is getting a bit long in the tooth? Just curious.

[Len Case]

Is there any thought to using a more recent WebKit in 5.5, since 13302 is getting a bit long in the tooth? Just curious.
Well, It's considerably newer than the system WebKit.

There are very good reasons we picked 13302--mostly because we would have to reimplement some features from scratch to move very far forward from there.

That said, we have already picked up some changes from later versions of webkit to fix other bugs and we have fixed some crashers that still don't have fixes on the head.

Once 5.5 has shipped, we will look at how hard it is to move forward from here.

On major feature that will have to be redone is "Zoomed Editing" since WebKit no longer uses the Cocoa Text System for editing text areas and our feature was based on that...

[daiyi666@yahoo.com]

On major feature that will have to be redone is "Zoomed Editing" since WebKit no longer uses the Cocoa Text System for editing text areas and our feature was based on that...

Does that mean we'll lose spell checking, too?

[Cryo]

This isn't possible because OmniWeb still requires a few customizations that aren't part of the Apple WebKit. These differences may go away in 10.5 and beyond but for the time being you're stuck with the webkit we provide :)

There's no way to move these changed out to say OmniWebKit.framework to be wrappers for WebKit.framework calls, so that you can drop in JavaScript* and Web* frameworks?

If there are specific WebKit changes, we're always willing to take patches (that aren't too application specific)!

[Len Case]

Right now we are focused on shipping 5.5 quickly so that all our users can receive the benefits of a newer WebKit and Universal Binary--not just the early adopters who are willing to run alpha software.

Where possible we are trying to re-implement our features within the normal workings of WebKit and avoid customization, but when that isn't possible we are taking the most direct route which currently means that we have added and removed ivars from WebKit classes which is not possible via a wrapper framework.

After we ship, we plan to evaluate all our changes vs. the current version of WebKit at that time and develop patches to submit but that isn't really feasable right now since WebKit is such a moving target and just getting our changes to the head is a project in itself.

[Cryo]

ok, cool. I was hoping that it was still at least somewhere on the table in the future :)