Re: should I use java.awt.* only or also use javax.swing in applets?
On May 5, 7:34 am, steveh44 <steve_...@yahoo.com> wrote:
..When I looked at some applets, most seem to be based on Applet, not
JApplet.
Most applet examples were written in the 1990s when the MSVM
plagued browsers. We have come up with an MSVMicide in the mean
time.
Basically I am asking, if I want to make sure my applet run best and
on most browser, should I just stick to awt and not include any swing
stuff?
No. Applets (by which I mean both java.awt.Applet &
javax.swing.JApplet)
will always experience little quirks when appearing in this or that
micro-version of 'name your favorite UA here'.
If you program the code as a JApplet, you are likely to get lots of
help when something goes wrong. If you ask about an Applet, people
will either ignore the post (mostly because they've forgotten how AWT
components work) or advise you to update to a JApplet.
..I know if I extend JApplet I can still use awt classes and
methods if I want to.
Be very wary of mixing Swing & AWT. Java 7 promises to provide
effortless mixing of Swing & AWT. Otherwise expect problems with
any floating Swing GUI element that overlaps an AWT component (e.g.
menus, combo boxes, tool tips etc.).
----------------------------------------------------------
BTW - G'day to all the regulars! It seems like an eon since I last
delved into usenet.
--
Andrew Thompson
http://pscode.org/