3 messages in com.googlegroups.google-gearsGears in an extension| From | Sent On | Attachments |
|---|---|---|
| dror...@gmail.com | 17 Dec 2007 00:03 | |
| Chris Prince | 17 Dec 2007 00:09 | |
| Dror Matalon | 17 Dec 2007 01:16 |
| Subject: | Gears in an extension![]() |
|---|---|
| From: | dror...@gmail.com (dror...@gmail.com) |
| Date: | 12/17/2007 12:03:13 AM |
| List: | com.googlegroups.google-gears |
Hi Folks,
A while ago I asked about using gears in an extension http://groups.google.com/group/google-gears/browse_thread/thread/f80b9299d4b0e89d/c80c52a1a2e158a8#c80c52a1a2e158a8
We've since done a bit of testing, and can get gears to work inside our extension, and disable the permission dialog box.
The only issue left is the ability to run our extension in parallel with
gears. That doesn't work for the obvious reason that the name spaces
clash. We're both using the google.gears name space to access the shared
library/dll.
Aaron's reaction to my initial question Gears was not designed for this use case, so you may encounter problems. Nobody has done any significant testing of using Gears from an extension.
Which I understand. We're willing to make the changes and do the testing on our own. My questions: * Are other people interested in this? * The obvious easy solution is to get the source, change google.gears to xxxxx.gears and use that as the name space. But it seems like there should be a nicer more generic solution. I guess I'd prefer to have a config file where I specify the name space to use and have the library pick it up at start time. How hard would that be? * Is this something that you would consider rolling into gears, if we provide the full solution? I'd rather not fork the code, and I'm guessing that it will be a minimal change.
Regards,
Dror
-- Dror Matalon Zapatec Inc 1700 MLK Way Berkeley, CA 94709 http://www.zapatec.com




