posted 24 years ago
Hmmmmn.....I did this once but it was messy. I think you can just jar up all of the appropriate classes for both applets and then call say something like
I say that this gets messy because you'll get two applet threads running and weird things may result. A better solution might be to put the contents of the second applet into a Frame and have the first applet create a new Frame. If you do this, simply pass the first applet as a parameter so that you can use it for any applet specific functionality that you may require in the second applet. I hope this provides a few leads.
Sean