Architecture

Starez is divided into two parts. A client and a (master-)server. The client connects to the server (preferably with an SSL connection), and communicates with the server according to the Starez protocol. The Starez master-server in it's turn uses other (web)servers for hosting content(such as downloads, and the game-information XML files).

Client

File structure

  • /: The root directory of Starez. Note that this is not the absolute root, but the root of the Starez directory, which is probably located at /usr/local/share/starez. This directory also contains files such as RunTest.py to run the tests located in the tests directory and a doxygen config file.
  • /bin: Contains the python source files
  • /icons: Obviously this directory contains the icons the client uses
  • /tests: This directory contains unit- and doctests.
  • /data: The data directory contains text-files, such as a XML file for loading the menu, a file with a list of master servers a file with all installed games etc.
  • /skins: This directory contains skins for the Starez client. You can add your own skins(a starez skin is the same as a gnome-skin), by creating a directory with the name of the skin in the skins directory. Your directory should contain a gtkrc file and all other related resources for the skin.
  • /temp: The temp directory should contain all the temporary files, such as downloads. When a download is only partly finished, it will be placed into the temp directory. After the game is installed, it will be removed again.
  • /locale: Directory containing translation files.
  • /log: Directory containing log-files.
  • ~/.starez: This is a hidden directory created in the user's home directory. This directory contains user-specific files such as the preferences.

Server

 
developer/architecture.txt · Last modified: 2008/04/21 19:17 by 81.71.182.26
 
Recent changes RSS feed Creative Commons License Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki