IBrowse 2.3 & Amiga.org = BAD

[samo79]

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

[duesi]

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 !

[Herewegoagain]

[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.

[futaura]

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.

[futaura]

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.

[Herewegoagain]

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.

[KennyR]

@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.