Browservice on X1000 and Sam460LE with Odyssey 1.23

Ah ! Bon à savoir, j'ai aussi téléchargé la dernière version de Browservice, je me demandais aussi pourquoi cela ne voulait pas télécharger.

Bon bah pour l'instant plus d'internet pour mon Amiga, panne d'internet et là je suis en 4G en partage de réseau.

Merci Maijestro.

@Maijestro

I just reread what you wrote, Maijestro. There's no version 9.6.4 of Browservice, only 9.6. Is that what you meant?

I just tried internally with version 9.12; it seems to work, but I can confirm this with my X5000 when my internet is fixed.

Raaaaaa! Another double post, sorry.

@Maijestro

I'm using 9.12 without any problem (Linux x86 version) and I applied the patch I explained above with this version.

Great for you if it working with a former version :)

Please, use the fix I mentionned (or try to spoof as Classilla) to avoid constant window resizing.

@K-L

Quote:

Which Agend user string do you use for Odyssey?

Tested with



and



but then there is a DSI when I start Odyssey.

@skynet

You can also use Browservice 0.9.9.2 to download files. All other versions later have broken it under Windows.

https://github.com/ttalvitie/browservice/releases/tag/v0.9.9.2

@Maijestro

Since I have modified the executable of the AppImage under Linux (patch), I don't need to spoof as anything (I stay with Odyssey).

For Windows:

Instructions on how to patch:

Download the Browservice v0.9.6.4 release package (any version will work BTW)

* Extract the release package.
* Open Git Bash/Cygwin in the extracted directory.
* Run the following commands:



* Start browservice.exe in the extracted directory normally.

And you won't have to do it again. No more problem with Odyssey

Browservice sounds like way to go for sure, just need a bit more polishing from our gui side.. On lastest videos from K-L i can see that scrolling of pages is pretty slow. So this need to be somehow sorted out in some (other than Odyssey?) gui. Also sound part need to be transfered too, if browservice support media transfers as well, and not only images. Also, proper address bar integration so to make it looks like native part of browser's gui need it too.

The best thing would be some board attached to PCI slot where we run browser, and a GUI specially written for from os4 side to access it. Browservice and co are only realistic way for us if we want to have up2date browser, IMHO. That were clear even few years ago for me.

@kas1e : regarding the GUI and a special board, this was indeed a thing I was thinking of (as a RPi4 insatlled in my X1000 and connected to the net).

Regarding speed : we should have accelerated (GPU) browser since we have to display images that are sent to Odyssey. The faster the image decoding is, the faster you surf. But there will be limits. I tried Browservice with a recent computer, it won't be as fast as native.

Don't stop on my videos, try it by yourself to make your own opinion (it's pretty usable with my X1000, 1st part of my video so it should be way faster on your X5000). On Sam460, I could lower the JPG quality to 80% to speed things up.

Regarding the sound, I think there's something with Browservice (I'm not sure) but the code is open.

But if you want to watch YouTube videos, forget it, it won't be possible at a decent speed (Browservice sends images to Odyssey, not a stream).

Anyway, for YouTube, I'm using VidoVortex.

Finally, regarding the GUI, it's possible to hide Browservice GUI and use the native one. I don't know if Odyssey supports this. I should try but since I use native Odyssey for supported websites and Browservice for heavy and/or unsupported websites, there's no problem for me having both.

If we had a little ARM bord attached to our system to handle this, a GUI should also be created to control it (connection to a WiFi network, IP attribution, and so on..).

IMHO the best solution for using a current web browser on AmigaOS 4.x, even if it's sounds wired, but I'm serious:
- Run Linux (ppc64le, not the for AmigaOS 4.x PPC systems usual 32 bit big endian Linux versions!) on a X1000 or X5000, or maybe even a Sam460. Execute browservice on this Linux host, which can use the additional CPU cores (X1000 and X5000 only).
- Emulate an A1XE with QEmu on this Linux host.
- Implement a QEmu virtual PCI device for sharing the browservice/CFE off-screen rendering buffer between host and guest, instead of transferring the web pages as PNG or JPEG images over a (virtual) network connection.
- Implement a very simple AmigaOS 4.x WebCore/WebKit based browser as GUI for it, something like the original OWB and Andrea's SDL AmigaOS 4.x ports of it: No GUI at all.

@joerg

Is Chromium working on Linux PPC? I don't think so. So Browservice based on Chromium Embedded Framework won't work.

The best option is still to rely to another architecture supported by Chromium (ARM or x86_64).

@K-L
Quote:Linux PPC/MIPS/ARM LE: Yes.
Linux PPC/MIPS/ARM BE: No.

@joerg

Thanks!

I have been "googleing" for Chromium PowerPC and found nothing (other than "it will be complicated" and "no one did it").

So whether it is Little Endian or Big Endian, it seems there is no Chromium PowerPC ATM.

@K-L

Thanks for explaining how to apply this patch; it worked perfectly for the Windows version of Browservice.

Here is a short video showing how it works on my X5000 with the Windows version of Browservice and Odyssey.

This is the perfect solution for me.

@Maijestro

Nice video. X5000 is even faster than X1000 and it shows.

Yes, once configured as wanted, it is the best solution.

@K-L
Quote:I probably mixed it with the WebCore PowerPC JavaScript JIT, which was available as early beta versions at the time I ported OWB to AmigaOS.
But it was completely unusable for my OWB port. Not sure anymore if it was limited to PPC64le, or if there were some other serious problems which made it unusable for the AmigaOS ports of OWB.