GTK port of Apple's WebKit rendering engine, called WebKitGTK. It is developed by the GNOME project for Unix-like systems. It is the default and official web browser of GNOME, and part of the GNOME Core Applications. Despite being a component of GNOME, Web has no dependency on GNOME components. Fedora and Arch Linux. Marco Pesenti Gritti, the initiator of Galeon, originally developed Epiphany in 2002 as a fork of Galeon. The fork occurred because of the disagreement between Gritti and the rest of Galeon developers about new features. Gritti regarded Galeon's monolithic design and the number of user-configurable features as factors that were limiting Galeon's maintainability and usability, but the rest of the Galeon developers wanted to add more features. Around the same time, the GNOME project adopted a set of human interface guidelines, which promoted simplification of user interfaces. As Galeon was oriented towards power users, most developers disapproved. As a result, Gritti created a new browser based on Galeon, with most of the non-critical features removed.
He intended Epiphany to comply with the GNOME HIG. As such, Epiphany used the global GNOME theme and other settings from inception. While Mozilla has an excellent rendering engine, its default XUL-based interface is considered to be overcrowded and bloated. Furthermore, on slower processors even trivial tasks such as pulling down a menu is less than responsive. Epiphany aims to utilize the simplest interface possible for a browser. Keep in mind that simple does not necessarily mean less powerful. We believe the commonly used browsers of today are too big, buggy, and bloated. Epiphany addresses simplicity with a small browser designed for the web-not mail, newsgroups, file management, instant messaging or coffee making. The Unix philosophy is to design small tools that do one thing, and do it well. Epiphany's main goal is to be integrated with the gnome desktop. We don't aim to make Epiphany usable outside Gnome. If someone will like to use it anyway, it's just a plus.
For example: Making people happy that don't have control center installed is not a good reason to have mime configuration in Epiphany itself. Galeon continued after the fork, but lost momentum due to the remaining developers' failure to keep up with changes in the Mozilla platform. Galeon development stalled and the developers decided to work on extensions to bring Galeon's advanced features to Epiphany. Gritti ended his work on Epiphany and a GNOME team led by Xan Lopez, Christian Persch and Jean-François Rameau now direct the project. Epiphany initially used the Gecko layout engine from the Mozilla project to display web pages. It provided a GNOME graphical user interface for Gecko, instead of Mozilla's cross-platform interface. The development of Epiphany was mainly focused on usability improvements compared to major browsers at the time. The most notable was the new text entry widget, which was introduced in version 1.8. The new widget supported icons inside the text area and reduced the screen space needed to present information, while improving GNOME integration.
The next major milestone was version 2.14, which was the first to follow GNOME's version numbering. It also featured network awareness using NetworkManager, smart bookmarks improvements, and the option to build with XULRunner. The latter was critical. Previously, Epiphany could only use an installed Mozilla web browser as a web engine provider. The XULRunner support made it possible to install Epiphany as the only web browser on the system. The development process suffered from major problems related to the Gecko backend. Notably, the release cycles of the two projects did not line up efficiently. Additionally, Mozilla increasingly disregarded third-party software that wished to make use of Gecko, until it became viewed as an integrated Firefox component. To address these issues, in July 2007, the Epiphany team added support for WebKit as an alternative rendering engine. On April 1, 2008, the team announced that it would remove the ability to build it using Gecko and proceed using only WebKit. July 1, 2009, when it was announced that 2.26 would be the final Gecko-based version.
|