According to this blog (and cross-checked with the referenced AROS bounty entry) Robert Norris has taken over the task of porting / implementing a WebKit based browser to AROS.
Could someone with a little more insight help me figuring out some questions, please?
Quote:
There has to be a clean seperation between the engine and the UI, so that the engine can be turned (later) into an .library, .mcc or something similar to use in your favourite application.
Would this .library / .mcc / something be useable "out of the box" on a non-AROS (yet MUI based) system, or is the MUI implementation of AROS (ZUNE) so much different to, let's say AmigaOS4/OS3 that some work still needs to be done to "back port" it to OS3/4?
edit: Added link to ZUNE dev docs edit2: Webcore dependecies from the blog, updated as worked on, it seems edit3: Polishing and updated edit4: AROS-Show interview with more answers to burning questions
Edited by Raziel on 2007/11/11 18:34:58 Edited by Raziel on 2007/11/14 16:48:06 Edited by Raziel on 2007/11/15 14:03:35 Edited by Raziel on 2007/11/16 11:53:02 Edited by Raziel on 2007/11/22 0:05:28
Yes, i left out the Sputnik part, i didn't want to cause too much cross references trouble.
But Sputnik would be partly closed source, whereas this effort would have everthing GPL, even the UI (which we may not be able to use as whole, but still as a starting point for one)
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.
BTW, does it really matter if Sputnik is partially closed-source? If he makes an OS4 port, we can use it.
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.
True, unfortunately "their" is just one dev - Andy Broad
At one point there was also plans to take the KHTML sources directly and rip the parts to integrate it into AWeb Wishful thinking at best, as there are too few devs
Quote:
However, the source-code is available, but no-one appears to have started work on integrating it with AWeb.
Care to share a link to the source? I can give it to the AWeb dev list and see if someone is interested?
Quote:
I'm guessing that the AROS port will be based on Sputnik's Webcore port.
Hmm, that maybe can only the porter answer, but from what i understand is
Quote:
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
Marcik took the source from the S60 branch whereas Robert N will use the Webkit/Core branch with is a branch from the original KHTML
Slightly different and confusing, isn't it?
Quote:
BTW, does it really matter if Sputnik is partially closed-source? If he makes an OS4 port, we can use it.
I guess not, thats why i left out Sputnik completely in the first place
I'm guessing that the AROS port will be based on Sputnik's Webcore port.
Hmm, that maybe can only the porter answer, but from what i understand is
Quote:
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
Marcik took the source from the S60 branch whereas Robert N will use the Webkit/Core branch with is a branch from the original KHTML
Slightly different and confusing, isn't it?
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.
Thanks for the link, completely missed it, sent to AWeb dev ml
Quote:
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.
Maybe he isn't allowed to take advantage? There is nothing stated in the bounty description, but maybe he has to use a build on his own sources and/or is eager to do it completely on it's own because he doesn't like foreign code?
I don't know as i'm no coder myself, how hard it would be to dig through some others guy code rather than coding from scratch?
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... that code is useless...
I can't follow you exactly...are you referring to the links i posted?
Quote:
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...
Of course, because Robert Norris (thanks Orgin) has only just started yet ... my intention in the very first post was just to ask IF a backport to OS4 from the THEN written sources MAYBE together with the ZUNE based browser UI would be possible ... nothing more
@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. ----------
So, the only thing we don't have (yet) is this ICU (whatever that is)?
Quote:
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 :)
codesets.library and locale.library can do some of what ICU does. It may be possible to use those (or a minimal icu emulation library) instead - depends what the browser is using it for.
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... that code is useless...
Actually, there is some "native" MorphOS code in the deps directory. Just do a search for MorphOS.
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
