After some more digging, I think the best shot is to instantiate a new jsrunner object. From what I gather, I'll simply pass it the JSRuntime I create, call initjsengine, and then I should be able to simply tell it to run the particular scripts I want (using the start method).
Those in the know, is this a reasonable way to go about this? What I'm most fuzzy about in gear's current implementation is how it links with the browser (for example firefox). I noticed js_runner_ff.cc appears to be a primary linking point, so this seems like the right approach. Any thoughts? -Nicolas On Aug 11, 11:37 am, Nicolas <[email protected]> wrote: > Since this is more a question about building/linking with the gears > library than the sdk, I thought this may be a more appropriate place > to ask my question (sorry for the crosspost). > > I currently have a standalone application with an embedded > spidermonkey JS engine. I'd like to take advantage of google gears > workerpool for concurrency, and was wondering what it would take to > embed gears workerpool into my application. > > Is there any documentation on how to connect my application to google > gears? I've found plenty of documention on using google gears from > within javascripts, but not much on interfacing with the gears library > itself. > > Looking through the source code, it seems like the main object is > GearsFactoryImpl. Are there any particular browser methods I need to > emulate in my application in order to be able to instantiate the > gears > factory? Or is it fairly straightforward? > > Any advice/help is appreciated. > > Thanks, > Nicolas
