How to port Gears to a WebKit based browser on Linux? Not Safari.
0 views
Skip to first unread message
Googol Lee
Aug 11, 2008, 5:54:20 AM8/11/08
to Gears Users
Hi, all
I want to port Gears to our browser, but I can't find any document or
project about the port. I find the web:
http://googlemac.blogspot.com/2007/05/google-gears-for-webkit.html
But seems it relate to Safari.
Could any one give me a guide about poring? Thanks.
Regards,
Li Zhaohai
I want to port Gears to our browser, but I can't find any document or
project about the port. I find the web:
http://googlemac.blogspot.com/2007/05/google-gears-for-webkit.html
But seems it relate to Safari.
Could any one give me a guide about poring? Thanks.
Regards,
Li Zhaohai
Ben Lisbakken
Aug 11, 2008, 11:36:37 AM8/11/08
to gears...@googlegroups.com
I think Jeremy Moskovich would know the most about this. He can probably comment since he has been working on Gears for Safari.
-Ben
Jeremy Moskovich
Aug 11, 2008, 12:18:11 PM8/11/08
to gears...@googlegroups.com
Hi,
I don't think we have any documentation specifically around this, though it would be cool if you could add some to the Gears wiki as you go along.
Which browser are you referring to?
Gears for Safari is currently implemented as an NPAPI plugin, but it also hooks pretty deeply into the browser at certain points and for the Safari port at least we use OS X-ony APIs to do this. Your browser will probably require different plumbing.
One such area is Localserver:
* Gears needs to be able to intercept the browser's outgoing http requests so that it can serve content offline and from the Gears cache when appropriate.
* The Gears plugin needs to load before any http requests are made by the browser, so that if we're offline and the first requested page can be served by Gears - we can satisfy the request. Then NPAPI spec doesn't support this, and on OS X we use an InputManager to load Gears at browser startup.
I'd recommend bringing up the modules in the following order:
* database.
* http_request.
* LocalServer
* Worker Pools
If you have any more questions, let me know...
Best regards,
Jeremy
I don't think we have any documentation specifically around this, though it would be cool if you could add some to the Gears wiki as you go along.
Which browser are you referring to?
Gears for Safari is currently implemented as an NPAPI plugin, but it also hooks pretty deeply into the browser at certain points and for the Safari port at least we use OS X-ony APIs to do this. Your browser will probably require different plumbing.
One such area is Localserver:
* Gears needs to be able to intercept the browser's outgoing http requests so that it can serve content offline and from the Gears cache when appropriate.
* The Gears plugin needs to load before any http requests are made by the browser, so that if we're offline and the first requested page can be served by Gears - we can satisfy the request. Then NPAPI spec doesn't support this, and on OS X we use an InputManager to load Gears at browser startup.
I'd recommend bringing up the modules in the following order:
* database.
* http_request.
* LocalServer
* Worker Pools
If you have any more questions, let me know...
Best regards,
Jeremy
On Mon, Aug 11, 2008 at 2:54 AM, Googol Lee <goog...@gmail.com> wrote:
Googol Lee
Aug 12, 2008, 5:42:28 AM8/12/08
to gears...@googlegroups.com
It's for ourself browser, based on WebKit.
Could you help to estimate how many time it need to port? I'm lost in code now. :(
Could you help to estimate how many time it need to port? I'm lost in code now. :(
2008/8/12 Jeremy Moskovich <play...@google.com>
Jeremy Moskovich
Aug 12, 2008, 12:12:19 PM8/12/08
to gears...@googlegroups.com
I can't really estimate how long it would take to port, this depends on many factors of your target platform.
Best regards,
Jeremy
Best regards,
Jeremy
2008/8/12 Googol Lee <goog...@gmail.com>
Reply all
Reply to author
Forward
0 new messages