🚀 go-pugleaf

Todd:

Not really.  Your browse will fetch all the <APPLETS> it finds them.  The
trick is to not stick all your code in the init() function.  Let the init()
function do the basics, like getting the components to the state that they
are presentable.  Do an Applet.show() at the end of init and put the guts
into the start() method, which is called after init().

You'll have to do some extra work to keep things cleaner though.  Some
browsers (netscape) call start() everytime you resize the browser.  You
gotta do some checking in your code to determing if you need to run the
start() mechanism again to protect against this.

For the non-Java stuff and having to wait....  All the browsers will let
you determine how to handle the time-intensive things like images.  You can
tell the browser to not load the images at all (until you click on them).
This gets the bulk of the information visible faster.  Of course, if you
have a site that depends on navigational bitmaps and other graphical
fru-fru with no textual backup then there's not much to be done.

-Rich

Todd Cary wrote:

> Beginners question:
>
> Rich -
>
> Is it possible to structure the html so one applet is fetched then some
> things are done so the user can interact with the page and then aonther
> applet is fetched?
>
> I notice that so many web pages (Java not present) make the user wait
> until everything is loaded before anything can be done.  Others put up
> enough so I can click on an area before all of the graphics and other
> features are present.
>
> Todd