AmiBrowser: new modern web browser

@amigakit

Thats amazing for 68k miggies but is it possible to get this browser on our os4 machines?

Quote:

Dreaming we can finally one day use our 2nd CPU core for this...sigh

@328gts
On OS4.1, I know they are porting OWB AROS version, although the best choice would be to be able to use OWB v3.0 64Bit, which is fast and comparable to a modern browser.

https://www.youtube.com/watch?v=haT1RsF7ZyM

First impressions of AmiBrowser by Proteque CBN on his A600GS:

https://youtu.be/j4YyEZAIj64

I'm using it right now and it works really well!

@LiveForIt

Looking for someone to compile this

https://github.com/libretro/libretro-uae

RetroArch uae core. But I always get conflicts
between int32 and other types defined in UAE
and exec/types.h. Did you have this in Full UAE
too and if yes how did you solve it?

@328gts
Or our 3rd and fourth cores! :)
X5000 40 owner here

@amigakit
Quote:

Kas1e, Managing Director of myself, remarked:

Quote:


Are you still cheating ? Of course we see that GUI is 3.x mui app. But you can't create core with 1 or 2 programmers in even few years , which will support all modern web. This mean, that you use core done by someone else , be it Webkit or Chromium, and as always didn't credit ppls work (as always) and then, via some api or so you render pages on "real" browser on linux or whatever, and then blit ready images (via arm library i assume) to the os3 mui app. Or kind of.

And there is nothing wrong with, the same way should be done on OS4 for years, but then, there no needs for you to cheat us and take us like ones who understand nothing, and forget to point that all hardcore work on the core were done by relevant ppls having no connection not to amiga , not to you.

Creating a gui, with limited options and features, and blitting ready images from real core browser pretty possible in few weeks, of course. But creating from scratch a browser with support of all web stuff absolutly unreal to do by 1-2 or even 10 programmers in such a small timeframe today. We all know it , and we know how ppls at chromium, webkit and co works.

So.. the way you choose for browser for sure correct one for limited resources, but the way how you cheat us like this is "fully new done from scratch" again stinks a bit like the story with Yam, sadly.

@kas1e
Exactly the same is possible since years on AmigaOS 4.x as well, for example using IBrowse as the GUI.
Using AWeb or NetSurf instead may work as well, but I don't know if anyone tested it.

The only difference to the Linux/ARM + AROS/m68k A600GS/A1200NG is that you need 2 computers: One running Linux with for example https://github.com/ttalvitie/browservice and an AmigaOS 4.x (or even just 3.x) one with an old, simple web browser like AWeb, IBrowse or NetSurf as the GUI for it.

With a QEmu emulated AmigaOS 4.x system that difference doesn't exist: The Linux or Windows host OS can run browservice and the guest OS (AmigaOS 4.x) the "GUI" (IBrowse, etc.) for it.

@interrogative

Quote:

The news release clearly mentions arm libraries, it's obviously a hybrid program, with no attempt to claim other wise, the 68k side would run on any amiga 68k installation up to the point where it couldn't find the need arm library and then quietly quit. Maybe a later version will give proper error report

It's always been our stated intention to make use of the arm processor via "arm libraries" up till now this has included specialist gfx acceleration (main alpha blending related, but also some format conversion code) and picture file format decoding in the datatypes.

This takes things up a notch!

For information:

This project contains three / four layers layers.

1. The back end is CEF and is an unmodified production build so all source code for that can be found in the relevant repositories

2a: A mainly C++ Arm64 layer that provides the needed classes to control the browser and quite lot of other stuff. This is written mostly from scratch based largely on the simples example client code, informed by the more complex (insanely complex!) full example cefclient, but very little like for like code because obvious the GUI is not Gtk , so everything needs reinterpreting for...

2b: An amiga like API using messages and BOOPSI ish methods that enables the Arm side and 68k side to communicate, which straddles the arm and 68k sides. Lots of fun with endianess, pointer sizes, pixel formats etc to overcome. Some inline arm64 assembler helps with that.

3: An MUI application and private custom class that interacts with the above and provides the 68k side of the interaction API, sends input events etc to the backend whilst fetching and displaying the rendered pages.

The end result will be tightly integrated with the 68k environment, allowing file downloads, loading of local files, rtc. The 68k side will handle bookmarking, long term browser history (rather than per session back and forth) and as much more as we have time for.

@joerg

Not really, this no WRP type setup. Not that there would be anything wrong with that, as a project.

@kas1eQuote:
Not sure I understand the hostility. It's clearly stated it uses arm libraries and doesn't claim they developed them from scratch. I think most people realize they didn't create those from scratch. How is this different from any other commercial program that uses available libraries and doesn't specifically list all the used libraries? Why not just celebrate the accomplishment and be happy for the users of those systems.

@ktadd
Quote:AmigaKit still claims the A600GS/A1200NG would be AmigaOS related in any way, while it's clearly not at all, but just another Linux/ARM system running a Emu68 emulated AROS/m68k (not AmigaOS!) instead.
Similar to ApolloOS running on Vampire systems, or any <= 30€ Raspberry Pi which can do the same, or even much more, than their > 100€ Orange Pi systems.

Quote:I guess it's just a way too small market to make profit suing them for it.

How about creating and selling a A600/A1200 PCIe Card to install in the X1000/X5000 that would allow Amiga OS to access the card and then the browser as well. Would sell more of these fancy computers and allow us X1K and X5K to access and play with them as part of the X5K experience.



TJ

@AmigaSociety
Quote:Due to the PCI(e) overhead that would be much slower than Álmos Rajna's PPC JIT m68k emulations (Petunia, included in AmigaOS 4.x, as well as his JIT in UAE).

@ktadd
Quote:

What is cleary state initialy (at least for me), it's secrecy about what core were used. Because Mattew as always play word-games and didn't credit a shit for the real hardcore part : a Chromium core, which done by non-amiga ppls, and make it sounds like everything were done for specially from scratch, while is not (see Andy comment).

Don't take me wrong, I see nothing wrong with this all, and definately Andy do quality stuff and it all good (and i wish we on OS4 have someday some HW dongle with some fast little endian cpu to run some browser and to have reaction gui utilizing it), just the way how Mattew made announcement misleading as always and words-cheating games and just make me mad.

@Andy
If this is not secret, what was the reason to go Chromium way, and not Webkit one for example ?

@joerg

Quote:

I think you're absolutely right. I've already watched a few videos... Amibench takes at least as long to boot as a fully configured AmigaOS 3.2 on my X5000 with E-UAE 1.x.

I'm not saying that this hardware is bad, but you can see that AmiBench is emulated in parts and not running natively, even though ARM libraries support the hardware.

It's exactly the same thing that
@LiveForIt is doing with E-UAE: interacting with the native host system, in our case AmigaOS 4.1 on PPC.

@kas1e

Quote:

Didn't notice this in your original post, or rather when I originally read it.

The reason we went with this, ie CEF, is that is is specifically designed for this purpose, ie to embed chrom(e|ium) in third party applications, it has an extensive API, allowing you to intercept and trigger browser actions and so implement your own browser around it. It's also pretty bang up to date, being based on chromium 138 !

@kas1e
Quote:WebKit is an obsolete platform since many years already, not only on AmigaOS since Pleyo stopped their OWB development and as consequence any AmigaOS(-like) port of it went useless.
It's only still used by a few niche platforms like Apple/Safari, and maybe KHTML.
Everyone else, incl. Opera and MicroSoft (Edge, Office, Exchange, ...), switched to the Chrome/Chromium engine a long time ago already.

You can write the Wraper application in a Docker, executable in any Linux system.
And the Client in any Amigaos system.
Why Amigakit has written this application only for Amyberry and ignore us. After spending a lot of money for the NG, Enhancer hardware, etc.?
Is the development of enhancer and system56 has interrupted?