MythTV  master
Here is a list of all modules:
[detail level 123]
 Database Subsystem
 LCD Subsystem
 MythTV Network ProtocolThe MythTV backend process currently opens sockets for three different types of commands; a custom protocol (by default at port 6543), an HTML server (by default for the status, and other services under that, like < HREF=""> ), and a UPnP media server (several ports that I cannot remember right now that throw around lots of little bits of XML :-)
 MythTV Startup SequenceMost MythTV programs follow a common sequence:
 MythTV Language SupportThere are three sets of language translations in MythTV; source code translation, menus, and MythWeb
 QObject is dangerous for your healthQObject derived classes can be quite useful, they can send and receive signals, get keyboard events, translate strings into another language and use QTimers
 Profiling MythTVYou can use any sampling profiler to profile MythTV, the most popular GPL one is OProfile and this section tells you how to use it to profile MythTV. For Intel also makes VTune, AMD makes CodeAnalyst, and Apple makes Shark. These all work similarly to oprofile, so the MythTV portions are the same
 Testing hints and shortcutsThe internal video playback can be tested by the programs/mythavtest tool:
 MythTV Database SchemaHow everything is stored in the MySQL database
 MythTV LibrariesThe shared libraries that the code base is split up into
 HouseKeeperFramework for handling frequently run background tasks
 MThreadPoolFramework for managing threads
 Command Line ProcessingUtility responsible for processing arguments from the command line
 LIRC Subsystem
 Audio Subsystem
 Plugin Architecture
 MythTV Media Manager
 Recorder Subsystem
 A/V Player Subsystem
 Video Subsystem
 OSD Subsystem
 MythTV User Interface LibraryMythUI has multiple components
 MythUI Widget and theme handling
 MythUI Painters and Renderers
 MythUI Input handling
 The zwp_idle_inhibit_manager_v1 interfaceThis interface permits inhibiting the idle behavior such as screen blanking, locking, and screensaving. The client binds the idle manager globally, then creates idle-inhibitor objects for each surface
 The zwp_idle_inhibitor_v1 interfaceAn idle inhibitor prevents the output that the associated surface is visible on from being set to a state where it is not visually usable due to lack of user interaction (e.g. blanked, dimmed, locked, set to power save, etc.) Any screensaver processes are also blocked from displaying