History: 3.27 (7.5.2010) - Updated to SVN revision 1446. - Updated libcurl (7.20.1), libcairo (1.8.10), libpixman (0.18.0), libxslt (1.1.26) and libxml2 (2.7.7). - Disabled SVG support in OWB and rarely used charsets in ICU, that way OWB needs about 8 MB less RAM which should help a little on systems with very few RAM like classic Amigas. - Fixed some of the memory leaks in the new OWB revision. - Fixed bugs.os4depot.net issues #87, #167, #168, #171, #293, #306, #323, #324, #361, #399, #420, #430, #443, #445, #447, #454, #455, #459, #460, #463, #464 and #467. - Added undo and redo edit menu items.
3.26 (28.4.2010) - Fixed another libpthread.a problem on AmigaOS 4.0.
Thanks for that new version but... Why disable SVG at all? Wasnt better to can choose that with an option? I use it... :P
PS Any help on rendering with the new cairo from AOS4.x Update2? PPS Any chnche to get the loading bar on bottom right again? was really ugly on top imho...
Anything that uses Cairo functions which have been hardware accelerated will automatically get hardware acceleration.
Wrong, only software using the AmigaOS bitmap surfaces can get hardware acceleration. And of course only software which uses the AmigaOS 4.1 libcairo.so at all, OWB doesn't.
As written in the changelog to save RAM, it's a feature next to nobody needs.
Quote:
Wasnt better to can choose that with an option?
An option to disable SVG would be completely pointless since the SVG code would still be in the much larger OWB executable.
Quote:
I use it... :P
Keep an old version of OWB for the very rare cases for which you need it, or wait until TimberWolf is released and use that instead for pages which need SVG.
I think that the charsets you disabled have broken greek text support, try www.in.gr for example, it's all unreadable now. I copied the older one from 3.25 and I'm working ok now, but maybe you should check it out again, maybe you removed something that you didn't intend to.
Well how about compling two different release, one without SVG for slower machines and the other one with SVG enabled ?
AFAIK this was the Fab's approach when he release two different version with or without SVG, one for Efika and the other one for all the other MorphOS solution
~Yes I am a Kiwi, No, I did not appear as an extra in 'Lord of the Rings'~ 1x AmigaOne X5000 2.0GHz 2gM RadeonR9280X AOS4.x 3x AmigaOne X1000 1.8GHz 2gM RadeonHD7970 AOS4.x
As written in the changelog to save RAM, it's a feature next to nobody needs.
Quote:
Wasnt better to can choose that with an option?
An option to disable SVG would be completely pointless since the SVG code would still be in the much larger OWB executable.
Is it possible to add SVG support in separate file and only if enabled to load it? This way both camps (SVG and non-SVG) will be happy. And the SVG enabling people will know the real cost of enabling SVG (less free RAM).