* Built the current versions of libcairo and libpixman-1 as static link libraries, with the static libraries OWB works on AmigaOS 4.0 again.
I assume these are built with newlib, right?
Of course.
Quote:
If so could you upload them to OS4Depot? I tried building them a while back but I must have done something wrong because the program I compiled with them just crashed immediately (I didn't have this problem with Andrea's port).
I didn't have to port anything, for both it was just configure && gmake. It's an incomplete version, I disabled everything not required by OWB (PDF, PostScript, etc.), it doesn't include the amiga bitmap surfaces of the AmigaOS 4.1 Cairo and I only built static link libraries, no shared objects, but if that's no problem I can upload the libraries and includes.
Very nice version! ... also for some reason earlier versions used 90-100% C PU when the "SAM" text at this page was showed (if I scrolled down to hide them it went down). It doesn't get that high anymore...
Besides is that normal and has it happened to anyone else?
Great work! Now it doesn't crash on starup anymore (me touches wood). Huge thanks!
Edited by Jack on 2008/11/23 0:58:52
"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
I also encountered this problem as well. I want to use a simple html file on my system as my "homepage", rather than accessing amigans.net or any other website thousands of kilometers away from where I live.
HOME=file:///dh0/owb/myfile.html Has worked fine with previous versions of OWB.
OWB 2.15 seems to just want "file:" to be assigned to something ... it doesn't seem to care where. Even ramdisk works.
Temporary fix .... I added the following to my user-startup file ...
Very nice version! ... also for some reason earlier versions used 90-100% C PU when the "SAM" text at this page was showed (if I scrolled down to hide them it went down). It doesn't get that high anymore...
Besides is that normal and has it happened to anyone else?
Same here, noticed the cpu load drop right away. from average of about 75% to something like 40%.
About file downloads: a menu attahced to a link or even shift-click or right click to copy url to the clipboard would be nice intermediate solution.
Very nice version indeed. First usable OWB here, and very usable! I think it is going to replace awb here, Even the bank's site works here, including almost correct rendering of Hebrew text (managed to pass the login, but due to malfunction on their side couldn't perform no queries)
Jack
"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
It seems a bit faster and smoother now. I noticed the screen shots on the OWB web page are of the first version which had the built in address book, is this function going to return at some point rather than using a limited external program?
Has anyone who has use OWB on facebook tried to use the chat system? as I have been able to open a window and type but when I press return to enter the text nothing happens.
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.
Never tried any versions of owb cos of slow,not too good in my thinking. But have problems with ib crashes,so i thought i'd give it a try. Must say igot very impressed. Is much faster now than i can remember from last time i tried. And no crashes yet. Even works where i didn't expect it to. Very good work.
Thank you vey much, this version is a lot faster and even more usable, now i have 4 pages open and tunenet running and everything is smooth, the only thing that it miss, to be a fully browser is the download option..
@jorg i have experienced a system hangup when (slowly) dragging vertical scrollbar several times. i wasnt able to observe more closely what leads to the crash. my system is basically a4k with csppc, mediator and voodoo if that is of any importance. other than that there is great improvement in speed, function and stability, the owb is becomming usable as first choice browser on os4 the way i see it. only that memory thirst worries me somehow. wouldnt that make sense to implement some kind of privately managed page file like clarissa or photoshop are using?
?h: havnt read the thread closely. i think my prob is the same as voodoo and k-l have reported