Netsurf V3.0 Amiga release 2

[unusedunused]

>It is made so you can browse other sites already. ffplay is run like other process.
>Click on browser window to focus. Hope that helps!

I change newest SDL so it use at default this way:
A sdl program with active window use normal pri (0).when the SDL window is deactivate then taskpri is change to -1.so your amiga can run at full speed wtih other programs, because SDL programs are most bad written and slow down whole system when a program run.

netsurf is compile with newest sdl.
But ffplay can release too with the new sdl.so when deactivate ffplay window other programs that run at pri 0 get more cpu time

but all tasks that are above 0 are not change in pri.so sound in ffplay have always priority>0.same is with the picture and network thread.only the main task, that read and decode ahead video data run at pri-1.

And if your system is slow and need play lots audio, then you have no good performance.

best is for classic use 3gp videos in grayscale play.

the behavior of SDL can switch off if you really notice problems with env var
env:SDL_NOLOWERTASKPRI

to get more better and more configurable task sheduler and responsnes of AOS, try out

http://aminet.net/package/util/misc/Executive

[Jose]

Soon I'm gonna be testing this in a system with overclocked 060 at 80Mhz and PicassoIV, I'll report how it goes

[unusedunused]

Because netsurf have many settings to speedup and get best performance depend on the CPU its also important to tweak the settings for slow systems

The default settings are very bad for a classis system.Default is this and it work good on a fast system.SO when you use a UAE on a 1 GHZ X86 this values are ok.maybe on SAM help tweak here too, but a aone/Peg should also with default values fast enough.

file is in resources/options.
Thats default of netsurf 68k

incremental_reflow:1
min_reflow_period:25
max_fetchers:24
max_fetchers_per_host:5
max_cached_fetch_handles:6

but when i disable JIT then its only possible to scroll when page is full load.

Important seem reduce the number of max_fetchers(mean how many data requests are send at once)this reduce the internet latency because there need not wait until the data is load for each image.

But for the classic its too much.I try below values and set all to 4.
also i increase the min_reflow_period to 500.this mean the page is not so often update.

But you should tweak yourself and put here the best values you get

with below values i get on winaue without jit enabled ( get 33 Mips and 23 mflops on sysspeed cpu/fpu Test)

when the page show correct layout(happen very soon on netsurf) but load some missing images, i get a scroll speed of 2-3 fps /sec now

incremental_reflow:1
min_reflow_period:500
max_fetchers:4
max_fetchers_per_host:4
max_cached_fetch_handles:4

please try out on your classic and post values so you reach better performance.
the complete page load is not important only important is that the page is show as soon as possible in correct layout and you can scroll or click on links

try also
incremental_reflow:0

but i see here no diffrence

also try out if with disabled antialiasing in netsurf more fps/sec on scroll can reach.usre text cant read then, but only to know if disable AA give a noticable speed increase

[Gulliver]

@MozzerFan

You can get OWB 1.6 68k from http://strohmayer.org/files/OWB_m68k_1.6.lha

[MozzerFan]

incremental_reflow:1
min_reflow_period:500
max_fetchers:4
max_fetchers_per_host:4
max_cached_fetch_handles:4
 
please try out on your classic and post values so you reach better performance.
the complete page load is not important only important is that the page is show as soon as possible in correct layout and you can scroll or click on links
 
try also
incremental_reflow:0
 

With these settings amiga.org loads faster on my classic system. It now takes about 40 seconds. Loading time of amigaworld.net is the same.

[MozzerFan]

@MozzerFan
 
You can get OWB 1.6 68k from http://strohmayer.org/files/OWB_m68k_1.6.lha

Thanks !!!
 
Just like 1.5 it doesn't work though :confused:
It won't even open a window.
 
I wonder if it has to do with the new ixemul.library.
 
Edit: just tried it with the old ixemul (48.x): same problem.
It's really weird: If I try to start it from CLI, it says it need exec.library from BB2, and that's the one I'm using.

[MozzerFan]

Found the problem with OWB 1.6: I had to disable AFA and use ixemul.library 48.x.
 
Running it under winuae was not really as fast as netsurf 68k, so after the test with owb 1.3 I decided no to try 1.6 on my real amiga.

[unusedunused]

>Found the problem with OWB 1.6: I had to disable AFA and use ixemul.library 48.x.

ah yes i download it and test from that link.
get the errors messages too when start from shell.
ixemul V48 or better need or exec V45 need.He does add checks so it dont work.but its possible to remove this checks and all work ok i think.

AFA and ixemul is fully compatible to older Versions.

that OWB can work well with newer ixemul and AFA you can see, when you try out OWB 1.2 OWB1.3 or OWB 1.4.all work ok.1.5 i not test.

I dont rememeber was there a news message about 1.6 OWB

[MozzerFan]

>Found the problem with OWB 1.6: I had to disable AFA and use ixemul.library 48.x.
 
ah yes i download it and test from that link.
get the errors messages too when start from shell.
ixemul V48 or better need or exec V45 need.He does add checks so it dont work.but its possible to remove this checks and all work ok i think.
 
AFA and ixemul is fully compatible to older Versions.
 
that OWB can work well with newer ixemul and AFA you can see, when you try out OWB 1.2 OWB1.3 or OWB 1.4.all work ok.1.5 i not test.
 
I dont rememeber was there a news message about 1.6 OWB

Well OWB 1.3 indeed works fine with the new ixemul and AFA, but the speed was horrible on my real amiga, as I wrote in my previous post.
I just wanted to see if 1.5 or 1.6 were any better.
 
OWB 1.5 gave me the same warnings as 1.6, so I guess both require the old ixemul and also that AFA has to be disabled.

[unusedunused]

>Well OWB 1.3 indeed works fine with the new ixemul and AFA, but the speed was horrible >on my real amiga,

speed is also horribly slow on winuae.
the readme of OWB 1.6/1.5 does not contain any text about more speed.

As far known Jörg have tell before 1.6 and 1.5 release, that he not want furtherdevelop OWB 68k.

The OWB 68k Port is so outdate and very few is new in 1.5 and 1.6, and the last few updates are really no reason that its not possible to work on AFA and newest ixemul.



History:
1.6 (23.5.2009)
- Relinked with OpenSSL 0.9.7m, https: works now.
- Delayed rendering while data is transferred can be disabled by setting
  the OWB_NODELAY variable now, for example use 'set OWB_NODELAY 1' in a
  shell before starting OWB from it. It's only usable that way if you
  have a *very* fast system.

1.5 (24.2.2009)
- Added GETTITLE and GETURL ARexx commands.

[MozzerFan]

I just wanted to try out OWB 1.6, because in your previous posts you asked me to also test the loading time of amiga.org in OWB.
 
With the new options-settings, netsurf is reasonably usable on a classic system, and by using netsurf I can also use AFA and the new ixemul.

[Tumbleweed]

incremental_reflow:1
min_reflow_period:500
max_fetchers:4
max_fetchers_per_host:4
max_cached_fetch_handles:4

please try out on your classic and post values so you reach better performance.
the complete page load is not important only important is that the page is show as soon as possible in correct layout and you can scroll or click on links

I have tried these values (A4000D as per signature) but for me their appears to be only a minor improvement. Page renders 2-3 seconds faster.

Weed

[0amigan0]

Is there someone who can help Artur do the MUI interface for Netsurf ??
What I'm missing right now in netsurf, compared with eg. Ibrowse, is the possibility to customize the interface however I want.

[unusedunused]

incremental_reflow:1
min_reflow_period:500
max_fetchers:4
max_fetchers_per_host:4
max_cached_fetch_handles:4

please try out on your classic and post values so you reach better performance.
the complete page load is not important only important is that the page is show as soon as possible in correct layout and you can scroll or click on links

I have tried these values (A4000D as per signature) but for me their appears to be only a minor improvement. Page renders 2-3 seconds faster.

Weed

The main reason for this settings is that you can scroll in a page before it is full load.the full load time is normaly not much faster.

for example:

with old settings when i want show http://www.amiga.oth without JIT and load it, than  press reload page button and keep and hold cursor down button, the page is scroll after 53 sec.

with the new settings i can scroll the page after 18 sec.
but the page is too only full load after 50 sec.

but after 18 sec you can scroll and press a link and you need not wait until full page is load.
so in praxis you get a speedup of 3*

does the classic not sooner scroll with that settings ?

next netsurf also have faster scroll, because netsurf use CPU and memmove to scroll data on GFX Card.thats slow on Amiga.Use SDL_BlitSurface is lots faster

[0amigan0]

next netsurf also have faster scroll, because netsurf use CPU and memmove to scroll data on GFX Card.thats slow on Amiga.Use SDL_BlitSurface is lots faster

Next Netsurf should also have MUI interface.
Here's a MUI programming tutorial (http://www.ezcyberspace.com/gcc/index.html ), in case you or Artur aren't particularly experienced in MUI.

[unusedunused]

@0amigan0

>Here's a MUI programming tutorial (http://www.ezcyberspace.com/gcc/index.html ), in >case you or Artur aren't particularly experienced in MUI.

change of GUI is lots work, and if its not sure when netsurf get Java Script and frames, i dont want spend much work on it.Because the netsurf devs do not care about MUI or amiga code, they can change at any time something, so the MUI Version fail to work(happen with MOS MUI code).and then there is more time need.

So its better to wait for a nicer GUI until netsurf have all features modern browsers have.

Artur have add to sdl GUI all features a modern browser need, download of files with progress request.show and download videos, bookmarks and hotlink buttons.

only scroll and textinput must enhance and all important can do with it as can do with a nicer GUI