Netsurf for 68k amigas, css capable web brower

[chris]

i get too the problem with http://www.nu.nl crash, netsurf only not continue to load and quit of netsurf is too not possible.

does this site work on MOS or OS4 netsurf ?

No, it busy-loops trying to retrieve something-or-other (doesn't crash though, I can browse to a different page).  Report it to the ml please.

Chris

[utri007]

This is great You get it work extremely fast

This sounds stupid from me but you should trust more your skills as a programmer _Arthur

Thanks

[0amigan0]

@__arti:


Any chance of a MUI version ??

[unusedunused]

@__arti:

Any chance of a MUI version ??

in the google code of summer project, there seem GUI implementation DOM large change.seem there is time to wait until it is finished if MUI or amiga OS work with new netsurf.

[chris]

in the google code of summer project, there seem GUI implementation DOM large change.seem there is time to wait until it is finished if MUI or amiga OS work with new netsurf.

AmigaOS4 will work with the changes, as I will argue against them being merged in until I get the necessary modifications in place  Ultimately it will mean less work per feature for new ports, and a more consistent interface across all platforms.

DOM is irrelevant as far as the platform code is concerned, as is the new CSS parser, except for possibly the odd minor change.

Chris

[wawrzon]

ok, im back in business (for the time being).
i had a terrible problem to get my dsl router up und running after i switched it off for two weeks. it has lost all data and the damn pc didnt wanted to reprogram the thing neither with iexpl nor firefox. hung around, some firewall prob or who knows.:/ in the end i throwed os4 with owb at that and voila. it worked immediately. so it seems aos4 is still good for something, right?

back to subject:
i looked at the nofreetype version. it is slightly faster, around 5% i would say. but i think its not worth it. some pages look trashed with internal type and the speedup is not significant.

edit: well, not quite, sometimes its pretty much faster, like +1/3
it would be good to get hold of this endiannes problem first i think. and it still runs out of memory. it has nothing to do with stack apparently.

 i see the bugtracker has already been taken care of too

btw, on os4 i have an impression that the current owb is quite a lot faster than netsurf so maybe it still would be worth a try.

[unusedunused]

ok, im back in business (for the time being).
i had a terrible problem to get my dsl router up und running after i switched it off for two weeks. it has lost all data and the damn pc didnt wanted to reprogram the thing neither with iexpl nor firefox. hung around, some firewall prob or who knows.:/ in the end i throwed os4 with owb at that and voila. it worked immediately. so it seems aos4 is still good for something, right?

back to subject:
i looked at the nofreetype version. it is slightly faster, around 5% i would say. but i think its not worth it. some pages look trashed with internal type and the speedup is not significant.

edit: well, not quite, sometimes its pretty much faster, like +1/3
it would be good to get hold of this endiannes problem first i think. and it still runs out of memory. it has nothing to do with stack apparently.

 i see the bugtracker has already been taken care of too

btw, on os4 i have an impression that the current owb is quite a lot faster than netsurf so maybe it still would be worth a try.

try the page

Edit:Page was before wrong

http://www.t-online.de

i notice on netsurf it is only show when it is full load.take 10 sec on my system

on OWB 68k same i can only scroll to down and read full text until all images are load.

but on firefox, safari there can scroll around and read the text after 3 sec.

but of course the images are not load complete.

what happen on OWB OS4 with that page ?

I dont know if netsurf use threads, i only see MOS netsurf use a GUI thread.but if this help to get better reaction when a page is not full load i dont know.

maybe somebody can tell what happen with the site on netsurf MOS.can there read text and scroll much time before all images are load ?

[wawrzon]

the page loads ages on 68k: around 80sec, both versions of ns, nofreetype was even some sec slower in this case.
approximate results:

68k ns-nofreetype ~68-83.s -has to load full, slight layout glitches doesnt scroll immediately after page is complete

68k ns ~77.s -has to load full

owb 68k 1.3 - difficult to benchmark, definitely much longer, but you can scroll a little after a minute or so, doesnt need to load full, rendered perfectly

owb 3.13 os4 - loads about a minute, able to scroll after ~20s (604/150), it opens a popup and default window size is much bigger of course.

netsurf2.1 on os4 starts to display but locks the system before the images load

for comparison my firefox needs ~13s on a athlon dual 4200+, my dsl is only 2k btw

[unusedunused]

the page loads ages on 68k: around 80sec, both versions of ns, nofreetype was even some sec slower in this case.
approximate results:

68k ns-nofreetype ~68-83.s -has to load full, slight layout glitches doesnt scroll immediately after page is complete

68k ns ~77.s -has to load full

owb 68k 1.3 - difficult to benchmark, definitely much longer, but you can scroll a little after a minute or so, doesnt need to load full, rendered perfectly

owb 3.13 os4 - loads about a minute, able to scroll after ~20s (604/150), it opens a popup and default window size is much bigger of course.

netsurf2.1 on os4 starts to display but locks the system before the images load

for comparison my firefox needs ~13s on a athlon dual 4200+, my dsl is only 2k btw

the OWB OS4 version have after 20 sec load, full page Text load, so can full scroll down to read last line ?

and your firefox result, is the 13 sec full page i guess ?

what time you get on your firefox until you can scroll full down to read last text line ?

[wawrzon]

owb os4 20 sec for scrolling 1 min for full page, just tried again and firefox rendered t-online in some 5 sec now, scrolling is possible immediately. as piru said the results vary so much it is difficult to make something out of this. the fact is on a pages like amiga.org netsurf sdl is already faster than ibrowse and renders quite well even if the scrolling is jerky. maybe there is a way to optimize this wit hwsurface or what it was?
i see the hit after closing the app has been disposed of, is it only on nofreetype or did you find the bug?

what is the policy now? to wait till the next release, because of endiannes prob and the gui? do this port stays on sdl? i suppose further features like window resizing will not be possible in this case? running out of memory on big pages is still a problem, regardless the stack. if the reason is unknown maybe it could be asked on ml?

[apj]

owb os4 20 sec for scrolling 1 min for full page, just tried again and firefox rendered t-online in some 5 sec now, scrolling is possible immediately. as piru said the results vary so much it is difficult to make something out of this. the fact is on a pages like amiga.org netsurf sdl is already faster than ibrowse and renders quite well even if the scrolling is jerky. maybe there is a way to optimize this wit hwsurface or what it was?
i see the hit after closing the app has been disposed of, is it only on nofreetype or did you find the bug?

what is the policy now? to wait till the next release, because of endiannes prob and the gui?

The endianess problem is fixed. I have submited Netsurf to Aminet. It should be ready tomorrow.

do this port stays on sdl? i suppose further features like window resizing will not be possible in this case?

Window resize can be done be editing Resources/Options file.

running out of memory on big pages is still a problem, regardless the stack. if the reason is unknown maybe it could be asked on ml?

Can you tell on which page do you get out of memory?

[unusedunused]

owb os4 20 sec for scrolling 1 min for full page, just tried again and firefox rendered t-online in some 5 sec now, scrolling is possible immediately. as piru said the results vary so much it is difficult ?

i think the fast firefox result is
because firefox have a cache you need a page reload do(press reload button).

but even if firefox is fast on cache , OWB and netsurf should of course too use the cache and show page faster.

its right that the internet time make things differ.But not very much.I test myself with proxy
 
If you have your amiga connect to a PC you can run a cache proxy here.

when you set a env var on amiga OS
http_proxy

127.0.0.1:0080

with content then it can use the proxy on the PC when you set the address and port to above values
this env var is used by all browsers that use libcurl.so OWB and netsurf use a proxy cache

I use allegro surf(its kn own as fast) and i notice no speedup of amiga browsers/firefox on pages with fastserver as the t-online site and other big sites i tell are.

>maybe there is a way to optimize this wit hwsurface or what it was?

yes, newest version is faster and use the gfx card blitter for scroll because it use HWsurface.

We send test versions to Thomas with sdl_software and SDL_HWsurface and on his slow Z2 system, sdl_HWsurface give same render speed, but scroll lots faster

also new is 16 and 32 bit mode is automatic detect, key input with shift and alt work, and speed should be faster,because to get correct endian, code  can remove

but there are still lots of known bugs that are netsurf SDL Problems, i have report them in ML, but because all work on integrate the google summer code, nobody have time, so need to wait for SDL and new DOM what happen here.

but what can say, netsurf run stable on  68k and the OS4 crashes are no fault of netsurf main code.

[x303]

Still don't know why netsurf 68k runs on some (winuae) systems, but not on mine. I've assigned amitcp as suggested earlier, but netsurf still doesn't see the connection. Pretty strange, as aweb and ibrowse do work perfectly.
Does anyone have some more suggestions

x303

[Fab]

Here, with OWB 1.3 for MorphOS, it takes about 20s to load fully, and you can already scroll to bottom after 4s (note that on MorphOS, OWB network manager is threaded).

FireFox gave a similar result, loading in about 20s too, and allowing to scroll after about 4-5s.

But i wonder once again why i replied about that kind of benchmark that depends on way too many factors.

[ami_stuff]

Great work Artur & Bernd.

[MozzerFan]

Still don't know why netsurf 68k runs on some (winuae) systems, but not on mine. I've assigned amitcp as suggested earlier, but netsurf still doesn't see the connection. Pretty strange, as aweb and ibrowse do work perfectly.
Does anyone have some more suggestions
 
x303

If you use AmiKit:
The default assignment for AMITCP: in AmiKit is the Ibrowse drawer, so make sure to replace this assignment.
edit: The assignment is made in user-startup. Either replace the current assignment, or after this assignment add the following:
Assign AMITCP: ADD
Check in a CLI window by entering "assign" to which drawer AMITCP is currently assigned.
 
Also check if you've installed all the fonts that come with Netsurf if your running the TTF version.
Edit: If the nofreetype version runs ok, you haven't installed the fonts correctly. You must install them in Fonts:truetype/ttf-bitstream-vera
 
Also check if you have the latest ixemul lib.