🚀 go-pugleaf

Ken:

Josh is mostly correct <g>.

Actually, with the exception of JBuilder 3.0 Solaris (first all-java edition) and
3.5, JBuilder has used the version of AppletViewer present in the JDK used by your
project.  There was a brief hiatus during the port where AppletTestBed was the only
option (hence the problems when trying to run JFC based applets with JDK 1.2), but
that was rectified in JB4.

In all cases, however, AppletViewer is a waste of time for real testing (in or out
of the IDE) once you've got your files laid out.  The main reason being that none of
the Browsers have implemented their Applet support to match AppletViewer.  To avoid
chasing ghosts, the best advice I can give you is to compile your classes into your
staging server location and run from the Browser(s) you need to support.  Once you
are satisfied, archive the classes into whichever archive type satisfies all your
clients, do another quick round of testing and then move the applet from staging to
production.

Since none of the Browsers supports JFC in any real way without the Plugin and each
Browser still has it's own quirks even when using the Plugin, most of this work
really has to be done outside the IDE.  For things like popups you'll inherit all of
the base JFC bugs for Applications *and* get the added benefit of some painting
decisions made for you by Netscape and Microsoft.

A quick thought, though, is that your popups are happening just fine but that there
is a heavyweight component in your UI that is masking your ability to see them.
Some quick diagnostic printlns would tell you if the code fragment is at least being
hit.

-Rich

Ken Warner wrote:

> Absolutly correct ... I won't be using the applet viewer to run the
> deployed applet.
>
> Anyway, I'm told by reliable sources that JBuilder doesn't use the appletviewer.
>
>      You might try posting the the Sun forums.  The appletviewer has
>      nothing
>      to do with JBuilder.
>
>      -Josh
>
> However, I may want to debug a custom component where I override
> the standard tooltips stuff and make my own tooltips stuff.  And then
> I'll be using whatever JBuilder uses to run the applet as I go through
> the edit-run-debug cycle.  And for that reason I need to know that
> when I'm running my applet and not seeing tooltips, it isn't my fault.
>
> I'm just trying to get my ducks lined up so that I don't chase ghosts.
>
> Rich Wilkman wrote:
>
> > Ken:
> >
> > Probably not, but it's really irrelevant because in the real world you won't
> > be using AppletViewer to run the Applet.
> >
> > -Rich
> >
> > Ken Warner wrote:
> >
> > > Hi,
> > >
> > > Had to repost this again and use twice the bandwidth because I violated
> > > the sacred rule against
> > > crossposting and my previous message was cancelled by the news group
> > > Gray Council.
> > >
> > > I have a Swing applet and I set the tool tip text for a component.  Then
> > >
> > > I test it by running it from the IDE and it runs in the applet viewer.
> > > But
> > > when I hover the mouse over the component, the tool tip doesn't show.
> > >
> > > Does the appletviewer not show tooltips?
> > >
> > > Environment: JBuilder Pro 4.0; WinNT 4.
> > >
> > > --
> > > Ken Warner
>
> --
> Ken Warner