Quote:



Quote:

Excellent, well done! My G5 and my PowerBook are in storage back in the UK and I'm missing my MorphOS fix. The race is on to see whether I'll go back and grab the PowerBook before you have an alpha browser. If I was a gambling man I'd put money on me losing that bet. lol

Quote:

Someone earlier wrote:

"Firefly (From the TV-series with the same name which actually had a rather cool atmosphere. It takes place on Serenity, a "Firefly-class" spaceship. And more important: It could also connect to Firefox and the MorphOS logo (butterflies fly) at the same time. I suppose a really cool logo could be made with this (butterfly, flames), signalling it's a MorphOS browser.)"

I like this name (as well as the TV series and later, fan sponsored movie "Serenity"). I'm sure a cool logo tying the well known Firefox browser and MorphOS butterfly could be created.

Before "Odyssey" was "Troy", not very helpful
How about "OWB 2"?

I would call it Pathfinder - to find the path in www.....

This is fantastic news. Donation sent.

Thank you for all the donations!

Really nice news, keep up the good work @jacadcaps !!

Pity Jacek,
As web playback is adequate on G5s for the most part

Quote:

I think what would really rock in a browser would be WebGL but that requires OpenGL-ES 2.0 or better. I don't think TinyGL is up to it.

It's not about TGL. It's about the graphics card that are predominant and often cannot be replaced (aka mini, PowerBooks, etc).

Do you plan to make the source and build instructions available when it is released? Also, what is your dev environment now?

Thanks!

Quote:

I guess you are asking because you want to know if the MorphOS community will be able to update and maintain the new browser, in case jadacaps becomes too busy with other projects, am I right? I recently sent jadacaps a donation, primarily to encourage him to continue working on this new browser, but also for his work on the Iris email program, and all the work he does on MorphOS itself. I hope that other users are doing the same, as it is very generous that all of the MorphOS Dev. Team members give us so much of their time, to create MorphOS and software to run on it, and rarely ever ask for anything in return.

Quote:

Sources will eventually land on github, I believe, but not necessarily open to everyone. For now I want to focus on this myself, with the help of the rest of the MorphOS Team. That said, anyone who feels like he can make a meaningful contribution should feel free to approach me.

The pre-requisites are mostly the same as with Odyssey (a couple of things like libicu, cairo or freetype had to be updated, but we've done this already). Other than the linklibs you need GCC 9 with ObjectiveC and libstdc++ that has threading features enabled. This project really stress tests the whole SDK and so far most of the related diffs are actually in compilers, binutils or libnix and not WebKit itself. I'm obviously cross-compiling all this...

Quote:

That is a good thing!

Why won't the MorphOS Team go the Patreon model? If that is too sticky, why not the most active members of the team have Patreon pages? I'm not a Patreon guy. The only Patreon I'd do is MorphOS projects.

[ Edited by redrumloa 05.03.2020 - 21:12 ]

Quote:

O(mitted) W(ebGL) B(rowser) !!!!

TBE (The Buttefly Effect)

V'Ger (see StarTrek)

So, there is good news and bad news.

The good is that I was able to link a project that references a WebCore::Page and implements quite a bit of WebKit interfaces (even if they're mostly placeholders).

The bad news, is that the resulting binary is already over 80MB, meaning memory requirements of the new browser will likely be ~1GB. Mind that the binary doesn't actually do much past instantiating a WebCore::Page, so it's bound to grow a lot by the time it starts resembling something usable.

Next step: figure out the minimal route to load & display contents, the dumbest way possible, just to verify that the WebCore internals are working.

For whatever reason, audio doesn't playback from online SDR radios like websdr.org . You see it going and all that, but it relies on HTML5 audio. Chrome itself won't work with it for whatever reason they have it disabled, but only works under firefox. Maybe the browser can support the audio on websdr.org would be nice. :)

A clean instance of Opera, which has all bells and whistles enabled, eats roughly 300MB of memory. The desktop version of Safari appears to be in the same ballbark.

So, 512MB of total system memory might be a bit tight while browsing so the 1GB memory requirement sounds quite plausible.

For Iris, it might actually make sense to stick with the older Webkit. It is not like HTML emails would require the latest generation of browser engines to display properly. (Thankfully.)

@jacadcaps

Whoa, sounds like a huge task! Good luck!

Quote:

Only if someone else does this. My starting point isn't Odyssey, it's plain WebCore. At this stage it'll be a huge success once I manage to actually render a HTML page into a BitMap. And an even bigger one once I can actually type into input boxes.

Quote:

I'm guessing that MorphOS for x64 will NOT have the same RAM limitation that MorphOS for PPC inherited from AmigaOS compatibility, so our MorphOS for x64 systems will be able to utilize much more than 2GB of RAM, and you won't have to worry about your new web browser's appetite for using RAM. But it is probably too much to hope that with the MorphOS Dev. Team concentrating most of their efforts on the x64 version of MorphOS, most members of the team will not want to spend time and effort to create any kind of extended memory for the current PPC version of MorphOS? Such discussions of how, and if any hack to extend memory for the current version of MorphOS have surely been had several times in the past and the answer has always been "NO", apparently, but until the G5 hardware was supported, there was little need to consider spending time trying to figure out a way to extend the RAM capacity of MorphOS, because "MOST" supported systems could not physically have more than 2GB of RAM on the hardware.

Can you give us any information regarding discussions the team has had in the past about the possibility of creating some kind of "extended" RAM for the current PPC version of MorphOS, after support for G5 systems that can have up to 8GB or 16GB of RAM installed on the motherboards?

Quote:

Loved the old VaporWare Voyager NG, so Voyager would be nice.

Its great to see AROS has advanced to x64 as well as MorphOS has its inner workings, that will eventually bring this new "Voyager".

Either supporting Nemo or AMD64 will surely bring my license. No space to buy new machines.

Quote:

Surely, that would be the point of going x64 :)
Or PPC64 too as a branch? (G5, Pa Semi and x5000 CPU?)

[ Edited by vox 21.03.2020 - 10:13 ]