PS. They probably wouldn't believe me anyway :)

Erm! Don't you have other things to do at the moment?

How can I show you the log?

from Robert Norris:

@Raziel: There's no list of WebKit dependencies as such, because it
really depends on the platform. Basically it needs a Unicode string
library, a network protocol suite, an XML parser and a database engine.
Its just a matter of writing the appropriate classes to integrate them
with WebKit.

I've chosen to use ICU, CURL, libxml2 and sqlite for these features
because they're what's used on OS X (Safari) and so should continue to
be well supported. Not all ports do this though, for example the QT port
uses QT itself for Unicode, the GTK+ port are contemplating using glib
functions for it, and so on.

Obviously if AROS had those facilities, I'd be trying to use them
instead.
----------

I had a quick skim through your amigans.net thread. To clarify:

My port is based on WebKit, that is the original code used by Apple in
their Safari browser, and being ported to a slew of other platforms.
WebKit was originally a fork of KDE's KHTML/KJS, but that was years ago
(around 2001) and the code is wildly different now. WebKit is has more
features and is better maintained than KHTML, to the point that KDE are
seriously considering dropping KHTML in favour of WebKit.

Sputnik is based on S60 WebCore, which is a fork of WebKit done by Nokia
for their mobile devices. This fork has not really been kept up to date
with the latest development in WebKit proper, which is why I didn't want
to use it. I had a brief look at it and it doesn't really look like
there was much I could use anyway. And, by using WebKit proper, I can
take advantage of the WebKit development community, who are very
actively encouraging and helping with ports.

It does seem that there's a feeling that I may have made the wrong call
by not using Marcik's or someone elses code (eg the OWB/SandLabs WebKit
port). I don't think most folks understand just how portable the WebKit
code is. Integration with AROS is going to be hard no matter what I
used.

I'm also committed to this code being 100% free to be used for whatever
people want it for. WebKit itself is LGPL licensed. Traveller will most
likely be GPL.

As for ports to non-AROS systems, they won't be done by me, but I
certainly have no issue with them and am happy to assist where I can.

Also, the code is out there already and I'm publishing every change into
my repositories as I make them. I'm also blogging a lot about what I'm
doing. I hope that that transparency will help curb any wild speculation
or trolling, though this is the Amiga community so who knows :P

Feel free to quote me in your forum thread or anywhere else. I may paste
this into a blog post, who knows. And do let me know if you have any
more questions, I'm happy to help where I can :)

There is no *NATIVE* (aka MUI code) code in that arkive and the webkit parts is empty.. there is only the static library......
also for some minor libs...

taken from the SFSConfig Guide:

Note: None of this settings is permanet. SFS forgets them after a reboot.
To make them permant add the proper SFSconfig command lines to your
Startup-Sequence - good for setting cache for the boot partition as early
as possible - or User-Startup.

But the S60 Webkit is itself based on the Webkit you mention, which is based on Webcore, which is based on KHTML. The guy porting it is free to do what he wants, but if I were in his position, I'd take advantage of the porting already done by the Sputnik author.

AWeb is open-source, and it's new version was supposed to use Webcore as well. Their plan was to take the MorphOS port of Webcore done by the Sputnik developer and use it in AWeb.

However, the source-code is available, but no-one appears to have started work on integrating it with AWeb.

I'm guessing that the AROS port will be based on Sputnik's Webcore port.

from Marciks KHTML page:
This isn't a direct port of KHTML from KDE, but is based on browser for S60 devices by Nokia (which is in turn based on WebCore, by Apple Inc.), which is based on KHTML from KDE

BTW, does it really matter if Sputnik is partially closed-source? If he makes an OS4 port, we can use it.