Site Specific Browser – Using WebRunner

I have been using the prototype WebRunner for a few days to access GMail and Zimbra. Overall, I am quite happy with the results. The webapps load fast and I like having them appear in my ALT+TAB list. I am using Firefox for browsing and not running webapps, which feels better too. Firefox stays snappy and I have not had to “kill” its process because of speed or hung webapp problems.

Of course there are things I miss when using WebRunner. Most notably:

  • Support for popup windows – Zimbra in particular uses (my preference) a popup to compose email.
  • Support for inline spell checking – Some webapps do have their own spellcheck support, but I really love Firefox’s system.
  • Support for float-over link destinations in the statusbar – Yes, I like to see where I am going if I click that link.
  • Support for a context menu – I use it infrequently, but I must use it enough to feel weird when its not there.

Adding support for popups turned out to be a 1-line preference fix. I learned about nsIXULBrowserWindow to get the link info in the statusbar. I updated the prototype for those of you playing at home:

Install (Windows-only): webrunner-setup-0.3.exe

Next up for WebRunner:

  • Adding support for inline spellcheck and suggestions on context menu.
  • Enabling extension support so WebRunner can be tweaked or enhanced.
  • Creating an “installer” so new webapps can be installed after the fact.
  • Creating an extension to allow Firefox to “install” webapps since most of this process starts in the browser.

11 Replies to “Site Specific Browser – Using WebRunner”

  1. I would love to see the ability to use CTRL + (+/-) like in Firefox so I can zoom the text since I am partially sighted.

  2. So Mozilla finally employs a couple of Developer Relations guys and one goes off on a anti-web tangent like single-site browsers. How is FUEL going Mark? ETA?

  3. Love this idea, here are a couple of bugs/thoughts:

    I get an XML error trying to download attachments from gmail.

    I’d like each window to have it’s own session. It would be really useful to have multiple gmail windows open to multiple accounts.

  4. For few months now I’ve been doing something “similar” to webrunner, but with Firefox.

    I have profiles in Firefox for some websites (gmail, google reader…) and launch them with “-no-remote -P someprofile” command line arguments (I have shortcuts for these in my desktop). This gives me possibility to use normal Firefox extensions and inline spell checking. Unfortunately links open in same window, but I don’t mind that much. I also use modified firesomething extension (modified so that it installs with firefox 2 also) in these profiles to change the title of the window to Gmail or something.

    Maybe this is a bit harder to use than webrunner (I don’t know, I haven’t checked webrunner), but it gives me same possibilities as webrunner currently.

  5. I don’t get the idea of WebRunner? I don’t know if a browser-based web app in a separate process is enough bang-for-the-buck?

    I thought this is what XULRunner was for? Use XUL to create a richer UI. Take advantage of the whole Mozilla platform. Is just slamming an app into a separate process worth the trouble unless it adds some significant value-add?

    And I think “Site Specific Browser” is not the best name either. We’re talking about applications here right? Not websites. And we’re talking about interacting with the application, not “browsing”.

    Ideally there would be room for all of these things, but it would be nice to see some clearer communication from Mozilla about what their strategy is for some of these endeavors. Especially with tough competition soon to be coming from one of the “adversaries” Adobe Apollo. 🙂

  6. To get popups working, use this preference:
    pref(“browser.chromeURL”, “chrome://application/content/browser.xul”);

    of course point it to your own browser xul file.

  7. Joshua – It will be in the next version. Thanks.

    pd – I don’t see it as anti-web, but rather better web application user experience. FUEL is getting reviewed for landing on the trunk. It can be viewed using

    Nick – I’ll try to get that fixed in the next version. Thanks.

    pn – Good idea. I do think the browser could be made to work better with webapps. A separate browser, like WebRunner, is not the only solution.

    enefekt – WebRunner is just an experiment, not a strategy or even a product. Web Runner *is* built on XULRunner. Part of WebRunner’s experiment is to show how XULRunner apps can be used in place of Apollo apps.

    therealpete – Yep, that is how I added popup support to this version.

  8. “WebRunner is just an experiment, not a strategy or even a product. Web Runner *is* built on XULRunner”

    OK, Alright, but thats the thing. This doesn’t seem like a good demo/experiment to show off XULRunner with. If you’re just adding a separate process to the mix, and mimicking the exact same experience and interface as a general web browser, it seems more confusing than interesting.

    I liked your XUL Explorer better. Why not integrate the MDC references better with the editing process. That would be cool.

    Some of the Apollo demos showed Google maps integration with your local address book, and merging your music library with flickr and wikipedia. Maybe not as practical and down to earth as keeping gmail up when your browser crashes, but it shows off the possibilites, and gets you thinking,

  9. >This doesn’t seem like a good demo/experiment to show off XULRunner with

    IMO this is a great use of XULRunner! I needed just this type of application to try to get ride of IE in a company Intranet. The issue is not allowing the user to surf the web because of security issues and to keep the support calls lower for non-technical users. And yes, I can (and did because I came across this too late for my client.) lock down IE but that was using a lot of registry settings and then it still is not a complete solution. I would have rather suggested using this.

    Thanks, this is GREAT little example of what XULRunner can do.

Comments are closed.