Quote:

"Journey"? Maybe Voyage? Hey, how about "Voyager?" :D

Now, seriously. If we're in the Greek mythology zone - there's been another epic journey: Jason and the Argonauts, in pursuit of Golden Fleece. So I propose "Argo".

After the "odyssey", we can make a "journey" on internet 😉

--
/me'll make a donation too for this insane project!

NewSense & tolkien: thank you!

I've absolutely no idea how it's going to be called.

Quote:

So what will it be called?

:-)

I will send you a donation in the next few days - it's not going to be a loan !!
[EDIT] -> Donation now sent 2-March-2020

Here goes a little donation. Not so much but take a few beers while doing so great work.
Thanks for the info and support.

JavaScriptCore's testapi test suite passing all tests on MorphOS now. I'm looking into getting most of WebCore to compile and reading up on how WebKitLegacy is structured (that's the part that mostly needs to be written from scratch for MorphOS).

Currently also dealing with a dead/unstable G5, which is stealing quite a bit of my spare time.

Feel free to donate via https://paypal.me/irismail if you want to support my efforts.

@ jacadcaps

- 'memory-lock' - as long as you work as much of your 'magic' as possible - that's all that can be expected I suppose

- 'YT' - if you can support what you can enable from the first release and develop what else is possible, and within the capabilities of the hardware, again that's all that can be expected

- it's all a big ask of you anyway, and I'm sure you, and the rest of the Dev Team, are up for the challenge for us all anyway. I appreciate what you've (all) done already, and can't wait to see what a newer browser has to offer, to try to keep pace with the race amongst mainstream browser development, and thanks for the insight into your initial work already.

Quote:

It might. There's quite a few memory management functions in WebKit that are not enabled in Odyssey - namely all the stuff Apple did for iOS devices, esp. when they were still 32bit. So we should be able to flush background tabs, etc when memory usage is too high. It remains to be seen how effective this would be though. Safari on my old iPhone 5C would sometimes crash on out-of-memory on some heavy pages so I don't think it'll be much better.

As for YT downloads, that means supporting user scripts. Dunno. There's nothing to retain since this is a completely new project, not an update of Odyssey. Some things (media playback included) may simply arrive in the years to come.

I forgot to ask - will this custom build to create, what will be, our new browser once-and-for-all free us of the 'memory lock' we suffer from with OWB where memory does not get released as the program is used until it is closed/quit?

Along the same line of thinking as jPV has questioned ... will we still be able to download videos from YouTube and other sites, as before, via the right context menu to view them via MPlayer as a separate downloaded video file, even if that cannot be done while on the webpage being viewed at the time? Surely that option can/should be retained!

Quote:
I won't miss the inspector either, but I surely would miss the media playback, because YouTube and other videos are still playing just fine for my needs on overlay modes even on Mac mini 1.5GHz, which I use as my main setup. I would think that videos would play even better on G5 systems... so definitely going to miss this and forces to go to two browser daily use, which makes things more clumsy. It wasn't fun in old days to use IBrowse + Sputnik combo etc when new browsers weren't yet as usable as IBrowse, but were needed to render some pages...

And does media playback include audio playback too? That isn't demanding and I'm using Bandcamp and other sites regularly too...

But of course it's better to have updated engine/browser even wihtout media playback than get stuck on all fronts... so I'll take it without media playback too, but still bit of a shame if it's not even an option to get that later...

Quote:

Same for YT playback.

The Inspector is quite useful sometimes to see into websites inner workings, or extract data that you couldn't get at otherwise, such as embedded images in the page(s). I take it I would still be able to run any older versions of OWB to gain the usefulness of the Inspector from those versions of OWB, as an alternative to any replacement browser you and the Dev. Team complete, just for such purposes?

Quote:

I won't be missing the Inspector, but... do you mean I won't be able to watch YouTube videos on MorphOS?

@ Jacadcaps - Thanks for the informative explanation regarding Webkit/WebKit2/Webcore/JavaScriptCore, which seems to me yet another beneficial addition of your approach to keeping us all well informed, which I personally am really grateful for. Nice to know you and others in the Dev Team have seemingly already made some progress, and thanks again for this timely update.

Just thought I'll share a bit since there was a bit of speculation in this thread.

Work is ongoing on a port of a fairly recent stable branch of WebKit. I do have a mostly working standalone jsc (JavaScriptCore command-line tool) and am now working towards making sure its testing suite fully works. WebKit has changed quite a bit since Orygin's days, enabled by improvements in C++ itself. The current port is generally only possible because we've stepped up our game with the SDK during the last two years (new binutils, gcc7-9, new perl, etc) so even though I'm working on WebKit on my own, this is really a Team effort - so far most of the crashes have been fixed in the compiler and or libnix (by Piru) and not by changing the WebKit source code itself.

The next step will now be to compile WebCore (that's where the layouter is, etc) and then port WebKitLegacy. Porting WebKit (previously known as WebKit2) makes no sense on MorphOS. The idea is to generally have a very simple class being able to display HTML first and then extend it with all the necessary interfaces - this is similar to the changes in OWB I've made to make it possible for it to be used in Iris.

Once that's done I'll be able to start on a browser application itself, isolated from WebKit & co.

And to make one thing clear: I've no intention of supporting things like the Inspector or media playback. There's no way these things will ever be fast enough on PPC to be satisfactory.