Two suggestions

Suggestion one:
Try to let users learn to include their code 'readable', it means indented. e.g. using the bracket open CODE]
and bracket open /CODE] tag. Naturally replacing 'bracket open' by [
suggestion two:
Let a guru answer the problem of 'certifiying' applets!
I would like a complete example (to mimic later).
(See my posting in applets) and howmany people try doing things
which will not work without certification.
Have a nice day

Peter

Suggestion one -
The link to UBB code tags appears just lef to the edit box used to create new messages. People will have to just notice it! I tried diting all the messages to add code tags for sometime, but it turned out to be too much of an effort. I still do it if I have time.
Suggestion two -
What do you mean by certifying applets? Certifying as to whether it is written correctly? Some kind of a code review? And where are these applets that we are talking about? Who will submit them? I am a little

Nice to get an answer

An applet runs normally in a 'sandbox' meaning in principle that the applet runs only in JVM and can not acces files on the client computer (e.g.) but only files from the server.
Certifying (to my knowledge means) that one can manage somehow or other that an applet may be trusted to do things outside of the 'sandbox': access resources on the client computer or other things Java can do in principle and which are shut off in a
'normal' applet because of security reasons.
I hope that this clears a little bit the second part?
Greetings to you Atjeh, I will be very soon on hollidays and will
return here midst of august

Peter, I am going to move this thread to Applets forum to draw the attention of our learned Applet experts. Keep checking the answers and you will find more than what you asked for