I just dont get it. I reinstalled my whole system today - wiped everything out and started with a fresh copy of XP. And to specifically test this problem, I downloaded the already published extension from this thread myself and installed it. THE RIGHT-CLICK MENU APPEARS JUST FINE FOR ME !!!! Now how the heck am I supposed to spot this bug It's like when the doctor is close by the disease runs away... Urggghhhhhhhh !!

when I right click on the extenstion it works for me...I get the pop up menu with the following options: Configure Credit Systems..., visit Astahost Forums, and About. Left clicking gives me a quick refresh.

THANK GOD man.. finally it works for someone.. all this while the rest of them led me to believe I was hallucinating about the right-click menu... lol.. I was very confuzzled - why it wouldn't come up for others, when it did for me EVERYTIME. But yeah.. relief.. EUREKA !!! IT WORKS !!!

You better check, what computer specs users have here, maybe you and logan have the same configuration, so you can see the right-click-menu, as for me, I can't see it

m^e .. just a thought .. do u have a beta build of FF ? or a Developer release sumthing like it ? cause we normally download from the link givin at the FF site. There could also be some programs installed on your PC and Logans PC which effect the working of ur extension, as in they could be inter-related with its working, like PHP or apache ?

I think if you re-installed the system and installed NO other program other than FF and then tried out .. maybe that would help, if it works that time then i guess we have some problem in configurations.

Regards
Dhanesh.

Dhanesh, I run the most current verison of Firefox, and have all the dev releases vakced up, and it's not that. I've also looked at m^e's code, and everything loks good, now that he explained the xul thing to me, it's baffling. One other thing m^e. what the heck is "chrome://creditsreporter"? Because that is the folder that all the files seem attached to, but for me they are inside "chrome://chromeFiles" but when I put that in, everything stops. (Oh by the way, I finally convinced Opaque to de ip blok me from gamma, some I can now test the extension once again, the onclickl part works, but not the context).

~Viz

OK this brings us to the topic of Chrome Registry - which was there previously too - but not as advanced as it is now. I need to chalk up a tutorial soon enough. Here's how it works:

Look OUTSIDE the chrome folder - in the root folder where you unzipped the extension. You'll find a file named: chrome.manifest. Starting from FF1.5 and above this file keeps track of all the folders that you're using to split out the contents of the extension. FF 1.5 onwards, this file is a must-be-present part of your extension.

If you open up the chrome.manifest file, you'll find three-four lines in there:


The first and last lines are again - MUST BE PRESENT in all extensions. The first line as you can see has three columns. It defines an entity called "content" (1st column) - which is a part of the "creditsreporter" (2nd column) extension - and the core files of this extension can be effectively located at "chrome/chromeFiles/content/" (3rd column).
This line has to be present, and if you wish NOT to follow the standardised folder structure of extensions, you can place your core files elsewhere and change the content folder here - to make FF read it from your customized folder.
For example I can write this line as:
content creditsreporter abcd/efgh/zyx

Now NOTE, that in effect what is getting defined is a pointer called content, under creditsreporter.. So we can refer to the contents of the above directory as:
chrome://creditsreporter/content/ . ( chrome://2nd column/1st column ) Advantage of this method is - if you change ur folder structure later on you don't need to go back and change it all over in your extension - it entirely eliminates the need to hardcoding the file paths.. Whenever you need to change the dir structure, you simply come to chrome.manifest and change it here - the change is reflected all over your extension..

Similarly - note how I defined a pointer to the graphics folder, using the word skin - which again is nested under creditsreporter.. The 3rd column here simply specifies a name for the skin - you're free to name it whatever or in some cases can have multiple skins with different names. Once again, this points to the folder chrome/chromeFiles/skin/
So in effect, chrome://creditsreporter/skin/ will point to this folder. As I've defined only ONE skin, this is the default one chosen.

Next we come to locale - which allows you to setup locale specific strings - so a user is free to switch the extension interface to the language of his choice..
Same STRUCTURE..
first locale, next creditsreporter, next the locale name string (en-US) that uniquely identifies the locale and fourth the folder where you'll find the locale files..
Putting it together - the files for en-US can be found at:
chrome://creditsreporter/locale/en-US/ which is turn will point to the folder mentioned in the chrome registry...

All these lines are very similar with just minor variations.. Confused ?? Let me know, i'll try to clear it up a little more.

It doesn't work for me, the FF stop responding when I click Option. Nothing is shown at the status bar.

Hey how come - are you receiving any sort of error messages ?? What version of FF are u using ? Is it one of the nightly builds ? Cant you give me sort more details please .. will help me figure out the bugs.

There's no error message here. I'm using FireFox version 1.0.7 (offical, not a nightly build). And here's the screenshoot.