Feeds

Open source closes gap on Microsoft's next Silverlight

Moonlight beams into future

Next gen security for virtualised datacentres

Code has been released for the open-source version of Silverlight that closes the gap on the as-yet-unfinished next version of Microsoft's browser-based media player.

Moonlight 2.0 has been delivered for preview featuring APIs from Microsoft's Silverlight 3.0 that the project's organizers said it made sense to add. Moonlight puts Microsoft's Silverlight on Linux and Unix.

Moonlight 2.0 is modeled on Silverlight 2.0 but since work began on the second version of Moonlight, Microsoft released a beta for the third edition of Silverlight with final code expected later this year.

Silverlight 3.0 brings major changes in workflow, video streaming, and hardware acceleration. Plus, there's the ability to drag content built in Silverlight out of the browser to run on the desktop.

APIs from Silverlight 3.0 in the second Moonlight will also let content run outside the browser using some manual tweaking, let you safely save content authored in Silverlight, provide expanded support for Silverlight's DeepZoom, and let you write codecs in managed code. You can see a list of the Silverlight 3.0 APIs included here.

Last October, Moonlight's organizers promised feature parity with the latest, official release of Silverlight - version 2.0 - in Moonlight 2.0.

Moonlight developer Chris Toshok blogged that it had made sense to spend a little extra time to add some of the features from Silverlight 3.0, given Microsoft released the beta after work had begun on Moonlight 2.0. Moonlight lead Miguel de Icaza said they'd decided to expose the Silverlight 3.0 APIs in a "forward-compatible fashion".

Otherwise, Miguel de Icaza called this the version of Moonlight he'd wanted to build since Microsoft released Silverlight 2.0 in late 2008.

Features from Silverlight 2.0 in the Moonlight preview include the CoreCLR security model to divide code by three criteria (transparent, safe-critical and critical) as well as controls released to open source by Microsoft under its OSI-approved Permissive License (Ms-PL), the ability to write content using IronRuby and IronPython, and adaptive streaming to adapt content flow to the bit-rate that's available. ®

Build a business case: developing custom apps

More from The Register

next story
Why has the web gone to hell? Market chaos and HUMAN NATURE
Tim Berners-Lee isn't happy, but we should be
Mozilla's 'Tiles' ads debut in new Firefox nightlies
You can try turning them off and on again
Microsoft boots 1,500 dodgy apps from the Windows Store
DEVELOPERS! DEVELOPERS! DEVELOPERS! Naughty, misleading developers!
'Stop dissing Google or quit': OK, I quit, says Code Club co-founder
And now a message from our sponsors: 'STFU or else'
Apple promises to lift Curse of the Drained iPhone 5 Battery
Have you tried turning it off and...? Never mind, here's a replacement
Uber, Lyft and cutting corners: The true face of the Sharing Economy
Casual labour and tired ideas = not really web-tastic
Linux turns 23 and Linus Torvalds celebrates as only he can
No, not with swearing, but by controlling the release cycle
prev story

Whitepapers

Gartner critical capabilities for enterprise endpoint backup
Learn why inSync received the highest overall rating from Druva and is the top choice for the mobile workforce.
Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Rethinking backup and recovery in the modern data center
Combining intelligence, operational analytics, and automation to enable efficient, data-driven IT organizations using the HP ABR approach.
Consolidation: The Foundation for IT Business Transformation
In this whitepaper learn how effective consolidation of IT and business resources can enable multiple, meaningful business benefits.
Next gen security for virtualised datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.