<?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"
	>
<channel>
	<title>Comments on: My Dream Way To Write A Firefox Extension</title>
	<atom:link href="http://www.azarask.in/blog/post/my-dream-way-to-write-a-firefox-extension/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.azarask.in/blog/post/my-dream-way-to-write-a-firefox-extension/</link>
	<description>-- aza &#124; ɐzɐ --</description>
	<pubDate>Thu, 11 Mar 2010 23:42:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Kelvin65</title>
		<link>http://www.azarask.in/blog/post/my-dream-way-to-write-a-firefox-extension/#comment-6031</link>
		<dc:creator>Kelvin65</dc:creator>
		<pubDate>Thu, 22 Oct 2009 14:59:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=397#comment-6031</guid>
		<description>Mark,It's not Google's fault that there's not a proper app. ,</description>
		<content:encoded><![CDATA[<p>Mark,It&#8217;s not Google&#8217;s fault that there&#8217;s not a proper app. ,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.azarask.in/blog/post/my-dream-way-to-write-a-firefox-extension/#comment-5308</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Fri, 01 May 2009 20:01:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=397#comment-5308</guid>
		<description>The biggest problem in extensions now is their disability to install without relaunching Firefox. I oftenn notice that it's takes too long time for me and that why I install the extencion only when I really really want it. 

Extensions could be like cookies. Any site should have possibility to install extension to your browser without relaunching browser. And you could allow or don't them to do it.

It could completely change the way how sites are built. For example, when you open gmail and allow their extension they could make special panel with a number of unread messages in your browser. They could add some buttons to firefox interface. Maybe it will be look much more like you opening desctop software. Firefox could transform interface from site to site adpting to what they need.</description>
		<content:encoded><![CDATA[<p>The biggest problem in extensions now is their disability to install without relaunching Firefox. I oftenn notice that it&#8217;s takes too long time for me and that why I install the extencion only when I really really want it. </p>
<p>Extensions could be like cookies. Any site should have possibility to install extension to your browser without relaunching browser. And you could allow or don&#8217;t them to do it.</p>
<p>It could completely change the way how sites are built. For example, when you open gmail and allow their extension they could make special panel with a number of unread messages in your browser. They could add some buttons to firefox interface. Maybe it will be look much more like you opening desctop software. Firefox could transform interface from site to site adpting to what they need.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Euge</title>
		<link>http://www.azarask.in/blog/post/my-dream-way-to-write-a-firefox-extension/#comment-4842</link>
		<dc:creator>Euge</dc:creator>
		<pubDate>Fri, 13 Mar 2009 19:47:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=397#comment-4842</guid>
		<description>Maybe it would be great to have an extension IDE or a visual-extension-creator-editor-etc"tor"...
I just finished a (2 hours!) GREAT session with Myk Melez and the guys/girls from the design challenge 2009! 
It was really a Bootcamp! (like the tittle of the session). I hope this will be available in a more "easy" way for the not-so-developer people (some code is always necessarily).

Greeting from Argentina!

pd:sorry about my english :-)</description>
		<content:encoded><![CDATA[<p>Maybe it would be great to have an extension IDE or a visual-extension-creator-editor-etc&#8221;tor&#8221;&#8230;<br />
I just finished a (2 hours!) GREAT session with Myk Melez and the guys/girls from the design challenge 2009!<br />
It was really a Bootcamp! (like the tittle of the session). I hope this will be available in a more &#8220;easy&#8221; way for the not-so-developer people (some code is always necessarily).</p>
<p>Greeting from Argentina!</p>
<p>pd:sorry about my english :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.azarask.in/blog/post/my-dream-way-to-write-a-firefox-extension/#comment-4841</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Fri, 13 Mar 2009 10:52:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=397#comment-4841</guid>
		<description>A rebellious thought. What if the entire chrome was actually a website, e.g. chrome.mozilla.org? The browser would be just a rendering engine, and the first thing it would do when loaded is display http://chrome.mozilla.org which contains the address bar, menus, etc. The actual websites would be something like iFrames inside this chrome.

Firefox extension development would then be similar to programming Facebook applications, i.e. they would be hosted on the Mozilla website. You can imagine perhaps having your own chrome at http://chrome.mozilla.org/users/{userid} which could be modified by the user via a web-based front end. Or even creating your own chrome at your own domain! What's more, you could even get a webkit or IE-based browser to display the Firefox chrome just by pointing it to your chrome URL. Any computer you connected to would then have access to your favourites, options etc just by using your chrome - as per Weave, but simpler.</description>
		<content:encoded><![CDATA[<p>A rebellious thought. What if the entire chrome was actually a website, e.g. chrome.mozilla.org? The browser would be just a rendering engine, and the first thing it would do when loaded is display <a href="http://chrome.mozilla.org" rel="nofollow">http://chrome.mozilla.org</a> which contains the address bar, menus, etc. The actual websites would be something like iFrames inside this chrome.</p>
<p>Firefox extension development would then be similar to programming Facebook applications, i.e. they would be hosted on the Mozilla website. You can imagine perhaps having your own chrome at <a href="http://chrome.mozilla.org/users/" rel="nofollow">http://chrome.mozilla.org/users/</a>{userid} which could be modified by the user via a web-based front end. Or even creating your own chrome at your own domain! What&#8217;s more, you could even get a webkit or IE-based browser to display the Firefox chrome just by pointing it to your chrome URL. Any computer you connected to would then have access to your favourites, options etc just by using your chrome - as per Weave, but simpler.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc Diethelm</title>
		<link>http://www.azarask.in/blog/post/my-dream-way-to-write-a-firefox-extension/#comment-4772</link>
		<dc:creator>Marc Diethelm</dc:creator>
		<pubDate>Thu, 05 Mar 2009 07:09:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=397#comment-4772</guid>
		<description>Mozilla the platform... There have been lots of discussions about this in recent years and the Mozilla team pretty much decided to focus on the browser. Which was probably a good move too. But it also explains why XUL has never been spec'ed, versioned and made complete. IMO that's were the focus, in terms of extension development (application development really), on Gecko should be: Create a version of XUL that lends itself to the building of any app (not only a browser), that provides a consistent layout on different OSs (without CSS hacking). Other things I woud consider very beneficial: an extended FUEL library and jQuery for Gecko (yes!).

I'll say it again: XUL 1.0 and jQuery for Gecko!!

That's just from the top of my hat, I'm at work.. ;)</description>
		<content:encoded><![CDATA[<p>Mozilla the platform&#8230; There have been lots of discussions about this in recent years and the Mozilla team pretty much decided to focus on the browser. Which was probably a good move too. But it also explains why XUL has never been spec&#8217;ed, versioned and made complete. IMO that&#8217;s were the focus, in terms of extension development (application development really), on Gecko should be: Create a version of XUL that lends itself to the building of any app (not only a browser), that provides a consistent layout on different OSs (without CSS hacking). Other things I woud consider very beneficial: an extended FUEL library and jQuery for Gecko (yes!).</p>
<p>I&#8217;ll say it again: XUL 1.0 and jQuery for Gecko!!</p>
<p>That&#8217;s just from the top of my hat, I&#8217;m at work.. ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Bradley</title>
		<link>http://www.azarask.in/blog/post/my-dream-way-to-write-a-firefox-extension/#comment-4767</link>
		<dc:creator>Jonathan Bradley</dc:creator>
		<pubDate>Thu, 05 Mar 2009 02:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=397#comment-4767</guid>
		<description>I would personally like to see a better framework that could integrate with eclipse, dreamweaver, textmate or maybe a visual editor.</description>
		<content:encoded><![CDATA[<p>I would personally like to see a better framework that could integrate with eclipse, dreamweaver, textmate or maybe a visual editor.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dr. Pain</title>
		<link>http://www.azarask.in/blog/post/my-dream-way-to-write-a-firefox-extension/#comment-4761</link>
		<dc:creator>Dr. Pain</dc:creator>
		<pubDate>Wed, 04 Mar 2009 20:57:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=397#comment-4761</guid>
		<description>I'm not sure why you're targeting any sort of "code" as the ideal extension development environment.  Most extensions are trying to make the browser/web sites/a particular web site look or behave differently.  Some kind of visual editor seems like a more powerful solution -- edit the website (your browser) to your liking and then automatically create the extension that gives you that functionality.  Platypus goes a little ways down this road but is limited by using Greasemonkey for implementation.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure why you&#8217;re targeting any sort of &#8220;code&#8221; as the ideal extension development environment.  Most extensions are trying to make the browser/web sites/a particular web site look or behave differently.  Some kind of visual editor seems like a more powerful solution &#8212; edit the website (your browser) to your liking and then automatically create the extension that gives you that functionality.  Platypus goes a little ways down this road but is limited by using Greasemonkey for implementation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nils Maier</title>
		<link>http://www.azarask.in/blog/post/my-dream-way-to-write-a-firefox-extension/#comment-4760</link>
		<dc:creator>Nils Maier</dc:creator>
		<pubDate>Wed, 04 Mar 2009 19:35:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=397#comment-4760</guid>
		<description>Most extensions are already a combination of javascript + xul + css (and sometimes some xbl).
Throw in some dtd/properties files if you want some l10n and you're done.
There is only a handful of extensions that actually uses C++.

So it is already pretty "webby" on the implementation side.

I say the way to go is simply to provide more FUEL-like APIs. Including jquery would be a great thing to do, however it has to be determined how much it might interfere with existing (extension) code.
The shared "namespace" is still a major obstacle.
Wladimir posted an article about some ways to overcome it recently, and it shows that it's actually still not exactly easy:
http://adblockplus.org/blog/avoiding-naming-conflicts-in-overlays

As for the packaging part: In my opinion it isn't that hard. 
Installation manifests and Chrome manifests are fairly well documented on AMO and the actual packaging is as easy as zipping the whole into an archive (or two if you want chrome.jar)
There are some issues, but most likely only "advanced" extensions will encounter those. Like window icons must be in chrome/icons and may not be jar'ed.

A major area which isn't addressed by your proposal at all is l10n.

In conclusion: Seems like a nice idea, however in my opinion the existing extensions "system" should be enhanced before thinking about an "extensions-light" variant (FUEL-like APIs, more documentation especially on how to achieve common tasks).</description>
		<content:encoded><![CDATA[<p>Most extensions are already a combination of javascript + xul + css (and sometimes some xbl).<br />
Throw in some dtd/properties files if you want some l10n and you&#8217;re done.<br />
There is only a handful of extensions that actually uses C++.</p>
<p>So it is already pretty &#8220;webby&#8221; on the implementation side.</p>
<p>I say the way to go is simply to provide more FUEL-like APIs. Including jquery would be a great thing to do, however it has to be determined how much it might interfere with existing (extension) code.<br />
The shared &#8220;namespace&#8221; is still a major obstacle.<br />
Wladimir posted an article about some ways to overcome it recently, and it shows that it&#8217;s actually still not exactly easy:<br />
<a href="http://adblockplus.org/blog/avoiding-naming-conflicts-in-overlays" rel="nofollow">http://adblockplus.org/blog/avoiding-naming-conflicts-in-overlays</a></p>
<p>As for the packaging part: In my opinion it isn&#8217;t that hard.<br />
Installation manifests and Chrome manifests are fairly well documented on AMO and the actual packaging is as easy as zipping the whole into an archive (or two if you want chrome.jar)<br />
There are some issues, but most likely only &#8220;advanced&#8221; extensions will encounter those. Like window icons must be in chrome/icons and may not be jar&#8217;ed.</p>
<p>A major area which isn&#8217;t addressed by your proposal at all is l10n.</p>
<p>In conclusion: Seems like a nice idea, however in my opinion the existing extensions &#8220;system&#8221; should be enhanced before thinking about an &#8220;extensions-light&#8221; variant (FUEL-like APIs, more documentation especially on how to achieve common tasks).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Fitchet</title>
		<link>http://www.azarask.in/blog/post/my-dream-way-to-write-a-firefox-extension/#comment-4741</link>
		<dc:creator>Scott Fitchet</dc:creator>
		<pubDate>Wed, 04 Mar 2009 05:19:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=397#comment-4741</guid>
		<description>Aza ... thanks for doing this. Would love to see your XUL notes from the last jQuery conference.

How would I get something like JSON feed data into this URL bar .... http://www.figital.com/xul ?</description>
		<content:encoded><![CDATA[<p>Aza &#8230; thanks for doing this. Would love to see your XUL notes from the last jQuery conference.</p>
<p>How would I get something like JSON feed data into this URL bar &#8230;. <a href="http://www.figital.com/xul" rel="nofollow">http://www.figital.com/xul</a> ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Quickredfox</title>
		<link>http://www.azarask.in/blog/post/my-dream-way-to-write-a-firefox-extension/#comment-4738</link>
		<dc:creator>Quickredfox</dc:creator>
		<pubDate>Tue, 03 Mar 2009 19:53:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=397#comment-4738</guid>
		<description>What's wrong with using greasemonkey + the user script compiler (http://arantius.com/misc/greasemonkey/script-compiler)? I mean, you did say it's the compiling and stuff that get complicated... how about edit-script-and-refresh-page? Coz that's what you get with greasemonkey</description>
		<content:encoded><![CDATA[<p>What&#8217;s wrong with using greasemonkey + the user script compiler (http://arantius.com/misc/greasemonkey/script-compiler)? I mean, you did say it&#8217;s the compiling and stuff that get complicated&#8230; how about edit-script-and-refresh-page? Coz that&#8217;s what you get with greasemonkey</p>
]]></content:encoded>
	</item>
</channel>
</rss>
