On Thu, Jul 30, 2009 at 22:59, johnjbarton<[email protected]> wrote: > > The jsdIScript object corresponds to a function in Javascript. > SourceFile is a Firebug invention that tries to group all of the > jsdIScript objects that logically belong together. Firefox has no such > grouping, it just a big pile.
Well, my question was more: how is the jsdIScript/SourceFile relation constrained in the Firebug framework? But i should probably get more familiar with Firebug SourceFiles before going there... Just to make it clearer though, i meant: as i understand it, it usually is about linking "spawned" jsdIScripts to a SourceFile, while in the GM-script discovery step it is about creating several SourceFiles objects in the context of one on(JsdI)Script handler. >> SandboxSourceFile is good, especially if Firebug defines some kind of >> interface allowing tiers components to provide sources for their >> Sandboxed scripts (and GM complies to that). ;-) > > You lost me here. Firefox compile, we watch. We watch but i understand we don't usually watch sandboxes which, i suppose, are particular. I'm assuming Firebug usually builds SourceFiles out of JS script DOM elements. In the case of a Sandbox (i.e. without corresponding DOM element), there seem to be no way for Firebug to build a proper SourceFile alone, when one is needed as is the case with GM scripts. It can only do so if it's provided with proper data by the Sandbox owner -- GM here. If that's the case, why not take it as an opportunity for Firebug to support Sandbox debugging? The idea being to provide an interface tiers chrome code can use to register Sandboxes they want to debug. I understand Firebug is focused on web page debugging (as opposed to chrome debugging), yet it makes sense to include chrome code dynamically altering said page, doesn't it? > You could try to see if Chromebug will show you the sandbox values. > Firebug is not really set up to deal with them. I suppose we could go > in that direction, but honestly I don't expect to do that. I've been unlucky with Chromebug: i tried to install it once but it was making FF crash (FF could not even start, iirc). But i did some (limited) testing of script Sandbox values poking around: it worked as mentioned. -- Olivier --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
