It looks good so far. Is it based on the latest Webkit?

Yeah, technical details, please?

_________________
- The wiki based MorphOS Library - Your starting point for MorphOS
- Software made by jPV^RNO

Great! Thank You, I bought an A600GS

_________________

That’s great news! Having a capable web browser is a must even for classic/retro computing machinery.

_________________

Having support from a company makes a difference

_________________

Congrats, this is great news! I do wonder how this is powered. It be a nice surprise if this is a 100% native port of a web browser, thats a lot of work, but my spider senses think it maybe some kinda of Rabbit Hole / AmiFox system.

Plus I saw the video of it playing the Youtube, looks just a bit slow, I did think that would be the case, as my Pi400 Amikit+Rabbit hole, would drop the odd frame, and thats a 40% more power device than this. The Pi5 however solves this.

This is why I hope Amigakit consider doing Amibench for more high end Orange Pi 5 boards that be more than capable of doing things like this.

Plus more power, may even allow AmigaOS4 running in emulation. I was surprised when I saw this video of OS4 running on Pi5, fairly smoothly
https://www.youtube.com/watch?v=7vDfZ4DRzSE

But still this is great news.

_________________
AmigaNG, YouTube, LeaveReality Studio

@AmigaNG

No this is not using the Rabbit Hole feature and is not using the method that AmiFox uses. It is a 68K/ARM library hybrid browser built in MUI (Zune compatible). It has been 6 weeks of intense development so far to get to this point.

It is not optimised yet. We wanted to get it first stable. functional and eliminate any bugs before proceeding with optimisation.

We will release it soon for A600 GS and the A1200 NG users to preview but without file download support and a few other features which are coming in September.

_________________
Amiga Kit Amiga Store
Links: www.amigakit.com | New Products | A600GS

Looks good!

@amigakit

Thanks for the news release and update.

Cheers,
redfox

Thank you AmigaKit

Salvatore

_________________

First impressions of AmiBrowser by Proteque CBN on his A600GS:

https://youtu.be/j4YyEZAIj64

_________________
Amiga Kit Amiga Store
Links: www.amigakit.com | New Products | A600GS

Looks like a great start to a modern web browser for the A600GS and A1200NG. Having this makes a world of difference.

_________________

"This is triumph
I'm making a note here, huge success
It's hard to overstate my satisfaction..."

This kind of 68k+ hybrid solution is certainly the thing about which some of us have been much enthused.
You listened, and now it's here.
Well done everyone.

_________________
All the way, with 68k

I guess that this means AmiStore functionality is right road the corner?

_________________
"Art challenges technology. Technology inspires the art."
John Lasseter, Co-Founder of Pixar Animation Studios

Weeks ?
It tooks many years to have a décent browser on Morphos and Aros so I wonder how it took only some weeks for you. I suppose this is possible because it’s based on existing work which I think should be credited.

The real truth is probably that this is some browser running on linux, and from aros via some api or so talk with native os3 gui, which render recieved images from real browser.

Why Mattew can't say that clear, and instead misleading like it's fully new browser created from scratch (which of course can't be true) is clear , because then you should say simple "we create native GUI to talk with other's ppls work, which doing all core-hadrcore stuff for us".

I assume this is Chromium or WEbkit build , and native mui code used for gui, and ARM for blitting bits. And there nothing bad in it, quite right way today, just as usual real hardcore work not credited , and mislead ppls like this is full new browser done from scratch.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

"the real truth is that probably" :D "Probably the real truth".. made my day.
I am interested as well in how it works but more form a point of how I can use the new libraries for own projects in terms of SDK. The device is running an JIT emulator and offloads already media rendering to ARM side (audio, pictures, music).. if you offload all that stuff I can imagine that 260Mips (plus some JIT peaks here an there) can be just enough to bring that performance on the table. On Facebook he explained in comments and in some forums that it is a 68k browser... I expect it to be based on one of the existing webkit based browsers build around there ARM libs/datatypes. It makes sense and feels the most natural way.

I have experimented with a fork of Netsurf and a proxy which reduces sizes of images and color depth to reduce significantly rendering times on low end 68K. It's basically that but with a better codebase than Netsurf. (just my bet)

_________________
AROS Broadway - AEROS - Aminux - AmiCloud - indieGO! Appstore - AmiWallet - VAN lossless video codec - AMC Amiga media Center -KrypUnite - LibertyNet - MinX - amigaNX

Quote:

I wonder how it took only some weeks for you

The actual HTML engine isn't running natively, that's why. It doesn't run on AmigaOS, it's not a browser port. Amigakit may try to tell you that it's not AmiFox, but the only difference is how it's integrated. It's still the same solution with a browser actually running on a different operating system / CPU.

There's a plausible sounding explanation: link

"It is based on CEF (Chromium Embedded) running under Linux/ARM with a small C++ wrapper around it, to facilitate the communication with the 68k-side.
The MUI/ZUNE program directs the the browser and sends intuition events over ... and fetches the rendered pages and displays it."

_________________
- The wiki based MorphOS Library - Your starting point for MorphOS
- Software made by jPV^RNO

@jPV
I prefer this link which your link is a paraphrase of

To save you you clicking :
Quote:

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.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad