Re: embedding with debugging support

No, I didn't do it for two reasons:
1 - that code is not present anymore inside that sample
2 - it seems that such code was needed to enable chrome:// support, but the current sample has this support by default
(I am able to open a simple chrome/XUL example app with no problems)
...so I guess that I don't need that change.

I am not aware of any security issues involved if opening venkman in the same window. But I wouldn't even mind to have such problems :-).
My intention is to only have it in a debug version of my c++ app so that the developers can track any html/js issues.

I'd be very happy to just see the venkman opened and running :-)

I just found some more information here https://developer.mozilla.org/en/Debugging_a_XULRunner_Application
But I have to understand how to configure a xul app to try that...

  Thanks Gijs,
    Chris

Gijs Kruitbosch wrote:
> Cristian Tarsoaga wrote:
>> In the end, I was able to start venkman by loading this url from
>> within the demo application: chrome://venkman/content
>> [source: old message from this forum, see
>> http://osdir.com/ml/mozilla.devel.jsdebugger/2002-04/msg00000.html]
>>
>> But it does not run properly: I was not able to open any http/file url
>> I could also not open DOM Inspector at all...
>>
> 
> Did you make the change suggested in that article, too? If not, that
> would be why it didn't "work", presumably. However, you would not want
> to load web content in the same browser element, in that case (because
> it will be privileged and be able to do whatever to your computer)... :-\
> 
> ~ Gijs