Comments on: What If… It Was Easy To Write Firefox Extensions http://www.azarask.in/blog/post/what-if-it-was-easy-to-write-firefox-extensions/ -- aza | ɐzɐ -- Thu, 18 Mar 2010 23:36:10 +0000 http://wordpress.org/?v=2.6.5 By: 深入Ubiquity | Hal Guo http://www.azarask.in/blog/post/what-if-it-was-easy-to-write-firefox-extensions/#comment-6518 深入Ubiquity | Hal Guo Fri, 27 Nov 2009 07:03:09 +0000 http://azarask.in/blog/?p=63#comment-6518 [...] 我们发现开发Firefox扩展是费时费力的. 为浏览体验添加一个新特性,竟然还要重启浏览器, 这实在是太过时了. 讽刺的是, 整个互联网都属于push模型, 但是浏览器, [...] [...] 我们发现开发Firefox扩展是费时费力的. 为浏览体验添加一个新特性,竟然还要重启浏览器, 这实在是太过时了. 讽刺的是, 整个互联网都属于push模型, 但是浏览器, [...]

]]> By: Aubrey http://www.azarask.in/blog/post/what-if-it-was-easy-to-write-firefox-extensions/#comment-4202 Aubrey Wed, 25 Feb 2009 17:25:21 +0000 http://azarask.in/blog/?p=63#comment-4202 If FF did something like this, it would virally reinvent the web. Especially if that same power could work through prism on the desktop to trigger things not conventially thought of controllable via web scripting. I'm an old school Amiga guy, and I remember when just about anything could be scripted with AREXX. If FF did something like this, it would virally reinvent the web. Especially if that same power could work through prism on the desktop to trigger things not conventially thought of controllable via web scripting. I’m an old school Amiga guy, and I remember when just about anything could be scripted with AREXX.

]]> By: Simply extending the browser « chimney http://www.azarask.in/blog/post/what-if-it-was-easy-to-write-firefox-extensions/#comment-2985 Simply extending the browser « chimney Wed, 10 Dec 2008 06:43:20 +0000 http://azarask.in/blog/?p=63#comment-2985 [...] simpler way to extend Firefox must be possible. As Aza Raskin suggested a long time ago, imagine if displaying an “Hello world!” alert box was this simple: [...] [...] simpler way to extend Firefox must be possible. As Aza Raskin suggested a long time ago, imagine if displaying an “Hello world!” alert box was this simple: [...]

]]> By: Aza’s Thoughts » Ubiquity In Depth http://www.azarask.in/blog/post/what-if-it-was-easy-to-write-firefox-extensions/#comment-2386 Aza’s Thoughts » Ubiquity In Depth Tue, 26 Aug 2008 19:44:54 +0000 http://azarask.in/blog/?p=63#comment-2386 [...] and time-consuming to write extensions to Firefox. There is something largely last-decade about requiring restarts to add a new feature to your browsing experience. It’s ironic that the entire Web is on a push [...] [...] and time-consuming to write extensions to Firefox. There is something largely last-decade about requiring restarts to add a new feature to your browsing experience. It’s ironic that the entire Web is on a push [...]

]]> By: Aaron Johnson – Links: 8-9-2008 http://www.azarask.in/blog/post/what-if-it-was-easy-to-write-firefox-extensions/#comment-2224 Aaron Johnson – Links: 8-9-2008 Sun, 10 Aug 2008 08:48:11 +0000 http://azarask.in/blog/?p=63#comment-2224 [...] Aza’s Thoughts » What If… It Was Easy To Write Firefox Extensions Quote (from the comments): I think a low tolerance for pain is critical when designing systems for other people. (categories: extensions ui programming plugins ux ) [...] [...] Aza’s Thoughts » What If… It Was Easy To Write Firefox Extensions Quote (from the comments): I think a low tolerance for pain is critical when designing systems for other people. (categories: extensions ui programming plugins ux ) [...]

]]> By: Aza’s Thoughts » Sharing Streamable Functionality http://www.azarask.in/blog/post/what-if-it-was-easy-to-write-firefox-extensions/#comment-1991 Aza’s Thoughts » Sharing Streamable Functionality Wed, 23 Jul 2008 21:46:28 +0000 http://azarask.in/blog/?p=63#comment-1991 [...] ones) and add-ons are available as static XPIs. There is something largely last-decade about requiring restarts to add a new feature to your browsing experience. It’s ironic that the entire Web is on a [...] [...] ones) and add-ons are available as static XPIs. There is something largely last-decade about requiring restarts to add a new feature to your browsing experience. It’s ironic that the entire Web is on a [...]

]]> By: links for 2008-07-02 « Breyten’s Dev Blog http://www.azarask.in/blog/post/what-if-it-was-easy-to-write-firefox-extensions/#comment-1856 links for 2008-07-02 « Breyten’s Dev Blog Wed, 02 Jul 2008 11:32:17 +0000 http://azarask.in/blog/?p=63#comment-1856 [...] What If… It Was Easy To Write Firefox Extensions (tags: firefox) [...] [...] What If… It Was Easy To Write Firefox Extensions (tags: firefox) [...]

]]> By: Sri Panyam http://www.azarask.in/blog/post/what-if-it-was-easy-to-write-firefox-extensions/#comment-1852 Sri Panyam Wed, 02 Jul 2008 01:24:58 +0000 http://azarask.in/blog/?p=63#comment-1852 This is not an outright solution, but in firefox one can set a couple of aprameters in the about:config page. When I do my extensions, it is only a matter of opening a new browser window and the changes to your extension sources kick in. Also this relies on you having a link from .mozilla/firefox/extensions/plugins/ to the real source folder of your but its a one of thing for development. Sorry I cannot recall the actual variables to be set, but these are documented in the firefox extension development documentation page. Cheers S This is not an outright solution, but in firefox one can set a couple of aprameters in the about:config page. When I do my extensions, it is only a matter of opening a new browser window and the changes to your extension sources kick in.

Also this relies on you having a link from .mozilla/firefox/extensions/plugins/ to the real source folder of your but its a one of thing for development.

Sorry I cannot recall the actual variables to be set, but these are documented in the firefox extension development documentation page.

Cheers
S

]]> By: Aza Raskin http://www.azarask.in/blog/post/what-if-it-was-easy-to-write-firefox-extensions/#comment-1513 Aza Raskin Mon, 02 Jun 2008 22:50:54 +0000 http://azarask.in/blog/?p=63#comment-1513 @Eric: I'm not sure if that holds for web-developers. We aren't used to long compile-time development practices. They aren't just inconvenient—they fundamentally change the fast modify-reload dev cycle. That said, I think you are right about needing to also focus on other areas that result in less need for specialized domain knowledge. @Eric: I’m not sure if that holds for web-developers. We aren’t used to long compile-time development practices. They aren’t just inconvenient—they fundamentally change the fast modify-reload dev cycle. That said, I think you are right about needing to also focus on other areas that result in less need for specialized domain knowledge.

]]> By: Eric Jung http://www.azarask.in/blog/post/what-if-it-was-easy-to-write-firefox-extensions/#comment-1490 Eric Jung Fri, 30 May 2008 16:07:50 +0000 http://azarask.in/blog/?p=63#comment-1490 Restarting an application during development is a common practice in many areas of software development (example: not all java application servers support hot deployment of code, and even the ones that do can be extremely flaky, resulting in frequent app server restarts). That's not to say restarts aren't barbaric, but it is a common theme. It's not a barrier-to-entry in terms of understanding and comprehension; it's merely an inconvenience. We should instead focus on simplifying other areas of extension development that result in less need for specialized domain knowledge (FUEL is a great start). Fixing development inconveniences like application restarts -- which many software developers are already accustomed to because of other programming environments -- will do nothing to reduce the current learning curve required to write one's first extension. Restarting an application during development is a common practice in many areas of software development (example: not all java application servers support hot deployment of code, and even the ones that do can be extremely flaky, resulting in frequent app server restarts).

That’s not to say restarts aren’t barbaric, but it is a common theme. It’s not a barrier-to-entry in terms of understanding and comprehension; it’s merely an inconvenience.

We should instead focus on simplifying other areas of extension development that result in less need for specialized domain knowledge (FUEL is a great start). Fixing development inconveniences like application restarts — which many software developers are already accustomed to because of other programming environments — will do nothing to reduce the current learning curve required to write one’s first extension.

]]>