| | 1 | {{{ |
|---|
| | 2 | #!html |
|---|
| | 3 | <h1 style="text-align: center; color: blue; font-size:3.0em">Welcome to Coherence</h1> |
|---|
| | 4 | }}} |
|---|
| | 5 | |
|---|
| | 6 | [[html(<div style="border: 3px solid #88ff88; background-color:#ddffdd; text-align: center">)]] |
|---|
| | 7 | -- Newsflash -- Stable version: [http://coherence.beebits.net/download/Coherence-0.6.6.1.tar.gz 0.6.6.1]. Development version: [http://coherence.beebits.net/wiki/WikiStart#Download 0.6.7 (svn)] |
|---|
| | 8 | [[html(</div>)]] |
|---|
| | 9 | |
|---|
| | 10 | [[TOC(heading=Content)]] |
|---|
| | 11 | |
|---|
| | 12 | [[BR]] |
|---|
| | 13 | [[BR]] |
|---|
| | 14 | |
|---|
| | 15 | == News == |
|---|
| | 16 | |
|---|
| | 17 | '' December 22, 2009'':: |
|---|
| | 18 | * Release of [changeset:1516 version 0.6.6.1 - the Red-Nosed Reindeer Reloaded] |
|---|
| | 19 | |
|---|
| | 20 | '' December 20, 2009'':: |
|---|
| | 21 | * Release of [changeset:1513 version 0.6.6 - the Red-Nosed Reindeer][[BR]] |
|---|
| | 22 | |
|---|
| | 23 | '' Oktober 2009'':: |
|---|
| | 24 | * ''[wiki:Sprints/Two Second Coherence/KDE sprint October 3/4 in Barcelona][[BR]] |
|---|
| | 25 | |
|---|
| | 26 | '' June 19, 2009'':: |
|---|
| | 27 | * [wiki:News/TropheesDuLibre Coherence Awarded "Special Jury Award" by 5th Annual Trophées du Libre] |
|---|
| | 28 | |
|---|
| | 29 | '' May 19, 2009'':: |
|---|
| | 30 | * Release [changeset:1272 version 0.2.2 - Let the Sunshine In -] of [wiki:UPnP-Inspector The Inspector] |
|---|
| | 31 | |
|---|
| | 32 | '' May 12, 2009'':: |
|---|
| | 33 | * Release of [changeset:1261 version 0.6.4 - Pont Mirabeau] |
|---|
| | 34 | |
|---|
| | 35 | '' April 23, 2009 '':: |
|---|
| | 36 | * Coherence has been announced as finalist in the media category of the [http://www.trophees-du-libre.org/content/blogcategory/24/69/lang,en/ Trophées du Libre] contest. |
|---|
| | 37 | The final round is planned to be on June 5 & 6, 2009. |
|---|
| | 38 | * ''[wiki:Sprints/One First Coherence/KDE sprint May 9/10 in Paris] |
|---|
| | 39 | |
|---|
| | 40 | '' February 24, 2009'':: |
|---|
| | 41 | * Release [changeset:1193 version 0.2.0 - Good Morning, Starshine -] of [wiki:UPnP-Inspector The Inspector] |
|---|
| | 42 | |
|---|
| | 43 | '' February 23, 2009'':: |
|---|
| | 44 | * Release of [changeset:1191 version 0.6.2 - Rosenmontag] |
|---|
| | 45 | |
|---|
| | 46 | [OldNews older news...] |
|---|
| | 47 | |
|---|
| | 48 | [[BR]] |
|---|
| | 49 | [[BR]] |
|---|
| | 50 | |
|---|
| | 51 | == What is it? == |
|---|
| | 52 | |
|---|
| | 53 | === For Users === |
|---|
| | 54 | |
|---|
| | 55 | Coherence offers a toolkit including: |
|---|
| | 56 | |
|---|
| | 57 | * a [wiki:MediaServer DLNA/UPnP MediaServer] stand-alone application, which exports local/home or online media files via [wiki:MediaServer its backends] to other [wiki:SupportedDevices UPnP clients]. |
|---|
| | 58 | * an audio/video [wiki:MediaRenderer DLNA/UPnP Media renderer] stand-alone application, based on the GStreamer framework (early stages). |
|---|
| | 59 | * [wiki:Cadre Cadre]: an image [wiki:MediaRenderer DLNA/UPnP Media renderer] stand-alone application, to be used as a picture frame. |
|---|
| | 60 | * [wiki:Mirabeau Mirabeau]: a standalone UPnP bridge application, to share your UPnP content between two or more local networks over the Internet (work in progress). |
|---|
| | 61 | * [wiki:UPnP-Inspector The Inspector]: a UPnP Device and Service analyzer/debugger tool, which can also be used as a UPnP control-point. |
|---|
| | 62 | * Plugins or extensions for other applications to open them to the UPnP world, thanks to the framework (either as media servers, control points or renderers). This includes [wiki:Totem Totem], [wiki:Nautilus Nautilus], [wiki:EyeofGnome Eye Of Gnome], [wiki:RhythmBox Rythmbox], [wiki:Banshee Banshee], Elisa, amarok... |
|---|
| | 63 | |
|---|
| | 64 | The toolkit is known to work on various Linux flavors, BSD, (Open)Solaris and Windows. It can be installed either as a standard python source-code download or through various OS-specific packages. |
|---|
| | 65 | |
|---|
| | 66 | === For Application Developers === |
|---|
| | 67 | |
|---|
| | 68 | Developers get a framework written in [http://python.org Python] with an emerging DBus API. This framework is designed to automate all UPnP-related tasks as much as possible and enable applications to participate in digital living networks, primarily the [http://upnp.org/ UPnP] universe. |
|---|
| | 69 | |
|---|
| | 70 | The core framework of Coherence provides: |
|---|
| | 71 | * an [htdocs:draft-cai-ssdp-v1-03.txt SSDP] server |
|---|
| | 72 | * an MSEARCH client |
|---|
| | 73 | * server and client for HTTP/SOAP requests |
|---|
| | 74 | * server and client for Event Subscription and Notification ([htdocs:draft-cohen-gena-client-00.txt GENA]) |
|---|
| | 75 | * A device implementation dock |
|---|
| | 76 | |
|---|
| | 77 | UPnP device implementations are pluggable. For instance, we can pick the MediaServer device and plug it into the core. Or attach the MediaRenderer device. Or attach both, or two MediaServers and a ControlPoint - this is the point where one of Coherence's particular features kicks in. |
|---|
| | 78 | |
|---|
| | 79 | This probably makes more sense if we look at how UPnP devices are implemented within Coherence. On one side of the device we have the connectors to the core, but on the other side there is a dock for a backend to be plugged in. So a device implementation is generally a simple translation map between the the core and its backend. |
|---|
| | 80 | |
|---|
| | 81 | As an example, a MediaServer connects to the core via the ContentDirectory and ConnectionManager services and bridges them to a filesystem backend. Or bridges them - let's say - to a less skimpy one, the MediaStore of a [http://en.wikipedia.org/wiki/Media_center MediaCenter] exposing its content in a way already presorted by album, artist, genre,...etc. |
|---|
| | 82 | |
|---|
| | 83 | More information is available in the [wiki:ArchitecturalOverview Architectural Overview]. |
|---|
| | 84 | |
|---|
| | 85 | == Current State == |
|---|
| | 86 | |
|---|
| | 87 | At the moment Coherence is primarily focused on the [http://upnp.org/specs/av/default.asp UPnP A/V] devices but any other UPnP device can be addressed, too. Such as a [http://upnp.org/standardizeddcps/lighting.asp Lighting Controls] bridge to [http://www.konnex.org/ EIB] home-automation. |
|---|
| | 88 | |
|---|
| | 89 | The core itself is fairly complete and can be used on its own for debugging purposes. |
|---|
| | 90 | |
|---|
| | 91 | == Supported Devices == |
|---|
| | 92 | |
|---|
| | 93 | Here is a [SupportedDevices list of devices] which have been reported to work with Coherence. Please keep us informed about your devices. |
|---|
| | 94 | |
|---|
| | 95 | == Download == |
|---|
| | 96 | |
|---|
| | 97 | * Binary packages are available for various environments: they are listed on the [wiki:Packages packages page][[BR]] |
|---|
| | 98 | * Alternatively, there is an entry in the [http://www.python.org/pypi CheeseShop] enabling you to install and upgrade with [http://peak.telecommunity.com/DevCenter/setuptools easy_install]: {{{ easy_install Coherence }}}[[BR]] |
|---|
| | 99 | * The source tarball for the current stable version is available [http://coherence.beebits.net/download/Coherence-0.6.6.1.tar.gz here][[BR]] |
|---|
| | 100 | * Source checkouts via [http://subversion.tigris.org/ Subversion] are possible too:[[BR]] |
|---|
| | 101 | * current stable release: {{{ svn co https://coherence.beebits.net/svn/tags/Coherence-0.6.6.1 Coherence}}}[[BR]] |
|---|
| | 102 | * current development: {{{ svn co https://coherence.beebits.net/svn/trunk/Coherence Coherence}}}[[BR]] |
|---|
| | 103 | |
|---|
| | 104 | == Documentation & Hacking == |
|---|
| | 105 | |
|---|
| | 106 | For information about installation and using Coherence with(in) your application and writing backends and plugins, please visit the DocumentationDepartment and the slowly growing list of SupportedDevices. |
|---|
| | 107 | |
|---|
| | 108 | There are also [http://netzflocken.de/categories/coherence some posts about Coherence] in my blog, these will sooner or later get incorporated into this site. |
|---|
| | 109 | |
|---|
| | 110 | == Contact and Discussion == |
|---|
| | 111 | |
|---|
| | 112 | * Please add your bug-reports, suggestions, patches or comments as [/newticket tickets] to this trac instance[[BR]] |
|---|
| | 113 | * You may also add your feature requests [wiki:FeatureRequests here][[BR]] |
|---|
| | 114 | * You need to [/register register] first, to reduce spam[[BR]] |
|---|
| | 115 | * Developers and users usually hang around on |
|---|
| | 116 | IRC: irc://irc.freenode.net/#coherence or irc://irc.freenode.net/#moovida [[BR]] |
|---|
| | 117 | * There are two mailing-list for Coherence:[[BR]] |
|---|
| | 118 | * [http://lists.beebits.net/cgi-bin/mailman/listinfo/coherence-announce coherence-announce]: only announces about updates and new releases, read-only[[BR]] |
|---|
| | 119 | * [http://lists.beebits.net/cgi-bin/mailman/listinfo/coherence-dev coherence-dev]: discussions, questions,... about development and usage issues[[BR]] |
|---|
| | 120 | |
|---|
| | 121 | For searching the history of the coherence-dev mailing list you can use [http://n2.nabble.com/coherence-dev-f2517470.html nabble]. |
|---|
| | 122 | |
|---|
| | 123 | Frank Scholz, the lead developer of Coherence, can be reached at [mailto:dev@coherence-project.org dev@coherence-project.org]. |
|---|
| | 124 | |
|---|
| | 125 | == History == |
|---|
| | 126 | |
|---|
| | 127 | Coherence has its roots in the work of |
|---|
| | 128 | |
|---|
| | 129 | * [http://frungy.org/~tpot/ Tim Potter] who started everything and set the code lose |
|---|
| | 130 | * [http://resnet.uoregon.edu/~gurney_j/ John-Mark Gurney] who continued it with the MediaServer [http://resnet.uoregon.edu/~gurney_j/jmpc/pymeds.html PyMeds] |
|---|
| | 131 | * and [http://www.fluendo.com/Fluendo Fluendo] who added a first ContentDirectory client for [https://core.fluendo.com/elisa/trac/wiki Elisa] |
|---|
| | 132 | |
|---|
| | 133 | == License == |
|---|
| | 134 | |
|---|
| | 135 | Coherence is licensed under the [http://www.opensource.org/licenses/mit-license.php MIT license]. |
|---|
| | 136 | |
|---|
| | 137 | == Dependencies == |
|---|
| | 138 | |
|---|
| | 139 | * Coherence in written in [http://python.org Python], and currently tested against version 2.4, 2.5 and 2.6 |
|---|
| | 140 | * depends on [http://peak.telecommunity.com/DevCenter/setuptools setuptools] for the installation process and plugin management |
|---|
| | 141 | * profits from the excellent event-driven networking framework [http://twistedmatrix.com Twisted] |
|---|
| | 142 | * needs [http://effbot.org/zone/element-index.htm ElementTree] for its XML processing (included in Python 2.5) |
|---|
| | 143 | * uses [http://pylouie.org/index.html Louie] for signal dispatching (included in Coherence >= 0.5.8) |
|---|
| | 144 | * [http://www.voidspace.org.uk/python/configobj.html ConfigObj] (optional since Coherence >=0.5, due to the [wiki:XMLConfig new XML configuration file format]) |
|---|
| | 145 | * [http://divmod.org/trac/wiki/DivmodNevow Divmods Nevow] (optional, for all the WebUI html, together with [http://divmod.org/trac/wiki/DivmodNevow/Athena Athena] for the AJAX bells and whistles) |
|---|
| | 146 | * [http://python.net/crew/theller/ctypes ctypes] (optional, included in Python 2.5 for the MediaServer file system backend) |
|---|
| | 147 | * [http://gstreamer.org GStreamer] (optional, for the MediaRenderer backend) |
|---|
| | 148 | * [http://alastairs-place.net/netifaces netifaces (optional, to handle on Windows OS the detection of the own IP) |
|---|
| | 149 | * [http://wwwsearch.sourceforge.net/mechanize/ Mechanize] (optional, for the account authentication in the [wiki:FlickR Flickr MediaServer] backend) |
|---|
| | 150 | * [http://code.google.com/p/gdata-python-client/ Google Data APIs Python Client Library] (optional, for the [wiki:YouTube YouTube MediaServer] backend) |
|---|
| | 151 | |
|---|
| | 152 | == Variety == |
|---|
| | 153 | |
|---|
| | 154 | There are other projects that are similar to Coherence or provide related functions, such as a dedicated UPnP MediaServer implementation. They are listed on the [wiki:Resources] page. |
|---|
| | 155 | |
|---|
| | 156 | == Publicity == |
|---|
| | 157 | |
|---|
| | 158 | * [http://www.ohloh.net/projects/6011 Coherence on Ohloh] [[OhlohBadge(6011)]] [[BR]] |
|---|
| | 159 | * [http://freshmeat.net/projects/coherence Coherence at FreshMeat] [[BR]] |
|---|
| | 160 | * The [http://pypi.python.org/pypi/Coherence Python Cheeseshop] |