On Thursday, October 24, 2013 9:04:13 PM UTC+5:30, Vasu Yadav wrote:
> On Thursday, September 19, 2013 10:06:30 AM UTC+5:30, Vasu Yadav wrote:
>
> > Hi
>
> >
>
> >
>
> >
>
> > We are facing problem with our Add-ons support for FireFox 24.Firefox is
> > crashing. In earlier approach we was
On Thu, Oct 24, 2013 at 5:34 PM, Vasu Yadav wrote:
> My plan is to pass a nsIDocShell pointer to javascript component and then
> let the javascript component execute the given javascript in a content
> window. ex. get/set window property, call a global function in window
>
- how can I find a glob
On Thursday, September 19, 2013 10:06:30 AM UTC+5:30, Vasu Yadav wrote:
> Hi
>
>
>
> We are facing problem with our Add-ons support for FireFox 24.Firefox is
> crashing. In earlier approach we was using 'JS_GetGlobalObject' to get global
> object from docShell.
> https://developer.mozilla.or
Vasu Yadav wrote:
I am able to Instantiate helloword JS-XPCOM component, when I am trying to
return object to nsISupports interface pointer. but not same when directly
tried to return object to nsIHelloWorld interface pointer.
Perhaps your nsIHelloWorld interface has not been properly regist
Hi Vasu,
I don't have time to help you debug your addon - sorry :-(. There are
lots of examples in the tree (like the test component I pointed you
to) that you can look at and play with to figure out how to make
things work.
Cheers,
bholley
On Thu, Oct 17, 2013 at 8:00 PM, Vasu Yadav wrote:
> O
On Wednesday, October 16, 2013 1:53:24 PM UTC+5:30, Bobby Holley wrote:
> As you've discovered, there's a lot of magic and boilerpate that's
>
> easy to get wrong. You can find some simple test XPCOM components in
>
> js/xpconnect/components. Try grabbing one of those, making sure that
>
> it wo
On Wednesday, October 16, 2013 1:46:48 PM UTC+5:30, Vasu Yadav wrote:
> On Friday, October 4, 2013 6:16:36 PM UTC+5:30, Bobby Holley wrote:
>
> > On Fri, Oct 4, 2013 at 2:36 PM, wrote:
>
> >
>
> >
>
> >
>
> > > Based on my understanding, I need to create a JS XPCOM component apart
>
> >
As you've discovered, there's a lot of magic and boilerpate that's
easy to get wrong. You can find some simple test XPCOM components in
js/xpconnect/components. Try grabbing one of those, making sure that
it works, and then iterating on it to turn it into what you need.
bholley
On Wed, Oct 16, 20
On Friday, October 4, 2013 6:16:36 PM UTC+5:30, Bobby Holley wrote:
> On Fri, Oct 4, 2013 at 2:36 PM, wrote:
>
>
>
> > Based on my understanding, I need to create a JS XPCOM component apart
>
> > from the existing C++ XPCOM component I already have. All the JavaScript
>
> > function calls nee
On Friday, October 4, 2013 6:16:36 PM UTC+5:30, Bobby Holley wrote:
> On Fri, Oct 4, 2013 at 2:36 PM, wrote:
>
>
>
> > Based on my understanding, I need to create a JS XPCOM component apart
>
> > from the existing C++ XPCOM component I already have. All the JavaScript
>
> > function calls nee
On Fri, Oct 4, 2013 at 2:36 PM, wrote:
> Based on my understanding, I need to create a JS XPCOM component apart
> from the existing C++ XPCOM component I already have. All the JavaScript
> function calls need to be made from JS XPCOM component.
>
Precisely.
> How will the C++ XPCOM and JS XPCO
On Thursday, October 3, 2013 6:51:10 PM UTC+5:30, Bobby Holley wrote:
> You should call Javascript functions from JS. If your app is mostly C++,
>
> then you can use a JS-implemented XPCOM component to do the JS work. If
>
> your core logic is easily convertible to JS, then you should do that, an
On Thursday, September 19, 2013 10:06:30 AM UTC+5:30, vasuyad...@gmail.com
wrote:
> Hi
>
>
>
> We are facing problem with our Add-ons support for FireFox 24.Firefox is
> crashing. In earlier approach we was using 'JS_GetGlobalObject' to get global
> object from docShell.
> https://developer
You should call Javascript functions from JS. If your app is mostly C++,
then you can use a JS-implemented XPCOM component to do the JS work. If
your core logic is easily convertible to JS, then you should do that, and
interface with native code via XPCOM and JS-CTypes.
On Thu, Oct 3, 2013 at 2:3
On Monday, September 23, 2013 9:33:59 PM UTC+5:30, Bobby Holley wrote:
> On Mon, Sep 23, 2013 at 5:12 AM, wrote:
>
>
>
> > Thanks a lot Bobby.
>
> > My issue is solved after use of nsCxPusher for JSContext.
>
> > Could you suggest me some alternative approach to do the same?
>
> >
>
>
>
>
On Mon, Sep 23, 2013 at 5:12 AM, wrote:
> Thanks a lot Bobby.
> My issue is solved after use of nsCxPusher for JSContext.
> Could you suggest me some alternative approach to do the same?
>
An alternative to nsCxPusher? My suggestion is to not use JSAPI, period.
Per another discussion on this lis
On Thursday, September 19, 2013 10:06:30 AM UTC+5:30, vasuyad...@gmail.com
wrote:
> Hi
>
>
>
> We are facing problem with our Add-ons support for FireFox 24.Firefox is
> crashing. In earlier approach we was using 'JS_GetGlobalObject' to get global
> object from docShell.
> https://developer
Calling JSAPI directly from C++ addon code is extremely dangerous. You
should stop doing it! I can provide advice on alternative mechanisms
to do whatever you're trying to accomplish.
The crash is probably related to the lack of an nsCxPusher here. See
the discussion in bug 911161. If you go that
18 matches
Mail list logo
