Sweet perfection !!

Something that hasn't worked for a while in Odyssey...

Re-Captcha (Youtube)

Quote:

Take your time. We are all stuck inside right now anyways.

Quote:
That ain't a problem at all as I heard MorphOS 3.14 is only taking 2 more weeks or so.

Besides... Great work!

This development will make me finally purchase MorphOS. Fantastic progress.

@ Jacadcaps and @ Piru - great work so far guys, and progress is better than I expected anyway.

Here's something a little better. The application is obviously only a testing playground.



The bad news is that there'll be no public beta before MorphOS 3.14 is out, because getting google.com to load required us to modify Netstack, exec, GCCs and a couple of other components :) Wouldn't be possible without Piru's work there.


[ Edited by jacadcaps 31.03.2020 - 05:01 ]

Great job!

Quote:

Brilliant! Well done! :)

Looks nice! Hope you'll make good progress and get it finished :)
I wonder if there's going to be a PPC Mit for Javascript. Sadly OWB's JIT version is pretty buggy

great! good job jacadcaps!

I can build that within an hour with Hollywood
Or DPaint. And where is the OS4 port?
Contains stolen code (Steffen Häusser told me so). The elf loader is crap anyway.


btw.: Good job!

Well hello there!

Good job!

Waiting next snapshot

wonderful!

Well, hello!

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 ]

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:

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.

@jacadcaps

Whoa, sounds like a huge task! Good luck!

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.)

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. :)

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.

V'Ger (see StarTrek)

TBE (The Buttefly Effect)