Phil H�hn (TL) wrote:That was a great suggestion, thanks, worked well!
var childNodes = browser.tabContainer.childNodes; for (var i=0; i < childNodes.length; ++i) { thisNode = childNodes[i];
Given each 'thisNode', how do I get the URL/URI for it???
That seems like a bad idea. Why use tabContainer? Why not browser.browsers[i].currentURI? (this is probably an nsIURI object rather than a string. I'm not sure about this though.)
I'm new to the Moz codebase so I was fumbling in the dark a little...
I must admit trying to unravel what the 'browser' object is seems to be hard, given that the browser object itself appears to be a document (it's interpreted), right? (I think I'm right there?)
Which leads me on to the next question - I have seen many docs describing where to get started, but I haven't found one describing (in laymans terms) the structure of Mozilla at a high level and a detailed level. Does any such documentation exist?
Has anyone tried using Doxygen with the Moz source?
_______________________________________________
Mozilla-xpcom mailing list
[EMAIL PROTECTED]
http://mail.mozilla.org/listinfo/mozilla-xpcom
