I agree as well, OWB is a core program for MorphOS, and requires regular updates to keep it relevant, which is no simple task, I would imagine, especially as it seems that WebKit is basically out-of-date anyway. It has to be funded somehow, as such a lot of maintainance requires recompense for anyone involved in carrying out these necessary updates.

I would consider a yearly payment to be a fair option, or any other method of paying for the updates, so that it remains useable for the future of MorphOS.

Maybe even users of Amiga OS4 could be persuaded to join the bounty or some annual, or any other type of payment option, as I believe they are suffering more with their older and thus more incompatible version of OWB.

We are all in this together, as IBrowse v2.5, if it ever gets released, is not going to be a modern alternative to OWB, and no-one is looking out for us, so we must maintain it ourselves, with our own finances it seems.

Quote:

Since we're in a trolling mode I see, let me tell you that I am looking into merging Fab's Odyssey into a 2017 state of WebKit with internetzel's patches included. If you guys feel like collecting some money for this cause will help - you are right. Do note, however, that any work I do is and will be exclusive to MorphOS.

WTF and JSCore are already patched by the way. Digging through WebCore right now. There's a lot of stuff that is totally obsolete in Fab's patches so a feature set of any new browser will be different than the old one.

Any specific reason why that would be a 2017 WebKit?
What would we be missing compared to a recent one?
What would that mean regarding future updates?

Bout a bounty:
What can we expect beyond the current OWB?
Are we talking months, years or just "2 more weeks"?
Are 50Zł enough? (*runs*)

Quote:
Because this happens to be most recent version that has already been adapted for big endian CPUs by internetzel for his "leopard-webkit" project.

Quote:
This is a bit of a loaded question. I think it makes more sense to focus on what can be gained from this, which is a browser engine that is 3 years newer than what you have on MorphOS now.

With regard to general compatibility, a 2 years old version is not that much worse than a week's old version. Mainstream online services are not generally designed to only work with a tiny subset of browser versions that happen to be the most recent ones.

If you know of a popular website that fails with our special 'tuned' 2014 version of Webkit, feel free to test it with leopard-webkit on MacOS. Chances are very good, the website will work.

Well "loaded question" or not, my 3rd one was the real issue here, would a 2017 WebKit turn into another deadend by 202x? Or will it be possible to trail behind bleeding edge for a longer time (aka a 2020 WebKit by 2022).

I don't expect a definite answer, just wether there are some major roadblocks ahead.

Quote:

This will include the PPC JIT for JavaScript I assume?

Quote:
As you know, the major roadblock has been the fact that browser engine developers have abandoned big endian processor architectures. This is unlikely to change.

While there have not been any updates for a year, it is still possible that internetzel will adapt a newer 2019 version of Webkit, which would simplify upgrading Odyssey to the latest and greatest Webkit as well.

Also, if MorphOS eventually supports little endian processors, then this would remove said major roadblock for future OS releases once and for all but this does not help people who are attached to their PowerPC machines but would still like to use a newer web browser.

Quote:

That is out of scope at the moment. And depends on bigfoot entirely.

Quote:

Not going to commit to anything at this stage, sorry. There are two immediate benefits of the work I'm doing: a) getting a 2017 state of WebKit, b) having a clean patch. Fab's patch is HUGE and contains tons of bloat (like plenty of useless Qt files). This may make any work on future integrations a bit easier.

OK, long story short: Whom do I need to pay and how much?

@koszer

I think you should chill for now. I'm done reviewing/applying Fab's patch and will be attempting to build stuff soon. It may still turn out that nothing working will come of this though.

But if you really want to support the work that I'm doing, Iris has a PayPal button.

Quote:

You don't plan on giving any changes you make back upstream or to the leopard-webkit guy?

I know you don't have to to comply with the licence but this makes me sad. :(

[ Edited by Intuition 24.03.2019 - 14:30 ]

Quote:

Oh I see.

Hopefully he'll find the time and motivation to adapt his jit to work with your new build.

Quote:
Edit: Removed.

Quote:

Upstream? You mean get them integrated by Apple? And what do you mean by 'not complying'? Which license are you talking about?

I don't think there would be any changes the leopard-webkit guy would like to integrate since I am basically working off his branch.

I guess you 2 missed the 2nd "to" in that sentence ;)

Seems like that Intuition is implying that making your changes available is not mandatory.

No idea wether thats really the case with the WebKit licence.....

Quote:
Fair enough.

Quote:
That is not generally the case. If you modify certain parts of Webkit, you must share these specific changes in order to comply with the license. Webkit uses both LGPL and BSD.

Quote:

I'm not sure that's trolling, just poorly worded.

It makes perfect sense not to rely on the goodwill of a single person for something as essential as a platform's only modern browser. For a start, that's not fair on Fab, who I assume has a life outside his computer and things he'd rather spend it on than update his software for free forever. Involving other people to lighten the burden, or failing that, then a bounty to reward that work seems reasonable enough to me.

@KennyR

Fab hasn't been active since the last bounty, so this is not a matter of lightening the burden but taking over.

I think it’s a great idea!

Related to this, is a small-endian version of MorphOS still in the cards? At all?

Quote:

Why not make it larger and include 68K too ?

Quote:
Because there is no AOS 68k port of Odyssey that could be updated to use a newer version of Webkit.

Bounty still open:

https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=11566&forum=32
https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=11761&forum=3

> OWB [...] requires regular updates to keep it relevant, which is no simple task,
> I would imagine, especially as it seems that WebKit is basically out-of-date anyway.

I'm not quite sure how to interpret this statement. In case it means that WebKit in general is out-of-date, then no, WebKit is still in active development.

Quote:

I'm very happy to read that one of my favorite developers, "jacadcaps", is looking into merging Fab's Odyssey work, with anything that will make a newer and more capable version of Odyssey for MorphOS users. Someone please set up a specific Odyssey bounty project, and consult with jacadcaps for the description of the exact work and goals, so we can advertise this bounty to the rest of the MorphOS users, and raise the money which will help Jacek thrive, while he works on this important program for all of us. If there is a way to add BigFoot, and his JIT work to the project, and fairly divide the bounty money between the two developers, that would be even better.

I don't mind donating to the Iris project, knowing that it will also help Jacek to work on Odyssey, but think that a separate bounty would generate much more interest, and donations.