🚀 go-pugleaf

In article <3621.6658T1133T1717@stack.urc.tue.nl> elvis@stack.urc.tue.nl (Mark van der Molen) writes:
> On 25-Mar-96 02:44:35  Lars Janssen (lars@mistral.co.uk) wrote :
> 
> >AWEB
> >  - Opens multiple network connections, to help make the most of your
> >    available bandwidth, especially with slower sites. Displays pages
> >    as they download.
> 
> Ibrowse does this too

Nowhere near as nice.

> Scrolling is as slow, and sometimes even slower than ibrowse(both running on a
> 64 color screen)

AWeb is much faster on my system, which is a cybergfx setup, 8 bit workbench.
Your 64 color screen is a native chipset screenmode, I presume?  That's gonna
be slow anyway.

> The aweb gui uses BOOPSI, because MUI would be too slow.Using both Ibrowse and
> Aweb I find Aweb's screen redraw is much slower than Ibrowse's.So what's the
> advantage of BOOPSI ?
> On the other hand in mui you can select to use BOOPSI images too.Getting
> Ibrowse to run on it's own screen is dead simple if you know how to use mui.
> But i think it would be more difficult if you have just started using MUI,
> then ppl have to learn using Ibrowse as well as MUI.

MUI is BOOPSI too.  Although it's classes are specific to MUI and the context in
which they run causes MUI apps to "stall" occasionally.  Normal Intuition BOOPSI
runs on a context independant of the app.  Normal Intuition BOOPSI classes can
be updating themselves despite what the program is doing.  For example, and this
is probably a bad one but nevertheless, AWeb and IBrowse both crash.  If you resize
AWeb's window, the gadgets will still resize.  If you resize IBrowse's window, the
gadgets will just be dead.  Even if AWeb itself is dead, the gadgets are still 
"alive" unlike the MUI gadgets of IBrowse which will be dead because the app is
dead.

As far as MUI allowing you to select BOOPSI imagery, that's totally unrelated.  

> Ibrowse has been very stable here, only the veryfirst release version crashed
> all the time

IBrowse has never worked for me other than local browsing, because their
AS225 support apparently breaks under INet-225 (every other AS225 program
I've seen works fine under INet, including AMosaic by essentially the same
team.)  Although in local browsing, IBrowse worked flawlessly for me.

Dan