Jump to content

Moonlight (runtime)

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Bender the Bot (talk | contribs) at 21:53, 27 November 2016 (→Desktop support: clean up; http→https for YouTube using AWB). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Moonlight
Developer(s)Novell
Initial releaseMarch 4, 2009; 15 years ago (2009-03-04)
Repository
Written inC, C++, C#
Operating systemLinux
TypeWeb Application framework
LicenseLGPL 2 with proprietary codecs
Website

Moonlight was a free and open source implementation of Microsoft's Silverlight for Linux and other Unix based operating systems, developed and abandoned by the Mono Project.[1][2] Like Silverlight, Moonlight was a web application framework which provided functionalities similar to those in Adobe Flash, integrating multimedia, graphics, animations and interactivity into a single runtime environment.

History and overview

Release History
Date Version
2009-02-11 Moonlight 1.0[3]
2009-12-17 Moonlight 2.0[4]
2010-02-03 Moonlight 3.0 Preview 1[5]
2011-02-15 Moonlight 4 Preview 1[6]

In an interview in the beginning of June 2007, Miguel de Icaza said the Mono team expected to offer a feasibility "alpha" demo in mid-June 2007, with support for Mozilla Firefox on Linux by the end of the year.[7]

After a 21-day hacking spree by the Mono team (including Chris Toshok, Larry Ewing and Jeffrey Stedfast among others), a public demo was shown at Microsoft ReMIX conference in Paris, France on June 21, 2007.[8][9][10][11]

However, in September 2007, developers still needed to install and compile a lot of Mono and Olive (the experimental Mono subproject for .NET 3.0 support) modules from the Mono SVN repository to be able to test Moonlight.[12] A Moonlight IDE, named Lunar Eclipse, exists in SVN for XAML designs. It is expected to be included or ported into MonoDevelop as an add-on in the future.[13] Moonlight uses Cairo for rendering.[14]

Moonlight was provided as a plugin for Firefox and Chrome on popular Linux distributions.[15] The plugin itself does not include a media codec pack, but when the Moonlight plugin detects playable media it refers users to download a free Media codec pack from Microsoft.

Moonlight 2.0 tracked the Silverlight 2.0 implementation. The first completed version, Moonlight 1.0, supporting Silverlight 1.0, was released 20 January 2009. Moonlight 2.0 was released on December 17, 2009.[16] The Moonlight 2.0 release also contained some features of Silverlight 3 including a pluggable media framework which allowed Moonlight to work with pluggable open codecs, such as Theora and Dirac.[17]

Preview releases of Moonlight 4.0, targeting Silverlight 4 compatibility, were released in early 2011.[18]

In April 2011, the Moonlight team demonstrated Moonlight running on Android tablets and phones at the MIX11 Web Developers conference in Las Vegas.[19]

Shortly after the April 2011 release, Attachmate, parent to developer Mono, laid off an undisclosed number of Mono employees[20] and announced a deal with startup Xamarin.[21] At that time, Xamarin CEO Nat Friedman affirmed their commitment to the Moonlight project; however, there have been no outward signs of any further development since the new partnership. Their published road map is quite out of date and the previously active release schedule (including nightly builds) has completely ceased since the new partnership was formed.[22]

In December 2011 Miguel de Icaza announced that work on Moonlight had stopped with no future plans. He explained that, although there was always some bloat, complication and over-engineering in the Silverlight vision, Microsoft had "cut the air supply" to it by omitting cross-platform components, making it a web-only plugin, and including Windows-only features. He advised developers to separate user interface code from the rest of their application development to ensure "a great UI experience on every platform (Mac, Linux, Android, iOS, Windows and Web)" without being dependent on third party APIs.[23]

DRM

Silverlight supports Digital Rights Management in its multimedia stack, but Microsoft will not license their PlayReady DRM software for the Moonlight project to use and so Moonlight is unable to play encrypted content.[24]

Desktop support

Moonlight was also usable outside of the browser as a Gtk+ widget (known as Moonlight.Gtk). A number of Desklets were written using this new technology during the Novell Hack Week in 2007.[25]

MoonBase,[26] an experimental set of helper classes built on top of Moonlight.Gtk that can be used to create full blown C# desktop applications using the Moonlight (Silverlight 4.0) widgets and XAML files. MoonBase also has a related XAML editor/previewer.[27]

Microsoft support

Shortly after the first demo at MIX 07 in Paris, Microsoft began cooperating with Novell to help the building of Moonlight.[28] Support includes exclusive access given to Novell for the following Silverlight artifacts:[29]

  • Microsoft's Test suites for Silverlight,
  • Silverlight specification details, beyond those available on the web,
  • Proprietary codecs made available free-of-charge for Windows Media Video and Audio, for VC-1 and MP3, and in the future H.264 and AAC, only licensed for use with Moonlight when running in a web browser. Other potential decoders include GStreamer and FFmpeg (used during the development stage) but Novell will not provide prepackaged versions of Moonlight with those libraries, because those decoders have not been granted licensing for the use of patented codec technologies.

Microsoft has released two public covenants not to sue for the infringement of its patents when using Moonlight. The first one covered Moonlight 1 and 2, is quite restrictive and it covered only the use of Moonlight as a plugin in a browser, only implementations that are not GPLv3 licensed, and only if the Moonlight implementation has been obtained from Novell. It also notes that Microsoft may rescind these usage rights.[30]

The second covenant is an updated and broader covenant that no longer limits the covenant to users that obtain Moonlight from Novell, it covers any uses of Moonlight regardless of where it was obtained. The updated covenant covers the implementations as shipped by Novell for versions 3 and 4, it no longer distinguishes Novell from other distributions of Moonlight and expands the covenant to desktop applications created with Moonlight. The covenant does not extend to forks licensed under the GNU GPL (Moonlight itself uses the Lesser GPLv2).[31]

Codecs integration

Although Moonlight is free software, the final version was going to use binary-only audio and video codecs provided by Microsoft which will be licensed for use with Moonlight only when used as a browser plugin (see above). The Windows media pack is not distributed together with the Moonlight plugin but the first time when media content in Silverlight is detected the user will be prompted to download the pack containing the codecs used in Silverlight directly from Microsoft.

Self built versions could still use the FFmpeg library and there was discussion about adding GStreamer support as an alternative to using Microsoft's binary codecs for those who wish to use GStreamer instead and also for use when used outside of a browser.

Mono architect Miguel de Icaza blogged that the Mono team prototyped Moonlight multimedia support using the LGPL-licensed FFmpeg engine but that they were unable to redistribute packaged versions that used that library due to FFmpeg codec licensing issues inside of the United States.[29][32]

Moonlight in other distributions

After the release of Moonlight 2, a covenant provided by Microsoft was updated to ensure that other third party distributors can distribute Moonlight without their users having to worry about getting sued over patent infringement by Microsoft.[33] This covenant can be found on the Microsoft website.

Kevin Kofler and Tom Callaway, of Fedora, have stated publicly that the last covenant was "not acceptable" for that distribution and that "it is still not permissible in Fedora".[34]

The version of Moonlight that was going to be available direct from Novell would have access to licensed closed source media codecs provided free of charge by Microsoft. Third-party distributions of Moonlight would only be able to play non-patent encumbered media like Vorbis, Theora and Ogg. To support other formats, the distributors would have had to choose from a few licensing options:

  • Negotiate licences directly with individual media codec owners (e.g. MPEG-LA, Fraunhofer Society)
  • Negotiate access to Microsoft's Media Pack as Novell have done
  • Use GStreamer or a commercial codec license
  • Use a hardware-specific software like VDPAU[33]

At the PDC conference on October 13, 2008, Microsoft placed the 'Silverlight XAML Vocabulary' under the Microsoft Open Specification Promise,[35] stating in a press release, "The Silverlight XAML vocabulary specification, released under the Microsoft Open Specification Promise, will better enable third-party ISVs to create products that can read and write XAML for Silverlight." Since Moonlight is essentially a XAML reader, Debian's position is that Moonlight is safe for them to redistribute (leaving each user to agree to their own licensing for Microsoft's and others' binary codecs).[36]

See also

References

  1. ^ a b Miguel de Icaza (May 29, 2012). "Miguel de Icaza on ASP.NET MVC, Moonlight, and the Android Lawsuit". InfoQ.com. Retrieved 2014. {{cite web}}: Check date values in: |accessdate= (help)
  2. ^ a b Foley, Mary-Jo. "Xamarin abandons its Silverlight for Linux technology". All About Microsoft. ZDNet. Retrieved 1 June 2012.
  3. ^ http://tirania.org/blog/archive/2009/Feb-11.html
  4. ^ http://tirania.org/blog/archive/2009/Dec-17.html
  5. ^ http://tirania.org/blog/archive/2010/Feb-03.html
  6. ^ http://tirania.org/blog/archive/2011/Feb-16.html
  7. ^ Dana Gardner. "the FASTforward blog: Expect a June demo of Silverlight on Linux, sans browser". Retrieved 2007-06-06.
  8. ^ "Implementing Silverlight in 21 Days". Miguel de Icaza. Retrieved 2007-06-22.
  9. ^ "Implementing Silverlight in 21 Days". Jeffrey Stedfast. Retrieved 2007-06-21.
  10. ^ "Moonlight". Chris Toshok. Retrieved 2007-06-21.
  11. ^ "Mono Silverlight implementation emerges after epic hackathon". Ars Technica. Retrieved 2007-06-22.
  12. ^ "Moonlight: Getting started". Mono Team. Retrieved 2007-09-02.
  13. ^ "Moonlight".
  14. ^ Moonlight Notes
  15. ^ "Moonlight Supported Platforms". mono-project.com. Retrieved 2009-05-17.
  16. ^ "Moonlight 2 is now available". The Silverlight Team blog. 2009-12-17.
  17. ^ "First Moonlight 2.0 Preview is Out". Miguel de Icaza. Retrieved 2009-05-04. We have developed a handful of open source codecs for Dirac, Vorbis and ADPCM that can be used with Silverlight 3/Moonlight Preview based on existing C# and Java implementations. Hopefully someone will help us fill in the blanks with more codecs (like Theora).
  18. ^ "Moonlight 4 Preview Now Available". The Silverlight Team Blog. 2011-02-15.
  19. ^ "Moonlight on Android". A Moment of Zen. 2011-04-15.
  20. ^ "Attachmate lays off Mono employees". 2011-05-03.
  21. ^ "SUSE Joins Xamarin for Mono". 2011-08-10.
  22. ^ "Moonlight Road Map". Mono-Project. 2011-11-08.
  23. ^ "Moonlight Mailing List". Xamarin. 2011-15-15. {{cite web}}: Check date values in: |date= (help)
  24. ^ "Discussion on official Silverlight forum".
  25. ^ "Moonlight Desklets demo on YouTube". Mono Team. Retrieved 2007-06-25.
  26. ^ MoonBase
  27. ^ XamlPreviewer
  28. ^ Foley, Mary Jo (2007-09-25). "Microsoft officially 'extends support' for Novell's Silverlight Linux port". zdnet.com. Retrieved 2007-10-13.
  29. ^ a b de Icaza, Miguel (2007-09-05). "Microsoft/Novell Collaboration on Silverlight". Retrieved 2007-10-13.
  30. ^ "Covenant to Downstream Recipients of Moonlight - Microsoft & Novell Interoperability Collaboration". Microsoft. 2007-09-28. Retrieved 2008-03-08. "Downstream Recipient" means an entity or individual that uses for its intended purpose a Moonlight Implementation obtained directly from Novell or through an Intermediate Recipient... Microsoft reserves the right to update (including discontinue) the foregoing covenant... "Moonlight Implementation" means only those specific portions of Moonlight 1.0 or Moonlight 1.1 that run only as a plug-in to a browser on a Personal Computer and are not licensed under GPLv3 or a Similar License.
  31. ^ "Covenant to End Users of Moonlight 3 and 4". Microsoft. Retrieved 2010-05-11.
  32. ^ Ramji, Sam (2007-09-05). "The Novell-Microsoft Wheeler Dealers Speak". Retrieved 2007-10-13. After a great deal of work between the Moonlight and .NET teams, we're ready to formally announce that we (Microsoft and Novell) will be bringing Silverlight to Linux (Sam Ramji is Director of Microsoft's Open Source Software Lab)
  33. ^ a b Miguel de Icaza (2009-12-17). "Releasing Moonlight 2, Roadmap to Moonlight 3 and 4". Retrieved 2009-12-18.
  34. ^ Tom Callaway (December 23, 2009). "Re: New covenant published". gmane.linux.redhat.fedora.devel. Retrieved 2010-01-11.
  35. ^ "Microsoft Releases Silverlight 2, Already Reaching One in Four Consumers Worldwide". Microsoft. 2008-10-13. Retrieved 2008-10-13.
  36. ^ "Moonlight for Debian". Debian Wiki. Retrieved 2010-03-09 (Page marked 'this page is out of date'). Moonlight 1.0 is essentially a XAML renderer with codec support. All plugin logic is handled by the browser's Javascript engine. XAML is covered by an irrevocable patent grant from Microsoft, as shown here. {{cite web}}: Check date values in: |accessdate= (help); External link in |quote= (help)
Retrieved from "https://en.wikipedia.org/w/index.php?title=Moonlight_(runtime)&oldid=751794285"