Monlight update before the arrival of mix 08

Before mix08 arrived, the mono team's boss Miguel de Icaza's posted the pre-mix 08: moonlight updates on the blog. According to the description in this blog, monolight has basically completed the development of the silverlight1.0 function:

1,Moonlight media support:In the past, the media support the FFMPEG pipeline. The FFMPEG's pipeline cannot meet the actual needs.CodeSupports Microsoft Media decoding. It no longer depends on ffmpegs pipelines, but uses ffmpegs audio and video decoding. The ultimate goal is to fully support Microsoft Media. See the following two figures:

Current media support methods

Final Media Support Method

2. Video Stream: Monolight now supports video stream playback. Previous versions can only support playback after video files are downloaded to a local temporary directory. Now, you only need to have enough cache data to play back the video, however, HTTP is also supported and MMS-over-HTTP is being supported. specs for HTTP-based streaming for Windows Media Servers will be released next week, this helps to better implement this function.

3. Test ToolsThe mono Team cooperates with the Microsoft development team. The mono team has obtained a large number of Silverlight testing tools, but those tools cannot be used directly on monolight. Microsoft agrees with the mono team to implement these open-source testing tools, this is very meaningful.

4,Mozilla installation package:Create an installationProgramInstallers

5. Checker: It is not very important for monolight 1.0, but it is very important for 2.0 and is being implemented.

6. No window support: Windowless is used in many Silverlight programs. Chris implements this function, but only supports firefox 3.0.

7. bug fixingAs the testing tool can run on the Linux platform, test all Microsoft test examples and implement some missing functions, such as window-free support.

8. Silverlight 2.0:Mix 08 Microsoft will release Silverlight 2.0 beta1, and monolight has no work on JIT support. There are two main reasons: A Silverlight 2.0 API has not been published yet, microsoft will publish the Silverlight 2.0 API next week. The second reason is that it is focusing on monolight1.0, so that monolight can reach the Silverlight 1.0 level.