The finite has no genuine beingGeorg Wilhelm Friedrich Hegel
1 - 4 
Also relates to Firefox and Co
Following on from my previous entry on the new Opera pre-production release, I just want to take a quick look at the extensions that expand the functionality of Firefox. Several friends and clients have test run Firefox (and previously Firebird) over the last 12 months, some even making it their regular browser. Yet nearly all of these users appear baffled when, on booting up this amazing browser that I am raving about, they are faced with a minimalist and featureless interface. Of course I point them to the Extensions repository and recommend a few useful addins to get them on their way, yet on revisiting clients months later, they are still using the minimal install or (worse still) have resorted back to the Exploder family!
I feel part of the problem here is that many users have an expectation of what a web browser is, based on their experience with Exploder, and so when a new browser is presented to them it is just regarded as Exploder in another guise. Plus of course lack of business time to install extensions (along with the profile backups and chrome editing this generally entails). This is not all doom and gloom though, since Firefox is after all a Technology Preview and not intended for direct public consumption.
Personally, I am a Firefox fanatic! I cannot get enough of this browser and its multitude of extensions. Right now I have four profiles set up, each serving a different purpose: manual reader; development browser; blogging browser; and research browser. On top of this I have two test profiles I use to put new or updated extensions through their paces to ensure none of the established profiles get mangled. The one rant I do have with the current installation process is the occasional extension (bar the script libraries) that automatically throws itself into the application directory without first confirming this is o.k. with me. Several times this has led to a complete reinstall due to the extension interfering with extensions in another profile. Ideally the XUL developer in question could specify when an extension will behave like this.
Anyway, enough of the rant. The intention of this entry is to list those extensions I have found most useful, in part for my own reference, and so I can point clients and friends to this entry to give them an idea of extensions worth taking time out to install. (Extensions marked with an asterisk * may not offer installation to profile directory).
Here are a couple of aesthetic extensions which add minimal but nice functionality:
Essential developer extensions that I cannot do without:
I have had all of these running under the same profile at some time or other with no conflicts. I would strongly recommend creating a new profile whenever you install new extensions beyond these, to avoid damaging current working profiles. I normally take the following process:
"C:\Program Files\Mozilla Firefox\Firefox" -profilemanagerfrom the command line (note the path to Firefox will depend on your installation).
"C:\Program Files\Mozilla Firefox\Firefox" -p profile_basic. Install the extension. Provided it prompts where to place the extension, choose profile - normally this just entails clicking OK.
"C:\Program Files\Mozilla Firefox\Firefox" -p profile_ext.
I am not suggesting this is a fail safe method, but after several hours lost reinstalling the application, profiles and extensions following an impulsive installation of a far from stable extension, I take caution when installing new extensions into my working profiles until I have confirmation of their stability. If the advanced test fails  yet the basic test succeeded , then a conflict exists with one of the currently installed extensions. If you want the new extension, the best option is to create a new profile for it. This is how I have come to have several different working profiles serving different purposes. It is also a perfect excuse to flavour each profile with a different theme. With a low RAM running machine I tend to go for the grayscale themes like Breeze and Smoke.
I hope perhaps this entry will point a few more people towards experimentation with Firefox. Believe me you will not look back once you start playing!
Also relates to SEO
This entry is a little late in the day, since with massive work commitments I forgot to post it, but on 14th April, Amazon released a beta version of its new search portal, A9.com. As well as the search results (supplied by Google), the portal offers two additional panels - Book Results shows results from an Amazon search on the keywords; Search History provides a chronological and actual history of keywords searched. The latter feature can be integrated with the browsing history offered by the A9 Tool Bar (IE only!) to offer quite a powerful tracking mechanism for intensive searches. A9 also offers a simple query mechanism direct through the URL by simply typing the keywords after the base URL (eg <a href="http://a9.com/severn solutions">http://a9.com/severn solutions</a>) - beneficial for those browsers that don't offer Quick Search features.
John Battelle discusses the Amazon/Google relationship in this venture, and the potential opportunities provided by the search history facility, while Resource Shelf plucks out some of the current weaknesses of the current beta release.
The Tool Bar offers a number of additional features. However, as is so often the case with search tool bars, it is only compatible with IE. Perhaps, someone has already followed the step taken by relatively new Eurekster to produce a XUL version of the tool bar for the blossoming number of Mozilla and co users. As for the design of the portal interface with three resizable panels: It is clear and usable on the major web browsers, but perhaps accessibility could be improved - Lynx illustrates the reliance of the panels on client-side scripting where they fail to work.
While the XUL Console discussed in the previous post is a useful tool
for learning the XUL language by example with instant testing, it embeds the
early days of XUL discovery focusing on the markup and CSS I decided to set up a Tool Configuration in
UltraEdit instead, to allow XUL applications to be run straight out of the editor. First the XUL package needs to be registered in installed-chrome.txt under the Mozilla root:
content,install,url,resource:/chrome/my_xul_file/content/ locale,install,url,resource:/chrome/my_xul_file/locale/en-US/ skin,install,url,resource:/chrome/my_xul_file/skin/
For some inexplicable reason I also found I had to manually enter the skin framework into the application chrome.rdf file:
<RDF:Seq about="urn:mozilla:skin:modern/1.0:packages"> [..] <RDF:li resource="urn:mozilla:skin:modern/1.0:my_xul_file"/> </RDF:Seq> [..] <RDF:Description about="urn:mozilla:skin:modern/1.0:findfile" c:baseURL="resource:/chrome/my_xul_file/skin/"> <c:package resource="urn:mozilla:package:my_xul_file"/> </RDF:Description>
The installed-chrome.txt file should have done this for me. Anyway, with the package registered, an UltraEdit Tool Configuration can be configured with the following command line:
"C:\Program Files\mozilla.org\Mozilla\mozilla.exe" _ -nosplash -chrome "chrome://%n/content/%n%e"
Where _ is a line continuation. By adding the tool to the menubar, my XUL previews are just one click away. Note that if another instance of Mozilla is
running at the same time, the preview will not update since it will use the chrome files from the instance that is already running. So I view the XUL Tutorial
and Programmer's Reference in Firefox while I work on my XUL.
Micro who?! ;) ]
I have had some problems getting the XUL Console to work on Mozilla 1.6. I caught a brief glimpse of the sample widgets the first time I ran it, but since then the console has been blank and totally functionless. Since I was keen to utilise the downloaded version of Alice Corbin's Periodic Table to help learn the markup, and with lack of bug reports for the console on MozDev, I decided to try and debug it myself.
The error was clear, the directory path to Mozilla was set in Windows format with escaped backslashes, while the additional path to the particular file (in this case the samples) was set with forward slashes. (One of the many Windows banes!). Well, time was not available to delve deep into the MozLib library and find out where this was originating, so I settled with adding a regular expression snippet at this point to correct the path and see if that would work.
var re = /\//g; var result = path.replace(re, "\\"); path = result;
The problem was resolved and now the XUL Console is functioning perfectly. I could have quite easily passed an hour reinstalling the extensions and editing chrome files in an attempt to fix this, but in 5 minutes Venkman had pointed me in the right direction and the problem was resolved - an excellent tool!
[ Back To Top ]
Copyright © 2002-2017 Severn Solutions.