Labs/Extensions2/Notes: Difference between revisions

= 1-clickweather =

* toolbar extension

* uses a JS import function to namespace javascript included from files

* uses some complicated object heirarchies to manage prefs / config

* uses it's own system to manage prefs

** uses observer pattern to get updates (as opposed to listenting to the prefs observers)

* basic statusbar overlay

** popupset

* uses windows for config/about/etc.

* capture in saved xml files

* wrote their own AJAX library to handle simple async requests

= adblock plus =

* content filter

* localized

* uses the built in prefs tools and defaults

* dialog for about

* window for subscribing

* sidebar

* stores filters as a line deliminted file in the profile

* handles it's own async calls with XMLHttpRequest() primitive

** used for synchronizing subscriptions for filters

= autopager =

* content enhancement

* has an interesting auto-xpath generator for grabbing the links it needs

* handles install with file, lots of poking profile dir, registering content

* option to install to profile :)

* uses firefox supplied prefs framework

* has a system to dynamically add the prefs file to prevent some of the weirdness in initializing new defaults

* extensive use of sidebar, mostly as a container for what appears to be "page" elements

* statusbar

* does not use settings overlay, builds it's own UI for that

* installation is handled seperately from everything else, involve file manipulation etc.

= boost =

* content enhancement

* uses firefox supplied prefs framework

* does not use settings overlay, builds it's own UI for that

** easily add / remove listeners

* basic status bar overlay

* prefs ui

* has it's own library, doing something weird involving chrome security contexts.

** /I/ think this is about adding in page elements that can be called into the chrome context, there's some work to sanitize content etc.

= colorfultabs =

* ui enhancement

* handles install with file, lots of poking profile dir, registering content

* uses firefox supplied prefs framework

* uses settings overlay

* basic status bar overlay

* uses settings overlay

* has it's own library, doing something weird involving chrome security contexts.

** /I/ think this is about adding in page elements that can be called into the chrome context, there's some work to sanitize content etc.

= ctrl-tab =

* ui enhancement

* uses firefox supplied prefs framework

* only the main overlay used to create a popupset that holds "tab images"

= download statusbar =

* statusbar

* includes localization

* uses firefox supplied prefs framework

* status bar overlay

* builds it's own window for managing prefs

= downthemall =

* functionality enhancement

* includes localization

* handles install with file, lots of poking profile dir, registering content

* uses firefox supplied prefs framework

* status bar overlay

* builds it's own window for managing prefs

= fast_video_download =

* toolbar extension

* is localized

* uses the firefox supplied prefs framework

* and makes use of the options ui

* uses the options overlay

* uses raw XMLHTttpRequest object

= febe =

* functionality enhancement (provides backups of firefox profile)

* is localized

* checks for first install and initializes

* double checks default prefs

* checks intialization of prefs to prevent exception calls

* uses the firefox supplied prefs framework

* lots of use of dialog boxes to present data to users

** including it's own error and alert and confirm boxes (odd)

= fire_fm =

* toolbar extension

* uses flash for playing files

* uses the firefox pref framework

* uses a comma delimited pref for complex data type

* overlays many of the dialogs for it's own alerts/errors

* toolbar overlay for main app

* overlays options

* extensive use of pref framework for storing state

* uses straight XMLHTTPrequest

* uses log4moz

= firebug =

* functionality enhancement (provides introspection)

* localized

* uses firefox prefs

= flashgot =

= greasemonkey =

* uses components

* preloads common scripts into namespace using component

= IE Tab =

* custom pref manager IN component

= ImageTweak =

* obvious custom logger

* domloaded

= Interclue =

* uses RDF format internally

* uses annoying register stylesheet methods (I had issues with this in Puff)

= NoScript =

* uses rdf for ui info

* various domloaded

* crazy amount of preferences (~100 on install)

* abstracts prefs interfaces

* giant overlay file that uses the component with small other files that use it

* okay so tons of classes in here, essentially everything is in the component

* uses component (8200 line file!!)

* uses file read/write

= StumbleUpon =

* most in one long file of many functions, tons of namespace polution

* sets a TON of "global" variables using su_xxx

* listens to almost every event, including domloaded of course

* uses component for helper functions, including logging and custom ajax

* uses prefs and the sqlite db

* has giant database abstraction layer

* csv file to populate db and sql file to build db

* 20k stumbleuponoverlay file that is largely one dimensional with just functions

= Tab Mix =

* sets about 200 preferences

* doesn't seem to have a pref abstraction layer

= Video Download Helper =

* uses built in xml parser loaded

* really impressive layout

** seems the brunt is in several components which are called by individual pages, so no namespace issues

* custom ajax

* uses rdf to store data

* custom pref layer

= Web Developer =

* has js and css files in content folder

* has an entire common folder with helpers to do almost everthing

** including pref and history managers, stylesheet managers, cookies, files, ajax

* preference abstraction functions

= WOT =

* interesting use of load/unload listeners in almost all js files.  they call core to start, including all the code, so i assume they just set these listeners to run checks when a new page loads.

* custom ajax

* built in api to easily deal with requests (i assume to it's server about a pages reliability)

* uses a config.js to store a ton of constants used throughout the app

* uses a prefs abstraction

* inline error handling just catching and dump()

* looks like they are using prefs beyond how they should

** ie storing delimited data (there stuff is a little confusing and im tired so im not 100% sure)