Mozilo: Malsamoj inter versioj

El Vikipedio, la libera enciklopedio
[nekontrolita versio][nekontrolita versio]
Enhavo forigita Enhavo aldonita
eNeniu resumo de redakto
e Projekto por Malferma Katalogo
Linio 40: Linio 40:
* the [[Bonsai CVS code management system]], a web-based query interface for the [[Concurrent Versions System|CVS]] [[revision control]] system, and
* the [[Bonsai CVS code management system]], a web-based query interface for the [[Concurrent Versions System|CVS]] [[revision control]] system, and
* the [[Tinderbox detective tool]], which allows developers to manage software builds and to correlate build failures on various platforms and configurations with particular code changes.
* the [[Tinderbox detective tool]], which allows developers to manage software builds and to correlate build failures on various platforms and configurations with particular code changes.
* the [[Open Directory Project]] was included as a web directory. The domain name http://dmoz.org/ stands for "directory Mozilla" and it's still available in the original location http://directory.mozilla.org/
* the [[Projekto por Malferma Katalogo|Open Directory Project]] was included as a web directory. The domain name http://dmoz.org/ stands for "directory Mozilla" and it's still available in the original location http://directory.mozilla.org/
=== Notable features of Mozilla's design ===
=== Notable features of Mozilla's design ===
One unique aspect of Mozilla is that the entire user interface, including menus and dialog boxes, is rendered by the Gecko layout engine, rather than by the host operating system's [[GUI]] library. This architecture has been controversial. Its defenders cite its flexibility and the fact that it can present a standard GUI across different platforms. Its critics argue that this architecture adversely impacts performance, and that it is a widely-accepted convention of application design to use the native GUI elements of the operating system interface. A number of browsers exist that use the rendering engine only to display the [[HTML]] page (see below).''
One unique aspect of Mozilla is that the entire user interface, including menus and dialog boxes, is rendered by the Gecko layout engine, rather than by the host operating system's [[GUI]] library. This architecture has been controversial. Its defenders cite its flexibility and the fact that it can present a standard GUI across different platforms. Its critics argue that this architecture adversely impacts performance, and that it is a widely-accepted convention of application design to use the native GUI elements of the operating system interface. A number of browsers exist that use the rendering engine only to display the [[HTML]] page (see below).''

Kiel registrite je 12:36, 21 feb. 2003

Komputiko > Interreto > TTT-krozilo > Mozilo


Mozilo (angle, Mozilla [mozila]) estas

En februaro de 1998, Netscape liveris plejparton da la fontodosieraro de sia populara programaro Communicator (inkluzivante TTT-legilon Navigator) per malfermafonta permesilo. Por teni la kunlaboradon pri Mozilo, Netscape kreis ankaŭ organizaĵon Mozilla kaj la TTT-ejo http://mozilla.org/. Kvankam oni forlasis la originalan fontodosieraron baldaŭ, la organizaĵo fine sukcesis produkti interretan programaron pli kapabla ol Communicator.

Laboro pri Mozilo daŭras. Ĝi iĝis bazo por aliaj programoj. Kelkaj estas troveblaj ĉe MozDev (angle).

Historio de Mozilo

La liberigo de Netscape Communicator, dum la pinto de la ekonomia apogeo de la finaj 1990-aj jaroj en Usono, estis akceptita kun miksitaj aprobo kaj skeptiko. Pluraj (ĉefe Linuksanoj) vidis ĝin kiel venko de la movado por libera programado kaj bona ŝanco por ke Netscape profitu.

Aliaj (la industrio de malfermita programaro) interpretis ĝin kiel fiasko de Netscape kontraŭ Internet Explorer de Microsoft en la batalo pri TTT-legiloj.

Programado per la fontokodo de Communicator malfacilis pli ol kalkulite:

  • La kodaro estis ega kaj kompleksa.
  • Oni devis labori por pluraj operaciumoj, respektante iliajn proprajn morojn kaj normojn.
  • Dum jaroj, Netscape-anoj devis rapide produkti novajn versiojn laŭ "Interreta tempo". Por tio, ili oferis modjulecon kaj programan eleganton.
  • Pluraj partoj ne estis liberaj, ĉar Netscape akiris ilin laŭ permesoj de ceteruloj.

Rezulte, la unua liveraĵo estis nek konstruebla nek ekzekutebla. Tio malfacilis por la kernaj programistoj de Mozilo (multaj salajrataj de Netscape) , kaj eĉ pli por eksteraj untaj kontribuontoj.

Fine, la kernaj programistoj decidis abandoni la heredan kodaron kaj reverki ĉion el komenco. Malkonsente, unu el la ĉefaj Netscape-aj programistoj Jamie ZAWINSKI, rezignis. La rezulta plano inkluzivis krei tute novan multsisteman programbibliotekon por komputil-homa interago kaj novan HTML-surekranigan meĥanismon.

Malmultaj antaŭvidis la rezulton. Rapida kompletigo de HTML-a pozicimeĥanismo Gecko kredigis, ke la tutan programon baldaŭ aperos. Tamen, ĝi nepris multe pli da tempo. Kaj mozilanoj jam viziis projekton trans simpla TTT-legilo. Nova Mozilo estus "bazo por interretaj programoj", tute programebla kaj modjula . Same bone ĝi ujus retpoŝtajn redaktilojn, tujaj mezaĝiloj, Usenet-legiloj, kaj ceteraj.


Tradukenda


Due to the effort required for this massive rewrite, the project fell far behind its original projected deadlines. In the years that followed, skepticism about Mozilla grew widespread, and some doubted that a finished Mozilla browser would ever see the light of day. However, the project persisted, continuing uninterrupted through both the purchase of Netscape by AOL and the end of the dot-com boom.

By 2002, the Mozilla project had produced a serviceable, standards based web browser that worked on multiple operating systems, including Linŭ, Mac OS, Solaris, and Microsoft Windows. The Mozilla 1.0 release was even praised for introducing new features that Internet Explorer lacked, including better support for user privacy preferences and some interface improvements. Additionally, the Mozilla browser became a de facto reference implementation for various World Wide Web Consortium standards, due to its strong support for those standards.

Mozilla technology

Spin-offs

The Mozilla software architecture was, of necessity, fairly modular. As a result, Mozilla development generated several components that have been reused in other contexts. The most prominent of these is the Gecko layout engine, which has been used in other browsers (see Spin-off browsers below).

Also, the task of Mozilla development itself spurred the creation of tools for geographically distributed, cross-platform software development. Some of these tools were widely adopted by the larger open source community, including the following:

Notable features of Mozilla's design

One unique aspect of Mozilla is that the entire user interface, including menus and dialog boxes, is rendered by the Gecko layout engine, rather than by the host operating system's GUI library. This architecture has been controversial. Its defenders cite its flexibility and the fact that it can present a standard GUI across different platforms. Its critics argue that this architecture adversely impacts performance, and that it is a widely-accepted convention of application design to use the native GUI elements of the operating system interface. A number of browsers exist that use the rendering engine only to display the HTML page (see below).

== Origins and prophecies: the "Mozilla" name == The Mozilla project takes its name from the cartoon lizard Mozilla, who served as Netscape's mascot in the company's early days. The name is a portmanteau of "Mosaic" (the Netscape browser's predecessor) and "Godzilla" (a movie monster that terrorized Tokyo and other locales). One can surmise that the employees of Netscape hoped to unseat Mosaic as the web's most popular browser. They succeeded---albeit briefly, yielding the position to Internet Explorer soon after. For more on the Mozilla mascot, see the external link for "The Mozilla Museum" (below).

When given the URL about:mozilla, the various versions of the Netscape browser would display a message, in white text on a lurid red background, in the browser window. Version 4 displayed the following prophecy:

And the beast shall come forth surrounded by a roiling cloud of vengeance.
The house of the unbelievers shall be razed and they shall be scorched to the earth. Their tags shall blink until the end of days.
from The Book of Mozilla, 12:10

"Their tags shall blink" refers to the controversial <blink> HTML tag introduced in an earlier Netscape version. This proprietary HTML extension, which made text blink on and off, was widely derided as annoying, distracting, and ugly. Soon after its introduction, the blink tag joined hideously garish backgrounds and animated GIFs as metonymy for badly designed web pages.

Later Netscape browser versions, which were actually based on the Mozilla code, displayed the following:

And the beast shall be made legion. Its numbers shall be increased a thousand thousand fold. The din of a million keyboards like unto a great storm shall cover the earth, and the followers of Mammon shall tremble.
from The Book of Mozilla, 3:31
(Red Letter Edition)

This text probably referred to Netscape's hope that, by opening the Mozilla source, they could attract a "legion" of developers who would help improve the software. Some suggested that "Mammon" referred obliquely to Microsoft, which seemed plausible given that Microsoft's Internet Explorer was Mozilla's chief competition.

Version History

Early versions of Mozilla were slow and buggy. Mozilla became about as stable as Netscape 4.7x only from 0.9.2 or 0.9.3 builds onwards.

  • From 0.9.5 (October 12th, 2001) onwards the releases have been fast and reliable, largely due to the implementation of formal code review techniques by the Mozilla project managers.
  • 0.9.6 (November 20th, 2001)
  • 0.9.7 (December 21st, 2001) Favicon support.
  • 0.9.8 (February 4th, 2002) included an ECMAScript debugger named Venkman and a Document Object Model inspector.
  • 0.9.9 (March 11th, 2002): a new mail notification sign that appears in the Windows System tray.
  • Mozilla 1.0 Release Candidate 1 (April 18th, 2002): viewing the source of a cgi generated page now works properly, reorganized menu bar and context menus, a new Download Manager.
  • Mozilla 1.0 Release Candidate 2 (May 10th, 2002):
  • Mozilla 1.0 Release Candidate 3 (May 23rd, 2002): 139 bug fixes since RC2.
  • Mozilla 1.0 (June 5th, 2002): the first 'official' release of the browser technology, with intended long-term stable APIs that can be used to support products by other developers.
    • Mozilla 1.0.1 (September 10th, 2002): over 650 bugfixes to 1.0.
    • Mozilla 1.0.2 (January 7th, 2003): further stability and security improvements and fixes for standards support.
  • Mozilla 1.1 (August 26th, 2002): Improvements to application and layout performance, stability, and web site compatibility. CSS, DOM and HTML standards support has also been enhanced.
  • Mozilla 1.2 (November 26th, 2002): Type ahead find implemented (allows quick navigation), keyboard access greatly improved, and link prefetching enabled (release also contains the usual performance, stability, and security enhancements.)
  • Mozilla 1.2.1 (December 2nd, 2002): released in order to correct a DHTML bug found in Mozilla 1.2.
  • Mozilla 1.3a (December 13th, 2002): basic junk mail classification capabilities have been added.

Early reviews of Mozilla 1.0 are favorable, describing Mozilla as fast and stable, and praising new features such as tabbed browsing and pop-up blocking.

One advanced setting which is highly beneficial to users of Mozilla is the ability to use HTML Pipelining, which results in much faster download times for sites with multiple images.

Spin-off Browsers

Browsers that use the Gecko layout engine for the entire user interface:

Browsers that just use the Gecko layout engine for webpage display only:

External links

Reviews of Mozilla 1.0:

Reviews of Mozilla 1.1: