MozillaZine

Full Article Attached MozillaZine Readers Sound Off

Sunday April 4th, 1999

MozillaZine readers Ho-Sheng Hsiao and Oliver White (aka cyanide) have written essays regarding recent events in the Mozilla community. The first, on the benefits of downloadable chrome, can be read here (or, click Full Article below). The second, musings on Mozilla and Open Source, can be found here. You can also get to the second essay by clicking the "Next" link at the end of the first essay.

The opinions stated in these essays do not necessarily reflect the opinions of MozillaZine.

If you have written an essay regarding Mozilla's first anniversary, feel free to submit it to MozillaZine. We can't promise we'll print all submissions, but we'll try.


#17 Re:MozillaZine Readers Sound Off

by paul <paul@qub.com>

Monday April 5th, 1999 8:38 PM

You are replying to this message

After spending some time browsing Mozilla's code, trying to do some hacking on different levels I'm not happy with the results.

It's not quite correct to call the Mozilla project "Open Source".

The level of _internal_ BS is much higher comparing with any other Open Source project.

If you want people to help you:

Publish the dataflow. Yes, Mozilla's dataflow is not perfect yet, Cut & Paste code resides in ... hmm... critical places of the system.

But it'l be honest and helpful to publish it. It'l be *much* more efficient than asking people to spend their free time hacking yet another heap of undocumented code full of hacks and temporary solultions.

"'Hacking Mozilla' tutorial" is not the tutorial. It's XPCOM propaganda. BTW - some places are handy, even Doczilla failes on it's own samples. It's not 'pre-Alpha' stage. Stop BS.

What to do to get more help from people who are not @netscape.com:

1. ASAP.

Finish good and scalable design ... not finished yet... You are a bit late with XPCOM... scalability was the priority - not the option ...

2. Some day ( say when )

Publish API's, marking hacks and temporary solutions with some special color.

3. Always. Keep key-developers...

4. Don't know when.

Assign one person who will answer to the particular design requests from the outher space and publish the e-mail of that person. It should be his *responcibility* to answer ( and publish answers widely ) questions like ( simplified ):

"In the existing design parser is registered as a stream listener. what is the best way to register some custom filter for pre-processing the input stream before invoking parser on it?"

Conclusion.

There still is some chance that Mozilla would not die, but Netscape should make some real and serious steps in helping developers from the 'outher space'.

------------------------------

<http://www.mozilla.org/newlayout/doc/parser.html>

<insert parser image here>