andpp/mopidy
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

docs: Include mixers in the class instantiation and usage diagram

Browse Source
This commit is contained in:
Stein Magnus Jodal 2010-03-08 20:49:55 +01:00
parent 38992bcf9c
commit d774ad90fb
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/development.rst
View File

@ -134,17 +134,22 @@ features we wished was there:
Class instantiation and usage
=============================
The following diagram shows how Mopidy with the despotify backend is wired
together. The gray nodes are part of external dependencies, and not Mopidy.
The following diagram shows how Mopidy with the despotify backend and ALSA
mixer is wired together. The gray nodes are part of external dependencies, and
not Mopidy.
.. digraph:: class_instantiation_and_usage
"spytify" [ color="gray" ]
"despotify" [ color="gray" ]
"alsaaudio" [ color="gray" ]
"__main__" -> "MpdServer" [ label="create 1" ]
"__main__" -> "AlsaMixer" [ label="create 1" ]
"__main__" -> "DespotifyBackend" [ label="create 1" ]
"MpdServer" -> "MpdSession" [ label="create 1 per client" ]
"MpdSession" -> "MpdHandler" [ label="pass MPD requests to" ]
"MpdHandler" -> "DespotifyBackend" [ label="use backend API" ]
"DespotifyBackend" -> "spytify" [ label="use Python wrapper" ]
"spytify" -> "despotify" [ label="use C library" ]
"DespotifyBackend" -> "AlsaMixer" [ label="use mixer API" ]
"AlsaMixer" -> "alsaaudio" [ label="use Python library" ]