From jbevain at novell.com  Thu Apr  3 08:16:22 2008
From: jbevain at novell.com (Jb Evain)
Date: Thu, 03 Apr 2008 14:16:22 +0200
Subject: [Moonlight-list] SL 2 for Moonlight, a small report
Message-ID: <47F4CA96.207@novell.com>

Folks,

Here's a small report written for Miguel who wanted to know what have 
changed in Silverlight 2.0, that we would need to support to be able to 
load SL 2.0 applications.

If you want to hack on this you can work in my ml2 branch:

/branches/jb/ml2

It contains a standard branched mcs/mono/olive/moon. It should compile, 
and it's able to run ported versions of Chess and Airlines.

So the biggest change we'll have to handle first, is how the 
applications are deployed. They are currently using the mime type 
"application/x-silverlight-2-b1", and I can guess using my super powers 
that the final one will be "application/x-silverlight-2".

The source, instead of being a xaml file, is now a .xap file. Raw .xaml 
are not supported anymore from what I got, only .xap files are supported 
is the mime type asks for SL2.

Anyway, a .xap file is simply a zip file, which contains a file named 
"AppManifest.xml", which has the following form:

<Deployment xmlns="http://schemas.microsoft.com/client/2007/deployment" 
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" 
EntryPointAssembly="PopTheBubble" EntryPointType="PopTheBubble.App" 
RuntimeVersion="2.0.30226.2">
   <Deployment.Parts>
     <AssemblyPart x:Name="PopTheBubble" Source="PopTheBubble.dll" />
     <AssemblyPart x:Name="System.Windows.Controls.Data" 
Source="System.Windows.Controls.Data.dll" />
     <AssemblyPart x:Name="System.Windows.Controls" 
Source="System.Windows.Controls.dll" />
     <AssemblyPart x:Name="System.Windows.Controls.Extended" 
Source="System.Windows.Controls.Extended.dll" />
   </Deployment.Parts>
</Deployment>

So it's basically a list of the assemblies contained in the xap file. 
What's important is the attributes on the Deployment node. 
EntryPointAssembly and EntryPointType are no brainer. The RuntimeVersion 
indicates that we have to modify our Mono loader to deal with the 
version of the Mono runtime we want to load.

We're currently using "moonlight" as the runtime identifier for 2.1, so 
we'll have to make that 2.0.30226.2 for the beta2.

Another interesting thing, is that there's basically almost no xaml 
parsing from the managed side, as the .xaml files are usually 
transformed to C#.

So basically, it's almost it. Let me know if you need some more infos.

-- 
Jb Evain  <jbevain at novell.com>

From jackson at ximian.com  Thu Apr  3 12:49:01 2008
From: jackson at ximian.com (Jackson Harper)
Date: Thu, 03 Apr 2008 12:49:01 -0400
Subject: [Moonlight-list] Error: Unable to create managed xaml loader
In-Reply-To: <9af7f65c0803190805j4e7218edja869b2ce16a43c41@mail.gmail.com>
References: <9af7f65c0803190724m4133eef1wf2fdcce16472b360@mail.gmail.com>
	<9af7f65c0803190805j4e7218edja869b2ce16a43c41@mail.gmail.com>
Message-ID: <1207241341.4271.1.camel@arr.interjections>


This project compiles and runs fine for me.   Based on the error message
it looks like there is a problem with an install.  Maybe there is an
older mono in your PATH before your newly installed one?

Jackson


On Wed, 2008-03-19 at 16:05 +0100, Michael Sch?ndorfer wrote:
> Hi,
> 
> I have a problem when I want to run my simple MoonlightTest-Site in my
> browser. I get this error-Message:
> 
>         Moonlight-Message: Mono Runtime: OK
>         ?Loader::CreateXamlLoader: Unable to create managed xaml
>         loader: Method `System.AppDomain:CreateDomain (string)' is
>         inaccessible from method `Mono.Helper:CreateDomain (intptr)'
>         
>         
>         (gecko:18524): Moonlight-WARNING **: PARSER ERROR, STOPPING
>         PARSING:  (-1) Unable to resolve x:Class type
>         'MoonlightTest.Page;assembly=ClientBin/MoonlightTest.dll'
>          line: 1   char: 0
> 
> The rest of the output is:
> 
>          Browser NPAPI version = 0.17
>         version requested = '1.1' (yes)
>          Browser NPAPI version = 0.17
>         PluginXamlLoader::TryLoad,
>         filename: /home/michael/Projects/MoonlightTest/MoonlightTest/Page.xaml, str: (null)
>         The file is /usr//lib/moon/plugin/moonlight.exe
>         ?Running Moonlight.cs 0
>         mscorlib: /usr/lib/mono/2.1/mscorlib.dll
>         agclr: /usr/lib/mono/gac/agclr/0.0.0.0__0738eb9f132ed756/agclr.dll
>         agmono: /usr/lib/mono/gac/agmono/3.0.0.0__0738eb9f132ed756/agmono.dll
>         setting error args
>         PluginXamlLoader::TryLoad: Could not load xaml
>         file: /home/michael/Projects/MoonlightTest/MoonlightTest/Page.xaml (error: ParserErrorEventArgs)
> 
> I have updatet mono, olive and moon to the latest version vom svn but
> i still get this error.
> 
> When I remove the "x:Class"-Line from my xaml-Page it shows the
> rectangle i have specified in the xaml.
> 
> I have attatched the Project so you could try it.
> 
> regards,
> Michael
> 
> 
> _______________________________________________
> Moonlight-list mailing list
> Moonlight-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/moonlight-list
-- 
Jackson Harper
jackson at ximian.com



From jhill at novell.com  Thu Apr  3 09:42:03 2008
From: jhill at novell.com (Joseph Hill)
Date: Thu, 03 Apr 2008 09:42:03 -0400
Subject: [Moonlight-list] [Ximian-mono-list] SL 2 for Moonlight,
	a small report
In-Reply-To: <47F4CA96.207@novell.com>
References: <47F4CA96.207@novell.com>
Message-ID: <1207230124.8133.9.camel@guenther.site>

In regards to the switch to .xap, has anyone looked at Chiron yet?  John
Lam demonstrated this at MIX, and they made sure to demonstrate it
running on Mono:

http://www.iunknown.com/2008/03/dynamic-silverl.html

It's a minimalist web server that serves a directory (containing xaml
and other resources) as .xap 


On Thu, 2008-04-03 at 14:16 +0200, Jb Evain wrote:
> Folks,
> 
> Here's a small report written for Miguel who wanted to know what have 
> changed in Silverlight 2.0, that we would need to support to be able to 
> load SL 2.0 applications.
> 
> If you want to hack on this you can work in my ml2 branch:
> 
> /branches/jb/ml2
> 
> It contains a standard branched mcs/mono/olive/moon. It should compile, 
> and it's able to run ported versions of Chess and Airlines.
> 
> So the biggest change we'll have to handle first, is how the 
> applications are deployed. They are currently using the mime type 
> "application/x-silverlight-2-b1", and I can guess using my super powers 
> that the final one will be "application/x-silverlight-2".
> 
> The source, instead of being a xaml file, is now a .xap file. Raw .xaml 
> are not supported anymore from what I got, only .xap files are supported 
> is the mime type asks for SL2.
> 
> Anyway, a .xap file is simply a zip file, which contains a file named 
> "AppManifest.xml", which has the following form:
> 
> <Deployment xmlns="http://schemas.microsoft.com/client/2007/deployment" 
> xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" 
> EntryPointAssembly="PopTheBubble" EntryPointType="PopTheBubble.App" 
> RuntimeVersion="2.0.30226.2">
>    <Deployment.Parts>
>      <AssemblyPart x:Name="PopTheBubble" Source="PopTheBubble.dll" />
>      <AssemblyPart x:Name="System.Windows.Controls.Data" 
> Source="System.Windows.Controls.Data.dll" />
>      <AssemblyPart x:Name="System.Windows.Controls" 
> Source="System.Windows.Controls.dll" />
>      <AssemblyPart x:Name="System.Windows.Controls.Extended" 
> Source="System.Windows.Controls.Extended.dll" />
>    </Deployment.Parts>
> </Deployment>
> 
> So it's basically a list of the assemblies contained in the xap file. 
> What's important is the attributes on the Deployment node. 
> EntryPointAssembly and EntryPointType are no brainer. The RuntimeVersion 
> indicates that we have to modify our Mono loader to deal with the 
> version of the Mono runtime we want to load.
> 
> We're currently using "moonlight" as the runtime identifier for 2.1, so 
> we'll have to make that 2.0.30226.2 for the beta2.
> 
> Another interesting thing, is that there's basically almost no xaml 
> parsing from the managed side, as the .xaml files are usually 
> transformed to C#.
> 
> So basically, it's almost it. Let me know if you need some more infos.
> 


From schoendorfer.m.biz at gmx.at  Thu Apr 10 05:50:42 2008
From: schoendorfer.m.biz at gmx.at (=?UTF-8?Q?Michael_Sch=C3=B6ndorfer?=)
Date: Thu, 10 Apr 2008 11:50:42 +0200
Subject: [Moonlight-list] Compile Moonlight with MonoDevelop
In-Reply-To: <9af7f65c0804090859w512b3b35pa6b3fa2b203f5c92@mail.gmail.com>
References: <9af7f65c0804090859w512b3b35pa6b3fa2b203f5c92@mail.gmail.com>
Message-ID: <9af7f65c0804100250v3eb4fd01rf7ee4bdbbd661c65@mail.gmail.com>

Hi,

I want to develop Moonlight-Apps with MonoDevelop, but they won't run when I
compile them.
When i built them with Visual Studio and run them under Moonlight, they work
properly.

So my question is: What do I have to do (change) in MonoDevelop to import a
Visual Studio Solution, which references do I have to add and which
Project-Options do I have to set to be able to built the Project.


best regards,
Michael Sch?ndorfer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/moonlight-list/attachments/20080410/0678a6dd/attachment.html 

From jamesmalone at variamobile.com  Mon Apr 21 16:30:17 2008
From: jamesmalone at variamobile.com (James Malone)
Date: Mon, 21 Apr 2008 13:30:17 -0700
Subject: [Moonlight-list] building moon without gtk
Message-ID: <1208798909.19007.2.camel@host-10-121-7-50.variamobile.local>

Hi,

I am working on developing Mono/Moonlight for a nondesktop environment,
and the graphical architecture makes using gtk costly.  Is there any way
to build Moonlight without the gtk dependencies?  Specifically,
Moonlight itself and mopen.

I plan on contributing work done on my end as I go along. :)

Jimmy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/moonlight-list/attachments/20080421/add846c4/attachment.html 

From gnorton at novell.com  Mon Apr 21 16:50:35 2008
From: gnorton at novell.com (Geoff Norton)
Date: Mon, 21 Apr 2008 16:50:35 -0400
Subject: [Moonlight-list] building moon without gtk
In-Reply-To: <1208798909.19007.2.camel@host-10-121-7-50.variamobile.local>
References: <1208798909.19007.2.camel@host-10-121-7-50.variamobile.local>
Message-ID: <1208811035.7110.11.camel@limestone>

James,

On Mon, 2008-04-21 at 13:30 -0700, James Malone wrote:

> I am working on developing Mono/Moonlight for a nondesktop
> environment,
> and the graphical architecture makes using gtk costly.  Is there any
> way
> to build Moonlight without the gtk dependencies?  Specifically,
> Moonlight itself and mopen.
> 
What portions of Gtk+ do you find "costly" for your environment?  We
dont use the widgets, mostly we just use GDK which is fairly
lightweight.

-g



From miguel at ximian.com  Mon Apr 21 16:55:36 2008
From: miguel at ximian.com (Miguel de Icaza)
Date: Mon, 21 Apr 2008 16:55:36 -0400
Subject: [Moonlight-list] building moon without gtk
In-Reply-To: <1208798909.19007.2.camel@host-10-121-7-50.variamobile.local>
References: <1208798909.19007.2.camel@host-10-121-7-50.variamobile.local>
Message-ID: <1208811336.24170.120.camel@linux.site>

Hey,

> I am working on developing Mono/Moonlight for a nondesktop
> environment,
> and the graphical architecture makes using gtk costly.  Is there any
> way
> to build Moonlight without the gtk dependencies?  Specifically,
> Moonlight itself and mopen.

Not currently, but we are taking patches.

To use Mono and Moonlight on embedded devices, you must obtain a
commercial license from mono-licensing at novell.com.


From jamesmalone at variamobile.com  Mon Apr 21 14:44:51 2008
From: jamesmalone at variamobile.com (Jimmy Malone)
Date: Mon, 21 Apr 2008 14:44:51 -0400
Subject: [Moonlight-list] building moon without gtk
In-Reply-To: <1208811035.7110.11.camel@limestone>
References: <1208798909.19007.2.camel@host-10-121-7-50.variamobile.local>
	<1208811035.7110.11.camel@limestone>
Message-ID: <1208803491.19460.3.camel@host-10-121-7-50.variamobile.local>

Geoff,

Without going down a long avenue of discussion, the reason for avoiding
gtk is because I am already using libraries optimized for hardware
acceleration for a specific platform.  

Jimmy

On Mon, 2008-04-21 at 16:50 -0400, Geoff Norton wrote:
> James,
> 
> On Mon, 2008-04-21 at 13:30 -0700, James Malone wrote:
> 
> > I am working on developing Mono/Moonlight for a nondesktop
> > environment,
> > and the graphical architecture makes using gtk costly.  Is there any
> > way
> > to build Moonlight without the gtk dependencies?  Specifically,
> > Moonlight itself and mopen.
> > 
> What portions of Gtk+ do you find "costly" for your environment?  We
> dont use the widgets, mostly we just use GDK which is fairly
> lightweight.
> 
> -g
> 
> 

From jamesmalone at variamobile.com  Mon Apr 21 14:47:15 2008
From: jamesmalone at variamobile.com (Jimmy Malone)
Date: Mon, 21 Apr 2008 14:47:15 -0400
Subject: [Moonlight-list] building moon without gtk
In-Reply-To: <1208811336.24170.120.camel@linux.site>
References: <1208798909.19007.2.camel@host-10-121-7-50.variamobile.local>
	<1208811336.24170.120.camel@linux.site>
Message-ID: <1208803635.19460.7.camel@host-10-121-7-50.variamobile.local>

Miguel,

On Mon, 2008-04-21 at 16:55 -0400, Miguel de Icaza wrote:
> Hey,
> 
> > I am working on developing Mono/Moonlight for a nondesktop
> > environment,
> > and the graphical architecture makes using gtk costly.  Is there any
> > way
> > to build Moonlight without the gtk dependencies?  Specifically,
> > Moonlight itself and mopen.
> 
> Not currently, but we are taking patches.
> 
> To use Mono and Moonlight on embedded devices, you must obtain a
> commercial license from mono-licensing at novell.com.
> 

I am inquiring about the licensing.

It's good to hear you are taking patches.  I wasn't sure if it was a
consideration since gtk is a de facto part of a graphical interface.  :)

From mdk at mdk.am  Mon Apr 21 18:07:58 2008
From: mdk at mdk.am (Michael Dominic K.)
Date: Tue, 22 Apr 2008 00:07:58 +0200
Subject: [Moonlight-list] building moon without gtk
In-Reply-To: <1208803491.19460.3.camel@host-10-121-7-50.variamobile.local>
References: <1208798909.19007.2.camel@host-10-121-7-50.variamobile.local>
	<1208811035.7110.11.camel@limestone>
	<1208803491.19460.3.camel@host-10-121-7-50.variamobile.local>
Message-ID: <67ed228e0804211507q3cc5d657k861402346bda8f02@mail.gmail.com>

On Mon, Apr 21, 2008 at 8:44 PM, Jimmy Malone
<jamesmalone at variamobile.com> wrote:
> Geoff,
>
>  Without going down a long avenue of discussion, the reason for avoiding
>  gtk is because I am already using libraries optimized for hardware
>  acceleration for a specific platform.

Take note that we're using Gtk/Gdk mostly for "infrastructure" (event
system, main loop, windows, etc.). The actual "heavy lifting"
(drawing) happens through cairo [1]. That's the place (and pretty much
the only place)  to look for hw optimizations.

[1]: http://cairographics.org/

Michael

>
>  Jimmy
>
>
>
>  On Mon, 2008-04-21 at 16:50 -0400, Geoff Norton wrote:
>  > James,
>  >
>  > On Mon, 2008-04-21 at 13:30 -0700, James Malone wrote:
>  >
>  > > I am working on developing Mono/Moonlight for a nondesktop
>  > > environment,
>  > > and the graphical architecture makes using gtk costly.  Is there any
>  > > way
>  > > to build Moonlight without the gtk dependencies?  Specifically,
>  > > Moonlight itself and mopen.
>  > >
>  > What portions of Gtk+ do you find "costly" for your environment?  We
>  > dont use the widgets, mostly we just use GDK which is fairly
>  > lightweight.
>  >
>  > -g
>  >
>  >
>  _______________________________________________
>  Moonlight-list mailing list
>  Moonlight-list at lists.ximian.com
>  http://lists.ximian.com/mailman/listinfo/moonlight-list
>

From miguel at ximian.com  Mon Apr 21 18:43:07 2008
From: miguel at ximian.com (Miguel de Icaza)
Date: Mon, 21 Apr 2008 18:43:07 -0400
Subject: [Moonlight-list] building moon without gtk
In-Reply-To: <1208803635.19460.7.camel@host-10-121-7-50.variamobile.local>
References: <1208798909.19007.2.camel@host-10-121-7-50.variamobile.local>
	<1208811336.24170.120.camel@linux.site>
	<1208803635.19460.7.camel@host-10-121-7-50.variamobile.local>
Message-ID: <1208817787.24170.144.camel@linux.site>


> It's good to hear you are taking patches.  I wasn't sure if it was a
> consideration since gtk is a de facto part of a graphical
> interface.  :)

We do use Gtk+ for a few pieces, important pieces, but it seems like
they can be abstracted out.

Its used for event input and for doing the actual painting, but they
could be made platform independent at some point by a motivated
developer.

From ceronman at gmail.com  Tue Apr 22 01:37:45 2008
From: ceronman at gmail.com (=?ISO-8859-1?Q?Manuel_Alejandro_Cer=F3n_Estrada?=)
Date: Tue, 22 Apr 2008 00:37:45 -0500
Subject: [Moonlight-list] XamlLoader and Surfaces
Message-ID: <796874fc0804212237i3b520633x4e7cf1f7ac84ec92@mail.gmail.com>

Hi Guys.

I'm starting to work on Lunar Eclipse as part of the Google Summer of
Code Program. The first problem I have encountered is that currently
LE is broken. This exception is thrown:

Unhandled Exception: System.Exception: The surface where the xaml
should be loaded is not set.

This is because somewhere in the code, this is called within a
System.Windows.Controls.Control child:

ellipse = (Ellipse)InitializeFromXaml("<Ellipse Name=\"Ellipse\" />");

The exception is thrown because LE is an application with multiple
surfaces (One for the canvas, another for the timeline, etc) and the
Loader didn't know which surface to use.

I could easily fix this loading the ellipse using
GtkSilver.InitializeFromXaml(). But this problem made me question
about some of the Moonlight internals.

My first question is: Why a XamlLoader needs a Surface?

Looking at GtkSilver's code, the proper way to initialize an object
when the application uses multiple surface is to specify the surface
to the XamlLoader:

loader = XamlLoader.CreateManagedXamlLoader (surface, plugin);

The problem is that the Surface class is not exposed to C#, I believe
that is not part of the Silverlight API. I don't know why this surface
must be specified when loading the Xaml. I have been looking at the
XamlLoader c++ code, and apparently, the only reason is to assign the
surface to the loaded object. I believe that maybe it's better not to
set this at Xaml Loading time. Maybe should be assigned when the
object is added to a parent.

Second question: Why AllowMultipleSurfacesPerDomain is handled within
XamlLoader and why it's needed at all? Has MS Silverlight a concept
similar for handling this?

I am starting to understand the Moonlight internals, so please excuse
me if I'm making dump questions.

Manuel.

From ceronman at gmail.com  Tue Apr 22 10:53:59 2008
From: ceronman at gmail.com (=?ISO-8859-1?Q?Manuel_Alejandro_Cer=F3n_Estrada?=)
Date: Tue, 22 Apr 2008 09:53:59 -0500
Subject: [Moonlight-list] XamlLoader and Surfaces
In-Reply-To: <017d01c8a479$ca6146f0$5f23d4d0$@com>
References: <796874fc0804212237i3b520633x4e7cf1f7ac84ec92@mail.gmail.com>
	<017d01c8a479$ca6146f0$5f23d4d0$@com>
Message-ID: <796874fc0804220753n79ef4de5u7af9704dfc070b40@mail.gmail.com>

Hi Rolf.

Thank you for your answer. It made me thinks clearer. And you're
right, it's a complicated issue. I have to keep studying the
Moonlight's code to know if there is another solution to this problem.

Manuel.

2008/4/22 Rolf Bjarne Kvinge <rolflists at ya.com>:
> Hi Manuel,
>
>
>
>  > -----Original Message-----
>  > From: moonlight-list-bounces at lists.ximian.com [mailto:moonlight-list-
>  > bounces at lists.ximian.com] On Behalf Of Manuel Alejandro Cer?n Estrada
>  > Sent: martes, 22 de abril de 2008 7:38
>  > To: moonlight-list at lists.ximian.com
>  > Subject: [Moonlight-list] XamlLoader and Surfaces
>  >
>  > Hi Guys.
>  >
>  > I'm starting to work on Lunar Eclipse as part of the Google Summer of
>  > Code Program. The first problem I have encountered is that currently
>  > LE is broken. This exception is thrown:
>  >
>  > Unhandled Exception: System.Exception: The surface where the xaml
>  > should be loaded is not set.
>  >
>  > This is because somewhere in the code, this is called within a
>  > System.Windows.Controls.Control child:
>  >
>  > ellipse = (Ellipse)InitializeFromXaml("<Ellipse Name=\"Ellipse\" />");
>  >
>  > The exception is thrown because LE is an application with multiple
>  > surfaces (One for the canvas, another for the timeline, etc) and the
>  > Loader didn't know which surface to use.
>  >
>  > I could easily fix this loading the ellipse using
>  > GtkSilver.InitializeFromXaml(). But this problem made me question
>  > about some of the Moonlight internals.
>  >
>  > My first question is: Why a XamlLoader needs a Surface?
>  >
>  > Looking at GtkSilver's code, the proper way to initialize an object
>  > when the application uses multiple surface is to specify the surface
>  > to the XamlLoader:
>  >
>  > loader = XamlLoader.CreateManagedXamlLoader (surface, plugin);
>  >
>  > The problem is that the Surface class is not exposed to C#, I believe
>  > that is not part of the Silverlight API. I don't know why this surface
>  > must be specified when loading the Xaml. I have been looking at the
>  > XamlLoader c++ code, and apparently, the only reason is to assign the
>  > surface to the loaded object. I believe that maybe it's better not to
>  > set this at Xaml Loading time. Maybe should be assigned when the
>  > object is added to a parent.
>  >
>  > Second question: Why AllowMultipleSurfacesPerDomain is handled within
>  > XamlLoader and why it's needed at all? Has MS Silverlight a concept
>  > similar for handling this?
>  >
>  > I am starting to understand the Moonlight internals, so please excuse
>  > me if I'm making dump questions.
>  >
>
>  This is not a dumb question, it's quite a complicated issue :)
>
>  The problem relies on the fact that in C# it is possible to do something
>  like this:
>
>  MediaElement me = new MediaElement ();
>  me.Source = "media/video.wmv";
>
>  Now how does the MediaElement resolve the relative url to a absolute URI? It
>  needs to know the URI of the base xaml or html file, so what we do in the
>  plugin/browser case is to store the Surface in AppDomain specific data, and
>  ensure we create a new AppDomain for every instance of the plugin in the
>  browser.
>
>  This trick doesn't work with LunarEclipse, since LE can have several
>  surfaces in each domain, so you have to specify the surface when loading
>  xaml.
>
>  One solution to this would be to delay downloading anything until the object
>  has been added to the xaml tree (and set the surface there), but that
>  doesn't work for the following code [1]:
>
>  Downloader dl = new Downloader ();
>  dl.Open ("GET", "media/video.wmv");
>  dl.Send ();
>
>  Now the downloader should start downloading, but there's no way the
>  Downloader can know how to resolve the relative url in LE, and it can only
>  work with the browser plugin if we store the surface in the AppDomain.
>
>  AllowMultipleSurfacesPerDomain is used to determine if a surface should be
>  stored in the AppDomain specific data area or not (if true, the surface is
>  not stored, since there may be several surfaces per AppDomain).
>
>  Silverlight does not have this concept, they do not have this problem since
>  SL doesn't need to allow multiple surfaces per domain (given that SL is
>  browser only they don't need to allow multiple surfaces per AppDomain).
>
>  I hope I made this a bit clearer, if you have other ideas about how to solve
>  this problem, feel free to expose them :)
>
>  Rolf
>
>  [1] Downloader isn't supported for C# in SL 2.0 anymore, it's replaced by
>  WebClient, but the problem remains.
>
>  > Manuel.
>  > _______________________________________________
>  > Moonlight-list mailing list
>  > Moonlight-list at lists.ximian.com
>  > http://lists.ximian.com/mailman/listinfo/moonlight-list
>  >
>  >
>  > --
>  > No virus found in this incoming message.
>  > Checked by AVG.
>  > Version: 7.5.524 / Virus Database: 269.23.2/1388 - Release Date:
>  > 20/04/2008 15:01
>
>
>



-- 
? Manuel Alejandro Cer?n Estrada
? ceronman at gmail.com
? http://ceronman.freaks-unidos.net

From toshok at gmail.com  Tue Apr 22 12:46:09 2008
From: toshok at gmail.com (Chris Toshok)
Date: Tue, 22 Apr 2008 09:46:09 -0700
Subject: [Moonlight-list] ff3 configure.ac
Message-ID: <d2ebeadd0804220946t112f24d7h15e2a2db96537a4e@mail.gmail.com>

Here's the configure.ac I was using for the ff2 + ff3 plugin bridge work I
started on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/moonlight-list/attachments/20080422/0ebb18cd/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: configure.ac
Type: application/octet-stream
Size: 15264 bytes
Desc: not available
Url : http://lists.ximian.com/pipermail/moonlight-list/attachments/20080422/0ebb18cd/attachment-0001.obj 

From Eric.Engler at zcsterling.com  Wed Apr 23 12:15:51 2008
From: Eric.Engler at zcsterling.com (Engler, Eric)
Date: Wed, 23 Apr 2008 12:15:51 -0400
Subject: [Moonlight-list] building moon without gtk
Message-ID: <6FE5B54E82FD4B4A93CD0D8730986CBB01A4A707@ATLEXCV01.zcs.corp>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


>To use Mono and Moonlight on embedded devices, you must obtain 
>a commercial license from mono-licensing at novell.com.

Wow, this changes my understanding of what Mono is all about. Is it only
Moonlight that requires a commercial license, or does that apply to Mono
as a whole?

Eric

-----BEGIN PGP SIGNATURE-----
Version: PGP Universal 2.6.2
Charset: US-ASCII

wsBVAwUBSA9gt8hfyUs+le7yAQhVKwgAjgaiYG9/WMwmO7pIbMBldKRs1TqTKJVh
WVrLPXg4wfMmRBEI1V227esXVsBygOX6EmxF7MuCffjbn9GlRhaWcwRF9kFsSVDS
jWUe+m+6bz8YXf0OYcKdK+BF+JeWlM/2SafQi+Tf9smQicc3cJhYd3fquHRJW/lb
bXNRvMNv8uu8etw4qQUxDMbfHTX0bl9W5PfEdzFJHIp+Sq8mYZmhHjI20JXek1K5
jUTlnoddgqpLWXkYGT1ISzrENY4X3XYY59BRWhrKNd3ivH6UQLg4zi2+XIZHGylu
Cl2YBWgKOmrRgvuhaIyPtOrc6e+R1NqFQjHBNf5w5Onm32BA9Wsb4Q==
=CZpN
-----END PGP SIGNATURE-----

From rustyhowell at gmail.com  Thu Apr 24 18:07:16 2008
From: rustyhowell at gmail.com (Rusty Howell)
Date: Thu, 24 Apr 2008 16:07:16 -0600
Subject: [Moonlight-list] Warning message for Windowless sites
Message-ID: <88d5f51b0804241507m220530b8gf5a98b3f1972da71@mail.gmail.com>

Miguel and I were chatting about the infamous windowless issue. We can't
support it in Firefox 2.
I think it would make us look bad if people using Firefox 2 try to go to
'windowless' websites and things don't work.

I think we should alert the user that the site may not work properly, much
like some sites (GMail) warn about Firebug if
they detect the Firebug plugin. Perhaps we should even suggest to the user
that they upgrade to Firefox 3.

Thoughts?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/moonlight-list/attachments/20080424/b530d3f6/attachment.html 

From debackerl at gmail.com  Fri Apr 25 06:16:20 2008
From: debackerl at gmail.com (Debacker)
Date: Fri, 25 Apr 2008 12:16:20 +0200
Subject: [Moonlight-list] building moon without gtk
In-Reply-To: <6FE5B54E82FD4B4A93CD0D8730986CBB01A4A707@ATLEXCV01.zcs.corp>
References: <6FE5B54E82FD4B4A93CD0D8730986CBB01A4A707@ATLEXCV01.zcs.corp>
Message-ID: <75751ca80804250316s76552a6ctadcea958224db66a@mail.gmail.com>

To answer to your question Eric:

*When do I need to obtain a license from Novell to the Mono Runtime?*
>
> We only require licensing for uses of Mono and Moonlight on embedded
> systems, or systems where you are unable to fulfill the obligations of the
> GNU LGPL.
>
> For example, if you manufacture a device where the end user is not able to
> do an upgrade of the Mono virtual machine or the Moonlight runtime from the
> source code, you will need a commercial license of Mono and Moonlight.
>
You can read more at http://mono-project.com/Licensing

Regards,
Laurent Debacker.

On Wed, Apr 23, 2008 at 6:15 PM, Engler, Eric <Eric.Engler at zcsterling.com>
wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
>
> >To use Mono and Moonlight on embedded devices, you must obtain
> >a commercial license from mono-licensing at novell.com.
>
> Wow, this changes my understanding of what Mono is all about. Is it only
> Moonlight that requires a commercial license, or does that apply to Mono
> as a whole?
>
> Eric
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGP Universal 2.6.2
> Charset: US-ASCII
>
> wsBVAwUBSA9gt8hfyUs+le7yAQhVKwgAjgaiYG9/WMwmO7pIbMBldKRs1TqTKJVh
> WVrLPXg4wfMmRBEI1V227esXVsBygOX6EmxF7MuCffjbn9GlRhaWcwRF9kFsSVDS
> jWUe+m+6bz8YXf0OYcKdK+BF+JeWlM/2SafQi+Tf9smQicc3cJhYd3fquHRJW/lb
> bXNRvMNv8uu8etw4qQUxDMbfHTX0bl9W5PfEdzFJHIp+Sq8mYZmhHjI20JXek1K5
> jUTlnoddgqpLWXkYGT1ISzrENY4X3XYY59BRWhrKNd3ivH6UQLg4zi2+XIZHGylu
> Cl2YBWgKOmrRgvuhaIyPtOrc6e+R1NqFQjHBNf5w5Onm32BA9Wsb4Q==
> =CZpN
> -----END PGP SIGNATURE-----
> _______________________________________________
> Moonlight-list mailing list
> Moonlight-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/moonlight-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/moonlight-list/attachments/20080425/02dbe41a/attachment.html 

From rolflists at ya.com  Fri Apr 25 08:27:38 2008
From: rolflists at ya.com (Rolf Bjarne Kvinge)
Date: Fri, 25 Apr 2008 14:27:38 +0200
Subject: [Moonlight-list] Warning message for Windowless sites
In-Reply-To: <88d5f51b0804241507m220530b8gf5a98b3f1972da71@mail.gmail.com>
References: <88d5f51b0804241507m220530b8gf5a98b3f1972da71@mail.gmail.com>
Message-ID: <02e101c8a6cf$dd5a41a0$980ec4e0$@com>

We might show a message covering the entire moonlight surface and which
disappears after a few seconds (something like the fullscreen message when
we go into fullscreen mode)

 

This way users will notice it for sure, and we won't break sites which work
even if they're windowless, since the message go away after a few seconds.

 

I think this is a wonderful idea, otherwise we'll get a lot of people
blaming us for something which is not our fault (and spend resources
figuring out what's wrong when people complain and/or file bugs).

 

Rolf

 

From: moonlight-list-bounces at lists.ximian.com
[mailto:moonlight-list-bounces at lists.ximian.com] On Behalf Of Rusty Howell
Sent: viernes, 25 de abril de 2008 0:07
To: moonlight-list at lists.ximian.com
Subject: [Moonlight-list] Warning message for Windowless sites

 

Miguel and I were chatting about the infamous windowless issue. We can't
support it in Firefox 2. 
I think it would make us look bad if people using Firefox 2 try to go to
'windowless' websites and things don't work.

I think we should alert the user that the site may not work properly, much
like some sites (GMail) warn about Firebug if 
they detect the Firebug plugin. Perhaps we should even suggest to the user
that they upgrade to Firefox 3.

Thoughts? 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/moonlight-list/attachments/20080425/7ca6cd88/attachment.html 

From rolflists at ya.com  Tue Apr 22 09:07:16 2008
From: rolflists at ya.com (Rolf Bjarne Kvinge)
Date: Tue, 22 Apr 2008 15:07:16 +0200
Subject: [Moonlight-list] XamlLoader and Surfaces
In-Reply-To: <796874fc0804212237i3b520633x4e7cf1f7ac84ec92@mail.gmail.com>
References: <796874fc0804212237i3b520633x4e7cf1f7ac84ec92@mail.gmail.com>
Message-ID: <017d01c8a479$ca6146f0$5f23d4d0$@com>

Hi Manuel,

> -----Original Message-----
> From: moonlight-list-bounces at lists.ximian.com [mailto:moonlight-list-
> bounces at lists.ximian.com] On Behalf Of Manuel Alejandro Cer?n Estrada
> Sent: martes, 22 de abril de 2008 7:38
> To: moonlight-list at lists.ximian.com
> Subject: [Moonlight-list] XamlLoader and Surfaces
> 
> Hi Guys.
> 
> I'm starting to work on Lunar Eclipse as part of the Google Summer of
> Code Program. The first problem I have encountered is that currently
> LE is broken. This exception is thrown:
> 
> Unhandled Exception: System.Exception: The surface where the xaml
> should be loaded is not set.
> 
> This is because somewhere in the code, this is called within a
> System.Windows.Controls.Control child:
> 
> ellipse = (Ellipse)InitializeFromXaml("<Ellipse Name=\"Ellipse\" />");
> 
> The exception is thrown because LE is an application with multiple
> surfaces (One for the canvas, another for the timeline, etc) and the
> Loader didn't know which surface to use.
> 
> I could easily fix this loading the ellipse using
> GtkSilver.InitializeFromXaml(). But this problem made me question
> about some of the Moonlight internals.
> 
> My first question is: Why a XamlLoader needs a Surface?
> 
> Looking at GtkSilver's code, the proper way to initialize an object
> when the application uses multiple surface is to specify the surface
> to the XamlLoader:
> 
> loader = XamlLoader.CreateManagedXamlLoader (surface, plugin);
> 
> The problem is that the Surface class is not exposed to C#, I believe
> that is not part of the Silverlight API. I don't know why this surface
> must be specified when loading the Xaml. I have been looking at the
> XamlLoader c++ code, and apparently, the only reason is to assign the
> surface to the loaded object. I believe that maybe it's better not to
> set this at Xaml Loading time. Maybe should be assigned when the
> object is added to a parent.
> 
> Second question: Why AllowMultipleSurfacesPerDomain is handled within
> XamlLoader and why it's needed at all? Has MS Silverlight a concept
> similar for handling this?
> 
> I am starting to understand the Moonlight internals, so please excuse
> me if I'm making dump questions.
> 

This is not a dumb question, it's quite a complicated issue :)

The problem relies on the fact that in C# it is possible to do something
like this:

MediaElement me = new MediaElement ();
me.Source = "media/video.wmv";

Now how does the MediaElement resolve the relative url to a absolute URI? It
needs to know the URI of the base xaml or html file, so what we do in the
plugin/browser case is to store the Surface in AppDomain specific data, and
ensure we create a new AppDomain for every instance of the plugin in the
browser.

This trick doesn't work with LunarEclipse, since LE can have several
surfaces in each domain, so you have to specify the surface when loading
xaml.

One solution to this would be to delay downloading anything until the object
has been added to the xaml tree (and set the surface there), but that
doesn't work for the following code [1]:

Downloader dl = new Downloader ();
dl.Open ("GET", "media/video.wmv");
dl.Send ();

Now the downloader should start downloading, but there's no way the
Downloader can know how to resolve the relative url in LE, and it can only
work with the browser plugin if we store the surface in the AppDomain.

AllowMultipleSurfacesPerDomain is used to determine if a surface should be
stored in the AppDomain specific data area or not (if true, the surface is
not stored, since there may be several surfaces per AppDomain). 

Silverlight does not have this concept, they do not have this problem since
SL doesn't need to allow multiple surfaces per domain (given that SL is
browser only they don't need to allow multiple surfaces per AppDomain).

I hope I made this a bit clearer, if you have other ideas about how to solve
this problem, feel free to expose them :)

Rolf

[1] Downloader isn't supported for C# in SL 2.0 anymore, it's replaced by
WebClient, but the problem remains.

> Manuel.
> _______________________________________________
> Moonlight-list mailing list
> Moonlight-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/moonlight-list
> 
> 
> --
> No virus found in this incoming message.
> Checked by AVG.
> Version: 7.5.524 / Virus Database: 269.23.2/1388 - Release Date:
> 20/04/2008 15:01



From rhowell at novell.com  Fri Apr 25 18:34:11 2008
From: rhowell at novell.com (Rusty Howell)
Date: Fri, 25 Apr 2008 16:34:11 -0600
Subject: [Moonlight-list] First Moonlight manual test run
Message-ID: <48125C63.5060109@novell.com>

Hey guys,

I just ran through our first run of the Moonlight manual test suite in
Testopia. I currently have 77 test cases that cover the sites listed on
the wiki, plus some more.  Here's the link, if you're interested.

https://bugzilla.novell.com/tr_show_run.cgi?run_id=6418

Here are the results of my run:
    openSuse 10.3 i686
    Firefox 2
    Moonlight r101821 (from the build bot)

    40 / 77 Passed   51.9%

Many tests (~ 30%) fail or are affected by the "windowless" issue. I
will be running this test suite again next week using Firefox 3, so
hopefully we'll see some improvement.  I also filed 12 new bugs today
that I found (2 regressions) and attached them to the test cases.

Have a great weekend!