Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: Johan Samuelsson on February 03, 2003, 05:47:26 PM
-
Hi there databoys!
I am trying out the new IB23 demo.
The first page i tried was amiga.org, and DOOOH there it was, a big fat ugly error requester.
"cant open javascript.library" - is there anyone else here that have/are experiencing the same thing?...
-
maybe i was a bit too fast on reporting the problem.. right after that i tried another problem site.. (hotmail) and ibrowse crashed..
but after the reboot, everything seems to be fine. no error req at amiga.org anymore!..
i am gonna give hotmail another try now! =)
-
The first page i tried was amiga.org, and DOOOH there it was, a big fat ugly error requester.
"cant open javascript.library" - is there anyone else here that have/are experiencing the same thing?...
Nope.. I have yet to see that error on any site.
-
Hi, I'm using the Ibrowse demo via winua with no problems viewing amiga.org.But it comes up with a java script eror when trying to post this reply.
(message too long.)
-
I'm 100% sure you never flushed the old javascript library. Please, investigate such errors a bit more before coming to the conclusion that IB won't work with Amiga.org. That helps avoiding a lot of misunderstandings.
Sincerely,
David Burström, IB team
-
I installed 2.3 a couple days ago and
I have not been getting errors 8-)
:python:
-
IB2.3 works almost flawlessly with Amiga.org. As Meldon said, maybe you had the 2.2 javascript library still in memory.
-
Well, the only issue I had was that JPG's didn't display. But that's a DT issue for me, I think.
-
No problems for me at all when using iBrowse v2.3 on the Amiga.org site. Works wonderfully on a lot more sites than 2.2 did.
@ Herewegoagain,
Why aren't you using iBrowse's internal image decoders??
-
The main reason I use Datatypes is because they are faster, being WarpOS datatypes, The only internal decoder I use is the Gif decoder because that animates them :-)
-
@ Ryu,
Ah. That makes sense. Didn't even think of it. Thanks.
-
Been using the IB demo for a couple of days now, and can't report anything negative about it. If this kepps up for a couple more days, I'll purchase the keyfile for the full version. Looks really good so far. :-)
-
It's a known issue with IB2.3 after you have ugraded from 2.2 without flushing the libraries or doing the recommended reboot. I saw it posted on the IB mailing list as well as the fix (just reboot to flush the libraries or use a flushlibs tool). If there are any other problems with IB2.3 when viewing Amiga.org which were not present in IB2.2 and not reproducable on any other web sites, let m know so I can look into the problem.
:pint:
-
I haven't really been having any problems with IBrowse and WinUAE. Other than the wierd;
when I'm either previewing or posting a reply/post.
Works fine on my real Amiga.
-
I don't know if Ibrowse 2.3 is a good release...but now i hope a quickly converstion of Mozilla or Opera....this is my secret dream ! :-)
samo79
An italian Amiga fun
http://digilander.libero.it/samo79
-
I had the same Problem in an earlier post...
( you must reboot or use the flushlibs command after install)
I use IBrowse since V 1.02
Yes the new 2.3 is really great (If you're don't registered it... Do it now !
-
[quote@ Herewegoagain,
Why aren't you using iBrowse's internal image decoders?? [/quote]
Well, that's how I started out by using IB's internal viewers. But it only showed broken link images for all jpg's. Gif's and png's showed just fine. So I looked at the Ibrowse folder and looked around until I found the components for the internal viewer (don't remember where they were now) but all were listed except for jpg. So I assumed it had something to do with the recent flurry over the jpg standard that it was not also included. That's why I switched it to external viewer, and pointed it to the jpg datatype in my devs folder. But that still didn't work.
Then I went to Aminet and ftp'd the akJPG datatype but everytime I lha'd it the file had corrupt data at the first half. I even pulled it down again, but the same thing happened. By that point I just gave up.
-
Well, that's how I started out by using IB's internal viewers. But it only showed broken link images for all jpg's. Gif's and png's showed just fine. So I looked at the Ibrowse folder and looked around until I found the components for the internal viewer (don't remember where they were now) but all were listed except for jpg. So I assumed it had something to do with the recent flurry over the jpg standard that it was not also included. That's why I switched it to external viewer, and pointed it to the jpg datatype in my devs folder. But that still didn't work.
IBrowse 2.3 does have an external JPEG decoder. In the codecs directory, you should find the following files:
gif.codec
imagedecode.module
jpeg.codec
png.codec
xbm.codec
The external viewers aren't intended for rendering of inline elements.
-
I haven't really been having any problems with IBrowse and WinUAE. Other than the wierd;
when I'm either previewing or posting a reply/post.
Works fine on my real Amiga.
Which version of the javascript.library did you install on UAE? I would suggest the 020 (non-fpu) version.
-
IBrowse 2.3 does have an external JPEG decoder. In the codecs directory, you should find the following files:
gif.codec
imagedecode.module
jpeg.codec
png.codec
xbm.codec
The external viewers aren't intended for rendering of inline elements.
Interesting. I had the same problem with the original settings to use internal viewers. It's funny, because I was thinking that there were only 4 files in the codec drawer when I looked, and you listing the files show there should be 5. I'll check later when I get home to see. But I never saw the jpg.codec, that's specifically what I went in there looking to find. And it must have not been there because all pages with jpg's on them (ala the top Aorg banner) always showed a broken image. That's the only reason I tried an external viewer to start with.
-
@ryu
The main reason I use Datatypes is because they are faster, being WarpOS datatypes
Really? Here using datatypes makes things a lot slower, and I have WOS datatypes too. They're faster for big pics, sure, but not in general. Especially sites like Amiga.org's comment entry page that has lots of small smiley images - that really slows to a crawl. I keep to the internal codecs.