I'm giving Firefox 3 Beta 5 a try, and yet again I find myself frustrated with the layout and interface of the Firefox Add-on site. There seems no way to search for extension by compatibility except by guessing at search strings, and there is not much consistency in how the Firefox versions are mentioned in the descriptions. This used to frustrate me already with Firefox2 every time there was a major update.
When browsing the site with Firefox 3.0b5 any compatible extensions show up with a green download button rather than grey, which enabled me to scan the pages 100 extensions at at time and find the compatible ones reasonably fast. But having done that once, I'd love to be notified when any extensions are updated. I can't find any rss feeds though. Would this be something a website watcher could help me with?
But surely the actual interface to the database could be improved in the first place. It's maddening. Firefox itself can obviously distinguish between compatible and non-compatible just through the browser window (as oppose to via a tool) which makes me wonder if the relevant info can be found in the metadata of the rendered html somewhere. I wonder if that's the kind of thing a greasemonkey script could ferret out, like the scripts people have written for Flickr. (Mind you, greasemonkey is not yet 3.0b5 compatible.)
When browsing the site with Firefox 3.0b5 any compatible extensions show up with a green download button rather than grey, which enabled me to scan the pages 100 extensions at at time and find the compatible ones reasonably fast. But having done that once, I'd love to be notified when any extensions are updated. I can't find any rss feeds though. Would this be something a website watcher could help me with?
But surely the actual interface to the database could be improved in the first place. It's maddening. Firefox itself can obviously distinguish between compatible and non-compatible just through the browser window (as oppose to via a tool) which makes me wonder if the relevant info can be found in the metadata of the rendered html somewhere. I wonder if that's the kind of thing a greasemonkey script could ferret out, like the scripts people have written for Flickr. (Mind you, greasemonkey is not yet 3.0b5 compatible.)


