> Is there a way for me to extend BrowserApplicationContext.HostApplet? and > override its methods? and in that way could use it as my current loader > adding its functionality?
It may be OK to make HostApplet non-final. Do you have the Pivot source code? You could prototype this change and see it it works. > just another question... I don't know why the repaint method is not working, > what will be the correct way of using it? >>> // window.paint(window.getGraphics()); As an app developer, you shouldn't often need to call paint() directly. The system ensures that paint() is called for you when you call repaint(), which marks a region of the screen for update. Multiple repaint() calls may be consolidated - however, this is all handled by AWT. Pivot just hooks into the Java2D paint system. If you wanted to draw a component (or some other Pivot visual) to a background image or something similar, you might call paint() yourself, but otherwise you should not need to do it. Again, I suspect that the reason your paints are not working has something to do with the fact that you are loading the Pivot applet from within another applet. Unfortunately, applets are pretty finicky as it is - this just adds another variable, and I have no idea what the other applet might be doing under the hood.
