Clarence (Andreas M. Schneider) wrote:
> "Steven T. Hatton" wrote:
>
>>I am trying to get a foothold in the architecture of Mozilla. I have
>>some understanding of what goes where, but I cannot seem to get a grasp
>>of the fundamental core. If I stripped off every bell and every wistel
>>and everything not needed to do this:
>>
>>hattons@hostname:~ > mozilla &
>>
>>and hit a page with
>>
>><HTML><HEAD></HEAD><BODY><H1>hello world</H1></BODY><HTML>
>>
>>and see "hello world" in a window, what components of Mozilla would be
>>remaining? I.e., what is the core of this beast? I know there is a NSPR
>>sitting between the browser and the OS. What else is needed for the
>>most basic functionality? Perhaps some of what I'm looking for is in
>>the NSPR.
>>
>>This seems to be a barrier to entry into the wonderful world of hacking
>>the Lizard. I suspect I'm not the only one who come to mozilla.org looks
>>around and feels completely lost.
>>
>>Pictures! Show me pictures!
>>
>
> 2 pages to start with:
> http://www.mozilla.org/docs/url_load.html
> http://www.mozilla.org/docs/source-directories-overview.html
> Both not 100% up to date, but most of it is still valid.
>
> Clarence
>
Thnaks for the reply, and thanks also to Fabian. What I'm really
looking for is how Window.open() works in JavaScript. How do I find the
Window object as it exists in source? Greppng the source tree is not
proving all that helpful, but who knows perhaps I figure out the magical
regexp. I'm kind of rusty on my C/C++, and I only studied it in school -
never used it on the streets. I'm not really sure what I should be
looking for. I suspect there is a *.h somewhere with the outline of the
Window object. (If that's even meaningful.) Any suggestions?
Steven
