I would at this point very much recommend putting your patches somewhere they can be looked at by others (ideally attached to a bugzilla.mozilla.orgbug), and then joining the #jsapi channel on IRC. It's much, much easier and quicker that way.
On Tue, Jan 14, 2014 at 7:56 PM, Andreas Schlegel < [email protected]> wrote: > I see the wrapper class is a child of the DirectProxyHandler, which I > haven't changed until now. Should I change only this class or the > underlying wrapper? > > Am 14.01.2014 19:52, schrieb Andreas Schlegel: > > Hello Till, > > I think the first answer of my question could be in an other direction. > I found the CrossCompartmentWrapper, you're speaking from. > I think I must insert the code there also. > There are also other wrapper child classes and the wrapper class must I > insert the method there if I change the CrossCompartmentWrapper? > > Am 14.01.2014 19:46, schrieb Till Schneidereit: > > On Tue, Jan 14, 2014 at 7:35 PM, Andreas Schlegel < > [email protected]> wrote: > >> My Questions are: >> >> Why is the proxy within the global not handled by a >> ScriptedDirectProxyHandler and which handler is used for? >> Why are the JSContext and JSRuntime identical, although the two objects >> should use two different Runtimes? >> > > I don't know the answer to the first question, sorry. > > As for the second: you can have arbitrarily many global objects in the > same runtime. To have two different runtimes, you'd have to create them > specifically. I don't know if that's even possible in the shell. > > The thing that's different for the two globals is the JSCompartment, which > every global has its own of. > > > > _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
