I’ve been checking out the phenomenal NIN remix site and I thought to myself, wow how nice that a site that empowers you with the ability to take part in the musical experience - free of charge - is also a perfect candidate for a WebApp!

Included in this webapp are the source files for the icon I created using Paint.Net (so you can change the background color or make other changes if you’d like - just keeping within the remix/open culture vein) . Enjoy!

Remix - NIN Remix site

Remix.NIN-WebApp (let me know what you think!)

Prism/WebRunner

UPDATE AGAIN! 080611
I’ve made a new post on this subject cause it’s easier to update by adding new posts instead of updating this one. Enjoy!

Update!!
Had to add a comment to the replacement code below in order for this to work.

080404 Update!!
Yet again, code changes for new versions and what not.

Looks like Mozilla has added WebRunner to it’s Mozilla Labs line up and changed the name to Prism. From what they say, it’s going to be a cross between an open version of Adobe Air and Microsoft Silverlight and a localized lancher for web applications. Which, by my definition, is what utility computing is supposed to be like. Prism is currently for Windows only (they’d better hurry up with a Linux version), but it runs the same webapp files and also has added style sheet support - among other things - so you can style your webapps your way.

Anyway, I’ve been kind of discouraged by the lack of extension availability for WebRunner (and XulRunner for that matter). You’ll find in another of my posts a webapp for accessing the WebRunner extensions panel. Using this webapp, you can add new extensions (by installing or dropping them onto the panel), but at this point, adding extensions will fail because the version checking mechanism for WebRunner/XulRunner. To get around that, you need to change the extension’s compatibility information. These instructions will not work for every extension and your results will vary…

I recommend you find a smaller extension, download it and make the following changes:

1. Open the extension package (you can open it with 7-zip, ALzip, Winzip or any other archive program that works with zip files.
2. Extract and open the install.rdf with a text editor, I’d recommend Wordpad if your using windows.
3. Locate and change the following or something that looks like the following (this will vary by extension, but look for the Firefox description section - and you may find that you have to remove all references to all other Mozilla programs that the extension is compatible with for this to work):

<!--Firefox-->
<RDF:Description RDF:about="rdf:#$djS7s"
  em:id="{ec8030f7-c20a-464f-9b0e-13a3a9e97384}"
  em:minVersion="0.8"
  em:maxVersion="2.0.0.*" />

To:

<!--Webrunner-->
  <RDF:Description RDF:about="webrunner"
    em:id="webrunner@webapps.org"
    em:minVersion="0.1"
    em:maxVersion="10.0" />

or (again it will depend on which way the developer implemented the Firefox description):

<em:targetApplication>
  <!--Webrunner-->
  <Description>
    <em:id>webrunner@webapps.org</em:id>
    <em:minVersion>0.1</em:minVersion>
    <em:maxVersion>10.0</em:maxVersion>
  </Description>
</em:targetApplication>

If you’re using Prism, change to the following:

<RDF:Description RDF:about="prism"
  em:id="prism@developer.mozilla.org"
  em:minVersion="0.1"
  em:maxVersion="10.0" />

or

<em:targetApplication>
  <Description>
    <!--Prism-->
    <em:id>prism@developer.mozilla.org</em:id>
    <em:minVersion>0.1</em:minVersion>
    <em:maxVersion>10.0</em:maxVersion>
  </Description>
</em:targetApplication>

4. Then save the rdf file and add it back into the xpi archive.
5. You should be ready to install the extension using the Extensions.webapp

I found this parts of this bit of magic on Alex Sirota’s website along with the tip to check in the applicaiton.ini file for any XulRunner application’s ID. If you run into errors, then something is probably malformed in the rdf file so check that first. I won’t be much help in trouble shooting, and I’m not about to offer support for other peoples extensions on an unsupported application, but if you have problems, post a comment and I’ll give editing the rdf a go myself.

I’ve struck upon a way to make WebRunner (and by extension, any other XulRunner application) pretty much portable!

I’m no real programmer, I mean, I know enough to be dangerous. I’ve got a good handle on html, css, javascript, asp etc. In the past I’ve played with the source code for Portable Firefox from PortableApps.com trying to get XulRunner portable. I didn’t have much luck. Ran into too many code errors to resolve myself. What I needed was a way to make the program portable without programming anything new.

X-Launcher

What I was able to find was X-Launcher. X-Launcher is a nifty little app that allows you to launch just about any application portably - that is, without leaving much of a trace on the host computer. I’ve been able to use X-Launcher without too much effort (hey, just my style :).

You can get X-Launcher from winPenPack.com (downloads section) along with a host of other open source software all made portable using X-Launcher or other means. WinPenPack is an Italian website, but you can get English on most pages by choosing it from the language menu. Nice site and a lot of good software!
X-Launcher itself is an easy to use program, you simply configure the X-launcher.ini file for it and you’re ready to use it. One of the things that really sets X-Launcher apart is the fact that you can have multiple launchers in the same directory. Just rename the X-launcher.ini file and the X-launcher.exe to any name you wish (just as long as both have the same file name) and you can put a second set of exe/ini files with a different set of names in the same directory together. Why would you do this? Well, for one, this allows you to run multiple versions of a program with wildly different configurations. Another thing this buys you (and more relevant to this discussion) is the ability to launch different WebRunner apps portably.

Normally if you launch a program you can pass it options through command line switches. If you’re using another program to launch the application you want to run, then you don’t usually have the option of passing switches to the second program from the first. With X-Launcher, these switches are built into the configuration file.

The default configuration file that comes with X-Launcher is loaded with information on feature settings, but it’s also a bit overwhelming. Fortunately, if you run X-launcher.exe with no like-named ini file, it will create it’s own, scaled down X-launcher.ini. This configuration file is a heck of a lot easier to read!

There are several application variables that can be defined, the most important one being the application name. This will eventually point to folder names and the application itself. Here’s the contents of a X-launcher.ini for a webapp with included explanations for most settings:

wikipedia.ini

[Setup]
AppName=WebRunner
;Application name, this will also be used below as the
;name of some of the folders.

[FileToRun]
PathToExe=$AppName$\$AppName$.exe
;This is the name and path to the file you're trying to
;launch.
WorkingDir=%HOME%
;This is the name of the directory which will be used
;by the program as it's working directory.
Parameters= -webapp wikipedia@luckydisasters.com
;List of any parameters to pass to the application, in
;this case we're telling WebRunner to load the webapp
;"wikipedia@luckydisasters.com"

[Environment]
HOME=$HOME$\$AppName$
;This folder will be used to save any user specific file
;information - like the Mozilla profiles folder.
USERPROFILE=%HOME%
;As you can see I've used the same folders for all the
;programs files, this will make it a lot easier later if we
;want to see what the program is doing or make
;changes.
PATH=%PATH%;@ScriptDir@
;This adds the @ScriptDir@ variable to the system
;path used by the application

[Functions]
DirCreate=%HOME%
;if this folder doesn't exist when you start the
;program, it will created. You can place other
;functions here as well if you need them.

[Options]
;These settings are other X-launcher application
;options, such as showing a splash screen and
;what not, feel free to make changes, but these
;should be fine as is
DeleteTemp=true
MultipleIstances=true
FixAppData=false
RunWait=true
ShowSplash=true
WriteLog=false

[SplashScreen]
;This section allows you to add a custom splash
;screen and sets the length of time the splash
;screen is shown. Leave the Image and Title blank
;for X-launcher defaults. The image path (as well
;as all paths in this ini file) are relative to the
;current location of the ini/exe files for the
;X-launcher app.
Image=
Title=
TimeOut=1500

Download the Wikipiedia X-launcher files here:
Wikipedia X-launcher

7-Steps

What I’ve done to use the above webapp portably is as follows (assume that the USB drive/portable device is drive letter “X”):

1. Make sure you have WebRunner and the Wikipedia.webapp installed.
2. Create a folder under “X:\PortableApps\” (or where ever you store your portable applicaitons) called “X-WebRunner” (”X:\PortableApps\X-WebRunner”)
3. Copy the “C:\Program Files\WebRunner” folder to “X:\PortableApps\X-WebRunner” (”X:\PortableApps\X-WebRunner\WebRunner”)
4. Copy the wikipedia.exe and the wikipedia.ini files into “X:\PortableApps\X-Webrunner”
5. Run the Webrunner.exe, this will create the user profile you’ll need to copy your webapp into
6. Now copy your webapp folder from your profile folder on your hard drive usually located about here:
   “C:\Documents and Settings\YOURUSERNAME\Application Data\WebRunner\Profiles\RANDOMSTRING.default\webapps\WEBAPPNAME”
   to your new profile folder on your portable device:
   “X:\PortableApps\Application Data\WebRunner\Profiles\NEWRANDOMSTRING.default\webapps\WEBAPPNAME“
7. Last step, start the wikipedia.exe file again, this will start the webapp that you’ve copied.

My “X-WebRunner” install:

Now you can start moving your webapps over and making X-launcher.exe and X-launcher.ini files for each one, the only line in the ini file that needs to be changed for each is “Parameters“, which gets changed to the webapp folder name for each webapp. So basically all you have to do is copy the original wikipedia.ini file, rename it and change the Parameters setting.

Next I’ll have to configure Plain Old Webserver USB (POWUSB) to run with X-launcher. Then I can carry around a nice little XUL Webserver!

Links:

winPenPack
X-Launcher download
My Wikipedia X-launcher configuration
My Wikipedia.webapp Bundle