Step 1
Navigate to the Prism installation directory, in Windows this is:
C:\Program Files\Prism\

Open up the extensions folder, then the DOM inspector extension folder:
C:\Program Files\Prism\extensions\inspector@mozilla.org

Now open the “install.rdf” file and find this section of code which can be used (usually) as-is in most extensions pasted in the right place (just use the extension’s preconfigured targets as your guide on where to place it):

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

Step 2
Open up your extension’s xpi file using 7zip or your favorite archiving tool and extract the install.rdf file.

Open that install.rdf file with a text editor (other than notepad which doesn’t understand the line breaks used by other editors) and find the area where it lists the installation targets and insert your copied text into that or modify one of the install targets with the appropriate information from the DOM inspector extension install.rdf file.

Step 3
Install the extension. This will get tricky due to the way Prism’s developers have modified the profiles and what not. Well, I say that, but it really only gets that tricky if you’re manually installing the extension. Prism developers have seen fit to include the Addons menu item from the Prism menu in the lower right of Prism’s window to help things go more smoothly.

One of the ways to use this new install feature for an extension is globally, which means all webapps will be able to use the extension. This is the least preferred manner due to the fact that you won’t want all extensions available for all webapps in most cases. An example would be having the Better Gmail extension available for Bloglines – don’t think that’s real necessary, do you? So plan accordingly.

Using the second, and more preferred method, you just open your webapp. Open your webapp’s Addons panel, then install by either dragging and dropping the extension onto it, or by clicking the “Install…” button and navigating to the extension and selecting it for installation.

Conclusion
That should be about it. My next Prism post will be about how to make one of two stand alone Firefox/Prism exention webapps – POW local server or Scribefire standalone webapp. Stay tuned, we get to play with chrome!!

Links:

Prism

I had read this morning that there was a new Ubuntu release and, as I was having problems with Debian and was about to reinstall Ubuntu 7.10, so I decided to give it a try. Well, it’s a Beta, but I’m not going to hold that against it! Compiz is installted by default (but just subtley enough you don’t know it till you’re seeing the tell tail fades and such), Firefox 3 Beta 4, wireless support includes WPA (which it has had built-in since the 7.10 release), improved dual screen support for laptops, hell – I didn’t even have to install 915resolution to setup my Intel display to 1440×900! I still had to install Amorok and vlc manually, but that’s cake compared to recompiling a kernel.

1. So far so good, performance is a bit sluggish (especially with the extra visual enhancements enabled), but I’m thoroughly tickled pink by the feature set and compatibility! THANK YOU UBUNTU COMMUNITY!!

Link:

Ubuntu Test Releases

• a file archiver – my favorite is 7-zip, but you can just as easily use any archiving program that is compatible with zip files
• a text plain text editor

For more advanced webapps, a more advanced context highlighting text editor can be helpful for coding custom style sheets or adding javascript customizations. And don’t forget icons! I use a combination of Paint.Net and @icon sushi (which covers everything but MacOS, which is because I can’t seem to find software for Linux or Windows to accommodate icons for it – recommendations anyone?).

The No “.webapp” WebApp

There are several ways to open webpages with Prism or WebRunner. The first and easiest is to install Prism, then create a link to it on your desktop. Then change that link adding the option “-uri” and the url of the page you want to open. Here are two examples:

Windows:
c:\your\path\to_prism\prism.exe -uri http://web_url_of_site c:\your\path\to_prism\prism.exe -uri c:\location\of\local_file

GNU/Linux:
/your/path/to_prism/prism -uri http://web_url_of_site /your/path/to_prism/prism -uri /location/of/local_file

This method does not require a webapp file, it just launches the website or file you specify. This means, no icons are required, but you also don’t get to add any custom themes or js files. This would be a really good method to use with applications like Wiki on a Stick (woas).

WebApp Bundles

The second method is also pretty straight forward (until you make it complex by adding more functionality). For the most basic webApp bundle you only need to create one file; the webapp.ini. Here’s the content from the example webapp.ini on the Prism wiki:

[Parameters] id=unique-app-id@unique-author-id.whatever uri=http://[the-url-what-you-want-to-connect-to]/ status=yes location=no sidebar=no navigation=no

The “id” parameter is required to be unique. I’ve been using my website’s url (as most others have done as well) preceded by the name of the site, but any unique identifier will work. The “uri” parameter is required and will accept both url of the target website as well as local file paths. Everything after that appears to be optional and the values show are the defaults. These remaining parameters are options to tell Prism whether or not to show certain GUI elements (“status” = status bar;”location” = address bar;”sidebar” = sidebar;”navigation” = well, quite frankly, I have no idea – maybe navigation buttons that haven’t been implemented yet?).

The next step after saving your changes to this document, is to use your archiving program to zip up this file creating, as an example, “your_webapp.zip”. Replace the “zip” extension with “webapp” and you’re ready to roll! Now either double click the webapp file or you can launch the webapp from the command line thusly:

Windows:
c:\your\path\to_prism\prism.exe -webapp your_webapp_bundle

GNU/Linux:
/your/path/to_prism/prism -webapp your_webapp_bundle

For more advanced webapps you can add icons, scripting and style sheet support (see the Prism page for more details).

Happy coding!

Prism
Prism/WebApp Bundle
Prism/Scripting
Prism/Styling
7-Zip
Paint.Net
@icon sushi
Wiki on a Stick

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.

Plain Old Webserver (POW)

POW is either a really cool Firefox extension that turns Firefox into a web server or a lightweight xulRunner web server. Either way it serves up web pages using server side javascripting. Sweat! I still have to play with this a bit to get a feel for it because I’ve never used javascript on a server before, but considering this is portable to any system that xulRunner or Firefox will run on, it makes it a very versatile package right out of the box. While the fact that it doesn’t have a php module means I can’t do local development of my website on it (yet), POW does offer sqllite as a database. You can also download some extras for it like a Firefox database management or directory file listing.

You can also use the xulRunner “portably”. I quoted that because, while the POWUSB package includes both Windows and MAC xulrunner versions (no Linux yet either!), it isn’t exactly portable in the way that say, FirefoxPoratable is. In other words, if you run the included xulRunner on Windows, it will still leave files on your local file system. To make this truly portable, you’d need to refrain from leaving footprints on the system you’re using, therefore this really doesn’t qualify as a portableapp quite yet…

What can I say, other than – freakin’ sweat! Contained in just 14 files is a (partial) javascript based blog, file management (will kind of, read on), and a *nix-like terminal (again, kind of). The reason for all those caveats is this; pretty much the fact that is is a work in progress AND, the fact that nearly the entirety of the system is contained in the one file: miniweb.html. Any new blog posts, files (which can be text or I think some form of executable – through some javascript magic), etc. are all stored in the miniweb.html file.

As I mentioned, it’s a work in progress, so nothing is complete, the terminal, the blog, pretty much everything but file viewing and management is incomplete. At this point I’m still just toying with it, so it pretty much takes on the Arthur C. Clark idiom of being so far beyond my understanding that it appears to be magic. To wield some of this magic Dean appears to use a home grown javascript compressor. Just… wow…

To check out MiniWeb click here. To download it and play with it on your own, click here. When you open up the file or depending on what you click on in what ever browser you’re using, you’ll probably have to get passed some of your browser’s security to fully use the software. In IE I think you need to allow the software to function on the bar that appears at the top of the browser window, in Firefox, depending on what you’re trying to do you may have to allow the script to complete some actions (don’t forget that “remember this decision” checkbox). Too much fun to pass up…

First create a new profile

This is actually really simple, you just need to do one of two things:

Select Case

Case 1

From a command prompt or Start menu > Run type:

“[path_to_firefox]\firefox.exe” -CreateProfile [profile_name]

For most of us running Windows this will look like:

“C:\Program Files\Mozilla Firefox\firefox.exe” -CreateProfile test

(“test” would be the profile name in this case)

Case 2

You can create a copy your Mozilla Firefox shortcut on your desktop, right click and select properties, then add the -CreateProfile [profile_name] in the “Target” field on the “Shortcut” tab of the properties dialog. Then click OK and double click the shortcut.

End Select

In either case, Firefox will create the new profile and not open any windows.

Now that you have a new profile you need to be able to open your new browser with the new profile (I’m assuming that you’ve downloaded a new browser and have extracted or installed it to your liking).

Create a new shortcut to you’re new browser

You can either copy your shortcut (if you’ve installed it) or create a new shortcut to the new version of firefox.exe, then (just like in Case 2 above) right click on the shortcut and in the “Target” text box, add -P test (or whatever you’ve used as your new profile’s name) to the end of the quoted firefox.exe path. The click OK.

Now, if you simply double click this icon you’ll open a new instance of your new browser build and you can start to play.

Just in case you want to use both your old browser and your new browser side-by-side

So, you say you’re curious if that website looks the same in your old browser as it does in your new browser, and you need them both open to tell? Well that’s no problem either. Open up the shortcut properties to your new browser just like you did above and after the “-P test” add in “-no-remote”. Now you can open multiple profiles, which should allow you to open your old browser and new browser side-by-side.

Have fun!

Reference Links from mozillaZine knowledge base:
Profile Manager
Command line arguments

Plenty of GNU/Linux resources from people all over the world on the internet. And that’s where this post comes in! IBM is dedicated to GNU/Linux, and not just by pouring millions into development and patenting! They have this huge database of how-tos, articles, download links and so forth available from their Linux developerWorks website. Like this nice little walk-through on how to use linux scripts to build your own wireless ISP. Now, you’d expect IBM to promote IBM Linux products (do they have those?), well, they don’t. This site’s instructions, recommendations and walk-throughs are all based around software that can be downloaded freely from other sources on the internet (checkout their downloads page if you don’t believe me!).

Links:
IBM developerWorks – Linux
IBM developerWorks – New to Linux
IBM developerWorks – Technical Library (be sure to checkout their LPI certification prep series!)

How To: Redirect Errors From Standard Out to Nowhere (*nux)

Here’s how to get rid of those annoying error messages you really don’t care about when running a script (everybody’s got their own excuse for not wanting to see this type of thing, even though it can be handy now and again):

user@computer:~$ [command] [options] 2>&1

Stick “2>&1” at the end of your command string, that about covers it!!

How To: Launch Firefox With a Specific Chrome Interface (Windows)

Ever install a nifty little Mozilla Firefox extension and want to run it as a standalone program? Here’s how:

C:\Program Files\Mozilla Firefox>firefox.exe -chrome [chrome path]

Add the “-chrome” option to the firefox command, then add the chrome path after that. Here’s an example of how to launch the bookmarks manager as a standalone program:

C:\Program Files\Mozilla Firefox&gt;firefox.exe <strong>-chrome chrome://browser/content/bookmarks/bookmarksManager.xul</strong>

Enjoy!!