Looks like I’m getting a lot of traffic looking for a Bloglines webapp. So, why not:
Bloglines.webapp

While I’m at it, here are a couple of other webapps I’ve cobbled together, I’ll appologize in advance for the low quality of the icons on all of these…
Google Page Creator Webapp
Google Webmaster Tools Webapp

At this point I should probably include a warning, so – keep in mind while running these webapps with WebRunner, that WebRunner itself is still a in pre-release/beta stages. Which means that the webapps found on this site, while working to view sites and what not, are not intended to be a replacement for your standard browser. The websites you’ll be viewing were not designed to be used with WebRunner, and therefore not all features on these sites may be compatible with it. I claim no responsibility for any malfunctions related to WebRunner. I’m providing files that allow you to access some websites, nothing more. Feel free to use the webapp files found on this site, but keep in mind you’re using them at your own risk – and without warranty!

Here are two more webapp files that should make life a little more easy for anyone trying to use WebRunner.

About:Config.Webapp

This webapp is for displaying the chrome about:config URI. This makes it a hell of a lot easier to modify the configuration (especially when adding a proxy for those of us trying to use this stuck behind a proxy).

Use this webapp to edit important settings such as:

• Cookies Rules
• Proxy Settings
• Pipelining Rules
• Password Rules

For more information on directly editing the about:config click here. For more on individual settings (for instance, figuring out which settings to add back in – like the afore mentioned proxy settings), click here.

Extensions.Webapp

This is the second webapp which gives access to WebRunner’s extensions panel. The thing about either one of these webapps (and WebRunner in general) is that you access each one separately – that is to say each gets launched as it’s own application – but any changes in either one affects any other webapp you might be running with WebRunner.

Now the only thing we need is for extensions to be modified and made available for WebRunner (like Lifehacker’s Better Gmail). There are ways to hack extensions to allow them to run in WebRunner, but that’s for another post.

Links:

Webapps:

• About:Config.Webapp
• Extensions.Webapp

Offsite References:

• Firefox Help: Editing Configuration Files
• mozillaZine: About:config entries

Other:

• Lifehacker
• Better Gmail

Disclaimer

Keep in mind while running these webapps with WebRunner, that WebRunner itself is still a in pre-release/beta stages. Which means that the webapps found on this site, while working to view sites and what not, are not intended to be a replacement for your standard browser. The websites you’ll be viewing were not designed to be used with WebRunner, and therefore not all features on these sites may be compatible with it. I claim no responsibility for any malfunctions related to WebRunner. I’m providing files that allow you to access some websites, nothing more. Feel free to use the webapp files found on this site, but keep in mind you’re using them at your own risk – and without warranty!

UPDATE – 071010 – after further testing I found a couple of errors in my original webapp file. So, I’ve updated the icon and a couple other things and reposted. Enjoy!

Over at Lifehacker they’ve posted about the standalone Mozilla based WebRunner. WebRunner is, well I’ve pretty much been over that already. The point is, you can launch a webapp from a standalone program, allowing you to do things without getting distracted by all that… extra web. I really like this concept, I now have links for Gmail, Google Reader, and all those other nifty web 2.0 apps I like.

I wanted to give this a try myself, so I’ve made a standalone Wikipedia launcher. Get it here. It’s a launcher for the Wikipedia’s English main page.

Make your own! It’s dead simple! All you do is install the WebRunner software, create an ini file for your app, create icons and zip these files together. Rename the zip file to your.webapp and your good to go!

There’s a couple of worrying things about the webapp files – from a security standpoint. The biggest of these is that you can include a js file with javascript that runs at an application level. In other words it has access to everything that the application has access to, like – oh I don’t know – the file system?! (in my best Church Lady voice – oh crap am I revealing my age!). Another is the fact that you’re using a zip format to distribute the rest of your files. Which of course can have it’s own security problems when used with other programs. You also don’t really have the ability to get at a lot of the standard Mozilla settings that WebRunner shares. So you can’t make adjustments to settings for cookies, passwords and the like.

At any rate, it’s still a relatively young application, so I’m sure they’ll get the security issues addressed, but for now, make sure you inspect those files before you run them!

Links:
WebRunner
Lifehacker post
My Wikipedia launcher

Disclaimer

Keep in mind while running these webapps with WebRunner, that WebRunner itself is still a in pre-release/beta stages. Which means that the webapps found on this site, while working to view sites and what not, are not intended to be a replacement for your standard browser. The websites you’ll be viewing were not designed to be used with WebRunner, and therefore not all features on these sites may be compatible with it. I claim no responsibility for any malfunctions related to WebRunner. I’m providing files that allow you to access some websites, nothing more. Feel free to use the webapp files found on this site, but keep in mind you’re using them at your own risk – and without warranty!