Delicious add-on: Yes No buttons swapped




delicious

Originally uploaded by jrharshath

I use the Delicious Official add-on for firefox extensively. I wonder if anyone has noticed this, or reported this to the delicious guys: the icons on the Yes and No buttons in this confirmation dialog are in the wrong place!

Perhaps its because of this: On a yes-no confirmation dialog in windows (yuck!), the Yes button always appears on the left side of the no button. But in linux, its always the reverse.
While writing the addon, if you specify that the button that means should say “Yes” and the “No” one should say “No”, then there won’t be any such glitches.

However, if you specify that the “Left” button should display “Yes”, this problem occurs. The left button is Yes alright, but the icons displayed are decided by the OS. So the icons kind of become OS dependent. Now we don’t want that, do we?

Advertisements

How firefox eats up my system resources

Despite all the cool stuff about firefox, it can voraciously eat up system resources when spiced up with just the right add-ons. When I first noticed this myself, I was pretty surprised: I though firefox was the Best app ever! Now I’ve grown wiser, and I know better.

Here’s how firefox eats up my RAM: and the steep cliff on the graph is the moment I close firefox.

I’ve tried to reduce this stat ever since I got the (horrifying!) pic

For one, I reduced the amount of data firefox would store in its online cache (yea, that means your RAM) by reducing its cache size from 50MB to 20MB (change it from about:config -> browser.cache.disk.capaciy )

I’ve also removed the addons I don’t use, or are redundant. Like, I used to use flashblock, but since I’ve started using NoScript (which also blocks flash), I’ve removed the former.

This brings me to flash. Flash stuff on websites tends to make firefox eat up even more of system resources. It is best to kep flash disabled and enable it only for certain websites (using NoScript or flashblock). Anyway flash violates all known and loved rules of web design anyway. Who wants flash? Go away!

Back to where I left off: I also checked the problematic addons list and removed all addons that have a history of memory leaks. In some cases even a solution for problems was available, like the case of noscript and flashblock.

Well, I’m not complaining. I still like firefox more than I do any other browser. And I am fiercely loyal to it. This is just how I try to coax my favourite (and most frequently used) application from not mauling my RAM every time I run it.