Seems pretty good actually. Apart from some omissions - like explaining why you overrode update(): the para looks self-contradicting without the explanation. Also some errors (stuff which I suspect you probably understand better now if you were rewriting this).
Would you (or someone else who's been doing applet coding recently) consider updating this a bit, making a few corrections, and then I'll put it on JGF.
Which makes me realise: if I'm going to post articles on JGF, I need a pool of volunteer article-reviewers, who can quickly read through them before they get published, and check for places where things are incorrectly described, or something is done wrong.
E.g. in a swing tutorial, if I saw *any* use of
I know it's wrong (unless there's a para explaining why the author is breaking Swing deliberately - for Swing, you're always supposed to use paintComponent( Graphics g ) where in AWT you would have used paint(...)).
I can do this kind of review myself for a considerable number of the libraries, but there are big areas where I wouldn't recognize such mistakes (especially with any of the techs I don't use, like ODE).
Reviewing articles is a LOT less work than writing them (by a factor of about 10-20) but is equally helpful in getting articles on the web for other peopl to use. So, if you have the skills but not the time for writing articles, please could you help with this? Email me or message me, saying what areas (e.g. "swing, JOGL, OpenGL") you feel capable of reviewing articles for.