2003 Patanjali Somayaji 2003 David Bordoley GNOME Documentation Project &legal; Patanjali Somayaji GNOME Documentation Project

patanjali@codito.com

David Bordoley Epiphany Development Team

bordoley@msu.edu

This manual describes version &appversion; of &fr;. Epiphany epiphany Browser &fr; is a GNOME web browser based on the mozilla rendering engine. A web browser is more than an application, it is a way of thinking, it is a way of seeing the world. Epiphany's principles are simplicity and standards compliance.

Simplicity: 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 messenging or coffee making. The UNIX philosophy is to design small tools that do one thing, and do it well. Epiphany also address simplicity with modularity to make a light and powerful application. If something can be implemented using external applications or components, we use it rather than wasting resources in the web browser. Integration will be achived with CORBA, Bonobo, and the ever popular command line. Mail will be handled with your favorite e-mail application (Evolution, pine, mutt, balsa, pronto, whatever). Standards compliance: The introduction of non-standard features in browsers could make it difficult or impossible to use alternative products like Epiphany if developers embrace them. Alternative (standards complying) browsers could not be able to fully access web sites making use of these features. The success of non-standard features can ultimately lead to forcing one browser, on one platform to dominate the market. Standards compliance ensures the freedom of choice. Epiphany aims to achieve this. USER INTERFACE LINES HIG compliance Epiphany is going to follow version 1.0 of the gnome user guidelines. Unless there are very seriuos reasons to make an exception not following it will be considered a bug. "I follow the HIG only when I like it" is not a legitimate approach. Any areas where we diverge from the HIG will communicated to the HIG team for future consideration. Gnome integration Epiphany's main goal is to be integrated with the gnome desktop. We dont aim to make epiphany usable outside Gnome. If someone will like to use it anyway, it's just a plus. Ex: Making people happy that don't have control center installed is not a good reason to have mime configuration in epiphany itself. Simple design Feature bloat and user interface clutter is evil :) Preferences We will follow the new gnome policy about preferences. I think Havoc Pennington already explained it a lot better than I could ever do. http://www106.pair.com/rhp/free-software-ui.html User target We target non-technical users by design. This happens to be 90% of the user population. (Technical details should not exposed in the interface) We target web users, we dont directly target web developers. A few geek-oriented feautures can be kept as long as they are non-obtrusive. &fr; was written by Marco Presenti Gritti (marco@it.gnome.org). To find more information about &fr;, please visit the Epiphany Web page. This manual was written by David Bordoley (bordoley@msu.edu) and Patanjali Somayaji (patanjali@codito.com). This program is distributed under the terms of the GNU General Public license as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. A copy of this license can be found at this link, or in the file COPYING included with the source code of this program.