On Amigans with Ibrowse with my new X1000

...and this is an 68k program? Are you kidding me? It has lightning speed! It looks like s-h-i-t-e, but a lightning one at that.... Amazing!

Well, OWB is pretty fast too, but more attractive...

All browsers would be fast if websites were not bloated with css and eye candy.

Well the slowdown it's now related to the CSS at all (without CSS you will browse the net like 1990) ..

It is very confotable surf web with any modern amiga. :)

Only browse wich isn't very fast is timberwolf.

Netsurf is also very fast.

So, why are web pages, 200K AND MUCH BIGGER in size then? No WONDER is so blasted SLOW!

I am not talking about pictures, audio and video, here, I mean the source itself.

The page that I'm writing this message in is ONLY 57344 bytes of HTML code.

I went to zap2it.com and viewed, then highlight, copy and pasted and got 61,605 bytes.

I then tried yahoo.com front page, "view source code" in google chrome.... and windows and ALL CONNECTED TO IT being TRASH AND GARBAGE, I tried to do highlighting of the source and it is SOOOOOO long that the computer, 3.4 GHz quad core, made google chrome throw up the "page unresponsive" warning TWELVE times, AND it took OVER FIFTEEN MINUTES!!!!! to complete the HIGHLIGHTING OF TEXT part!!!!!!!!!!! I'll leave it to you to try it and see what I saw as the size the html was.


And it is NOT that easy to code the stuff, either.

@Athiest

I tried uk.yahoo.com in owb and did a "Save as HTML..." from the project menu and got a 230,169 byte file, then tested some others...

hebus.org 17,470
f2s webmail 26,117
Hyperion forum 35,508
Amigaworld 59,510
Yahoo webmail 82,567
Amigakit 87,776,
play.com 99,898
bbc.co.uk 107,662
Amazon.co.uk 247,033

hebus is blown away by heavy gfx usage.
Doesn't take long to eat up your bandwidth if you're on a limited amount like I am :(

Then there's other nastyness you have to be careful with... For example hebus.org is a very good wallpaper site. it uses css heavily so looks better in muiowb but DON'T USE IT. use IBrowse instead. I found a nice wallpaper, chose 1980x1020 to download and it showed it on screen after taking quite a long time... I selected 'save image as' and muiowb didn't save the copy in ram, but downloaded it again which doubles the bandwidth used, the pic was 7.5mb btw...
If you use IBrowse the display is ugly as you would expect but it does save the image in ram after checking it hasn't changed.

USE IBROWSE FOR GFX DOWNLOADS AND HALF YOUR BANDWIDTH

Quote:

NetSurf works perfectly on that site - displays it correctly and doesn't re-download images.

Note that a CSS browser is going to eat up more bandwidth, as non-CSS browsers don't have to download the CSS files, whereas CSS ones do.

I find timberwolf to be quite usable on the x1000.

Looks like someone's just now noticed the problem.

http://gadgets.ndtv.com/apps/news/goo ... chrome-for-android-337896

Congratulations on your X1000.
There is nothing faster than IBrowse,
but MUI-OWB gives a good display and isn't too slow.

MUI OWB Video

@Severin

With OWB, there's no file cache, so the image is only stored in memory cache, in raw format, and it has to be downloaded again (or encoded).

On the other hand, you can use "copy image" context menu item, which copies the content in IFF format to the clipboard, without redownloading anything.

@ FAB

If an update to MuiOWB is ever released for OS4.1 would it be possible to add a "file cache" ability?

Thanks,

BCP
Indianapolis, IN USA

@Fab
Quote:

Saving clips:0 to wherever:whatever.iff is an option I suppose but you do lose the filename and format :(