If the architecture separates the web browsing engine, from the Amiga GUI, which is exactly how Wayfarer does it (and Iris), then there's no reason in the future that you couldn't have a different browsers lke ibrowse and netsurf all sharing the webkit engine where it's available.

you could even let the user choose, using the ibrowse engine on aminet say, and webkit on a modern website. This would minimise the memory usage by avoiding using the webkit engine on simpler websites that work with a simpler engine.

Firefox used to have a plugin to do this on windows, letting you use the IE engine for websites that had compatibility issues.

This is a very 'Amiga' way to architect it i.e. a pluggable framework.

However there would be considerable work in defining such an interface.

@kas1e

Thanks and I used your guide first time around when i spent many hours trying to make it work. I know very well how to use putty but no luck.

Anyway the root cause of the issue is not that, the root cause is the keyboard problem. I don't understand how the keypress can work to stop the boot sequence, take me to console, but then no more keypresses work. I had that with 3 different keyboards including the dumbest one i could find with no hub or compound features.

Yes I know. i have null modem to USB. Plug the USB end into windows laptop. Never works.

i tried many times to use a serial to USB cable to connect the only other machine i have but it never worked.

@vagappc

This is covered many times here and elsewhere - Wayfarer is written using a MorphOS objective-C based environment that does not exist on OS4. So even if the developer wanted to release the code it's of no use in porting to Amiga. Better use the OWB or Odyssey browser chrome or just start anew to make the user interface / application framework.

As for webkit, the wayfarer patches for webkit itself are on github and are open source thanks to a generous sponsor, while walkero and team get it building and running on OS4.

Oh wow... I'm on old firmware trying to update to the latest one which I just bought..

Having some problems using keyboard with Uboot that is preventing me from... installing new uboot with better keyboard support

I am aware it's fussy about what keyboards it supports. I have some that it just fails to see at all.

But the others I have that let me press a key to get to the uboot setting or console... they work for the first keypress. Then immediately stop working again.

Do i just have to keep searching for an old keyboard that works? Or is there a trick to make these 'almost works' keyboards... work?

Your case almost certainly expects a USB 3 header. The Amiga board is probably a USB 2 header, like on the Sam460ex. If so, the connectors are different, you will need an adapter.

no more than netsurf and definitely much more capable than iBrowse. it's just designed for lower power machines thats all. Runs on other 68k platforms.

@abalaban

Any news on a newer FLTK? Might allow the Dillo web browser to be ported

@Maijestro

Given that Amiga is very much a hobby for people who simply enjoy tinkering, it's a very small price to pay to buy what little commercial software is released. I pay for pretty much every new bit of Amiga software that comes out whether I use it or not, and if I do use it it's probably for hours at the most. But I still pay.

@Hans

LOL no worries I'm happy it had plenty of responses including plenty of on-topic ones.

Besides I'm also curious about the ffmpeg port and Emotion - on the one hand I'm glad the EntwicklerX team made it, on the other hand I wish there was better documentation and/or there isn't so much good stuff hidden behind the 'only OS4 beta testers and Enhancer team insider have the cool stuff'. At this point I'm pretty sure there are more people who are insiders than left on the outside like me. So why not do things in the open.

@rjd324

what's that supposed to mean? because it's more OS3 related?

@joerg

Yes of course I'm aware of datatypes and the IFF system.. Quicktime even in those days was an order of magnitude more sophisticated, it was a proper pipelining multimedia framework with pluggable codecs, containers, source and sinks, timers etc.

Amiga had datatypes, realtime library and, uh, nothing else. A natural addition therefore would be a multimedia framework IMHO.

Well the topic is what features should have come next in the roadmap, not what leadership was missing. The latter is well understood and not particularly interesting to debate IMHO. The former is I think still a fun intellectual exercise at least for me.

The delta between AmigaOS and the MacOS of the day, and even windows 95 is not that big, Amiga was even ahead in some areas of course, and behind in a lot of others. But the gap is not huge when factoring in the 'third party' stuff like AmiTCP, Reaction (albeit MFC was a lot more substantial than Reaction), Envoy, P96, AHI, and your own efforts among others. Again, in my mind the biggest miss is a multimedia framework like Mac had with Quicktime, and to a lesser extent windows media. I like what the EntwhistlerX guys have done with Emotion and FFMpeg. I feel that comes close to filling the gap for OS4.

Yes true but not on topic

Any update to Emotion? any SDK for the ffmpeg wrapper?

One of my Amiga obsessions is what-if-ing over what AmigaOS would be in it's next iteration after the original 3.1.

Now of course we have a real 3.2, which is wonderful, and it certainly does a great job of 'finishing' the things left hanging like adding Help and BOOPSI (with Reaction), as well as rounding out things like modern filesystem support.

Then of course we have defacto standard extensions such as P96 and AHI.

So what's left? If there was an Amiga 1400 in 1995 for example, what features would it have to help it compete with Mac OS 7.6 and 8, and Windows 3.11 and 95?

I don't mean memory protection and things that the hardware just can't do, and I also exclude virtual memory since memory is cheap now even if it wasn't then.

Some obvious candidates - TCP/IP and LAN working were filled then by AmiTCP and Envoy, and now by Roadshow, and SMBFS.

For me the obvious missing piece is a multimedia framework, equivalent to Quicktime, or gstreamer. I'd like to think there's a parallel universe where Amiga had its own Quicktime like API with all that that entails.

What's on your wishlist?

ask chatGPT, it knows Amiga stuff!

there's no driver for it. but it wouldn't be a huge job to create one, relative to other things AmigaOS is missing at least