name = GNOME
caption = A GNOME 2.24 desktop
developer = The GNOME Project
latest_release_version = 2.24.0
latest_release_date = release date|mf=yes|2008|09|24
language = Multilingual (more than 35)
GNU Lesser General Public License GNU General Public License
website = [http://www.gnome.org/ www.gnome.org]
working_state = Current
GNOME (pron-en|gəˈnəʊm in RP or pron-en|gəˈnoʊm in the US/Canada) [ cite web | url = http://news.zdnet.co.uk/software/0,1000000121,2071014,00.htm | title = LinuxWorld: Linux readies its desktop assault | accessdate = 2008-10-02 ] is a
desktop environment—the graphical user interfacewhich runs on top of a computer operating system—composed entirely of free software. It is an international project that includes creating software developmentframeworks, selecting application softwarefor the desktop, and working on the programs which manage application launching, file handling, and window and task management.
GNOME is part of the
GNU Projectand can be used with various Unix-likeoperating systems, most notably Linux, and as part of Java Desktop Systemin Solaris.
The name originally stood for "GNU Network Object Model Environment", though this acronym is deprecated. cite web | url = http://mail.gnome.org/archives/desktop-devel-list/2006-April/msg00436.html | title = Desktop Development mailing list | accessdate = 2006-05-07 ]
The GNOME project puts heavy emphasis on simplicity, usability, and making things “just work”. The other aims of the project are:
* Freedom—to create a desktop environment that will always have the source code available for re-use under a
free software license.
* Accessibility—ensuring the desktop can be used by anyone, regardless of technical skill or physical disability.
Internationalization and localization—making the desktop available in many languages. At the moment GNOME is being translated to over 100 languages. [cite web |url=http://l10n.gnome.org/languages/ |title=GNOME Languages |accessdate=2008-01-20]
* Developer-friendliness—ensuring it is easy to write software that integrates smoothly with the desktop, and allow developers a free choice of programming language.
* Organization—a regular release cycle and a disciplined community structure.
* Support—ensuring backing from other institutions beyond the GNOME community.
In 1996, the
KDEproject was started. Although KDE was free software, it relied on the then non-free Qt widget toolkit. Members of the GNU project became concerned with the use of such a toolkit for building a free software desktop environment. In August 1997, two projects were started in response to KDE: the Harmony toolkit(a free replacement for the Qt libraries) and GNOME (a different desktop without Qt and built entirely on top of free software). [cite web | url = http://linuxtoday.com/news_story.php3?ltsn=2000-09-05-001-21-OP-LF-KE | author = Richard Stallman | title = Stallman on Qt, the GPL, KDE, and GNOME | accessdate = 2005-09-09 |date=2000-09-05 ] The initial project leaders for GNOME were Miguel de Icazaand Federico Mena.
In place of the Qt toolkit,
GTK+was chosen as the base of the GNOME desktop. GTK+ uses the GNU Lesser General Public License(LGPL), a free software license that allows GPL-incompatible software (including proprietary software) to link to it. The GNOME desktop itself is licensed under the LGPL for its libraries, and the GPL for applications that are part of the GNOME project itself. Having the toolkit and libraries under the LGPL allows applications written for GNOME to use a much wider set of licenses (including proprietary softwarelicenses). [cite web |url=http://www.fsf.org/licensing/licenses/lgpl.html |title=GNU Lesser General Public License - Free Software Foundation |accessdate=2008-01-20] While Qt is dual-licensed under both the QPLand the GPL, the freedom to link proprietary software with GTK+ at no charge makes it differ from Qt. However proponents of the free software philosophydeem the LGPLa disadvantage for free softwaredevelopers. Using the ordinary GPLfor a library gives free software developers an advantage over proprietary developers: a library that they can use, while proprietary developers cannot use it. [ cite web | url = http://www.gnu.org/licenses/why-not-lgpl.html | title = Why you shouldn't use the Lesser GPL for your next library | accessdate = 2008-09-11 ]
The name “GNOME” was proposed as an acronym of GNU Network Object Model Environment by Elliot Lee, one of the authors of
ORBitand the Object Activation Framework.Fact|date=February 2007 It refers to GNOME’s original intention of creating a distributed objectframework similar to Microsoft’s OLE. [ cite web | url = http://developer.gnome.org/doc/GGAD/ggad.html | title = GTK+ / Gnome Application Development | accessdate = 2006-09-08 | last = Pennington | first = Havoc | authorlink = Havoc Pennington | year = 1999 ] This no longer reflects the core vision of the GNOME project, and the full expansion of the name is now considered obsolete. As such, some members of the project advocate dropping the acronym and re-naming “GNOME” to “Gnome”.
As with most free software projects, the GNOME project is loosely managed. Discussion chiefly occurs on a number of public mailing lists. [ cite web | url = http://mail.gnome.org | title = GNOME mailing lists, rules and FAQs ]
In August 2000 the
GNOME Foundationwas set up to deal with administrative tasks and press interest and to act as a contact point for companies interested in developing GNOME software. While not directly involved in technical decisions, the Foundation does coordinate releases and decide which projects will be part of GNOME. Membership is open to anyone who has made a non-trivial contribution to the project. [ cite web | url = http://foundation.gnome.org/membership/ | title = Membership of the GNOME foundation | accessdate = 2005-09-08 ] Members of the Foundation elect a board of directors every November, and candidates for the positions must be members themselves.
Developers and users of GNOME gather at an annual meeting known as
GUADECin order to discuss the current state of the project and its future direction. [ cite web | url = http://guadec.org/about | title = About GUADEC ]
GNOME often incorporates standards from
freedesktop.orginto itself to allow GNOME applications to appear more integrated into other desktops (and vice versa), and encourages cooperation as well as competition.
GNOME is built from a large number of different projects. A few of the major ones are listed below:
* Bonobo – a
GConf– for storing application settings.
GVFS– a virtual file system.
GNOME Keyring– for storing encryptionkeys and security information.
* GNOME Translation Project – translate documentation and applications into different languages.
GTK+– a widget toolkit used for constructing graphical applications. The use of GTK+ as the base widget toolkit allows GNOME to benefit from certain features such as theming (the ability to change the look of an application) and smooth anti-aliased graphics. Sub-projects of GTK+ provide object oriented programming support (GObjects), extensive support of international character sets and text layout ( Pango) and accessibility (ATK). GTK+ reduces the amount of work required to port GNOME applications to other platforms such as Windows and Mac OS X.
Human interface guidelines(HIG) – research and documentation on building easy-to-use GNOME applications.
LibXML– an XML library.
ORBit– a CORBAORB for software componentry.
A number of
language bindings are available allowing applications to be written in a variety of programming languages, such as C++( gtkmm), Java ( java-gnome), Ruby ( ruby-gnome2), C#, (Gtk#), Python ( PyGTK), Perl( gtk2-perl) and many others. The only languages currently used in applications that are part of an official GNOME desktop release are C, C# and Python. [cite mailing list |url=http://mail.gnome.org/archives/desktop-devel-list/2006-April/msg00332.html |title=Mono bindings a blessed dependency? [Was: Tomboy in 2.16] |date= 2006-04-20|accessdate=2007-09-20 |mailinglist=desktop-devel |last=Newren |first=Elijah |authorlink= ]
Look and feel
GNOME is designed around the traditional computing
desktop metaphor. Its handling of windows, applications and files is similar to that of contemporary desktop operating systems. In its default configuration, the desktop has a launcher menu for quick access to installed programs and file locations; open windows may be accessed by a taskbar along the bottom of the screen and the top-right corner features a notification area for programs to display notices while running in the background. However these features can be moved to almost anywhere the user desires, replaced with other functions or removed altogether.
Metacityas its default window manager. Users can change the appearance of their desktop through the use of themes, which are sets consisting of an iconset, window manager border and GTK+ theme engine and parameters. Popular GTK+ themes include Bluecurveand Clearlooks(the current default theme).
GNOME puts emphasis on being easy for everyone to use. The HIG helps guide developers in producing applications which look and behave similarly, in order to provide a cohesive GNOME interface.
Since GNOME v2.0, a key focus of the project has been
usability. As a part of this, the GNOME Human Interface Guidelines (HIG) were created, which is an extensive guide for creating quality, consistent and usable GUI programs, covering everything from GUI design to recommended pixel-based layout of widgets.
During the v2.0 rewrite, many settings were deemed to be of little or no value to the majority of users and were removed. For instance, the preferences section of the Panel were reduced from a dialog of six tabs to one with two tabs.
Havoc Penningtonsummarized the usability work in his 2002 essay "Free Software UI", emphasizing the idea that all preferences have a cost, and it's better to "unbreak the software" than to add a UI preference to do that: [ cite web | url = http://ometer.com/free-software-ui.html | title = "Free Software UI" | accessdate = 2007-03-08 ]
Cquote|A traditional free software application is configurable so that it has the union of all features anyone's ever seen in any equivalent application on any other historical platform. Or even configurable to be the union of all applications that anyone's ever seen on any historical platform (Emacs *cough*).
Does this hurt anything? Yes it does. It turns out that preferences have a cost. Of course, some preferences also have important benefits - and can be crucial interface features. But each one has a price, and you have to carefully consider its value. Many users and developers don't understand this, and end up with a lot of cost and little value for their preferences dollar.
Some people believe that GNOME should be more functional. One of these is
Linus Torvalds, creator of the Linux kernel, who commented in a usability-related discussion on the GNOME usability mailing list: [ cite web | url = http://mail.gnome.org/archives/usability/2005-December/msg00021.html | title = Printing dialog and GNOME | author= Linus Torvalds|date=2005-12-12 | accessdate=2007-12-13 ]
Each of the parts making up the GNOME project has its own version number and release schedule. However, individual module maintainers coordinate their efforts to create a full GNOME stable release on a roughly six-month schedule.
The releases listed in the table below are classed as stable.
GNOME releases are made to the ftp.gnome.org FTP server [ cite web | url = http://ftp.gnome.org/pub/gnome/sources/ | title = GNOME stable release ftp server ] in the form of
source codewith configure scripts, which are compiled by operating system vendors and integrated with the rest of their systems before distribution. Most vendors use only stable and tested versions of GNOME, and provide it in the form of easily installed, pre-compiled packages. The source code of every stable and development version of GNOME is stored in the GNOME Subversion source code repository. [ cite web | url = http://svn.gnome.org/ | title = Information about the GNOME source code repository ]
A number of build-scripts (such as
JHBuildor GARNOME) are available to help automate the process of compiling the source code.
There are many sub-projects under the umbrella of the GNOME project, and not all of them are currently included in GNOME releases. Some are considered purely experimental concepts, or for testing ideas that will one day migrate into stable GNOME applications; others are code that is being polished for direct inclusion. Some examples include:
* Project Soylent – making “people” and their interactions first-class objects within the GNOME framework. [ cite web | url = http://trac.galago-project.org/wiki/ProjectSoylent | title = Project Soylent homepage ]
* Project Ridley – to consolidate several small undermaintained libraries into GTK+, such as libgnome and libgnomeprint. [cite web |url=http://live.gnome.org/ProjectRidley |title=ProjectRidley - GNOME Live! |accessdate=2008-01-20]
The next version of the desktop environment was officially announced at the 2008
GUADECconference held in Istanbul in July. Release has been targeted for 2010, in place of version 2.30 of the current branch. Although the desktop will undergo a major revision, changes planned so far are mostly incremental. [cite web |url=http://arstechnica.com/news.ars/post/20080714-gnome-3-0-officially-announced-and-explained.html |title=GNOME 3.0 officially announced... and explained|accessdate=2008-08-02]
GNOME is the default desktop environment for several Linux distributions, most notably
Debian, Fedora and Ubuntu. Foresight Linuxshowcases the latest releases of GNOME.
"For derived and other distributions, see Comparison of Linux distributions and Comparison of Linux Live Distros."
List of GNOME applications
Comparison of X Window System desktop environments
List of operating systems using GNOME
* [http://www.gnome.org/ The GNOME website]
* [http://live.gnome.org/ Official GNOME Live Wiki] .
* [http://www.gnomedesktop.org/ FootNotes] – a news site and discussion forum
* [http://www.gnomejournal.org/ GNOME Journal] – an online magazine devoted to the GNOME Desktop
Wikimedia Foundation. 2010.
См. также в других словарях:
gnome — gnome … Dictionnaire des rimes
Gnome — 3.2 Basis … Deutsch Wikipedia
GNOME — GNOME … Википедия
GNOME — 2.22 Basisdaten … Deutsch Wikipedia
GNOME — Captura de GNOME 3.2 Desarrollador … Wikipedia Español
GNOME Do — en acción (Interfaz clásico) Desarrollador GNOME Do Core Team … Wikipedia Español
Gnôme — Gnome et Rhône Gnome et Rhône Activité(s) Constructeur de cyclomoteurs … Wikipédia en Français
gnome — [ gnom ] n. m. • 1583; lat. alchim. gnomus « intelligence »; cf. gnomique ♦ Petit génie laid et difforme qui, selon le Talmud et les kabbalistes, habite à l intérieur de la terre dont il garde les trésors. Le monde surnaturel des gnomes. ♢ Homme… … Encyclopédie Universelle
GNOME Do — en action … Wikipédia en Français
GNOME-DB — is the database application of GNOME Office, the office suite of the GNOME desktop. The project aims to provide a free unified data access architecture to the GNOME project for all Unix platforms. GNOME DB is useful for any application that… … Wikipedia
GNOME-DB — est une application de base de données faisant partie de GNOME Office, la suite bureautique de l environnement GNOME. Le projet a pour but de fournir une architecture unifiée d accès aux données pour le projet GNOME, pour toutes les platformes… … Wikipédia en Français