Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: quenthal on August 21, 2006, 01:04:18 AM
-
Somewhere along the ride my Aweb had start using internal picture decoders for jpeg, gif etc. I didn't browse with Aweb that much so I didn't notice the difference in speed.
Now I changed them back in my Aweb 3.5.0.8 to use WarpOS-versions of jpeg and gidf aweb-plugins... well this caused only problems. With SnoopDos I managed to see that it was looking for awebplugin.library, which AFAIK is not a real file at all. At least I couldn't find it in any Aweb-packages I had. I tried with AWEB APL3.4 these plugins, they worked fine, and according to SnoopDOS it never even tried to open awebplugin.library.
In addition, it seems that compliled Aweb downloads after 3.4 has not been optimized for 060, only 020. So is there 060-version available somewhere, or is it required to complile it by myself? And even better, is there any way I could use PPC for aweb at all? IBrowse feels much faster. What is the difference between default and internal in Aweb for pictures? How to force it to use datatypes (I've WarpDTs).
-
Aweb can use datatypes for loading gif,jpeg and png pictures if you delete plugins or if you change config
make this:
go to aweb preferences and on the part of "viewers" select "internal" for each one of the images....jpeg,gif and png
now aweb will can use your ppc datatypes
anyways Ibrowse is better
bye, Laser
-
@Laser
Thanks, I'll try that.
-
Well, just tried internal-setting, and it still seems much slower than IBrowse when loading/showing pictures. This is strange, since both should now use datatypes. This is especially noticeable when page has multiple small pictures, like when replying at a.org, and in the reply.php page there is all those message icon and smilie selections. Aweb sloowly shows them one by one, while IBrowse is much more responsive, and quickly draws all those pictures.
Btw., what is difference between default and internal in Aweb?
-
ah I forget something
for gif images leave awebplugin instead internal
it is very faster anyways
cause datatypes not suppport gifanims..only gif images files so...
if you use datatypes for gif you can't see gifanims on websites that have gifanims
bye, Laser
-
internal and default are the same thing
(I believe) cause both functions use datatypes
bye
-
using datatypes in a browser, its a nonsense.
What you gain with PPC decoding, is eaten by context-switches.
Use Aweb (if you prefer....) with its plugins or IBrowse with its interna decoders.
ah... and don't use the old 3.4 PPC plugins on the newer 3.5.xx
-
@Framiga
If you have slow 68k (i.e. 040) it makes sense using PPC datatypes to decode images. Decoding large pictures is faster but small pictures are decoded little slower, though. And of course, progressive display is lost.
-
I have noticed that AWeb is just slow, either with 68k or PPC plugins or datatypes.
I now use Ibrowse 1.2 Free Aminet CD version with its own internal decoder and it is the fastest web i have ever seen on my amigas (with 030, 040 and 060). Even animated GIF are working.
I use AWeb only for SSL pages.
-
Never figured out how to wake up AWeb either, it seems like it only works when used in UAE or the OS4 version
Ibrowse and Voyager are the only usable 68k browsers I'm afraid.
-
AMIGAZ wrote:
Never figured out how to wake up AWeb either, it seems like it only works when used in UAE or the OS4 version
Naaaahhh - I'm still using the latest commercial AWeb version - on my A4kPPC with OS3.9/Wos16.1 (since 1998)...
AMIGAZ wrote:
Ibrowse and Voyager are the only usable 68k browsers I'm afraid.
Well - from my experiences AWeb is as well usable as the latest IBrowse version I also have.
-
Dandy wrote:
AMIGAZ wrote:
Never figured out how to wake up AWeb either, it seems like it only works when used in UAE or the OS4 version
Naaaahhh - I'm still using the latest commercial AWeb version - on my A4kPPC with OS3.9/Wos16.1 (since 1998)...
AMIGAZ wrote:
Ibrowse and Voyager are the only usable 68k browsers I'm afraid.
Well - from my experiences AWeb is as well usable as the latest IBrowse version I also have.
Well, it's usable but slow
If it's running as fast as Ibrowse in your Amiga can you please share your secret settings then? :-D
I have the fastest non overclocked Amiga you can get with the optimal parches/system setup but still Ibrowse is 2-3x faster than AWeb
-
Aweb is slow even on MOS for PowerUP with its PPC native version! go figure! Above all the latest 3.5.xx versions.... close to unusable with a 68K. The Aweb Team is doing a great job but with AmigaNG platforms as target
-
AMIGAZ wrote:
...
AMIGAZ wrote:
Ibrowse and Voyager are the only usable 68k browsers I'm afraid.
Well - from my experiences AWeb is as well usable as the latest IBrowse version I also have.
Well, it's usable but slow
If it's running as fast as Ibrowse in your Amiga can you please share your secret settings then? :-D
[/quote]
Note that I said "its as usable as Ibrowse" - not "it's running as fast as Ibrowse".
Maybe the speed-difference only becomes obvious if you have a fast (broadband) internet connection - and with a 56k modem (like I have) you can't see/feel the difference?