🚀 go-pugleaf

In article <jasonb.827996764@cs.uwa.edu.au> jasonb@cs.uwa.edu.au (Jason S Birch) writes:
>If AWeb put the image decoding at a lower priority itself (which is a
>reasonable thing to do, and even more desired if you're not running
>Executive -- using Gadtools and CA means that the buttons respond to
>your clicks immediately, but the whole thing still feels sluggish if

It wouldn't be sluggish if Executive didn't drop the priority.

>This raises an interesting point. The image processing and network
>downloading tasks are handled separately, but it appears the page
>layout is handled by the same task that handles user interface events.

An educated guess here, if you don't mind: It is equally good design
to keep all routines that directly affect a window in the task that is
responsible for a window. If the layout was done in another task, it
could easily get desynchronised with the window itself, and obviously
any results would be at best worthless.

>etc. I think IBrowse will still turn out to be the best overall,
>however, once a stable release version is on the market.

You'll find a lot of people have strong doubts of that ever
happening. In the meanwhile, if you think AWeb development has
stopped, you're mistaken.

-- 
Never underestimate the power of human stupidity.
| "Osma Ahvenlampi" <mailto:oa@iki.fi> <http://www.iki.fi/oa/> |
| Amiga&BeBox&ClassAct&Voodoo&ARTech cool stuff: I-Net225&AWeb |
                                                              --