logo

TheoWorlds Builder SDK v2 Documentation

Building applications using TIE

1. Creating your own applications

You can create your own applications using Theo Isometric Engine (TIE). The SDK code is structured in a way that makes it easy to separate the engine code from the UI code.

As a first step, you can check the Simple Application built with TIE.

The two full-featured applications that come with this SDK: TheoChat v2 and Theo MapEditor v2 are examples of applications that use TIE.

Use those applications as a reference and apply the same framework to your own applications.

2. TheoChat v2 UML

Below is the UML scheme of TheoChat v2 application, showing all the classes and the connections between them:

TheoChat UML

Description:

  • (1) TheoApp is the base class that any Theo application should inherit from. It contains all the main Theo application functions.
  • (2) TheoChat is the main application class and contains functions related to this particular application.
  • (3) TheoChatUI is the class that manages all the UI functions of a particular application. It lets you separate the application logic from the UI logic.
  • (4) ITheoUI is an interface class that every UI class has to implement.
  • (5) TIE is a set of classes that form together the core isometric engine. Read more about its structure on Theo Isometric Engine™ page.
  • (6) ServerES or (7) ServerSF or (8) ServerLC are classes that implement the communication logic between Theo application and a socket server application - Electroserver or SmartFox Server. The ServerLC works with Local Connection class and can be used to test Theo application without a socket server. Such a separation allows to easily switch between socket servers or even add the support of other socket servers.
  • (9) Server is the class that any server communication class should inherit from - it contains all the common functions.

Theo MapEditor v2 uses the same structure.

 

Last updated: September 16, 2009