WWT_WC_Architecture
- UI Layer controls user interface interaction, menus, display, and so forth.
- MIDI Control handles I/O with MIDI devices and other input devices such as the XBox 360 controller. Integrates communication with the Layer Manager, Settings, and the Space-Time controller.
- Layer Control API (LCAPI) enables programmatic control over exchanging data with WWT. This can include 2D and 3D image data, and time series data. For more details, see WWT Layer Control API.
- Layer Manager defines the scene graph hierarchy, which determines how all elements will be displayed.
- Core Display iterates through the Layer Manager hierarchy to get the scene graph for rendering. Nearly all of the rendering code goes through the Layer Manager.
- Space-Time Controller handles all aspects of temporal and spatial location, providing consistent per-frame time and location from which the observation location is derived. Note that light travel time is not taken into account from the camera viewpoint.
- Settings handles user preferences for a variety of things including MIDI controllers, constellation figures, image quality, zoom speed, network caching, and so on.
- Net Control controls multiple instances of WWT, as used in planetarium projection setups. The master server uses TCP multicast to communicate with projector servers over the local network.
- WorldWide Telescope Markup Language (WTML) loads and manages WTML files, which contain the imagery catalogs for WWT. You can search within these catalog files.
- Tours and Timelines handles all interaction with tours and timelines. Interaction is controlled by tour/timeline data, in contrast to interactive mode where the user controls the interaction.
- Web Server enables the WorldWide Telescope client to communicate with other WWT instances, and receive LCAPI commands and data.
- Output Rendering generates all output file formats (spherical, warp, stereo, blend).