Wayfarer, the most feature rich Web Browser that the Amiga has ever seen so far, is apparently closing in on its 4.0 release. It will be based on the recent WebKitGTK 2.36.3!

Quote:

First post from Wayfarer 4.0... The MorphOS betatesters just got access to a first build of a Wayfarer rebased onto the latest WebKitGTK 2.36.3. It will take between days to weeks before it's ready for a public release, though.

@TRIPOS

Nice!

@TRIPOS

@TRIPOS

Development is going strong, great achievement!

Wayfarer Version 4.0
Rebased to WebKitGTK 2.36.3
HLS stream qualities also accessible from the Media menu
Updated cURL and other libs

Wayfarer has now been updated to the latest stable WebKitGTK branch.

@t0lkien

Iris alo got updated. Jaca is a code animal - does he ever sleep?

Updates went smoth and both programms are working smoothly.

_________________
My programs: via.bckrs.de
MorphOS user since V0.4 (2001)

@TRIPOS

Nice, can we expect a version for OS 4.1FE soon?

Is so difficult to build a pipeline that builds a MorphOS version and AmigaOS4 version at the same time?

For years build pipelines for different platforms are very common thing right.

_________________
AmigaScene.nl

@sananaman

Quote:

Is so difficult to build a pipeline that builds a MorphOS version and AmigaOS4 version at the same time?

That's not the issue here. The issue is getting the technology in OS4 on par with MorphOS so that a port can be made in first place. So far any progress in that direction appears to be very, very slow.

@sananaman

Quote:

Is so difficult to update OS4 to technologically as good as MorphOS so you can build a MorphOS version and AmigaOS4 version at the same time?

FTFY.

@jacadcaps

The progress is very impressive. Some amazing work to date.

Please send me an email. I very much would like to know the prerequisite technologies that would be needed to support Wayfarer. If there’s an opportunity to support it in the Enhancer Software then it is worth exploring.

_________________
Amiga Kit Amiga Store
Links: www.amigakit.com | New Products | A600GS

@amigakit

There no needs for emails as jaca already explain everything in latest few years. For OS4 we need someone working on our toolchain (adtools) to fix GCC and/or kernel, to be able at least to make this one work: https://github.com/sba1/adtools/issues/82

And then, there will be more issues to deal with in kernel and gcc/binutils which someone should take care on (and no, the speed how works Steven and co. on the kernel is unnaceptable and very uber slow).


But again, who will support and update aos4 version even if it will happens ?:) We better to go some hardware-emulation route with VNC or something whih will looks transparent, with just some written GUI on top of some remote API connected to the browser core on some other platform. That way visually everything will be like native, but core will be updated/worked out by the army of other coders who have no needs to worry about amigaos and endianes. We only need to wrote custom GUI on top of that and implement "connection" to x86 core or something of that sort.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@kas1e

Quote:

We better to go some hardware-emulation route with VNC or something whih will looks transparent, with just some written GUI on top of some remote API connected to the browser core on some other platform

Would something like this be a starting point ?

https://github.com/DanielGibson/sdl2_vnc

_________________
AmigaOS4 Beta-Tester
----------------------------------
Amiga X5000 8GB Radeon RX 560
Amiga A1222 2GB Radeon RX 550
Sam 460 2GB RadeonRX 550

@Zylesea

"Iris alo got updated. Jaca is a code animal - does he ever sleep?"


Indeed he is a code animal, never seen this update rate on
an Amiga OS EVER! Hope he doesn't burn out-

Sleep?
I think he codes the most when he's awake and the rest
sleeping with one eye open! ;)

_________________

@amigakit

All of the really important pre-requisites are listed here:

https://github.com/jacadcaps/webkitty/blob/master/PORTING.md

@kas1e

>But again, who will support and update aos4 version even if it will happens ?:) We better to go >some hardware-emulation route with VNC or something whih will looks transparent, with just some >written GUI on top of some remote API connected to the browser core on some other platform. That >way visually everything will be like native, but core will be updated/worked out by the army of other >coders who have no needs to worry about amigaos and endianes. We only need to wrote custom >GUI on top of that and implement "connection" to x86 core or something of that sort.

That is a no go, when I want x86 I will power on my Windows machine ;)

What happened with Firefox or OWB for AmigaOS4.1? Wasn't that the future a decade ago?

I guess Amiga is dead, noone will buy an OS4 system when there is no updated browser. Sad but true. AmigaOS4 could have been great if the right desicions was made. Now it's to late.

James Brown is dead.

@jacadcaps

Quote:

That's not the issue here. The issue is getting the technology in OS4 on par with MorphOS so that a port can be made in first place. So far any progress in that direction appears to be very, very slow.

Hi jacadcaps,

Can you point out what technology is missing in OS4 why a Wayfarer build is not possible.
It would be good to know what to focus on.

_________________
AmigaScene.nl

@Am!ga

Quote:

What happened with Firefox or OWB for AmigaOS4.1? Wasn't that the future a decade ago? I guess Amiga is dead, noone will buy an OS4 system when there is no updated browser. Sad but true. AmigaOS4 could have been great if the right desicions was made. Now it's to late. James Brown is dead.

I agree that Amiga has danced the wrong way for many years of where the majority of operating systems went (and therefore what people know as the norm).

But with the momentum that is going on right now, with a lot of people joining back their beloved platform, there could be a fun future for the platform and the people who still like it, like myself.

Nowadays everything is "internet" so not having a modern browser on a modern OS is like a car with no wheels.

Also to Trevor , Hyperion and AmigaKit :
Having a multicore priority over a modern browser is very odd. I believe that the AmigaOS as a product is driven by what individuals "want" to develop instead of what is "required" to develop.
Understanding that Amiga is a niche market, I am willing to pay around 30-40 euro's for a proper Firefox or Webkit port that is being maintained like the AmigaOS itself.

_________________
AmigaScene.nl

@sananaman

You need an SDK with modern C++ support (covering most of Standard Library, and covering it in a way that things are actually compliant with the C++ standards). To get there, we've had to update the MorphOS' exec.library.

I've no reason to believe the same can be achieved on OS4 without modifying exec / kernel components, at least if you want decent performance.

All of the other dependencies are even already there (unchanged from Odyssey) or are relatively easy to port (compiles with minimal patches).

@sananaman

I think OS4 lags too far behind in many aspects. Better focus on *one* system instead of doing work twice and waste development resources. Hence, drop OS4, join MorphOS. You don't need to ait for a modern browser there - it's already available.
And no, this is no flame invitation (we chewed that through and through in recent years), but it just has developd as it has:
MorphOS has the development tools, the hardware and useable internet software.
And if you don't like the default look of MorphOS, you can easily skin MorphOS to look like OS4.
Of course also on MorphOS there are issues and flaws, but with joined resources it would be easier to bring it forward.

It's only a friendly invitation, everyone is free to decide.

_________________
My programs: via.bckrs.de
MorphOS user since V0.4 (2001)