NetSurf 68k V 2.0

[unusedunused]

>Still wonder why amiga version is so power hungry? RiscOS version >works fine with 16mb and 030 equalent cpu.

>It must be SDL

Have you test it on same pages with Risc OS ?.how many sec does it need to show amiga.org page ?

I profile a little and the time of SDL function use and graphic draw is very very few.the netsurf core need speedup to be faster.

and they plan to do that.

""""""
http://wiki.netsurf-browser.org/Development_Plan

Once we move to using LibDOM, we should give a big speed improvement over NetSurf 2.x. There will be a lot less string copying and string compares will be much faster due to usage of string interning library LibWapcaplet in NetSurf, LibDOM, LibCSS and Hubbub.
"""""

>1) Seems to be some freeze (like mouse will freeze) a bit when pages load. Sometimes you >think it's hung but you wait and it comes back

The mouse Pointer when it is show from SDL (in white) freeze on slow systems during page load lots.

[unusedunused]

Well I was testing it on Amithlon on a 2.4GHz AMD Athlon which is waaayyy faster than my 060 system and it was still appearing it was hung for some time.

SDL just sucks  Sooner it can be gone the better!  If NetSurf was native amiga app it would be way faster I think.

to see that the problem is not SDL you can do a simple test.

show the ibrowse/history.html file that is in size 74 kb and have many lines with netsurf

file:///............

showing antialiased text is the biggest graphic action a browser must do.
this big test is on a classic 10* faster as show just a simple forum page with many text

[unusedunused]

>Just a question, what's the purpose of Wget within NetSurf?

It is use when download a file, then its download over wget.so there is resume mutliple download possible.

>I think dropping sdl in favor of mui would be great. Artur ->

what does it help, the most problem that netsurf have, no java script, no frames and some other page view things still not work.also it get not faster with MUI. I am sure.

Please can somebody do the test and tell what time the html file need, so all is clear that the slowness come from netsurf core, maybe CSS render etc and not from graphic output over SDL

http://www.ibrowse-dev.net/download.php

show the ibrowse/history.html file that is in size 74 kb and have many lines with netsurf

then type as url

file:///ram:ibrowse2.4-020+/history.html

(is 74 kb in size)

and look what time it need to show the page.

and if you unhappy with the GUI, look on the OS4 version of OWB and netsurf.
this versions have very few GUI, netsurf 68k have more features for daily use.

Thats >http://www.netsurf-browser.org/about/screenshots/wip/
OS4 Version

http://www.netsurf-browser.org/about/screenshots/wip/

thats 68k version

http://www.a1k.org/forum/attachment.php?attachmentid=27963&d=1278938999