Firefox hacking guides you must have

Get FirefoxMost of the times I go through the web for finding tweaks for Firefox. I found these articles are very interesting and tweaks contained in these articles help me to improve the performance of Firefox.

  1. About:config Entries – This is a reference to about:config entries which you can get basic understanding about those entries.
  2. Ten Mysteries of about:config – about:config tweaks from Linux Journal.
  3. Top Firefox 2 config tweaks – Written by Gina Trapani from
  4. Firefox about:config Hacks and assorted tips – Some greate performance hacks for Firefox from Tech Yantra.
  5. Make Firefox much faster about:config tutorial – Video tutorial from and you can find more from related video list.
  6. The secrets of about:config – Firefox Hacks from computerworld.
  7. Firefox Tweak Guide – 12 page Firefox tweak guide from
  8. Firefox Tweaks – Firefox tweaks for network connections and plugins.
  9. Firefox performance tweaks – Another Firefox performance hacks.
  10. Firefox memory tweaks – High usage of memory is some time a problem for Firefox users. This guide will help you to tweak the memory settings.

These guides some times contain same tweaks but I prefer you to read these and choose the best things.


Comments (4)

Download Managers for Linux

Most of the people suffering from low speed of downloading. Some suffering from crashed downloaded when using browser’s download manager. Here are four popular download managers for Linux. All of them are free software. I have tested these on Ubuntu 7.04.

D4X(Downloader for X) – Simple Linux download manager.

Install using sudo apt-get install d4x in Ubuntu.

wxDownload Fast – Cross platform tool with more features. Free Software.

Debian package can be found at this link.

KGet – This work with KDE and Konqueror browser. Also works well with Gnome.

Gwget – Wget front-end for Gnome.

Install using sudo apt-get install gwget in Ubuntu.

Comments (3)

Ultimate Source Browsers for C Projects

Csope is a ultimate tool for interactively locating specified elements of C code. Cscope will make your life easier with it’s features.

  • Allows searching code for:
  • all references to a symbol
  • global definitions
  • functions called by a function
  • functions calling a function
  • text string
  • regular expression pattern
  • a file
  • files including a file
  • Curses based (text screen)
  • An information database is generated for faster searches and later reference
  • The fuzzy parser supports C, but is flexible enough to be useful for C++ and Java, and for use as a generalized ‘grep database’ (use it to browse large text documents!)
  • Has a command line mode for inclusion in scripts or as a backend to a GUI/frontend
  • Runs on all flavors of Unix, plus most monopoly-controlled operating systems.

KScope is a KDE front-end to Cscope. It provides a source-editing environment for large C projects, such as the Linux kernel.


Comments (1)

GSOC 2007 Project Proposal for Dojo Foundation

Synopsis is a project aimed at implementing read-only datastore that reads semi-structured data from MediaWiki sites by creating data items from the data in info-boxes and parameterized templates. Currently Dojo Data module support Csv files, Opml format files, Yahoo Search Web service, web service and RDF data sources. Current implementations lacks the support of MediaWiki content.

Main area of focus in this project is to implement standard set of data-access APIs to support read semi-structured content from MediaWiki site. The support for MediaWiki based content as data sources will be an added advantage because, now data which describes most of the things in the world is exposed as Wikis and content of these Wikis are added and created by the community in all parts of the world.
And I believe this project will help to achieve the goals of Dojo data-access APIs by supporting for another data source.

Project Details

Sites that allow visitors to add, remove, edit, and change content without the registration normally called a wiki. This ease of interaction and operation of Wikis, they have become fantastic tool that allows collaborative authoring.
MediaWiki is a web based wiki software application used by all projects of MediaWiki foundation, all wikis hosted by Wikia and many other largest and popular wikis. MediaWiki project is originally started to host the Wikipedia free encyclopedia and now used by many companies all over the world as a knowledge management solution and content management solution.
MediaWiki use infobox, generalization of a taxobox which summarizes information for an organism or group of organisms to  provide summary information consistently between articles with common subject or to improve navigation between articles which have common subject. As described in WikiPedia infobox is a table that formatted in consistent manner.
Parameterized Templates are use in MediaWiki to reuse the view of common structured data that have differences in few parameters.
Example from Wikipedia:

Template: Name-Example

:I am a template example, my first name is ”'{{{firstName}}}”’ and my last name is ”'{{{lastName}}}”’.
:You can reference my page at [[{{{lastName}}}, {{{firstName}}}]].
We can use this Template in following way inside page: {{Name-example | firstName=John | lastName=Smith}}

:I am a template example, my first name is ”’John”’ and my last name is ”’Smith”’.
:You can reference my page at [[Smith, John]].

Dojo Data module is a datastore object provider which can use in Javascript programs to access various data sources. module currently provides standards set of basic data-access APIs, and five simple datastore implementations. Main goal of module is to have standard set of data-access APIs, and a large set of datastore implementations that implement those APIs.

Main aim of this project is to provide read-only datastore conforms to the standard set of data-access API which read semi structured content from the previously described MediaWiki ifoboxes and parameterized templates. This datastore will provide data synchronously from the Mediawiki data sources.
The will implement API as initial stage. datastoore will parse the  content inside infoboxes and parameterized templates and create the data item using that data. Infoboxes and parameterized templates are described data in semi-structured manner and manipulating these data and converting them to the data item will be the main challenge in this project.
The project will mainly focused on preparing suitable documentation and some examples after completing the datastore and extending the functionality of the datastore.


1.Complete implementation of which supports info-boxes and parameterized templates.
2.Documentation relevant to project
3.Examples and Test Cases

Project Plan

My main goal of this project is to implement datastore with required documentation and samples. Motivation for this project came with the my interest on Javascript based toolkits, Web Design, Semantic Web, and my involvement in the Mashup server project at my internship period.
Currently module have five datastores, bu it does not include datastore that support MediaWiki Infoboxes and parameterized templates. Implementing MediaWiki datastore will take another step towards the main goal of providing large set of datastore implementations that conforms to data access APIs.
First I’ll study the architecture of, APIs and MediaWiki content structure. After that I’ll design and implement  the necessary algorithms and routines to manipulate MediaWiki content which will be used to implement the data access APIs.
Then these algorithms and routines will be used to implement the MediaWiki datastore according to standard APIs.
After completing the implementation I’ll mainly focus on preparing the documentation, writing samples and preparing test cases to make sure the functionality of the project.

Project Schedule

April 11th to May 28th
Studying the Dojo Toolkit, Dojo Data Module and MediaWiki structure and become more familiar with Dojo toolkit by doing examples and tutorials available.

May 29th to June 2nd
Designing main architecture of the datastore to read content from MediaWiki based Infoboxes and parameterized templates.

June 3rd to July 2nd
Implementing initial part of datastore

July 3rd July 5th
Test the implemented features and get the comments and suggestions from the community.

July 6th to July 31st
Extend the functionality and features of the MediaWiki datastore.

August 1st to August 20th
Prepare documentation and samples. And submitting the complete project to Google.


I am a 22 years old undergraduate student at Computer Science and Engineering Department,  University of Moratuwa, Sri Lanka. I am currently in Level 3 and will start the Level 4 (Final year) next May.
I have worked on Axis2/C Code Generation Tool and several other parts of Axis2/C. I was accepted as Apache Committer in January this year for the contribution I have done to Axis2/C project. I have been working with WSS4J project prior to working in Axis2/C. In parallel with Axis2/C project I have worked on Javascript based Screen Scraping tool and Javascript based UI for Mashup Server and have experinced in some Javascript toolkits like YUI, Prototype, and YUI-EXT.
I am really interested in Javascript related projects and I hope this project will give me the opportunity to work and learn Javascript related technologies and improve my knowledge about Web 2.0 concepts. I am sure that previous work I have done in Axis2/C Web Services project and Javascript based project will be helpful in successfully completing this project.

Leave a Comment

Some Great Typography Tutorials

Comments (2)

Flows, Phases, Handlers, and Modules in Apache Axis2/C

Apache Axis2/C is the C language implementation of popular Axis2 Architecture. Axis2/C can be used as a web service client and web service application server that will host web services. In this Article Axis2/C project lead Samisa Abeysighe discuss four main concepts of Axis2/C architecture which will make the Axis2/C the Webserivce Engine.


Leave a Comment

Compiling Spidermonkey under Ubuntu Edgy

1. Download the Spidermonkey source from following link.

2. Extract the tarball to directory somewhere in your system. It will create ‘js’ sub directory.

Derectory Structure look like tihs:

. .. jsd/ READMe src/
3. Then change to the ‘src’ directory.

4. Use ‘make -f Makefile.ref’ to build the source.

When tried to installing under Uuntu Edgy (6.10) you can ended up with following compiling errors.

It turns out these errors were caused by the -g debugging flag when compiling jscpucfg.

Please change the following part of which is under src directory

120: ifdef USE_MSVC
121: OPTIMIZER  = -Zi
122: else
123: OPTIMIZER  = -g
124: endif
125: DEFINES    += -DDEBUG -DDEBUG_$(shell whoami)


120: ifdef USE_MSVC
121: OPTIMIZER  = -Zi
122: else
123: OPTIMIZER  = 
124: endif
125: DEFINES    += -DDEBUG -DDEBUG_$(shell whoami)

5. When build is complete you shuold see some messages probably similar to this.

This says the build was successful. is stored inside ‘Linux_All_DBG.OBJ’ directory.

6. Now you can use these commands to move the libs and headers to default locationd.

Once you follow these steps Spidermonkey is successfully installed in your system.

Comments (3)

Older Posts »