Prism 0.9 - Now as a Firefox Extension

Prism 0.9 has finally been released. Getting platform specific features to work on 3 platforms really is harder than it looks. A big thank you to Matt Gertner (plasticmillion) and Fredrik Larsson (nossralf) for all the work they did on this release.

The big news for this release is Prism for Firefox, a full blown Prism and a Firefox extension all in one. This means that you can now easily “make” web applications directly from Firefox. In addition, Prism now uses Firefox as its runtime, so you don’t need to download the XULRunner runtime. Yes, I have mentioned in the past that Firefox 3 will be able to run XUL applications. Here are some things the extension can do:

  • Allow you to manually convert a website into a Prism-ified web application.
  • Detect a web application bundle embedded on a website and prompt the user to install it.

The standalone version of Prism is still available. Download it from here: Windows (installer, archive), Mac and Linux.

Here is a quick list of Prism changes (extension and standalone):

  • We separated web applications into isolated processes, with isolated profile data.
  • Web application icon support via favicon or custom image. You can now choose the image used to represent a web application on the desktop.
  • We also added some platform specific features. Some, like “popup notifications” (all platforms) and “dock badging” (OS X) can be used via a custom webapp.js (more in a followup post). Others like “minimize to tray”, are not quite ready on all platforms. So we are holding off exposing those until the next release.
  • We fixed a lot of bugs and probably added a bunch different ones.

Now that we have a good foundation for platform features (and people who know more about Linux and OS X than me), we can start adding a few more goodies. Here are a list of things we are working on for the next release:

  • Minimize to tray support. The basics are in there now, but we have more work to do.
  • Context menu support for dock and tray. Again, we are close to having this working.
  • Support for a web content JS API so the web application itself can access some of the platform features. See bug 420661 for more information.
  • Simplified methods of embedding web application information into a website. Currently, the Prism extension uses a webapp bundle, but this can be made easier for web application authors. See bug 420878 for more information.

We are eager to hear more, so let us know what you think: