<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Disqus - Friends of noahrichards</title><link>http://disqus.com/people/noahrichards/</link><description></description><language>en</language><lastBuildDate>Sat, 14 Nov 2009 11:41:14 -0000</lastBuildDate><item><title>Re: - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Nov-12-2.html#comment-23036500</link><description>Moonlight's engine (animation, graphics, video, audio) can be used either with a browser plugin, where a security sandbox is in effect or as a library that can be consumed by C/C++/C# applications.&lt;br&gt;&lt;br&gt;That being said, perhaps initially the video editor needs to run entirely on  the browser to reach more users (Mac and Windows users do not have Moonlight at this point).&lt;br&gt;&lt;br&gt;Silvelright and Moonlight both can request access to the file system in a secure way, this could be used temporarily for this purpose, or both could just do video editing over the web, or they could contact a local shell application that delivers the videos (tiny HTTP server used to serve files)  depending on how we want to handle the adoption piece we can pick one or the other.&lt;br&gt;&lt;br&gt;What I envision is that the result of encoding the video is actually a XAML file that lists all the sources and the times at which each video start playing, including transitions (using alpha channel changes, or in the future pixel shader effects) to produce the final video.&lt;br&gt;&lt;br&gt;The encoding from this to an actual set of files would have to be handled by Moonlight as we can make Moonlight run with an artificial clock (for example if you want to generate 60 fps, regardless of whether your computer can do 60 fps at the desired resolution).&lt;br&gt;&lt;br&gt;The output would be a list of frames, which can then be encoded by any third party encoder.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Sat, 14 Nov 2009 11:41:14 -0000</pubDate></item><item><title>Re: - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Nov-12-2.html#comment-23036496</link><description>Moonlight's engine (animation, graphics, video, audio) can be used either with a browser plugin, where a security sandbox is in effect or as a library that can be consumed by C/C++/C# applications.&lt;br&gt;&lt;br&gt;That being said, perhaps initially the video editor needs to run entirely on  the browser to reach more users (Mac and Windows users do not have Moonlight at this point).&lt;br&gt;&lt;br&gt;Silvelright and Moonlight both can request access to the file system in a secure way, this could be used temporarily for this purpose, or both could just do video editing over the web, or they could contact a local shell application that delivers the videos (tiny HTTP server used to serve files)  depending on how we want to handle the adoption piece we can pick one or the other.&lt;br&gt;&lt;br&gt;What I envision is that the result of encoding the video is actually a XAML file that lists all the sources and the times at which each video start playing, including transitions (using alpha channel changes, or in the future pixel shader effects) to produce the final video.&lt;br&gt;&lt;br&gt;The encoding from this to an actual set of files would have to be handled by Moonlight as we can make Moonlight run with an artificial clock (for example if you want to generate 60 fps, regardless of whether your computer can do 60 fps at the desired resolution).&lt;br&gt;&lt;br&gt;The output would be a list of frames, which can then be encoded by any third party encoder.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Sat, 14 Nov 2009 11:41:14 -0000</pubDate></item><item><title>Re: - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Nov-12-2.html#comment-22867905</link><description>I am just thinking that we need to look at applications that do not exist, are not complete or still require a lot of work ahead of them.&lt;br&gt;&lt;br&gt;Banshee seems pretty mature.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Thu, 12 Nov 2009 19:45:33 -0000</pubDate></item><item><title>Re: The future of Moonlight - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Nov-12-1.html#comment-22853312</link><description>Hello,&lt;br&gt;&lt;br&gt;Yes, this is already possible and available *today*.Just check out moon/examples for code that is actually compiled against the mscorlib 2.0 family of libraries.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Thu, 12 Nov 2009 15:21:11 -0000</pubDate></item><item><title>Re: - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Nov-12-2.html#comment-22852454</link><description>I cant wait to see this!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Thu, 12 Nov 2009 15:07:33 -0000</pubDate></item><item><title>Re: - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Nov-12-2.html#comment-22852362</link><description>I do not know who will pay for it.&lt;br&gt;&lt;br&gt;I am wondering if we could get enough companies/individuals interested in funding this activity?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Thu, 12 Nov 2009 15:07:08 -0000</pubDate></item><item><title>Re: - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Nov-12-2.html#comment-22852276</link><description>I agree 100%.&lt;br&gt;&lt;br&gt;This has been in the back of my mind since we started with Moonlight.   I might have even brought this up publicly.&lt;br&gt;&lt;br&gt;There are a couple of ways of doing this.   I would personally like to see Microsoft open source the OOXML SDK as that code would not only take care of loading/saving files in OOXML format, it would also provide a foundation on which to build the actual editing/rendering capabilities.   The office replacement could be built on top of the object model exposed.&lt;br&gt;&lt;br&gt;Microsoft today gives it away for free, but without access to the source code, or the rights to make changes, so it can not be used for Silverlight apps.    I think we need to keep asking Microsoft to opensource that library.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Thu, 12 Nov 2009 15:06:33 -0000</pubDate></item><item><title>Re: The future of Moonlight - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Nov-12-1.html#comment-22851895</link><description>Running NetFlix is not the problem, supporting the DRM system is.&lt;br&gt;&lt;br&gt;Microsoft licenses Play Ready for use on certain locked-down systems (like set top boxes, cell phones and other locked devices) but does not make it available in standard desktops, so this is a major challenge.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Thu, 12 Nov 2009 15:03:20 -0000</pubDate></item><item><title>Re: - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Nov-12-2.html#comment-22851810</link><description>Max, &lt;br&gt;&lt;br&gt;This is very intriguing!    I want to start working on the platform abstraction now that trunk has been opened to make sure that we can bring the Moonlight engine to multiple platforms, exactly for the purpose stated in your comment.&lt;br&gt;&lt;br&gt;I am also looking forward to what Microsoft will have to say about Silverlight 4;  Perhaps there is full alignment, perhaps not.  Only time will tell.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Thu, 12 Nov 2009 15:02:06 -0000</pubDate></item><item><title>Re: - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Nov-12-2.html#comment-22838784</link><description>Agreed.&lt;br&gt;&lt;br&gt;On a different note, I believe that we need a XAML editor (both Microsoft and us) that is cross platform.   Currently Blend is a windows-only technology and I bet Microsoft is going to have a hard time convincing Mac-loving designers to use Windows to create content for the web.&lt;br&gt;&lt;br&gt;So a Silverlight-based in-browser XAML designer seems to me like a choice that would benefit both Linux and Mac users.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Thu, 12 Nov 2009 13:18:19 -0000</pubDate></item><item><title>Re: Aleviating Memory Fragmentation in Mono - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Nov-09.html#comment-22826321</link><description>With the correction, it should:&lt;br&gt;&lt;br&gt;# alleviate - relieve: provide physical relief, as from pain; "This pill will relieve your headaches"&lt;br&gt;# alleviate - facilitate: make easier; "you could facilitate the process by sharing your knowledge"&lt;br&gt;wordnetweb.princeton.edu/perl/webwn&lt;br&gt;&lt;br&gt;# alleviation - relief: the feeling that comes when something burdensome is removed or reduced; "as he heard the news he was suddenly flooded with relief"&lt;br&gt;wordnetweb.princeton.edu/perl/webwn&lt;br&gt;&lt;br&gt;# alleviated - (of pain or sorrow) made easier to bear&lt;br&gt;wordnetweb.princeton.edu/perl/webwn&lt;br&gt;&lt;br&gt;# alleviation - easing: the act of reducing something unpleasant (as pain or annoyance); "he asked the nurse for relief from the constant pain"&lt;br&gt;wordnetweb.princeton.edu/perl/webwn&lt;br&gt;&lt;br&gt;# alleviate - To make less severe, as a pain or difficulty&lt;br&gt;en.wiktionary.org/wiki/alleviate</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Thu, 12 Nov 2009 10:38:27 -0000</pubDate></item><item><title>Re: Aleviating Memory Fragmentation in Mono - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Nov-09.html#comment-22784297</link><description>Fixed.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Wed, 11 Nov 2009 17:52:59 -0000</pubDate></item><item><title>Re: Mono Tools for Visual Studio - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Nov-10.html#comment-22706838</link><description>Yes;   We are working on it.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Wed, 11 Nov 2009 08:16:16 -0000</pubDate></item><item><title>Re: Mono Tools for Visual Studio - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Nov-10.html#comment-22638307</link><description>It currently only debugs XSP, not the module loaded with mod_mono;&lt;br&gt;&lt;br&gt;We are looking at debugging mod_mono for version 1.2</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Tue, 10 Nov 2009 17:31:46 -0000</pubDate></item><item><title>Re: Aleviating Memory Fragmentation in Mono - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Nov-09.html#comment-22633105</link><description>Right, your post contains a gratuitous attack on Mono.   You can go make those comments elsewhere.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Tue, 10 Nov 2009 16:18:34 -0000</pubDate></item><item><title>Re: Aleviating Memory Fragmentation in Mono - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Nov-09.html#comment-22473916</link><description>We agree, we are like Mickey Mouse: Known and loved by billions worldwide</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Mon, 09 Nov 2009 16:15:10 -0000</pubDate></item><item><title>Re: Aleviating Memory Fragmentation in Mono - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Nov-09.html#comment-22473753</link><description>Thanks for the link, that is an interesting idea!&lt;br&gt;&lt;br&gt;Mono's new compacting GC uses a similar setup: large objects are not allocated in the shared heap, they are tracked separately on the large object list (details are at &lt;a href="http://www.mono-project.com/Compacting_GC" rel="nofollow"&gt;www.mono-project.com/Compacting_GC&lt;/a&gt;)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Mon, 09 Nov 2009 16:12:19 -0000</pubDate></item><item><title>Re: Aleviating Memory Fragmentation in Mono - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Nov-09.html#comment-22466094</link><description>Right, the access performance would degrade slightly, as we need to lookup the chunk, before we dereference the pointer, not a lot of work.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Mon, 09 Nov 2009 14:39:03 -0000</pubDate></item><item><title>Re: - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2008/Nov-05.html#comment-22157730</link><description>Unity has a license agreement with Novell that grants them a commercial license.   Send me email, and I can put you in contact with the OEM licensing group that handles this.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Sat, 07 Nov 2009 18:40:43 -0000</pubDate></item><item><title>Re: - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2008/Nov-05.html#comment-21946855</link><description>Not necessarily;   But you have to distribute your object files and any other files necessary for the user to be able to relink the application when he upgrades or patches Mono on his own.&lt;br&gt;&lt;br&gt;If this is not suitable for you, you can buy a license from Novell for static linking that gives you the rights to the Mono runtime for commercial/non-LGPL use.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Thu, 05 Nov 2009 11:47:11 -0000</pubDate></item><item><title>Re: Introducing Debugging for MonoTouch - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Nov-04.html#comment-21900413</link><description>MacOS X should already have a working debugger, we just need to package it.&lt;br&gt;&lt;br&gt;But it should make it simpler to support debuggers in strange platforms.   You still want to have the hard debugger around, so a port would not hurt anyone.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Wed, 04 Nov 2009 19:41:08 -0000</pubDate></item><item><title>Re: 10 years of Ximian - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Oct-19.html#comment-20531477</link><description>The other day I found the business cards for "International Gnome Support" ;-)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Mon, 19 Oct 2009 16:08:02 -0000</pubDate></item><item><title>Re: Event mapping in MonoTouch - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Oct-15.html#comment-20194267</link><description>I have never heard of this problem in .NET, can you be more specific?&lt;br&gt;&lt;br&gt;But also keep in mind that there is an overloaded word in this post about delegates.   The C# delegates and the Objective-C delegate pattern.   Two different concepts that we blended together.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Fri, 16 Oct 2009 09:39:10 -0000</pubDate></item><item><title>Re: Event mapping in MonoTouch - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Oct-15.html#comment-20175769</link><description>The system works a little bit like that, but we wanted to keep objects lightweight, so if you do not use the C# event, you do not pay the price in memory use.&lt;br&gt;&lt;br&gt;To the programmer, it is transparent.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Thu, 15 Oct 2009 22:53:57 -0000</pubDate></item><item><title>Re: Git# - First Public Release - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Oct-12.html#comment-19989335</link><description>Bringing IKVM to the iPhone or Silverlight is likely a major effort;   So fewer dependencies using only the core of C# is a good idea. &lt;br&gt;&lt;br&gt;That way C# is not at a disadvantage.   &lt;br&gt;&lt;br&gt;That being said, jGit or C# GIT would be further along if you contributed code to either effort.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Tue, 13 Oct 2009 15:39:34 -0000</pubDate></item></channel></rss>