Jump to content

Recommended Posts

  • 3 weeks later...
Posted

Can't understand why you are attacking this guy, even if his code is shitty you cant stop him from learning/coding/sharing his work. 

 

give this guy a motivation to keep learning, and dont cut off his wings, all of you were on his coding level once upon.

Posted (edited)

HTMs are good because of HtmCache, which is caching htm info. Understand than once read at least once, it is cached and then content can be retrieved way faster. It also avoids to generate objects, cause atm you build one StringBuilder each time you access it (well at least you didn't use String concatenation, which is a really good point). Tbh as you use dynamic data you still have to build that StringBuilder anyway, so in that case the performance hit is probably low (you still avoid to append though).

 

HTM is also way easier to manage, a simple //reload htm is enough to see direct changes (as saif Elfo, flexibility/readability).

 

------------

  • You should use "if / else if" instead of "if / if", because atm you are testing each condition, no matter if you already reached one successfully.
  • The try catch blocks got no uses. The only thing to catch is basically the split && Integer.parseInt() of command.
  • The override of onAction doesn't seem useful at all. You probably can use overidden showChat.

Except the points above, the code seems ok.

Edited by Tryskell

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



×
×
  • Create New...