[Mono-list] What features would be missed when developing
alan.mcgovern at gmail.com
Tue Sep 18 11:08:17 EDT 2007
Read up here: http://mono-project.com/Moonlight
There is a completely separate set of assemblies for moonlight as compared
to regular mono.
On 9/18/07, Engler, Eric <Eric.Engler at zcsterling.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> >> Mono's Moonlight may have trouble keeping up unless WPF will be
> >> implemented in Mono at some point. The main reason Mono's Moonlight
> >> works today is because there's only a small amount of WPF
> >> functionality in Silverlight at this time.
> > For 1.1, a severely trimmed down version of the CLR is used and
> > as a browser plugin. This is true for both Silverlight and Moonlight
> I hope this is the case. I saw an interview video that led me to believe
> the 1.1 assembly that gets downloaded to the browser would run with the
> regular Mono CLR instead of a smaller CLR installed as a plugin. I was
> left with the impression that the Moonlight plugin was only glue between
> the browser and the regular Mono CLR.
> I strongly prefer a scaled down CLR built-in to the plugin since that
> would ease portability. There are many flavors of linux and we can't
> assume a given user will have the right version, or any version, of the
> Mono CLR. It wouldn't be good if we just give him an error and die. If,
> however, the CLR was built-in to the plugin we'd only have to have him
> upgrade his plugin.
> -----BEGIN PGP SIGNATURE-----
> Version: PGP Universal 2.6.2
> Charset: us-ascii
> -----END PGP SIGNATURE-----
> Mono-list maillist - Mono-list at lists.ximian.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-list