Moonlight 4 Preview 1 is the first preview of Moonlight that includes support for the Siverlight 3 APIs and partial support for Silverlight 4 APIs. We consider the Silverlight 3 API support to be feature complete while the Silverlight 4 APIs are both partial and might be missing features.
The major change from Moonlight 2 is that we now implement the Silverlight 3 API as well as parts of the Silverlight 4 API. The actual missing pieces from the API are documented below.
New Rendering Engine
Moonlight's rendering engine has been rewritten to support hardware acceleration, 3D transformations and pixel shaders. The engine provides a backend system that makes it easy to implement hardware acceleration support for new platforms. The brilliant Gallium3D open source project is used as the default software rendering backend on systems that lack sufficient hardware acceleration support.
The following sections describe how this new rendering engine is used.
If your system has a GPU with OpenGL 2.0 drivers installed for it, Moonlight can offload the visual tree composition to the GPU and developers can also direct Moonlight to cache images directly into the GPU to accelerate rendering and animations on a case-by-case basis.
Developers can also choose to use GPU acceleration for images by using the CacheMode property and setting it to BitmapCache.
Go to the OpenGL status page to find out if your driver is currently supported by Moonlight.
This release of Moonlight supports all of the 3D transformations that were introduced in Silverlight. 3D transformations are typically used to create elements or animations that have perspective in them.
You can see some demos here.
Moonnlight supports both the pre-defined blur and drop shadow effects on any visual element(exposed by the BlurShadowEffect and the DropShadowEffect classes) it also supports user-specified pixel shaders that allow developers to apply complex effects to their visual elements.
New Platform Abstraction Layer
In order to ease porting to other operating systems, messaging systems, windowing systems, and hardware configurations, moonlight 4 has been restructured so that all interactions with these systems goes through an abstract layer, called the PAL.
There are several interfaces within each subsection, some of which are listed below:
- MoonEvent and various specialized subclasses
OOB Application Installation
Out of Browser Execution
Moonlight now supports out of browser execution of the websites that support it.
Moonlight supports capture using V4L2. The following pixel formats are supported at present.
If your camera or tuner card doesn't work, please let us know the model and/or any other info about your hardware setup, and we'll make it work.
We are providing certain features for developers that want to improve the performance of their application or want to debug how Moonlight is rendering things. When you right-click on a Silverlight surface, the "Advanced" tab has features that will let you:
- Display the Frames Per Second counters
- Track exposed regions
- Track clipping rectangles
- Show UIElement bounding boxes
- Show textbox bounds
- Enable/disable occlusion culling
- Emulate the Windows Platform key codes
- Some applications have hardcoded Windows platform key codes, this lets those applications run on Moonlight.
- Allows users to use the Curl bridge over the browser HTTP stack
- Enable or disable the GPU acceleration stack.
In addition to supporting Firefox, the new Moonlight preview ships with Google Chrome packages and works as an out-of-browser plugin.
Linux Chrome libjpeg issue
Current google-built linux versions of chrome link against the widely deployed libjpeg.so.62. All linux distributions should have this library installed, but some of them (including openSUSE 11.3) install them for legacy purposes only, and link their own libraries against libjpeg.so.8.
It is very easy to end up in a situation where both versions of libjpeg are loaded into the same process, at which time it's also very easy to end up in a situation where code compiled to use libjpeg.so.8 is actually calling through to dynamic symbols exported from libjpeg.so.62. This causes an immediate abort().
For moonlight specifically this happens because the chrome process pulls in libjpeg.so.62, and the gdk-pixbuf jpeg loader pulls in libjpeg.so.8. We have added code (pending for preview 2, in git already if you're tracking it) specifically to check for this situation and disable jpeg loading entirely if we find it to be present. Chrome has plans to move to libjpeg-turbo in the future, so this will eventually not (hopefully) be an issue.
If there are chromium packages as part of your linux distribution, those might fix the problem, as they are more likely to link against the blessed libjpeg.so, whatever version it might be.
Some other chrome issue regarding libjpeg versions are:
In addition to the MP3, VC1, WMA, and the various WMV codecs that were supported in Moonlight 2, the Microsoft Media Pack that Moonlight uses also contains the video codec for H.264 and the AAC audio codec.
Even though Moonlight 2 shipped with support for Smooth Streaming, the underlying pipeline that is used by the Smooth Streaming system has been upgraded.
Moonlight supports the System.Windows.Messaging namespace which allows for multiple moonlight plugins on the same web page (or different webpages) to communicate directly, and safely.
Some features are presently missing or incomplete:
- RichTextBox (incomplete)
- Printing (missing)
- Elevated Trust (incomplete)
- WebBrowser (missing)
- CachedComposition ???
- TextInput event (missing)
- Navigation (incomplete)
- Microphone (missing)
- WebCam (incomplete ???)
- UDP sockets
- UdpAnySourceMulticastClient (not implemented)
- UdpSingleSourceMulticastClient (not implemented)
- Analytics (missing)
- ChildWindow (incomplete)
- NotificationWindow (not implemented)
- Seadragon BlurFactor (missing)
Obtaining Moonlight 4 Preview 1
The current release of Moonlight can be downloaded here.
Keeping up with Moonlight 4
You can always download the most recent bleeding edge bits (basically the last successful compile) from here. Be aware these have had no testing done on them at all. They might crash your browser, or worse.
Source code for current and previous moonlight releases is available from our ftp site.
If you plan on tracking the source it's much easier to use git. The instructions for checking things out can be found here.