Custom web-page control for IE and FireFox

I need a custom web page control that my clients can install on their Windows PC.? The control needs to display inside web pages as a? small fixed-size graphic.? The graphic contents consists of a small icon, and some text (the text needs to be "drawn" - it's not static).? Javascript inside my web pages needs to be able to communicate with the control.? The control needs to work in IE 6+ and Firefox (this probably means 2 different controls that both do the same thing - 1 for IE, one for FF). Finally - I need a stand-alone commandline program that lives on the client PC and communicates with the control. As an example of how this all works - my clients will install "GreaseMonkey", then load a web page.? My greasemonkey script will embed the custom control into the web page the customer visits (eg: hotmail).? While the customer is viewing this web page, it must be possible for the commandline script to "talk" to the control and tell it what icon and text to display, as well as be able to? ask it? questions (eg: like - what the current text being displayed is).? This must show up inside the control in the web page.? Also - javascript on the web page must be able to "talk" to the control too - to get or set variables and change the text. I prefer "shared memory" for communication between the control and the commandline program. This control must work properly, even if the customer has 10 different web pages open, all with this? control in each one, and also when the customer leaves those web pages open, "logs off", and someone else logs in to the same PC and opens more web pages with controls in them. There is, however, only 1 "state" for all controls.? No matter how many - whatever text/variables is being displayed/set - it applies to them all at once.? (there is no individual context). ## Deliverables Seller must exhaustively test deliverables - buyer does not have time/resources to help with testing. control is intended to be included in the web page via simple HTML? (eg: object or embed or similar tags) All communication between the control and either the web page javascript, or the clinet-pc commandline program consists simply of a single text string, no longer than 255 characters.? Communications is 2-way - when the javascript sends a text string to the control, it expects another text string back in reply. shared memory is preferred for communication between commandline and control, however, if better technology exists for this, I'm open to suggestion.