Stendhal code design: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
imported>Durkham No edit summary |
imported>Durkham |
||
| Line 1: | Line 1: | ||
== Client == |
== Client == |
||
==== Issues ==== |
|||
* The client side of current stendhal implementation lacks of thread handling even graphic code like draw is done in main. |
|||
* The login window is never released until end of game. |
|||
* All handling of changes is done by polling rather than be pushing. |
|||
:The information already given by the way marauroa handles changes is ignored and the values are retrieved from the updated underlying object. |
|||
:A different way of reacting to changes in rpobject is shown in the refactored BuddyPanel. |
|||
* The client code is a big monolith (same with server) |
|||
* To have all the client code restructured on client side, we need to tear down every single line of code and replace it. |
|||
* There are way to few tests for client side. |
|||
=== GUI === |
=== GUI === |
||