I’ve also been running into a problem described by commenter Marcel, here. I’ve been getting a similar error under Windows for different extensions when I try to install them. Don’t know why, and what makes it worse is that these errors crop up in extensions that I’ve had no problems installing before on other computers (maybe I need to have Webrunner installed along side Prism?). I’ve also had problems with version 0.9 not installing and using the included icons for webapp files. I’m going to have to look into that one a bit further before I can comment more on it though.

At any rate, I’m going to list as much information in this post as I can find on Prism to refer back to, then I’m going to create a new post on how to install an extension for Prism manually. I’d also like to post a how-to on getting POW to work under Prism as well, but I don’t know whether or not I’ll get to that (maybe over Thanksgiving break). So, first some links.

LINKS:
Mozilla Labs’ Prism Page – A broad overview of the goals of the Mozilla Prism Project
Mozilla Developer Center’s Prism Page
MDC’s Prism Page on Extensions
Mozilla Labs’ Prism Forum
Mozilla Wiki Prism Page – Along with the Dev Center’s page, a good source for documentation on  Prism
Mark Finkle’s Blog (one of Prism’s developers – BTW – THANK YOU MARK!!!)
SVN for Prism’s source code
List of Prism Contributors on ohloh.net
Douglas Meyer’s Blog post on getting Google Gears to work with Prism
Commenter Manlo’s blog post on getting RTM working with Prism (does not appear to be working)
Wikipedia Entry

Next, here’s a list of all the files that Prism makes use of in the user’s profile directory on Windows and Mac OS X – Linux to come (I don’t have access to my Linux box at the moment).

Default Prisim Folders in User’s Home directory (Windows as of Prism v0.9):

Under C:\Documents and Settings\{user name}\Application Data\

Prism\
Prism\profiles.ini
Prism\Profiles\
Prism\Profiles\{random string}.default\
Prism\Profiles\{random string}.default\cert8.db
Prism\Profiles\{random string}.default\compatibility.ini
Prism\Profiles\{random string}.default\compreg.dat
Prism\Profiles\{random string}.default\cookies.sqlite
Prism\Profiles\{random string}.default\extensions
Prism\Profiles\{random string}.default\extensions.cache
Prism\Profiles\{random string}.default\extensions.ini
Prism\Profiles\{random string}.default\key3.db
Prism\Profiles\{random string}.default\localstore.rdf
Prism\Profiles\{random string}.default\mimeTypes.rdf
Prism\Profiles\{random string}.default\permissions.sqlite
Prism\Profiles\{random string}.default\places.sqlite
Prism\Profiles\{random string}.default\prefs.js
Prism\Profiles\{random string}.default\secmod.db
Prism\Profiles\{random string}.default\xpti.dat
Prism\Profiles\{random string}.default\extensions\

Under C:\Documents and Settings\{user name}\Local Settings\Application Data\

Prism\Prism\
Prism\Prism\updates\
Prism\Prism\updates\0\

For Each WebApp Prism creates (Windows as of Prism v0.9):

Under C:\Documents and Settings\{user name}\Application Data\Prism\

{webapp name}\
{webapp name}\profiles.ini
{webapp name}\Profiles\
{webapp name}\Profiles\{random string}.default\
{webapp name}\Profiles\{random string}.default\cert8.db
{webapp name}\Profiles\{random string}.default\compatibility.ini
{webapp name}\Profiles\{random string}.default\compreg.dat
{webapp name}\Profiles\{random string}.default\cookies.sqlite
{webapp name}\Profiles\{random string}.default\extensions
{webapp name}\Profiles\{random string}.default\extensions.cache
{webapp name}\Profiles\{random string}.default\extensions.ini
{webapp name}\Profiles\{random string}.default\extensions.rdf
{webapp name}\Profiles\{random string}.default\key3.db
{webapp name}\Profiles\{random string}.default\localstore.rdf
{webapp name}\Profiles\{random string}.default\mimeTypes.rdf
{webapp name}\Profiles\{random string}.default\permissions.sqlite
{webapp name}\Profiles\{random string}.default\places.sqlite
{webapp name}\Profiles\{random string}.default\pluginreg.dat
{webapp name}\Profiles\{random string}.default\prefs.js
{webapp name}\Profiles\{random string}.default\secmod.db
{webapp name}\Profiles\{random string}.default\signons3.txt
{webapp name}\Profiles\{random string}.default\xpti.dat
{webapp name}\Profiles\{random string}.default\extensions\

Under C:\Documents and Settings\{user name}\Application Data\WebApps\

{webapp name}@{webappaddr}\
{webapp name}@{webappaddr}\localstore.json
{webapp name}@{webappaddr}\override.ini
{webapp name}@{webappaddr}\webapp.ini
{webapp name}@{webappaddr}\webapp.js
{webapp name}@{webappaddr}\icons\
{webapp name}@{webappaddr}\icons\default\
{webapp name}@{webappaddr}\icons\default\{icons included in webapp bundle}

Under C:\Documents and Settings\{user name}\Local Settings\Application Data\Prism\

{webapp name}\
{webapp name}\Prism\
{webapp name}\Prism\updates\
{webapp name}\Prism\updates\0\
{webapp name}\Profiles\
{webapp name}\Profiles\l05apnbh.default\
{webapp name}\Profiles\l05apnbh.default\XPC.mfl
{webapp name}\Profiles\l05apnbh.default\XUL.mfl
{webapp name}\Profiles\l05apnbh.default\Cache\
{webapp name}\Profiles\l05apnbh.default\Cache\_CACHE_001_
{webapp name}\Profiles\l05apnbh.default\Cache\_CACHE_002_
{webapp name}\Profiles\l05apnbh.default\Cache\_CACHE_003_
{webapp name}\Profiles\l05apnbh.default\Cache\_CACHE_MAP_
{webapp name}\Profiles\l05apnbh.default\Cache\{other cache files}

Default Prisim Folders in User’s Home directory (Mac OS X as of Prism v0.9):
Under /Users/{user name}/Library/Application Support/Prism/

Profiles/
Profiles/profiles.ini
Profiles/{random string}.default/
Profiles/{random string}.default/cert8.db
Profiles/{random string}.default/compatibility.ini
Profiles/{random string}.default/compreg.dat
Profiles/{random string}.default/cookies.sqlite
Profiles/{random string}.default/extensions.cache
Profiles/{random string}.default/extensions.ini
Profiles/{random string}.default/key3.db
Profiles/{random string}.default/localstore.rdf
Profiles/{random string}.default/mimeTypes.rdf
Profiles/{random string}.default/permissions.sqlite
Profiles/{random string}.default/places.sqlite
Profiles/{random string}.default/pluginreg.dat
Profiles/{random string}.default/prefs.js
Profiles/{random string}.default/secmod.db
Profiles/{random string}.default/xpti.dat
Profiles/{random string}.default/extensions/

For Each WebApp Prism creates (Mac OS X as of Prism v0.9):

Under /Users/{user name}/Library/Application Support/{webapp name}/

Profiles/
Profiles/profiles.ini
Profiles/{random string}.default/
Profiles/{random string}.default/cert8.db
Profiles/{random string}.default/compatibility.ini
Profiles/{random string}.default/compreg.dat
Profiles/{random string}.default/cookies.sqlite
Profiles/{random string}.default/extensions.cache
Profiles/{random string}.default/extensions.ini
Profiles/{random string}.default/key3.db
Profiles/{random string}.default/localstore.rdf
Profiles/{random string}.default/mimeTypes.rdf
Profiles/{random string}.default/permissions.sqlite
Profiles/{random string}.default/places.sqlite
Profiles/{random string}.default/pluginreg.dat
Profiles/{random string}.default/prefs.js
Profiles/{random string}.default/secmod.db
Profiles/{random string}.default/xpti.dat
Profiles/{random string}.default/extensions/

Under /Users/{user name}/Library/WebApps/{webapp name}@{webappaddr}/

{webapp name}@{webappaddr}/localstore.json
{webapp name}@{webappaddr}/override.ini
{webapp name}@{webappaddr}/webapp.ini
{webapp name}@{webappaddr}/webapp.js
{webapp name}@{webappaddr}/icons/
{webapp name}@{webappaddr}/icons/default/
{webapp name}@{webappaddr}/icons/default/{icons included in webapp bundle}

Default Prisim Folders in User’s Home directory (Linux as of Prism v0.9):

Under /home/{user name}/

.prism/prismdir.lin.txt
.prism/profiles.ini
.prism/{randomstring}.default/
.prism/{randomstring}.default/Cache/
.prism/{randomstring}.default/cert8.db
.prism/{randomstring}.default/compatibility.ini
.prism/{randomstring}.default/compreg.dat
.prism/{randomstring}.default/cookies.sqlite
.prism/{randomstring}.default/extensions/
.prism/{randomstring}.default/extensions.cache
.prism/{randomstring}.default/extensions.ini
.prism/{randomstring}.default/key3.db
.prism/{randomstring}.default/localstore.rdf
.prism/{randomstring}.default/mimeTypes.rdf
.prism/{randomstring}.default/.parentlock
.prism/{randomstring}.default/permissions.sqlite
.prism/{randomstring}.default/places.sqlite
.prism/{randomstring}.default/prefs.js
.prism/{randomstring}.default/secmod.db
.prism/{randomstring}.default/XPC.mfasl
.prism/{randomstring}.default/xpti.dat
.prism/{randomstring}.default/XUL.mfasl
.prism/{randomstring}.default/Cache/
.prism/{randomstring}.default/Cache/_CACHE_001_
.prism/{randomstring}.default/Cache/_CACHE_002_
.prism/{randomstring}.default/Cache/_CACHE_003_
.prism/{randomstring}.default/Cache/_CACHE_MAP_

For Each WebApp Prism creates (Linux as of Prism v0.9):

Under /home/{user name}/.prism/

{webapp name}/
{webapp name}/{randomstring}.default/
{webapp name}/{randomstring}.default/Cache/
{webapp name}/{randomstring}.default/Cache/_CACHE_001_
{webapp name}/{randomstring}.default/Cache/_CACHE_002_
{webapp name}/{randomstring}.default/Cache/_CACHE_003_
{webapp name}/{randomstring}.default/Cache/_CACHE_MAP_
{webapp name}/{randomstring}.default/cert8.db
{webapp name}/{randomstring}.default/compatibility.ini
{webapp name}/{randomstring}.default/compreg.dat
{webapp name}/{randomstring}.default/cookies.sqlite
{webapp name}/{randomstring}.default/extensions/
{webapp name}/{randomstring}.default/extensions.cache
{webapp name}/{randomstring}.default/extensions.ini
{webapp name}/{randomstring}.default/key3.db
{webapp name}/{randomstring}.default/localstore.rdf
{webapp name}/{randomstring}.default/mimeTypes.rdf
{webapp name}/{randomstring}.default/.parentlock
{webapp name}/{randomstring}.default/permissions.sqlite
{webapp name}/{randomstring}.default/places.sqlite
{webapp name}/{randomstring}.default/prefs.js
{webapp name}/{randomstring}.default/secmod.db
{webapp name}/{randomstring}.default/XPC.mfasl
{webapp name}/{randomstring}.default/xpti.dat
{webapp name}/{randomstring}.default/XUL.mfasl
{webapp name}/profiles.ini

From the above lists of file locations, it should be apparent (okay, if you really really look, hard) that there are two ways to go about installing an extension for Prism. The first is install that extension “globally”, which is to say that you install that extension for every webapp. For this method the extension gets installed into Prism’s extension directory. The second method is to install the extension “locally”, or on a per-webapp basis. In this case each extension is installed in the individual webapp’s extension directory.

The first method is more difficult because by default, installing an extension will be done when you have a webapp loaded, so it will install the extension into that webapp’s extension folder. In order to install a webapp globally, you’ll need to perform a manual installation or open a new webapp that loads the addon’s xul (chrome://global/content/config.xul). I should mention that this worked on Prism/Webrunner 0.8, but I have yet to test this on Prism 0.9, so this may no longer work.

…

So, why they heck would I list all the files and directories here? Well, I want a reference to point at when I start explaining which files to make changes to in order to install an extension manually.

Code Snippit for Prism Extensions’ install.rdf

<em:targetApplication>
  <!– Prism –>
  <Description>
    <em:id>prism@developer.mozilla.org</em:id>
    <em:minVersion>0.8</em:minVersion>
    <em:maxVersion>1.0.0.*</em:maxVersion>
   </Description>
</em:targetApplication>

Code Snippit for Prism Extensions’ extension.rdf (information is required from the **install.rdf**)

<RDF:Description
    RDF:about="urn:mozilla:item:{**extension id from install.rdf**}"
    NS1:installLocation="app-profile"
    NS1:version="**from install.rdf**"
    NS1:optionsURL="**from install.rdf**"
    NS1:iconURL="**from install.rdf**"
    NS1:name="**from install.rdf**"
    NS1:description="**from install.rdf**"
    NS1:creator="**from install.rdf**"
    NS1:homepageURL="http://**from install.rdf**"
    NS1:contributor="**from install.rdf**">

More to come…

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