vit-svoboda / svg-engine Goto Github PK

• Cache map data.
• Redraw only what changed.

• Server should send small rectangles of map data with each update. Size of the screen or smaller.
• Client has to render only what can be visible on the screen no matter what he recieves from the server.

Maybe they will be faster than the animated tiles. At the end of the day just another option of tile content for the client to create.

• Decide whether tiles should contain vector graphic or bitmap sprite or both.
• Decide whether loading original OpenTTD sprites from *.grf packages should be implemented.
• Based on these decisions create various tile types and implement logic to display them based on map data.

Say we have a tile and place a building on that tile. Now we place second level on that building.

• The second store has to look right.
• Refreshing ground in the background must not cover the second store.

• Design an API for passing game logic code through the engine to UI events.
• Implement some example UI events:
  • Scroll through the map.
  • Zoom?
  • Build action on tile.
  • Unit travel from A to B.

Engine has to support obtaining "full information" of an object. Normally only the information necessary for the display is returned but when user say clicks on the tile, he gets other information like value, price, etc.

• Server communication
• Content creation
• UI handling

Nothing too complicated

• Hills
• Lakes

When only couple tiles changed, server returns only changed tiles instead of the full rectangle.
Engine has to be ready for this kind of response.