Am I the only one who noticed that MorphOS on this screenshot runs on QEMU?

Quote:

Glad you tested that. Goats are my go to search these days. :)

> https://tunkki.dk/~jaca/webkit_goats.png

"goats", that was close ;-)

@ jacadcaps - Most impressive, most impressive indeed you are ... and far better progress than I'd expected so far.

Excellent jacadcaps !!!

Fantastic success! :D

So ever since the initial google.com screenshot I've been battling a bug that made WebKit lose sanity as soon as some heavier page was loaded - usually in the middle of the load.

This caused subsequent loads to fail too and several of my headaches. Anyway...

I'm just having to scrabble around in the dark here, as my mind just popped, and my jaw has fallen on the floor, so give me a moment ...

Fortunately my hands remained attached, so I can type ... All those ideas seem excellent, and it's fantastic what you've achieved so far, in such a brief amount of time, hoping this all comes good in the end ...

Quote:

This is how Iris works already. It interfaces via JS commands. I'm mostly just making use of what I've learnt while working on Iris now.

As for a "hybrid", Iris has used that for a while - having a separate app that overlapped Iris' window to display HTML. This is, sadly, too messy to handle. It's far easier to simply link the whole thing together.

Anyway, I have now rebased to Safari-609.1.20.111.8, which is Safari 13.1 - meaning the latest there is, basically. Appears to work, too (at least to the same extent the old version did, there's still a ton of problems to address).

[ Edited by jacadcaps 08.04.2020 - 19:10 ]

@ takemehomegrandma

Quote:

A "hybrid app runtime" derived from Odyssey has been in existence in various incarnations since 2018. Considering that Odyssey uses a less demanding Webkit version, this seems like a good fit considering applications designed to be run locally and on certain operating systems can usually be tailored to the features of specific Webkit versions whereas websites are constantly evolving, thus require browser engine upgrades.

The main downside of running multiple applications in what is close to a UI-less Odyssey is that iconifying one application window will iconify all windows associated with the runtime application. This would require some option to hide the iconify button just like it exists for the "Close" window button in MUI. I doubt this will ever get implemented though.

Also, this is very much unrelated to the new web browser, of course, which is the main topic of this discussion.

Quote:

This is a really good idea!

That would open up for a lot of creative uses in new programs, Iris being far from the only one!

Ideally it should also be possible to run JS etc in it to make a full web app, enclose it all in a proper MUI GUI with all necessary controls, and make it possible for the web-app and MUI-app to communicate to become one entity. It would IMHO make a lot of sense to create, say, a word processor this way. HTML for the document contents, JS for doing all the editing of it, one css for screen, one for paper print, and a MorphOS/MUI program around it to handle everything related to the OS and user interface. I believe the Spotify apps and many more are built in a similar way.

Quote:

Nice to see you posting here Fab. I hope that you are your family are healthy and staying safe, as all of us should be doing. Now that most people are staying home, due to the COVID-19 virus, do you perhaps have a little extra free time to help jadacaps with some of the work needed on the new web browser he has started? No doubt your experience in coding Odyssey, and your long experience programming in general, would be a great addition to his work.

I wish I had more coding skills, so that I could offer to help with some of the simplest parts.

Hey Fab :)

Yes, the idea is to make an ObjC WkWebKit class & related delegates so that the web browser (or any other) application doesn't even need to include anything from WebCore or WTF on its own.

But right now I still have to get all the necessary systems up and running.

Quote:

Quite some work, since a lot must have changed in platform/webcore API layers since latest Odyssey's webkit codebase.

But maybe it's time to have a more modern user interface, and rework it from scratch (or at least seriously rework it). I'm confident Jaca will do a great job there. :)

Anyway, it would also be nice to have webkit as a "library" (maybe not dynamic, but at least static), that way it could be reused in other applications "easily", as it was done for Iris (even if it's a stripped-down version of WebKit).

Quote:

How hard would be wiring Odissey with Jaca's updated webkit? Would it save time?

He is alive! :))

Fab!

Heh, great jaca, congratulations.

Glad to see all the build dependencies are there. The worst part is really to make it work at all. Then it's "just" a matter of wiring everything properly (which is what takes most of the time though :)).

Happy to see a recent webkit running, really.

>> MorphOS 3.13 works just fine on QEmu

> I wasn't aware that QEmu was working on MorphOS

;-)

> Maybe the updated browser will need QEmu to run

Jacadcaps' point regarding confusion still stands, it seems.

> in which case I'd need to update then

According to comment #60, MorphOS 3.14 or later will be needed anyway.

> thanks for pointing the QEmu factor out. :-D

There's a thread dedicated to MorphOS and QEMU here on MorphZone:

https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=5774&forum=9#145222

Quote:

Now that would be 100% pointless (unless you plan to run a Window3.x virtual machine).

@ jacadcaps - The reason why I wasn't aware that QEmu was working on MorphOS ... is that I haven't as yet installed v3.13.

As I haven't seen much, or heard of much that was of interest to me in the update, that affected my use of MorphOS, and would enhance it right now, and QEmu isn't on the top of my list of user features, though I know I'm only 1 user, and you're working toward a different goal than I am using it.

Maybe the updated browser will need QEmu to run, in which case I'd need to update then, unless I see some other feature of MorphOS in general that benefits me using it before that occurs, but thanks for pointing the QEmu factor out.

Jaca, you are the best. MorphOS would be weak without you. 👍

I think you're a bit confused, NewSense. MorphOS 3.13 works just fine on QEmu and it is often convenient for me to test things on the machine that I'm developing this on. That's obviously an Intel box since compiling this on MorphOS would take ages. My build VM gets 10 cores and 12GB of RAM and it still takes over 15 minutes for a full build...

Back to the point though: obviously this works just fine on my PowerPC hw and I often test on a Mini and a G5.

Quote:
Nice to see you're working through some of the limitations that has held us back with OWB, though as you said it's only been tested through QEmu at the moment.

Is the whole interface useable only through QEmu currently?

Sweet perfection !!