I was investigating svg parsing libraries (I could only find one other
viable alternative, libsvg), and I am interested in the progress of this
I tried to compile it from SVN, but two errors cropped up:
Makefile:8: build/makefiles/Makefile.tools: No such file or directory
Makefile:45: build/makefiles/Makefile.top: No such file or directory
suggesting, that some files were missing for the build process.
I plan to use an/this svg parser for loading svgs (im not too worried about
the full svg specification) for rendering inside a 2d game engine, as such,
I may have some time in the near future to improve upon it. One of the
things I did note, however, was that groups were not exposed by the API of
libsvgtiny, of which would be useful in my case. The preserved hierarchy
would potentially be useful in my application for animations.
Tai Chi Minh Ralph Eastwood
I've found another stop/abort type crash :(
Returning NULL from gui_download_window_create causes NetSurf to
crash, rather than just aborting the pending download.
Logs attached. Stack trace line numbers:
9.Files:Projects/netsurf_svn/netsurf> a2l netsurf-cairo 753a0
9.Files:Projects/netsurf_svn/netsurf> a2l netsurf-cairo 751b0
9.Files:Projects/netsurf_svn/netsurf> a2l netsurf-cairo 569bc
9.Files:Projects/netsurf_svn/netsurf> a2l netsurf-cairo 5474c
9.Files:Projects/netsurf_svn/netsurf> a2l netsurf-cairo 531d0
On Sat, 16 Jul 2011 13:53:22 -0000, wibbled on for an age:
> Ensure buttons update (stop button activates) when new URL starts to load
Stopping a page from loading whilst in the "Fetching, Processing"
stage seems to consistently cause NetSurf to crash in box_coords()
Last three crash lines from stack trace:
8.Files:Projects/netsurf_svn/netsurf> a2l NetSurf-Cairo 9ed58
8.Files:Projects/netsurf_svn/netsurf> a2l NetSurf-Cairo b11e4
8.Files:Projects/netsurf_svn/netsurf> a2l NetSurf-Cairo 54274
may a user with RISC OS can post time values too.
this are netsurf speed values between 68k 2.7 SDL netsurf and OS4 2.7 netsurf on a SAM 667 MHZ.
newest OS4 and a Pegasos 1 GHZ OS4
more stand here in earlier posts.its german
the test site for time test was www.osnews.com
maybe a user with a risc OS machine can do the test, to see if SDL is fastest possible speed.
a classic amiga is a very slow system, and if OS4 netsurf have no speedbrake somewhere, a SAM or a
Peg should get at least same sec on virtual 100 MHZ.
The OS4 SAM and Pegasos values and 68040/40 netsurf values are from cha05e90.a User who like OS4.so
its no OS4 bashing result possible.only too fast OS4 values are maybe possible ;-)
100 MHZ line mean the values is calculate to a 100 MHZ CPU, to make it more easy possible, to
compare performance /MHZ.less time is better.you can see that on OS4 performance /100 MHZ is more
than 3* slower as on netsurf SDL 68k.
because the 1 GHZ G4 in compare to 667 MHZ SAM is 2.3* faster with netsurf it show that inet access
is no important speed brake.also the BPPC 060/50 mhz values are from a diffrent user, values are
simular, so diffrent
SDL netsurf 68k
BLIZZARD 2040 68040/40 MHZ
init load 35.10 sec reload 28.1 sec
100 MHZ init load 14.04 sec reload 11.24 sec
amiga OS 3.1 A3000-PPC PHASE5 68060 50 MHZ 128MB
init load 23.8 sec reload 17.5 sec
100 MHZ init load 11.9 sec reload 8.75 sec
BPPC 060/50 mhz und Bvision mit 800x600x16 Screen
init load 24.4 sec reload 18.8 sec
100 MHZ init load 12.2 sec reload 9.4 sec
SAM 667 MHZ OS4.x
init load 8.4 sec reload 5.0 sec
100 MHZ init load 56 sec reload 33.35 sec
Pegasos 1 GHZ G4 OS4.x
init load 4.1 sec reload 2.1 sec
100 MHZ init load 41 sec reload 21 sec