»

[OlafS3]

I have made a small update to 1.5.1. because I have a working version of Netsurf 68k (2.6 or 2.7, 2.8 and 2.9 not working at the moment)

A screenshot showing Netsurf "in action":
http://www.natami-news.de/Aros/Screenshot.png

All improvements:

Added:
Netsurf 68k (thank you Wawa)

Updated:
Wazp3D (Warp3D)
newest Roms (14.7.)
new Shortcuts (ALT I for Netsurf)

Full Download:
http://www.natami-news.de/html/distr..._download.html

Only Netsurf 68k:
http://www.natami-news.de/Aros/Netsurf.zip

When integrating it yourself: it needs stacksize 500000 and can only be started from CLI (not by clicking on icon)

Extended compatiblity page (Games and Applications):
http://www.natami-news.de/html/compatibility.html

Screenshots:
http://www.natami-news.de/html/screenshots.html

[utri007]

You have done lots of work for this

Could you consider to gave native GUI for Netsurf? Current version is SDL based, it missing lots of functions, it is slow, it doesn't feel "like native amiga app", freesez amiga when downloading, etc.

Here what would need to do

http://vlists.pepperfish.net/piperma...ry/002304.html

Netsurf is usefull tool even with low end RiscOS machines, equalent to 030, Amiga version is useless with 060 66mhz. I would bet that netsurf is only realistic option for 68k Amigas to get usefull www browser.

[OlafS3]

No there is already work to port the newest OWB version to 68k. So hope is there :-)

[utri007]

I'm little bit pessimistic about OWB, can it be usefull with real Amiga? At least Netsurf has smaller foot print?

[OlafS3]

It is about the OS4 port of Netsurf I think. I am not a C programmer (I never liked the language) so I do not think I could do it. Second problem regarding Aros 68k. I have only classact installed in it. Reaction is the new GUI in 3.9. and the main GUI of AmigaOS. It would have been better if they had used MUI instead of Reaction but portability was certainly no goal.

[utri007]

Who knows what has changed from Classact to Reaction Classact might do

[chris]

Originally Posted by OlafS3

Reaction is the new GUI in 3.9. and the main GUI of AmigaOS. It would have been better if they had used MUI instead of Reaction but portability was certainly no goal.

"They" do not know anything about MUI so it wasn't an option. There are barely any Reaction gadgets used anyway (if you ignore the prefs GUI) - it's literally buttons, a custom string gadget, a couple of scrollers, a tab bar and lots of empty space. Everything else is rendered into said empty space.

Nothing there that ClassAct can't do, although the tags and functions used may well need to be changed.

[wawrzon]

@utri007;
olaf is not the guy who made netsurf 68k port. arti, who actually did it, never added non sdl gui to his port likely for lack of skills or time, or motivation, or because its easier to maintain it, or because you have a stable version without too many self introduced bugs, or.. whatever. he did not.

so either we use it as is or someone adds gui to that. i dont see anyone who would. chris is constantly telling it is easy to port his gui to 68k, but for some reason doesnt do that himself. except aros 68k has no reaction or classact wrapper so all the stuff using it doesnt work, at least outta the box. therefore it wouldnt help. what concerns owb we will see what it does as soon as it works. here ive posted some of my results with netsurf 68k under aros68k on my a4k/060/50:
http://amigaworld.net/modules/news/a...=6452&start=20
i only had a very early compile of owb 68k for aros so i can confirm it loads already very long, and it crashed without loading completely. as far as im informed it loads now but misses mui classes.

[chris]

Originally Posted by wawrzon

chris is constantly telling it is easy to port his gui to 68k, but for some reason doesnt do that himself.

I'm busy with other things, and don't use 68k any more, so I'm not interested in back-porting it. Clearly nobody else is interested either.

The biggest job is probably making it work on palette-mapped screenmodes. I am intending to tackle this myself (as it is useful for OS4 and might improve the speed on 16-bit modes, which are a bit sluggish atm), however it has very low priority.

If somebody else was tackling a 68k port and feeding code back into the OS4 version, I would be happy to help. But I am not, under any circumstances, going to undertake a 68k port myself.