Jump to content

Gecko (software): Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Nomaxxx (talk | contribs)
174 edits
ITxT (talk | contribs)
46 edits
Line 85: Line 85:
*[[Skipstone]] for POSIX
*[[Skipstone]] for POSIX
*[[Sleipnir (web browser)|Sleipnir]] for Windows
*[[Sleipnir (web browser)|Sleipnir]] for Windows
*[[Torpack]]<nowiki>*</nowiki> (web browser) for Windows
*[[Torpark]] (web browser) for Windows


===Other applications===
===Other applications===

Revision as of 23:42, 15 March 2007

Gecko
Developer(s)Mozilla Foundation / Mozilla Corporation
Stable release
1.8.1.2 / February 23, 2007
Repository
Operating systemCross-platform
TypeLayout engine
LicenseMPL, MPL/GPL/LGPL tri-license
Websitewww.mozilla.org/newlayout

Gecko is the open source, free software web browser layout engine used in all Mozilla-branded software and its derivatives, including later Netscape releases. Written in C++ and licensed under MPL/GPL/LGPL triple license, Gecko is designed to support open Internet standards. Originally created by Netscape Communications Corporation, its development is now overseen by the Mozilla Foundation.

Gecko offers a rich programming API that makes it suitable for a wide variety of roles in Internet-enabled applications, such as web browsers, content presentation, and client/server[1]. Primarily it is used by Mozilla browser derivatives, such as Mozilla Firefox, Camino, Flock, SeaMonkey, K-Meleon, and Netscape, to render websites and, in some cases, the application user interface written in XUL. Gecko is cross-platform and works on a number of different operating systems, including Microsoft Windows, BSDs, GNU/Linux, and Mac OS X.

Gecko is generally considered to be the second most-popular layout engine on the Web, after Trident (used by Internet Explorer for Windows since version 4), and followed by WebCore (used by Safari) and Presto (used by Opera).

Standards support

From the outset, Gecko was designed to support open Internet standards. Some of the standards Gecko supports include:

*The SVG font, color profile, animation, view, and cursor modules are yet to be implemented and the filter and text modules are only partially implemented. The extensibility module is also implemented but is currently disabled[2]

In order to support web pages designed for legacy versions of Netscape and Internet Explorer, Gecko supports DOCTYPE switching. Documents with a modern DOCTYPE are rendered in standards compliance mode, which follows the W3C standards strictly. Documents that have no DOCTYPE or an older DOCTYPE are rendered in quirks mode, which emulates some of the non-standard oddities of Netscape Communicator 4.x, however, some of the 4.x features (such as layers) are not supported.

Gecko also has limited support for some non-standard Internet Explorer features, such as the <marquee> tag and the document.all property (though pages explicitly testing for document.all will be told it is not supported). While this increases compatibility with many documents designed only for Internet Explorer, some purists argue that it harms the cause of standards evangelism.

History

Development of the layout engine now known as Gecko began at Netscape in 1997, following the company's purchase of DigitalStyle. The existing Netscape rendering engine, originally written for Netscape Navigator 1.0 and upgraded through the years, was widely considered to be inferior to the one used in Microsoft Internet Explorer. It was slow, did not comply well with W3C standards, had limited support for dynamic HTML and lacked features such as incremental reflow (when the layout engine rearranges elements on the screen as new data is downloaded and added to the page). The new layout engine was developed in parallel with the old, with the intention being to integrate it into Netscape Communicator when it was mature and stable. At least one more major revision of Netscape was expected to be released with the old layout engine before the switch.

After the launch of the Mozilla project in early 1998, the new layout engine code was released under an open-source license. Originally unveiled as Raptor, the name had to be changed to NGLayout (next generation layout) due to trademark problems. Netscape later rebranded NGLayout as Gecko. While Mozilla Organization (the forerunner of the Mozilla Foundation) initially continued to use the NGLayout name (Gecko was a Netscape trademark)[3], eventually the Gecko branding won out. For a time, Gecko was used to refer to both the old NGLayout layout engine and XPFE (cross-platform front-end)—the new XML-based Mozilla user interface, rendered by NGLayout—but it is now used solely to refer to the layout engine.

In October 1998, Netscape announced that its next browser would use Gecko (which was still called NGLayout at the time) rather than the old layout engine, requiring large parts of the application to be rewritten. While this decision was popular with web standards advocates, it was largely unpopular with Netscape developers, who were unhappy with the six months given for the rewrite. It also meant that most of the work done for Netscape Communicator 5.0 (including development on the Mariner improvements to the old layout engine) had to be abandoned. Netscape 6, the first Netscape release to incorporate Gecko, was released in November 2000 (the name Netscape 5 was never used).

As Gecko development continued, other applications and embedders began to make use of it. America Online, by this time Netscape's parent company, eventually adopted it for use in CompuServe 7.0 and AOL for Mac OS X (these products had previously embedded Internet Explorer). However, with the exception of a few betas, Gecko was never used in the main Microsoft Windows AOL client.

On July 15, 2003, AOL laid off the remaining Gecko developers and the Mozilla Foundation (formed on the same day) became the main steward of Gecko development. Today, Gecko is developed by employees of the Mozilla Corporation, employees of companies that contribute to the Mozilla project, and volunteers.

Future

Some information on the work being done for the next version of Gecko is available in the Gecko 1.9 roadmap.[4]

One of the main initiatives in 1.9 is an overhaul of the graphics infrastructure.[5][6] Instead of using the platforms' API, Cairo will be used for all graphics outputs. This will result in improved 2D graphics capabilities and, via Glitz, acceleration using 3D graphics hardware. It will also mean that there will be a single rendering pipeline for HTML/CSS, canvas and SVG, so that SVG effects can be applied to HTML content. Because of Cairo, it will also be possible to output the graphics as formats like PNG and PDF (Linux only), allowing users to export Web content in these formats.

Another major change in Gecko 1.9 is refactoring of reflow code [7], which fixed many layout bugs, in particular some of the bugs leading to incorrect rendering of the Acid2 standards-compliance test.

Gecko-based applications

Web browsers

Other applications

* Also uses Gecko to render its entire user interface via XUL.

See also

References

  1. ^ Embedding Mozilla
  2. ^ Mozilla SVG Status
  3. ^ nglayout project: identity crisis
  4. ^ DRAFT Gecko 1.9 Roadmap
  5. ^ Mozilla2:GraphicsPlan
  6. ^ Glimpse Of The Future
  7. ^ Gecko:Reflow Refactoring
Retrieved from "https://en.wikipedia.org/w/index.php?title=Gecko_(software)&oldid=115436678"