Hi Drew,
I definitely think that a lot of what you are proposing here is very
interesting. And, as you mention, much of it needs user approval.
However, I don't think we can use UI as simple a what we use for
enabling popups. The reason is that it's something that is IMHO too
easy to social
Drew Wilson wrote on 06/03/09 23:39:
...
- Worker UI:
From the worker standpoint, the main difference between a
PersistentWorker and other types of workers is that the normal way of
interacting with the user (via an open browser window) is not
available, since there may be no windows open to
Thanks for the info - I wasn't aware of the new Ubuntu notification
infrastructure. Notes below:
On Mon, Mar 9, 2009 at 10:42 PM, Matthew Paul Thomas m...@myrealbox.comwrote:
Speaking for Ubuntu, we are making active efforts to reduce the number
of elements in the notification area (aka
My team at Google is experimenting with supporting persistent SharedWorkers
(SharedWorkers whose lifetime is not linked to being entangled with an
active browser window). I've reviewed some of the mailing list archives, so
I'm aware of at least some of the past discussions on this topic - I wanted
Drew Wilson wrote:
- Permissions:
Installing a persistent worker is essentially giving a web application a
near-permanent footprint on your PC - we need explicit permission from
the user, and we need some mechanism in the user agent to revoke this
permission. There are a number of examples
Agreed, there is definitely some overlap between extensions and persistent
workers. I've been trying to sort out exactly how similar they are (Note:
I'm mostly familiar with Firefox extensions/plugins, and mostly as an
end-user - some of my assumptions may be incorrect):
* Install - they both
