<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: mozilla embedding overview &amp; meetup notes</title>
	<atom:link href="http://www.0xdeadbeef.com/weblog/2008/04/mozilla-embedding-overview-meetup-notes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.0xdeadbeef.com/weblog/2008/04/mozilla-embedding-overview-meetup-notes/</link>
	<description>I wuv you.</description>
	<lastBuildDate>Tue, 16 Mar 2010 12:00:37 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Between the Lines mobile edition</title>
		<link>http://www.0xdeadbeef.com/weblog/2008/04/mozilla-embedding-overview-meetup-notes/comment-page-1/#comment-140591</link>
		<dc:creator>Between the Lines mobile edition</dc:creator>
		<pubDate>Tue, 15 Jul 2008 11:53:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=359#comment-140591</guid>
		<description>[...] Chris Blizzard outlined some of the key facets of Mozilla&#8217;s embedding effort in April. He noted how it was imperative that Mozilla had a consistent story and approach for developers that wanted to embed its applications elsewhere. [...]</description>
		<content:encoded><![CDATA[<p>[...] Chris Blizzard outlined some of the key facets of Mozilla&#8217;s embedding effort in April. He noted how it was imperative that Mozilla had a consistent story and approach for developers that wanted to embed its applications elsewhere. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: blizzard</title>
		<link>http://www.0xdeadbeef.com/weblog/2008/04/mozilla-embedding-overview-meetup-notes/comment-page-1/#comment-135951</link>
		<dc:creator>blizzard</dc:creator>
		<pubDate>Tue, 01 Jul 2008 14:37:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=359#comment-135951</guid>
		<description>Martin - 

Did you want to post that to the .embedding newsgroup?</description>
		<content:encoded><![CDATA[<p>Martin &#8211; </p>
<p>Did you want to post that to the .embedding newsgroup?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Lütken</title>
		<link>http://www.0xdeadbeef.com/weblog/2008/04/mozilla-embedding-overview-meetup-notes/comment-page-1/#comment-135859</link>
		<dc:creator>Martin Lütken</dc:creator>
		<pubDate>Tue, 01 Jul 2008 07:39:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=359#comment-135859</guid>
		<description>I have tried incapsulating some of the core DOM interfaces into STL/stdc++ like ones. It seems to work pretty well. I have iterates for collections, lists and everywhere I use std::string. Also I have tried to mimic the javascript naming and interface as much as possible. So I return values instead of just the error result and so on. 

It is notcomplete but it is good enough for my purpose but perhaps the ideas could be used in this context. I also have had some wild toughts about whether itwould be possible to extens the XPIDL &quot;compiler&quot; to also generate those STL like interfaces automatically .</description>
		<content:encoded><![CDATA[<p>I have tried incapsulating some of the core DOM interfaces into STL/stdc++ like ones. It seems to work pretty well. I have iterates for collections, lists and everywhere I use std::string. Also I have tried to mimic the javascript naming and interface as much as possible. So I return values instead of just the error result and so on. </p>
<p>It is notcomplete but it is good enough for my purpose but perhaps the ideas could be used in this context. I also have had some wild toughts about whether itwould be possible to extens the XPIDL &#8220;compiler&#8221; to also generate those STL like interfaces automatically .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will&#8217;s Miro dev blog &#187; Blog Archive &#187; June 3rd chat &#8212; follow-up and some more answers</title>
		<link>http://www.0xdeadbeef.com/weblog/2008/04/mozilla-embedding-overview-meetup-notes/comment-page-1/#comment-127621</link>
		<dc:creator>Will&#8217;s Miro dev blog &#187; Blog Archive &#187; June 3rd chat &#8212; follow-up and some more answers</dc:creator>
		<pubDate>Wed, 04 Jun 2008 16:23:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=359#comment-127621</guid>
		<description>[...] really like to help Mozilla on their embedding efforts. I&#8217;d also really like to get more involved in gstreamer, Python 3000 and a bunch of other [...]</description>
		<content:encoded><![CDATA[<p>[...] really like to help Mozilla on their embedding efforts. I&#8217;d also really like to get more involved in gstreamer, Python 3000 and a bunch of other [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will&#8217;s Miro dev blog &#187; Blog Archive &#187; Miro hackfest in Boston</title>
		<link>http://www.0xdeadbeef.com/weblog/2008/04/mozilla-embedding-overview-meetup-notes/comment-page-1/#comment-122318</link>
		<dc:creator>Will&#8217;s Miro dev blog &#187; Blog Archive &#187; Miro hackfest in Boston</dc:creator>
		<pubDate>Thu, 22 May 2008 16:21:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=359#comment-122318</guid>
		<description>[...] out the fledgling Mozilla embedded API with the gtkx11 [...]</description>
		<content:encoded><![CDATA[<p>[...] out the fledgling Mozilla embedded API with the gtkx11 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jmdesp</title>
		<link>http://www.0xdeadbeef.com/weblog/2008/04/mozilla-embedding-overview-meetup-notes/comment-page-1/#comment-109246</link>
		<dc:creator>jmdesp</dc:creator>
		<pubDate>Fri, 02 May 2008 07:32:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=359#comment-109246</guid>
		<description>C vs. C++: You&#039;re talking about embedding here, so in some case that might mean going backwards in terms of compilers/tools wrt the standard today. Also when you need to integrate from a completely different language, binding problems can be huge. So it would be good if those who for some reason really need it could avoid using c++, like having a c interface for platform code and c++ for embedding.</description>
		<content:encoded><![CDATA[<p>C vs. C++: You&#8217;re talking about embedding here, so in some case that might mean going backwards in terms of compilers/tools wrt the standard today. Also when you need to integrate from a completely different language, binding problems can be huge. So it would be good if those who for some reason really need it could avoid using c++, like having a c interface for platform code and c++ for embedding.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dennis</title>
		<link>http://www.0xdeadbeef.com/weblog/2008/04/mozilla-embedding-overview-meetup-notes/comment-page-1/#comment-107301</link>
		<dc:creator>Dennis</dc:creator>
		<pubDate>Wed, 30 Apr 2008 10:38:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=359#comment-107301</guid>
		<description>In the light of extending the JS context. You might also want to add having the ability to add new XML languages (like XFORMS). In other words adding XTF support to the Embedding API. Right now you&#039;ll have to use the XPCOM Component Manager for that.</description>
		<content:encoded><![CDATA[<p>In the light of extending the JS context. You might also want to add having the ability to add new XML languages (like XFORMS). In other words adding XTF support to the Embedding API. Right now you&#8217;ll have to use the XPCOM Component Manager for that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Smoogen</title>
		<link>http://www.0xdeadbeef.com/weblog/2008/04/mozilla-embedding-overview-meetup-notes/comment-page-1/#comment-107048</link>
		<dc:creator>Stephen Smoogen</dc:creator>
		<pubDate>Tue, 29 Apr 2008 22:23:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=359#comment-107048</guid>
		<description>Oh if you go for the network stack and such... make sure you have an intelligent agent to keep track of each of the sub-agents. In some ways you end up with a miniature OS to make sure that your various &#039;stacks&#039; are operating correctly etc.</description>
		<content:encoded><![CDATA[<p>Oh if you go for the network stack and such&#8230; make sure you have an intelligent agent to keep track of each of the sub-agents. In some ways you end up with a miniature OS to make sure that your various &#8217;stacks&#8217; are operating correctly etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Smoogen</title>
		<link>http://www.0xdeadbeef.com/weblog/2008/04/mozilla-embedding-overview-meetup-notes/comment-page-1/#comment-106985</link>
		<dc:creator>Stephen Smoogen</dc:creator>
		<pubDate>Tue, 29 Apr 2008 19:23:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=359#comment-106985</guid>
		<description>Wow... that was like reading the design notes from Spyglass in 1996 or so.. They had gone through the wringer with Microsoft and Mozilla and were trying to figure out where to go. It was pretty much the same &#039;layout&#039; and such but a lot of the items were way ahead of the hardware/infrastructure at that time (having to craft their own widgets etc and build a TCP/IP stack because well the gasoline pump wouldn&#039;t have it.)</description>
		<content:encoded><![CDATA[<p>Wow&#8230; that was like reading the design notes from Spyglass in 1996 or so.. They had gone through the wringer with Microsoft and Mozilla and were trying to figure out where to go. It was pretty much the same &#8216;layout&#8217; and such but a lot of the items were way ahead of the hardware/infrastructure at that time (having to craft their own widgets etc and build a TCP/IP stack because well the gasoline pump wouldn&#8217;t have it.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
