mazilla mozilla
Introduction
What's mozilla
Purpose of this page
Characteristics of mozilla
Survey of mozilla
Module
Web tool
Technology of mozilla
Other resource
Building mozilla
Construction of environment
for building
Checkout of source
Procedure for building
Image of after-building
Execute mozilla
Embedding
What's embedding
Concept of embedding
Structure of PPBrowser
Analysis of PPBrowser
Structure of embedding
Structure of marbrow
Analysis of marbrow
Fizzilla
What's fizzilla
Build fizzilla
Embedding of fizzilla
FAQ
Talk with Mr. Yatsugi

FAQ

Can FAQ be pronounced ?



For understanding mozilla, is it necessary to learn XPCOM ?

Yes, it is ! It is absolutely necessary. It is not too much to say that huge number of objects making up mozilla are all implemented by XPCOM. Moreover, the design of mozilla itself owes a lot to XPCOM.

For example, let's consider the case that you add a new module to mozilla.

The story is that... , you list up functions of the module. Then, to realize these functions, you lay out what objects are necessary, and what interfaces each object should implement and so on. Of course, if an existing mozilla object or interface can be used, you should use them. ...The strategy is something like this, maybe.

Designing which object is necessary is ordinary things in object-oriented programming. But, designing which interfaces is specific to [XP]COM.

And, in the case of embedding, you are mostly using XPCOM objects already designed and implemented by mozila. But, in this case, your main work is to fix up which object you should create, and which method of which interface you should use in that object.

Is it difficult to initialize embedding ?

Once upon a time, it is quite complicated, but now, EmbedAPI makes it brief. NS_InitEmbedding() and NS_TermEmbedding() do almost all tasks.

For embedding, is it enough to extract Gecko ?

Gecko is a layout module. It is a part managing the layout of HTML and XML. It is one of the largest modules in mozilla.

But, from the point of view of embedding the browser, Gecko itself is not enough. Actually, for embedding a simple browser owning no added function, quite a number of mozilla modules are necessary. The core of tasks may be in Gecko, but to make Gecko function usefully, other various mozilla modules are necessary.

First, it's better to complete embedding application that realize all necessary functions from the full set mozilla, then you should look for modules which can be deleted.

What is the difference between XUL and XML ?

XML is a markup language that can define your original tag unique to your usage. It defines tag by schema (generally, DTD).

XUL is XML that defines DTD which can describe the structure of mozilla's user interface parts.

Can't XUL be used in embedding ?

The top level functions for using XUL is implemented by XPFE in mozilla module, because XUL itself defines front-end of mozilla.

Generally speaking, embedding is to replace a part corresponding to this XPFE with your original front-end application. Therefore, it is difficult to use XUL in embedding, unless all the XUL functions in XPFE could been implemented by yourself.

What is MileStone ?

The turning-point of the mozilla development. Goals that must be reached until each MileStone are planed in the roadmap. By prefixing M as the first letter of MileStone, they are called

... M14, M15 ... M17, M18


Is MileStone already lost ?

After M18, which correspond with Netscape 6, almost all the functions of mozilla has been implemented and mozilla was going to be under bug fix mode, therefore the name of MileStone of mozilla changes to

Mozilla 0.6, 0.7, 0.8, 0.9, 1.0, 1.1, 1.2 ...


When will mozilla fix ?

For the present, it is right to think that Mozilla 1.0 is the fix of mozilla. It will come between April and June 2001 at the earliest.

I show the calendar gotten from mozilla-buils mailing list below.

December 2000 
  S  M Tu  W Th  F  S 
                 1  2 
  3  4  5  6  7  8  9 
10 11 12 13 14 15 16 
17 18 19 20 21 22 23 Mozilla 0.7? 
24 25 26 27 28 29 30 
31 
January 2001 
     1  2  3  4  5  6 
  7  8  9 10 11 12 13 
14 15 16 17 18 19 20 
21 22 23 24 25 26 27 
28 29 30 31 
   February 2001 
              1  2  3 
  4  5  6  7  8  9 10  Mozilla 0.8 
11 12 13 14 15 16 17 
18 19 20 21 22 23 24 
25 26 27 28 
   March 2001 
              1  2  3 
  4  5  6  7  8  9 10 
11 12 13 14 15 16 17   Mozilla 0.9 
18 19 20 21 22 23 24 
25 26 27 28 29 30 31 
   April 2001 
 S  M Tu  W Th  F  S 
  1  2  3  4  5  6  7 
  8  9 10 11 12 13 14 
15 16 17 18 19 20 21  Mozilla 0.9.1 or 1.0* 
22 23 24 25 26 27 28 
29 30 
   May 2001 
        1  2  3  4  5 
  6  7  8  9 10 11 12 
13 14 15 16 17 18 19 
20 21 22 23 24 25 26  Mozilla 0.9.2 or 1.0* 
27 28 29 30 31 

* depending on level of completion 
   towards mozilla 1.0 

For more information, please see mozilla development roadmap .


c_o_n_t_a_c_t
Copyright (C) 2000-2002 Symphony, Inc. All Rights Reserved.
Japanese