up

The purpose of this page is to present how the game visualizer will be refactored, along with a description of technologies used and other important information.

TBA

With the most part of Power TAC project being moved out of Grails and porting to Spring, major technology for Visualizer development will most likely be Spring/Java as well. Main assumption used for choosing technology is possibility for future easier integration with the PowerTAC server.

The basic idea of Visualizer refactoring are expressed with the following bullets:

• Fully reuse of Visualizer's web design: Most of the HTML and CSS can and will be easily ported into the Spring.

• Getting rid of periodic page refresh and using Ajax instead for better user experience.

• Web design update to meet Power TAC's requirements.

• Application logic based on Grails will not be refactored, but some of the ideas might be reused (such as MVC architecture, use of services etc.).

• We are expecting an interface/proxy on the server-side with which Visualizer will be able to communicate with the Power TAC server. Dummy interface (simple messeage generator) for interaction between server and Visualizer would be much appreciated.

If you would like to post your own ideas for Visualizer or things that you did not like in the old Visualizer, please be free to reply in the following thread: Visualizer Refactoring at PowerTAC Developers.

Additional information will be added as soon as possible.