What can be done it create vector based image of web content, that way you can render only the visual parts, saving lots of mb of bitmap memory.
That would required implementing a new browser based on OWB, which wouldn't make any sense since it would be much more work than for example a FireFox3 port, and you'd still only have a WebCore browser with which much less sites work, without an email client (with a FireFox port you'd get Thunderbird as well), and with much more bugs, for example the WebCore based KDE4 Konqueror has at least some of the frame bugs OWB has as well.
By the way, I downloaded the LHA version from your site and installed it but the debug output is now back (normal?).
Ooops,?disabling stdio when started from Workbench was in the sources of the old memory allocator and I forgot to copy it to the new one. I've built a new version and uploaded it.
You may have Verdana, but I very much doubt you have a "Veranda" font installed Probably a typo on a webpage.
Missing fonts are no problem, as long as the DejaVu ones included in OS4 are complete.
Yes, you are right, I did a google for veranda.ttf, and came up with an entry (and downloadable file) veranda.ttf on sharesource.org, which states that veranda.ttf is a font based on Microsoft's verdana font in windows.
Yes, you are right, I did a google for veranda.ttf, and came up with an entry (and downloadable file) veranda.ttf on sharesource.org, which states that veranda.ttf is a font based on Microsoft's verdana font in windows.
Is it worth installing it?
Only if you want the page which uses it displayed exactely as it should be, and only if it's using this single font name instead of a list like "Veranda, Verdana, sans-serif".
Because OWB needs 512 MB RAM, or even more, with the public version of newlib.library. OWB 1.14 uses the one from the current beta versions, just statically linked into the OWB executable (it's still based on the same dlmalloc, just using different parameters).
Could this be "part" of the problem i have then? I mean, it's newlib which crashes afterall?
Quote:
The one I used in my previous versions of OWB was of course based on AmigaOS4 memory allocators as well, 17 ItemPools and 2 MemoryPools, and especially the ItemPools are very fast with a very low overhead, but because of the memory trashing bugs in OWB there were too much problems, with the dlmalloc based memory allocator the OWB bugs seem to cause much less crashes.
[/quote]
That "could" explain why i haven't had those strange crashes in earlier versions ... so, i think it would be best for me to wait for the next OS4 update and if it doesn't solve the issue, get back peskering you?
...and sorry for hijacking the thread, great work, joerg!
I'm probably being dense, but I've just installed 1.15, and am getting the old 'ELF Library' popup - "Required object is missing", and I can't remember how to fix it ! I did have 1.12 working fine(ish) before I updated.
Yet another update they are coming thick and fast now, great. I did have a problem with AmiUpdate this time it gave an error saying I need to connect to the internet first to updating, err hello if it wasn't connected to the internet how did it know there was an update? That one was as bad as the old M$ classic "could not find drivers for your modem device, would you like to connect to the internet to find drivers".
Luckly I was able to use the old fashioned way.
Still keep them coming.
Hmm has anyone else noticed a problem with text input and screen update, I am using OWB now and it goes a bit screwy if you scroll the screen in the middle of entering text. Edit: Just read some of the previous posts, I guess some of you have seen the problem. Oh well something to look forward to being fixed with the next update.
A1XE G4 800Mhz, 512Mb, Sil0680, ATI9200se 128Mb, Sounblaster Live & Catweazle Mk3 with SID chip +OS4.1. A4000 233MhzPPC/04025Mhz, 112Mb, CyberPPC, OS3.9 Other Amiga's A4000, A2000 A500+, A500 & various hardware. 15+ other retro machines.