We need an iBrowse replacement for 68k!!!

[Fab]

If you want to have a proper HTML5 browser on Amiga, the only realistic way is to use WebKit.
It would be quite easy to port using Odyssey sources, even, but obviously, it would only make sense on UAE setups, considering memory and cpu requirements.

@magnetic

There is so many hoops to jump through, compiler probs, IDE probs, tricky gui stuff to integrate, etc

If by IDE you think about GUI editor, there's zero need for that in that kind of application development. In any serious development, you always leave this GUI editor sh*t behind, it's always a loss of time in the end (i have enough experience with XCode and Visual Studio to know how horrible they are).

As for compiler, GCC4 toolchain is enough, and editors like Golded or Scribble are good enough. Only issue might be libnix too outdated, but it can easily be completed.

And there's no tricky GUI stuff to integrate. Coding with MUI is really easy compared to similar stuff you have to do in other toolkits, actually.

[Fab]

No proper javascript support discards it for what was asked before: feature-complete HTML5 browser.

As for its speed, disable JS in WebKit, and it also gets much faster, surprisingly... Though there are other issues with it on OS4, blitting speed seems slower than it should be.

[Fab]

jason has compiled aros owb for 68k, and i (and others) have tested it. it is almost usable, which means webkit browser might altogether be usable even on real amigas (060).
i expect fabs odyssey might be somewhat more responsive as this outdated version of aros owb.

Considering AROS OWB didn't have blitter support at all, it could only be faster, and not a little. I still think it would be rather slow on 060.

thanks to jason and deadwood i have been able to build aros68k toolchain, configure the odyssey project somewhat but making ive run immediately into some (define) problems, because the project wants to build whith pthreads. i couldnt find the cause, fab, you might recall ive asked you too.

Well, you just need to set the thread backend you use when invoking cmake, if you didn't already.
That's USE_THREADS=MORPHOS.
So for instance
cd cross-build
cmake -DCMAKE_CROSSCOMPILING=ON -DCMAKE_TOOLCHAIN_FILE=../morphos.cmake  -DUSE_IMAGEDECODER=GENERIC -DUSE_THREADS=MORPHOS ..  etc...