release-notes r1246 - in branches/gnome-2-0: . help help/C help/C/figures
- From: murrayc svn gnome org
- To: svn-commits-list gnome org
- Subject: release-notes r1246 - in branches/gnome-2-0: . help help/C help/C/figures
- Date: Mon, 3 Nov 2008 11:07:03 +0000 (UTC)
Author: murrayc
Date: Mon Nov 3 11:07:03 2008
New Revision: 1246
URL: http://svn.gnome.org/viewvc/release-notes?rev=1246&view=rev
Log:
2008-11-03 Murray Cumming <murrayc murrayc com>
* Moved from the releng module, rearranging the directory
structure as appropriate, and adding necessary nodes to the abstract
node in the XML.
Added:
branches/gnome-2-0/
- copied from r1245, /branches/gnome-2-2/
branches/gnome-2-0/help/C/menuediting.xml
branches/gnome-2-0/help/C/release-notes.xml
Removed:
branches/gnome-2-0/help/C/epiphany.xml
branches/gnome-2-0/help/C/figures/acme.png
branches/gnome-2-0/help/C/figures/control_panel_fonts.png
branches/gnome-2-0/help/C/figures/control_panel_fonts_details.png
branches/gnome-2-0/help/C/figures/control_panel_theme.png
branches/gnome-2-0/help/C/figures/control_panel_theme_details.png
branches/gnome-2-0/help/C/figures/fileroller.png
branches/gnome-2-0/help/C/figures/highcontrastinverse.png
branches/gnome-2-0/help/C/figures/lowcontrast.png
branches/gnome-2-0/help/C/figures/multimedia_util_soundrecorder.png
branches/gnome-2-0/help/C/figures/nautilus.png
branches/gnome-2-0/help/C/figures/nautilus_context_menu_plugin.png
branches/gnome-2-0/help/C/figures/nautilus_preferences.png
branches/gnome-2-0/help/C/figures/nautilus_property_page_tab_audio.png
branches/gnome-2-0/help/C/figures/nautilus_property_page_tab_image.png
branches/gnome-2-0/help/C/figures/nautilus_view_as_audio.png
branches/gnome-2-0/help/C/figures/panel.png
branches/gnome-2-0/help/C/figures/panel_action_open_recent.png
branches/gnome-2-0/help/C/figures/panel_action_run_program.png
branches/gnome-2-0/help/C/figures/panel_action_search.png
branches/gnome-2-0/help/C/figures/panel_applet_notification_area.png
branches/gnome-2-0/help/C/figures/panel_applet_wireless.png
branches/gnome-2-0/help/C/figures/panel_show_desktop.png
branches/gnome-2-0/help/C/figures/smallfoot.png
branches/gnome-2-0/help/C/figures/theme.png
branches/gnome-2-0/help/C/figures/themes_crux.png
branches/gnome-2-0/help/C/figures/themes_grand_canyon.png
branches/gnome-2-0/help/C/figures/themes_high_contrast.png
branches/gnome-2-0/help/C/figures/themes_high_contrast_inverse.png
branches/gnome-2-0/help/C/figures/themes_large_print.png
branches/gnome-2-0/help/C/figures/themes_mist.png
branches/gnome-2-0/help/C/figures/themes_ocean_dream.png
branches/gnome-2-0/help/C/figures/themes_smokey_blue.png
branches/gnome-2-0/help/C/figures/themes_traditional.png
branches/gnome-2-0/help/C/figures/util_charactermap.png
branches/gnome-2-0/help/C/figures/util_eog.png
branches/gnome-2-0/help/C/figures/util_gedit.png
branches/gnome-2-0/help/C/figures/why_preferences.png
branches/gnome-2-0/help/C/rna11y.xml
branches/gnome-2-0/help/C/rnapplets.xml
branches/gnome-2-0/help/C/rnapplications.xml
branches/gnome-2-0/help/C/rncontrolcenter.xml
branches/gnome-2-0/help/C/rndesktop.xml
branches/gnome-2-0/help/C/rndocs.xml
branches/gnome-2-0/help/C/rnepiphany.xml
branches/gnome-2-0/help/C/rnfileroller.xml
branches/gnome-2-0/help/C/rnfonts.xml
branches/gnome-2-0/help/C/rngames.xml
branches/gnome-2-0/help/C/rngcalctool.xml
branches/gnome-2-0/help/C/rngnomemeeting.xml
branches/gnome-2-0/help/C/rngnomeutilities.xml
branches/gnome-2-0/help/C/rngpdf.xml
branches/gnome-2-0/help/C/rngucharmap.xml
branches/gnome-2-0/help/C/rni18n.xml
branches/gnome-2-0/help/C/rninstallation.xml
branches/gnome-2-0/help/C/rnmultihead.xml
branches/gnome-2-0/help/C/rnmultimedia.xml
branches/gnome-2-0/help/C/rnmultimediakeys.xml
branches/gnome-2-0/help/C/rnnewmaintainers.xml
branches/gnome-2-0/help/C/rnpanel.xml
branches/gnome-2-0/help/C/rnplatform.xml
branches/gnome-2-0/help/C/rnstandards.xml
branches/gnome-2-0/help/C/rnsysadmin.xml
branches/gnome-2-0/help/C/rnterminal.xml
branches/gnome-2-0/help/C/rnthanks.xml
branches/gnome-2-0/help/C/rnthemes.xml
branches/gnome-2-0/help/C/rntoc.xml
branches/gnome-2-0/help/C/rnutilities.xml
branches/gnome-2-0/help/C/rnwhy.xml
branches/gnome-2-0/help/C/rnwm.xml
branches/gnome-2-0/help/C/rnzenity.xml
Modified:
branches/gnome-2-0/configure.in
branches/gnome-2-0/help/Makefile.am
Modified: branches/gnome-2-0/configure.in
==============================================================================
--- /branches/gnome-2-2/configure.in (original)
+++ branches/gnome-2-0/configure.in Mon Nov 3 11:07:03 2008
@@ -1,4 +1,4 @@
-AC_INIT([release-notes],[2.2])
+AC_INIT([release-notes],[2.0])
AM_INIT_AUTOMAKE
AM_MAINTAINER_MODE
Added: branches/gnome-2-0/help/C/menuediting.xml
==============================================================================
--- (empty file)
+++ branches/gnome-2-0/help/C/menuediting.xml Mon Nov 3 11:07:03 2008
@@ -0,0 +1,213 @@
+<?xml version="1.0"?>
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd";[
+]>
+<article>
+ <title>Menu Editing</title>
+ <sect1 id="introduction">
+ <title>Introduction</title>
+ <para>
+ Menu editing in the GNOME 2 desktop has undergone a large amount of
+re-work
+ to move to using <ulink
+
+url="http://developer.gnome.org/doc/API/gnome-vfs/";>gnome-vfs</ulink>, the file system abstraction library and
+ an implementation of a <ulink
+url="http://www.freedesktop.org";>proposed
+ vfolder spec</ulink>.
+ </para>
+ <para>
+ The menus in GNOME are based on a collection of <ulink
+
+url="http://www.freedesktop.org/standards/desktop-entry-spec/desktop-entry-spec.html";>.desktop
+files</ulink>
+ arranged in a suitable order depending on their contents. For
+GNOME
+ 1.4, there were 2 main problems with the way these .desktop files
+were
+ handled:
+ </para>
+ <sect2 id="nostandardlocation">
+ <title>No Standard Location</title>
+ <para>
+ With no standard location, 3rd party application developers do not
+ know where to install their .desktop files for them to be picked
+up by
+ the menu. Many distributions have their own idea of where this
+ location should be, creating a large amount of unecessary
+ inconsistency and heartache trying to integrate your application
+on
+ various distributions.
+ </para>
+ </sect2>
+ <sect2 id="menustructureproblem">
+ <title>Structure of menu is set by the location on disk</title>
+ <para>
+ With a set location, and consequently a set menu structure, it is
+not
+ possible to change the layout of the menus without adversely
+affecting
+ 3rd party application developers. This inflexibility has bitten
+many
+ people in the past.
+ </para>
+ </sect2>
+ </sect1>
+ <sect1 id="howdoesitwork">
+ <title>How Does It All Work?</title>
+ <para>
+ The menu system, as mentioned in the previous section, is based on
+ gnome-vfs using a 'vfolder' mechanism. Menu vfolders aren't much
+unlike
+ Evolution's mail vfolders in that they filter out the menu items, in
+ this case the .desktop files, according to their category.
+ </para>
+ <para>
+ The vfolders are based around <ulink
+
+url="http://cvs.gnome.org/bonsai/cvsblame.cgi?file=gnome-vfs/doc/vfolder-info-spec.dtd&rev=&root=/cvs/gnome";>.vfolder-info
+files</ulink>, which are xml
+ based. In this file you specify how your menu should filter the
+ .desktop files in terms of order, category, whether it should
+include
+ optional .desktop file locations, omit certain .desktop files and
+many
+ other rules.
+ </para>
+ <para>
+ Each menu is based on a .directory file, which for all intents and
+ purposes is another .desktop file.
+ </para><para>
+The order of items, both menu items and menu categories, is determined alphabetically based on the name field in the .desktop or .directory file as appropriate.
+</para>
+ <para>
+ With the introduction of this mechanism, it has been necessary to
+ introduce 2 new keys to the .desktop file format -
+ </para>
+ <sect2 id="categories">
+ <title>Categories</title>
+ <para>
+ This key describes the application and it's potential position
+within
+ the menus. It is based on a set of distinct, non free
+form, <ulink
+
+url="http://www.freedesktop.org/standards/FIXME/vfolder-spec.html";>keywords</ulink>.</para>
+ <para>
+ For example, an application like GNOME Calculator would have the
+ following in its .desktop -
+ <programlisting>
+ Categories=Application;Utility;
+ </programlisting>
+ </para>
+
+ </sect2>
+ <sect2 id="showonlyin">
+ <title>ShowOnlyIn</title>
+ <para>
+ This optional key is used when some applications is desktop
+specific
+ eg. GNOME Panel Preferences.
+ </para>
+ </sect2>
+ </sect1>
+ <sect1 id="practicalities">
+ <title>Making It Work</title>
+ <para>
+ <warning>
+ <para>
+ The following is included only for benefit of system
+administrators
+ and others who need fine-grained control over menu
+ configurations. It is not supported.
+ </para>
+ </warning>
+ The standard default location for .desktop files is
+ <filename>/usr/share/applications</filename>, or if that is not
+available
+ <filename>$prefix/share/applications</filename>. The best
+advice is to
+ look at the existing examples of the various files and try to
+copy by
+ example.
+ </para>
+ <para>
+ The standard location for applications.vfolder.info and .directory files is
+ <filename>$prefix/etc/gnome-vfs-2.0/vfolders</filename>. These
+can also be
+ mirrored in <filename>~/.gnome2/vfolders</filename> (.desktop
+files in
+ subdir applications). If you want global menus, edit files in
+ <varname>$prefix</varname>, if you want per user edit
+ files in user directory. The files in user directory take
+precedence over
+ system files. Changes to system files will not override user
+settings.
+ </para>
+ <sect2 id="addentries">
+ <title>To Add Menu Entries</title>
+ <para>
+ Create a desktop file using an existing file as a template. edit
+this
+ file and add/edit a "Categories=" line at the bottom.
+This
+ should include a keyword matching the appropriate menu item eg: for
+an
+ Internet app you should have
+ <programlisting>
+Categories=Application;Network
+ </programlisting>
+ </para>
+
+ <para>
+ Restart the panel.
+ </para>
+ </sect2>
+ <sect2 id="removeentries">
+ <title>To Remove Menu Entries</title>
+ <para>
+ Edit appropriate <filename>applications.vfolder-info</filename> to
+ include an <Exclude> </Exclude> entry for the
+appropriate
+ .desktop file.
+ </para>
+ <para>
+ Restart the panel.
+ </para>
+ </sect2>
+ <sect2 id="remaddsubmenuapps">
+ <title>To remove/add submenus in the 'Applications' menu</title>
+ <para>
+ Edit appropriate <filename>applications.vfolder-info</filename>.
+ </para>
+ <para>
+ Create appropriate <filename>.directory</filename> file (remember
+name
+ is set by the name field in the <filename>.directory</filename>
+file).
+ </para>
+ </sect2>
+ <sect2 id="createnewsubresearchapp">
+ <title>To create a new submenu 'Research' in the 'Applications'
+menu</title>
+ <para>
+ Add $prefix/share/gnome/vfolders/Research.directory
+ </para>
+ <para>
+ Edit appropriate <filename>applications.vfolder-info</filename>
+file.
+ </para>
+ </sect2>
+ </sect1>
+ <sect1 id="additionalinfo">
+ <title>Additional Information</title>
+ <para>
+ Additional details on manual editing of menus can be found <ulink
+
+url="http://web.archive.org/web/20070820180707/www.redtux.demon.co.uk/docs/gnome_menu_edit_doc.20_6.html";>
+ here</ulink>.
+ </para>
+ </sect1>
+ </article>
+
+
Added: branches/gnome-2-0/help/C/release-notes.xml
==============================================================================
--- (empty file)
+++ branches/gnome-2-0/help/C/release-notes.xml Mon Nov 3 11:07:03 2008
@@ -0,0 +1,1427 @@
+<?xml version="1.0"?>
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd";[
+<!ENTITY g2 "GNOME 2">
+<!ENTITY g2x "GNOME 2.0.2">
+<!ENTITY version "2.0">
+]>
+
+<article id="index" lang="en" xmlns:xi="http://www.w3.org/2001/XInclude";>
+ <articleinfo>
+ <title>GNOME &version; Release Notes</title>
+
+ <authorgroup>
+ <author role="maintainer">
+ <firstname>John</firstname>
+ <surname>Fleck</surname>
+ <affiliation>
+ <orgname>GNOME Documentation Project</orgname>
+ </affiliation>
+ </author>
+ </authorgroup>
+
+ <publisher>
+ <publishername>GNOME Foundation</publishername>
+ </publisher>
+ <pubdate>2004-03-31</pubdate>
+ <edition>&version;</edition>
+
+ <abstract role="description">
+ <para>GNOME has a time-based release schedule. This means that there is a
+ new GNOME release with accompanying notes every six months.</para>
+ </abstract>
+
+ </articleinfo>
+
+<sect1 id="intro">
+
+ <title>Introduction</title>
+ <para>
+ &g2x; is the newest version of the complete, free and easy-to-use GNOME
+ desktop environment. In addition to basic desktop functionality, it
+ includes a powerful application framework for software developers, with
+ support for object embedding, internationalization and accessibility.
+ GNOME is part of <ulink url="http://www.gnu.org/";>The GNU
+ Project</ulink>, and is free software.
+ </para>
+ <para>
+ The &g2x; Desktop and Developer platform includes a complete suite of
+ libraries necessary to support GNOME applications. It also includes all
+ the basic utilities for your day-to-day computing, from a simple
+ weather monitor to a powerful file manager.
+ </para>
+ <para>
+ &g2x; is compatible with a number of platforms, including GNU/Linux,
+ Solaris, HP-UX, Unix and BSD.
+ </para>
+ </sect1>
+
+ <sect1 id="whatsnew">
+ <title>What's New in &g2;</title>
+ <para>
+ The lengthy &g2; development cycle allowed the introduction of a
+ number of features that improve performance and usability. It also
+ includes a powerful new framework that can be leveraged by developers.
+ </para>
+ <sect2 id="fontsandgraphics">
+ <title>Improved Fonts and Graphics</title>
+ <itemizedlist>
+ <listitem>
+ <para>Fonts can be antialiased (or not, or only antialiased at certain
+ sizes, or whatever you like).</para>
+ </listitem>
+ <listitem>
+ <para>No flicker in GTK apps</para>
+ </listitem>
+ <listitem>
+ <para>Images are composited onto backgrounds with full alpha channel,
+ accelerated via MMX and the RENDER extension.</para>
+ </listitem>
+ <listitem>
+ <para>New enhanced icons.</para>
+ </listitem>
+ </itemizedlist>
+ </sect2>
+
+ <sect2 id="ui">
+ <title>Usability</title>
+ <para>
+ Streamlining, consistency and coherence have been the primary foci for
+ &g2; Usability work. Above all we have tried to consider you, the
+ user, as the focus of our design.
+ </para>
+ <para>
+ <emphasis>Streamlining:</emphasis> Rather than adding a great pile of
+ new gadgets and preferences, &g2; has been streamlined. Interface
+ clutter had led to a GNOME where you could almost literally "do less
+ with more". &g2; removes many obscure or rarely used features (one or
+ two of which may have been dear to you personally). In exchange you will
+ find that most of the features you care about are much easier to access
+ because they are not obscured by a million other items.
+ </para>
+ <para>
+ <emphasis>Consistency:</emphasis> Interfaces that behave according to
+ consistent patterns are easier to learn, faster to use, and less prone to
+ error. The <ulink
+ url="http://developer.gnome.org/projects/gup/hig/1.0/";>GNOME Human
+ Interface Guidelines</ulink> have helped make the &g2; interface more
+ predictable, producing consistency between applications and promoting
+ usable patterns within individual applications.
+ </para>
+ <para>
+ <emphasis>Coherence:</emphasis> The &g2; desktop fits together
+ well. From "Log In" to "Log Out", usability studies,
+ countless brainstorming hours, and tireless hacking have produced a
+ holistic desktop - more than a loose confederation of modules.
+ </para>
+ <para>
+ Specific user-visible improvements include:
+ </para>
+ <sect3 id="menusandpanel">
+ <title>Menus and Panel</title>
+ <para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ Windows can be dragged between workspaces with the Workspace
+ Switcher applet
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Menus scroll when they get too big
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Smarter menus accommodate diagonal mouse movements
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </sect3>
+
+ <sect3 id="dialogs">
+ <title>Dialogs</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ File selector doesn't forget filenames when selecting a
+ different directory
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Revamped color and font selectors
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ New <application>Run Program</application> dialog with
+ command completion
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Text fields include right-click menus for cutting, copying and
+ pasting text
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </sect3>
+
+ <sect3 id="iconsandthemes">
+ <title>Icons and Themes</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ New stock icons and color palette
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Support for theming of stock icons
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <application>CD Player</application> and login screens are
+ now themeable
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ A clean and attractive default appearance
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </sect3>
+
+ <sect3 id="applications">
+ <title>Applications</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Redesigned and easier to use <application>Search Tool
+ </application>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Brand new lightweight help application, <application>Yelp
+ </application>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <application>Control center</application>
+ applications for controlling GNOME 2 properties
+ have been greatly simplified and reduced in number
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Increasing compliance with <ulink url="http://freedesktop.org/"; type="http">
+ freedesktop.org</ulink> standards
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Rewritten terminal application with tabs and profiles
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ A brand new dynamic, centralized configuration system
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Many applications have been renamed to better suit their
+ purpose
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </sect3>
+ </sect2>
+
+ <sect2 id="performance">
+ <title>Performance</title>
+ <para>
+ &g2x; exhibits notable performance
+ improvements over its predecessors and some competitors, even on older,
+ slower machines:
+ </para>
+ <sect3 id="testimonial01">
+ <title>Bradley Shuttleworth</title>
+ <para>
+ <emphasis>Just installed it smoothly on a P2-233 with 96 Mb RAM.
+ <application>Nautilus</application> fires up a new window in
+ under 5 seconds (which, given that <application>Nautilus
+ </application> took longer than that in 1.4 on my Gigahertz
+ laptop, is a pleasant change).</emphasis>
+ </para>
+ <para>
+ <emphasis>(And to brag, its faster than Windows XP on my laptop,
+ too... XP takes a shine longer to fire up
+ <application>Explorer</application>, and various other tasks are
+ slightly faster.)</emphasis>
+ </para>
+ </sect3>
+ <sect3 id="testimonial02">
+ <title>Mads Villadsen</title>
+ <para>
+ <emphasis>I run it quite comfortably on a K6-300 with 96MB
+ RAM. Everything feels at least as fast as with GNOME 1.4
+ - and
+ <application>Nautilus</application> has become really usable as
+ well. All in all it is pleasure to use :-)</emphasis>
+ </para>
+ </sect3>
+ </sect2>
+ <sect2>
+ <title>Keyboard Navigation</title>
+ <para>
+ Thanks to the <ulink url="http://developer.gnome.org/projects/gap/";>
+ GNOME Accessibility Project</ulink>, &g2; has improved keyboard
+ navigation, including mnemonics that are easier for developers to
+ implement, improved keyboard navigation of the new tree widget and
+ key bindings that are more consistent where standards already exist.
+ </para>
+ </sect2>
+
+ <sect2 id="a11y">
+ <title>Accessibility</title>
+ <para>
+ Keyboard navigation is a key part of accessibility support that will be
+ useful to all users, but there are many other aspects to it.
+ </para>
+ <para>
+ The core of accessibility support is a set of hooks in GTK that allow
+ an external program to query applications about their GUI. For
+ example, an external program can ask what buttons and menu items
+ there are, their state, what their labels contain, and so on. This can
+ be used by a screen reader to tell a blind user what's on the screen,
+ for example.
+ </para>
+ <para>
+ This would allow a high-level scripting feature with commands
+ such as "activate the <guimenu>File</guimenu> menu, choose
+ <guimenuitem>Open</guimenuitem>, <guimenuitem>Select All</guimenuitem>,
+ <guimenuitem>Copy</guimenuitem>" This kind of scripting would use high
+ level user comprehensible GUI features and would not depend on special
+ application support for scripting. It would just work automatically
+ with any GTK app.
+ </para>
+ </sect2>
+
+ <sect2 id="i18n">
+ <title>Internationalization</title>
+ <para>
+ Internationalization has two major changes:
+ <itemizedlist>
+ <listitem>
+ <para>
+ &g2; has moved to Unicode throughout, so you can mix multiple
+ languages and scripts in the same document, and use funky
+ symbols such as bullets and dingbats in a document.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ &g2; handles <quote>hard</quote> languages such as right-to-left
+ languages and languages that have ligatures and
+ reordering.
+ </para>
+ </listitem>
+ </itemizedlist>
+ One major implication of Unicode is that the same code paths will now
+ be used for European and Asian text, so GNOME will almost certainly
+ work out-of-the-box for people in all countries (except for input
+ methods).
+ </para>
+ </sect2>
+ <sect2 id="libxml">
+ <title>XML</title>
+ <para>
+ &g2; marks the first GNOME release to use <ulink
+ url="http://www.xmlsoft.org/";>libxml2</ulink>, one of the most complete and
+ standards-compliant free <acronym>XML</acronym> libraries available. It
+ includes <application>libxslt</application>, a complete implementation of
+ the <acronym>XSLT</acronym> specification.
+ </para>
+ </sect2>
+
+
+ </sect1>
+
+ <sect1 id="beyond">
+ <title>Beyond the Desktop</title>
+ <para>
+ While the &g2; Desktop and Developer Platform was designed so that
+ users could continue to user their GNOME 1.x applications, in many cases
+ they will not have to wait long for &g2; versions of their favorite
+ software. A number of developers have already begun porting their
+ applications to the new platform prior to its release in order to take
+ advantage of its new features. Examples include:
+ <variablelist>
+ <varlistentry>
+ <term>Gnumeric</term>
+ <listitem>
+ <para>
+ <ulink
+ url="http://www.gnome.org/projects/gnumeric/download.shtml";>Gnumeric</ulink>,
+ the spreadsheet. The 1.1.x series contains the &g2; versions.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>GNOME-DB</term>
+ <listitem>
+ <para>
+ <ulink
+ url="http://www.gnome-db.org/download.php";>GNOME-DB</ulink>, a
+ database integration toolkit.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Galeon</term>
+ <listitem>
+ <para>
+ <ulink url="http://galeon.sourceforge.net/";>Galeon</ulink> web
+ browser. A port is underway, but depends on completion of the GTK+ 2
+ port of <ulink
+ url="http://bugzilla.mozilla.org/show_bug.cgi?id=92033";>Mozilla</ulink>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>GIMP</term>
+ <listitem>
+ <para>
+ <ulink url="http://www.gimp.org/devel_ver.html";>GIMP</ulink>, the
+ GNU Image Manipulation Program.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Xchat</term>
+ <listitem>
+ <para>
+ <ulink url="http://xchat.org/files/source/1.9/";>Xchat</ulink>, an
+ <acronym>IRC</acronym> client
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>MrProject</term>
+ <listitem>
+ <para>
+ <ulink url="http://mrproject.codefactory.se/";>MrProject</ulink>
+ project management software.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>File Roller</term>
+ <listitem>
+ <para>
+ <ulink url="http://fileroller.sourceforge.net/";>File
+ Roller</ulink>, an archive manager.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Bluefish</term>
+ <listitem>
+ <para>
+ <ulink
+ url="http://pkedu.fbt.eitn.wau.nl/~olivier/snapshots/";>Bluefish</ulink>
+ <acronym>HTML</acronym> editor.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Gthumb</term>
+ <listitem>
+ <para>
+ <ulink
+ url="http://gthumb.sourceforge.net/download.html";>Gthumb</ulink>,
+ an image manager.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Eclipse</term>
+ <listitem>
+ <para>
+ <ulink
+ url="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-swt-home/dev.html";>Eclipse</ulink>
+ development platform.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </para>
+ </sect1>
+
+ <sect1 id="installation">
+ <title>Installation</title>
+ <sect2 id="buildorder">
+ <title>Build Order</title>
+ <para>
+ The packages should be built in the following order:
+ <orderedlist>
+ <listitem>
+ <para>libxml2</para>
+ </listitem>
+ <listitem>
+ <para>libxslt</para>
+ </listitem>
+ <listitem>
+ <para>intltool</para>
+ </listitem>
+ <listitem>
+ <para>scrollkeeper</para>
+ </listitem>
+ <listitem>
+ <para>pkgconfig</para>
+ </listitem>
+ <listitem>
+ <para>audiofile</para>
+ </listitem>
+ <listitem>
+ <para>esound</para>
+ </listitem>
+ <listitem>
+ <para>gtk-doc</para>
+ </listitem>
+ <listitem>
+ <para>glib</para>
+ </listitem>
+ <listitem>
+ <para>linc</para>
+ </listitem>
+ <listitem>
+ <para>atk</para>
+ </listitem>
+ <listitem>
+ <para>gnome-common</para>
+ </listitem>
+ <listitem>
+ <para>pango</para>
+ </listitem>
+ <listitem>
+ <para>libIDL</para>
+ </listitem>
+ <listitem>
+ <para>ORBit2</para>
+ </listitem>
+ <listitem>
+ <para>bonobo-activation</para>
+ </listitem>
+ <listitem>
+ <para>gtk+</para>
+ </listitem>
+ <listitem>
+ <para>GConf</para>
+ </listitem>
+ <listitem>
+ <para>libart_lgpl</para>
+ </listitem>
+ <listitem>
+ <para>libzvt</para>
+ </listitem>
+ <listitem>
+ <para>libbonobo</para>
+ </listitem>
+ <listitem>
+ <para>gnome-mime-data</para>
+ </listitem>
+ <listitem>
+ <para>gnome-vfs</para>
+ </listitem>
+ <listitem>
+ <para>libglade</para>
+ </listitem>
+ <listitem>
+ <para>libgnome</para>
+ </listitem>
+ <listitem>
+ <para>libgnomecanvas</para>
+ </listitem>
+ <listitem>
+ <para>libbonoboui</para>
+ </listitem>
+ <listitem>
+ <para>libgnomeui</para>
+ </listitem>
+ <listitem>
+ <para>libwnck</para>
+ </listitem>
+ <listitem>
+ <para>libgnomeprint</para>
+ </listitem>
+ <listitem>
+ <para>libgnomeprintui</para>
+ </listitem>
+ <listitem>
+ <para>libgtop</para>
+ </listitem>
+ <listitem>
+ <para>librsvg</para>
+ </listitem>
+ <listitem>
+ <para>gail</para>
+ </listitem>
+ <listitem>
+ <para>eel</para>
+ </listitem>
+ <listitem>
+ <para>libgtkhtml</para>
+ </listitem>
+ <listitem>
+ <para>gtk-engines</para>
+ </listitem>
+ <listitem>
+ <para>gnome-desktop</para>
+ </listitem>
+ <listitem>
+ <para>gnome-panel</para>
+ </listitem>
+ <listitem>
+ <para>gnome-session</para>
+ </listitem>
+ <listitem>
+ <para>gnome-terminal</para>
+ </listitem>
+ <listitem>
+ <para>gnome-utils</para>
+ </listitem>
+ <listitem>
+ <para>gnome-applets</para>
+ </listitem>
+ <listitem>
+ <para>control-center</para>
+ </listitem>
+ <listitem>
+ <para>gnome-games</para>
+ </listitem>
+ <listitem>
+ <para>bug-buddy</para>
+ </listitem>
+ <listitem>
+ <para>eog</para>
+ </listitem>
+ <listitem>
+ <para>nautilus</para>
+ </listitem>
+ <listitem>
+ <para>gnome-system-monitor</para>
+ </listitem>
+ <listitem>
+ <para>yelp</para>
+ </listitem>
+ <listitem>
+ <para>gedit</para>
+ </listitem>
+ <listitem>
+ <para>librep</para>
+ </listitem>
+ <listitem>
+ <para>rep-gtk</para>
+ </listitem>
+ <listitem>
+ <para>sawfish</para>
+ </listitem>
+ <listitem>
+ <para>gnome-media</para>
+ </listitem>
+ <listitem>
+ <para>gdm</para>
+ </listitem>
+ <listitem>
+ <para>at-spi</para>
+ </listitem>
+ <listitem>
+ <para>libgail-gnome</para>
+ </listitem>
+ <listitem>
+ <para>gconf-editor</para>
+ </listitem>
+ <listitem>
+ <para>gnome2-user-docs</para>
+ </listitem>
+ </orderedlist>
+ In addition to the disk space required to build each package
+ (give after the dash in the above list), the total space required to install
+ these packages is 341 MB.
+ </para>
+ <para>
+ It is possible to build all these packages in a different location from
+ the default <filename class="directory"><replaceable>/usr/local
+ </replaceable></filename> (by passing the <cmdsynopsis> <arg
+ choice="plain">--prefix= <replaceable>location</replaceable></arg>
+ </cmdsynopsis> flag to the <command>configure</command> script in each
+ tarball). If you do that, however, you should put the new location as
+ the first component of your <envar>$PATH</envar> (to avoid existing
+ versions of scrollkeeper being picked up, for example). This new
+ <envar>$PATH</envar> should be visible to each package as it compiles
+ (so that it sees, for example, the pkg-config files from the earlier
+ packages in the build).
+ </para>
+ </sect2>
+ <sect2 id="parallellinstall">
+ <title>Parallel Install</title>
+ <para>
+ &g2x; may be installed in parallel with the GNOME 1.4.1 release
+ libraries, allowing you to use &g2x;'s primary desktop functions
+ - <application>panels</application>,
+ <application>Nautilus</application>, etc. - while also running
+ applications that have not yet been ported and therefore still
+ require GNOME 1.4 libraries.
+ <note>
+ <para>
+ For some GNOME 1.x apps, you need the GNOME 1.x control-center (eg:
+ <application>gnome-pilot</application> for use in
+ <application>Evolution</application>).
+ </para>
+ </note>
+ </para>
+ </sect2>
+
+ <sect2 id="garnome">
+ <title>GARNOME</title>
+ <para><application>GARNOME</application> builds &g2x; from released
+ tarballs. It is maintained by Jeff Waugh, the &g2; release
+ coordinator, and can be found <ulink
+ url="http://www.gnome.org/~jdub/garnome/";>here</ulink>.</para>
+
+
+ </sect2>
+ <sect2 id="giglink">
+ <title>GNOME Installation Guide</title>
+ <para>
+ Karsten Reincke has written a
+ <ulink url="http://karubik.de/gig/2.0/";>GNOME
+ Installation Guide</ulink>.
+ </para>
+ </sect2>
+
+
+ <sect2 id="upgrading">
+ <title>Upgrading from GNOME 1.4</title>
+ <para>
+ After building and/or installing all of the packages successfully, there
+ are a couple of things that need to be done start using the latest
+ release.
+ </para>
+ <para>
+ Ensure that any existing GNOME 1.x sessions have been exited and check
+ that GConfd has stopped (run <userinput>ps ax | grep [g]conf</userinput>).
+ If <application>gconf</application> is still running, execute the command
+ <userinput>gconftool-1 --shutdown </userinput> to stop it.
+ </para>
+ <para>
+ In order to have anti-aliased fonts in menus and applications, you will
+ need to make sure that the environment variable
+ <envar>GDK_USE_XFT</envar> is exported before running the appropriate
+ applications, enabling rendering to use GNOME 2's new font
+ architecture. For example, you might put the following in
+ <filename>$HOME/.gnomerc</filename>:
+ <programlisting>
+ export GDK_USE_XFT=1
+ exec gnome-session
+ </programlisting>
+ (This assumes you are using <application>gdm</application> as your
+ interface to log into GNOME. If you are starting X from a command
+ prompt - using <command>startx</command> -
+ then just put the above lines into your
+ <filename>$HOME/.xinitrc</filename> file.)
+ </para>
+ <para>
+ With this set, fonts will then be rendered
+ according to the configuration of /etc/X11/XftConfig (moving to
+ /etc/fonts/fonts.conf in a future version, as we move to fontconfig
+ instead of Xft1). Settings in XftConfig or fonts.conf determine how
+ fonts are rendered, including whether to use hinting and
+ antialiasing.
+ </para>
+ <para>
+ There have been cases of the initial login to GNOME 2 not going quite
+ smoothly and a lot of errors about CORBA connections not being completed
+ popping up in error boxes (and nothing else starting). This can be
+ probably fixed by stopping the session (returning to the
+ <application>gdm</application> screen or to
+ the command prompt) and then (in a terminal) removing the
+ <filename class="directory">/tmp/orbit-<replaceable>user</replaceable></filename>
+ directory (and all of its contents), where
+ <replaceable>user</replaceable> is replaced with the appropriate user's
+ login name.
+ </para>
+ </sect2>
+
+<!-- platforms goes here -->
+<sect2 id="platforms">
+ <title>Platforms</title>
+ <sect3 id="bsd">
+ <title>BSD</title>
+ <para>
+ The FreeBSD GNOME Project is providing <ulink url="http://www.freebsd.org/gnome/";>
+ ports</ulink>.
+ </para>
+ </sect3>
+ <sect3 id="solaris">
+ <title>Solaris</title>
+ <para>Notes about building on Solaris.</para>
+ <para>
+ The following packages above and beyond those found on a complete Solaris
+ system are needed:
+ <itemizedlist>
+ <listitem>
+ <para>
+ gettext 0.10.40
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ popt 1.6.2
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ freetype >= 2.0.2
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ libaudiofile >= 0.2.3
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ sox >= 12.17.3
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ jpeg v6b
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ libpng 1.0.12
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ tiff 3.55
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ scrollkeeper 0.3.10
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ ghostscript 6.53
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ <para>
+ In addition, you need a compiler, either
+ <application>gcc</application> or <application>Forte 6 update
+ 2</application>. Older versions of
+ <application>forte/Sunpro</application> have been known to cause
+ problems.
+ </para>
+ <para>
+ There are a number of patches recommended for building GNOME on
+ Solaris, which can be obtained from <ulink
+ url="http://sunsolve.Sun.COM/pub-cgi/show.pl?target=patches/patch-access";>http://sunsolve.Sun.COM/pub-cgi/show.pl?target=patches/patch-access</ulink>:
+ <programlisting>
+ * Solaris8/sparc:
+ 108528-14 108827-20 108989-02 110934-07 111293-04 112396-02
+ 108652-51 108987-09 110380-04 111111-03 111310-01 112438-01
+
+ * Solaris8/x86:
+ 108529-14 108828-22 108990-02 110935-07 111294-03 111311-01
+ 112439-01 108653-41 108988-09 110403-04 111112-03 111307-03
+ 112397-02
+ </programlisting>
+ </para>
+ <note>
+ <para>
+ If you are using the native iconv implementation on Solaris
+ instead of libiconv, you'll need to make sure that you have
+ the converters between locale encodings and UTF-8 installed.
+ At a minimum you'll need the SUNWuiu8 package. You probably
+ should also install the SUNWciu8, SUNWhiu8, SUNWjiu8, and
+ SUNWkiu8 packages.
+ </para>
+ </note>
+ </sect3>
+ <sect3 id="darwin">
+ <title>Darwin</title>
+ <para>
+ With the latest releases, the GTK family builds cleanly out of
+ the box. More work is needed to get GNOME running, however. A <ulink
+ url="http://mail.gnome.org/mailman/listinfo/gnome-darwin-list";>
+ gnome-darwin-list</ulink> has been set up for those interested in
+ working on issue.
+ </para>
+ </sect3>
+ <sect3 id="linux">
+ <title>GNU/Linux</title>
+ <para>
+ Building &g2x; on GNU/Linux requires a number of standard packages
+ included with most distributions. Below are listings of the packages as
+ they are named in several of the most common distributions.
+ </para>
+ <sect4 id="debian">
+ <title>Debian</title>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>libpng2-dev</para>
+ </listitem>
+ <listitem>
+ <para>libjpeg-dev</para>
+ </listitem>
+ <listitem>
+ <para>libtiff-dev</para>
+ </listitem>
+ <listitem>
+ <para>xlibs-dev</para>
+ </listitem>
+ <listitem>
+ <para>libpopt-dev</para></listitem>
+ <listitem>
+ <para>libgdbmg1-dev (librep)</para></listitem>
+ <listitem>
+ <para>libgmp3-dev (librep)</para></listitem>
+ <listitem>
+ <para>texinfo (librep)</para></listitem>
+ <listitem>
+ <para>libbz2-dev, zlib1g-dev (gnome-vfs, others)</para></listitem>
+ <listitem>
+ <para>python2.2 + python2.2-xml (libglade)</para></listitem>
+ <listitem>
+ <para>docbook-xml (Docbook DTD 4.1.2) + docbook-xsl (Docbook XSL Stylesheets)</para></listitem>
+ </orderedlist>
+ </para>
+ </sect4>
+
+ <sect4 id="redhat">
+ <title>Red Hat</title>
+ <para>
+ All of the following packages are required for a full build. Most
+ should be installed by default and all will be available from the
+ distribution itself. Alternatively, www.rpmfind.net is a good place
+ to find the appropriate packages. I have used the
+ <quote>official</quote> Red Hat names for each one. This is taken
+ from a Red Hat 7.3 box, so it should be the same names across all
+ Red Hat 7.x boxes and there are possibly some small changes on the
+ 6.x boxes (plus some version problems on those boxes, too).
+ <orderedlist>
+ <listitem>
+ <para>gcc</para>
+ </listitem>
+ <listitem>
+ <para>make</para>
+ </listitem>
+ <listitem>
+ <para> glibc-devel</para>
+ </listitem>
+ <listitem>
+ <para>libpng</para>
+ </listitem>
+ <listitem>
+ <para> libpng-devel</para>
+ </listitem>
+ <listitem>
+ <para>libjpeg</para>
+ </listitem>
+ <listitem>
+ <para> libjpeg-devel</para>
+ </listitem>
+ <listitem>
+ <para>libtiff</para>
+ </listitem>
+ <listitem>
+ <para> libtiff-devel</para>
+ </listitem>
+ <listitem>
+ <para>XFree86</para>
+ </listitem>
+ <listitem>
+ <para> XFree86-devel
+ <note>
+ <para>Plus whatever XFree86 packages are required for the
+ system to run.</para>
+ </note>
+ </para>
+ </listitem>
+ <listitem>
+ <para>freetype</para>
+ </listitem>
+ <listitem>
+ <para>freetype-devel</para>
+ </listitem>
+ <listitem>
+ <para>popt</para>
+ </listitem>
+ <listitem>
+ <para>gdbm</para>
+ </listitem>
+ <listitem>
+ <para> gdbm-devel</para>
+ </listitem>
+ <listitem>
+ <para>gmp</para>
+ </listitem>
+ <listitem>
+ <para> gmp-devel
+ <note>
+ <para>This is the GNU multi-precision library, not libgpm,
+ the mouse library.</para>
+ </note>
+ </para>
+ </listitem>
+ <listitem>
+ <para>texinfo</para>
+ </listitem>
+ <listitem>
+ <para>bzip2</para>
+ </listitem>
+ <listitem>
+ <para>bzip2-libs</para>
+ </listitem>
+ <listitem>
+ <para>bzip2-devel</para>
+ </listitem>
+ <listitem>
+ <para>zlib</para>
+ </listitem>
+ <listitem>
+ <para>zlib-devel</para>
+ </listitem>
+ <listitem>
+ <para>gettext</para>
+ </listitem>
+ <listitem>
+ <para>byacc or bison</para>
+ </listitem>
+ <listitem>
+ <para>flex</para>
+ </listitem>
+ <listitem>
+ <para>python >= 2.0 with expat support
+ <note>
+ <para>
+ This means you need to be able to start python, it has
+ to be version 2.0 or greater and <quote>from xml.parsers
+ import expat</quote> must work from the Python prompt.
+ In other words, running <userinput>python2 -c "from
+ xml.parsers import expat"</userinput> from a shell
+ prompt and having no error reported is sufficient.
+ </para>
+ </note>
+ </para>
+ </listitem>
+ <listitem>
+ <para>openjade</para>
+ </listitem>
+ <listitem>
+ <para>sgml-common</para>
+ </listitem>
+ <listitem>
+ <para>docbook-dtds</para>
+ </listitem>
+ <listitem>
+ <para>xml-common
+ </para>
+ </listitem>
+ <listitem>
+ <para>docbook-style-xsl</para>
+ </listitem>
+ <listitem>
+ <para>docbook-style-dsssl</para>
+ </listitem>
+ </orderedlist>
+ </para>
+ </sect4>
+
+ <sect4 id="mandrake">
+ <title>Mandrake</title>
+ <para>
+ &g2; binary packages are available in <ulink
+ url="http://www.mandrakelinux.com/en/cookerdevel.php3";>Mandrake
+ Cooker</ulink> (Mandrake's experimental / unstable) distribution).
+ <warning>
+ <para>
+ These packages haven't yet been customized to fully integrate in
+ Mandrake Linux (all available applications are not show in menu,
+ some features available in Mandrake version of GNOME 1.4 have not
+ been ported yet to &g2;).
+ </para>
+ </warning>
+ These packages should only be used on full cooker system (not
+ 8.2/cooker mixed system) and feedback for these packages should be
+ sent to the <ulink url="http://www.mandrakelinux.com/en/cookerdevel.php3";>
+ cooker mailing list</ulink>.
+ </para>
+ <para>
+ All of the following packages are required for a full Mandrake
+ build. Most should be installed by default and all will be available
+ from the distribution itself. Packages are from Mandrake Linux
+ 8.2. (Hint : use urpmi <replaceable>my_package</replaceable> to
+ install <replaceable>my_package</replaceable>)
+ <orderedlist>
+ <listitem><para>gcc</para></listitem>
+ <listitem><para>make</para></listitem>
+ <listitem><para>glibc-devel</para></listitem>
+ <listitem><para>libpng3</para></listitem>
+ <listitem><para>libpng3-devel</para></listitem>
+ <listitem><para>libjpeg62</para></listitem>
+ <listitem><para>libjpeg62-devel</para></listitem>
+ <listitem><para>libtiff3-devel</para></listitem>
+ <listitem><para>libtiff3-devel</para></listitem>
+ <listitem><para>XFree86</para></listitem>
+ <listitem><para>
+ XFree86-devel (Plus whatever XFree86 packages are required
+ for the system to run.)
+ </para></listitem>
+ <listitem><para>freetype2</para></listitem>
+ <listitem><para>freetype2-devel</para></listitem>
+ <listitem><para>popt</para></listitem>
+ <listitem><para>libgdbm2</para></listitem>
+ <listitem><para>libgdbm2-devel</para></listitem>
+ <listitem><para>libgmp3</para></listitem>
+ <listitem><para>libgmp3-devel (This is the GNU multi-precision
+ library, not libgpm, the mouse library.)</para></listitem>
+ <listitem><para>texinfo</para></listitem>
+ <listitem><para>bzip2</para></listitem>
+ <listitem><para>libbzip2_1</para></listitem>
+ <listitem><para>libbzip2_1-devel</para></listitem>
+ <listitem><para>zlib1</para></listitem>
+ <listitem><para>zlib1-devel</para></listitem>
+ <listitem><para>gettext</para></listitem>
+ <listitem><para>byacc or bison</para></listitem>
+ <listitem><para>flex</para></listitem>
+ <listitem><para>python >= 2.0 with expat support. This means you
+ need to be able to start python, it has to be version 2.0 or
+ greater and <quote>from xml.parsers import expat</quote> must
+ work from the Python prompt. In other words, running
+ <userinput>python2 -c "from xml.parsers import
+ expat"</userinput> from a shell prompt and having no
+ error reported is sufficient.
+ </para></listitem>
+ <listitem><para>openjade</para></listitem>
+ <listitem><para>sgml-common</para></listitem>
+ <listitem><para>docbook-dtd41-sgml</para></listitem>
+ <listitem><para>docbook-dtd412-xml</para></listitem>
+ <listitem><para>docbook-style-xsl</para></listitem>
+ <listitem><para>docbook-style-dsssl</para></listitem>
+ </orderedlist>
+ </para>
+ </sect4>
+ <sect4 id="gentoo">
+ <title>Gentoo</title>
+ <para>
+ <ulink url="http://www.gentoo.org/";>Gentoo Linux</ulink> provides
+ &g2; support. Details <ulink
+ url="http://www.gentoo.org/~spider/";>here</ulink>.
+ </para>
+ </sect4>
+
+ </sect3>
+ </sect2>
+ <sect2 id="systemrequirements">
+ <title>System Requirements</title>
+ <para>
+ As discussed <xref linkend="performance"/>, &g2; requires less resources than GNOME 1.4. We
+ recommend a P400 or equivalent with 128M RAM for using
+ the desktop, but it has been known to work on a system with as little
+ as a P166 with 64M RAM.
+ </para>
+ </sect2>
+
+
+ </sect1>
+ <sect1 id="themes">
+ <title>Themes</title>
+ <para>
+ Themes - changing the look of your desktop - are a favorite
+ preoccupation for many GNOME users. GNOME 2 offers abundant opportunities
+ to play with themes, including gtk+, the window managers,
+ <application>GDM</application>, <application>Nautilus</application>
+ and more.
+ </para>
+
+
+ <para>
+ A GNOME themes web site, <ulink
+ url="http://www.sunshineinabag.co.uk/";>Sunshine in a Bag</ulink>, has been
+ established.
+ </para>
+ </sect1>
+
+
+ <sect1 id="quirks">
+ <title>Quirks</title>
+ <para>Things that may bite or surprise... or both!</para>
+
+ <sect2 id="menuvfolders">
+ <title>Panel Menus Disappear</title>
+ <para>
+ With the return of menu editing, old vfolder configurations and changes
+ may affect your menus in the 2.0.2 release. You can remove past menu
+ changes by deleting your ~/.gnome2/vfolders/ directory and restarting the
+ panel.
+ </para>
+ </sect2>
+
+ <sect2 id="dialogues">
+ <title>Dialogue Buttons</title>
+ <para>
+ Dialogue buttons are slightly different in GTK+ and GNOME 2.x, to fit
+ in with our new <ulink
+ url="http://developer.gnome.org/projects/gup/hig/1.0/";>Human Interface
+ Guidelines</ulink>. Whilst the new button order may simply look
+ 'backwards', they do adhere to a consistent and elegant design. It is
+ described in the <ulink
+ url="http://developer.gnome.org/projects/gup/hig/1.0/windows.html#alert-button-order";>Alert
+ Buttons</ulink> section of the HIG.
+ </para>
+ </sect2>
+
+ <sect2 id="autoapply">
+ <title>Auto-apply</title>
+ <para>
+ As a rule, preference dialogs are now auto-apply, so do not be
+ surprised by the lack of an <guibutton>Apply</guibutton> button.
+ </para>
+ </sect2>
+
+ <sect2 id="tearablemenus">
+ <title>Tearable menus</title>
+ <para>
+ Tearable menus are gone by default. To reinstate them, use
+ <application>gconf-editor</application> and change the value of
+ <varname>/desktop/gnome/interface/menubar_detachable</varname> to TRUE.
+ <note>
+ <para>
+ Changing this GConf key does not instantly apply. To ensure that
+ the change takes place, you must log out, kill any GNOME daemons
+ still running (such as
+ <application>bonobo-activation</application>), and log in again.
+ </para>
+ </note>
+ </para>
+ </sect2>
+
+ <sect2 id="cutandpaste">
+ <title>Cut and Paste</title>
+ <para>
+ The clipboard is a common source of confusion. GTK has always done the
+ right thing for the clipboard, and the version used in GNOME 2 is no
+ different. See <ulink url="http://www.freedesktop.org/standards/clipboards.txt"; type="http">
+ http://www.freedesktop.org/standards/clipboards.txt</ulink>. If the
+ clipboard doesn't work it's because some application is not following
+ the spec correctly; please file bug reports for those applications.
+ <note>
+ <para>
+ Qt 2 does not follow the clipboard specs correctly, so correct
+ applications do not interoperate with Qt 2. Qt 3 fixes this
+ problem.
+ </para>
+ </note>
+ </para>
+ </sect2>
+
+ <sect2>
+ <title>Nautilus default desktop selections have changed colors</title>
+ <para>
+ In the process of fixing bug <ulink
+ url="http://bugzilla.gnome.org/show_bug.cgi?id=82194";>bug
+ 82194</ulink>, the way nautilus displays selected text on the
+ desktop was changed; this makes all existing nautilus themes use
+ the gtk selection color in this case. This may look like a bug
+ but it is, in fact, a feature :) If the old behavior is still
+ desired, the theme has to be fixed. For more on this, including
+ how to fix themes to display the old behavior, see Federico's
+ emails to <ulink
+ url="http://lists.gnome.org/archives/nautilus-list/2002-August/msg00041.html";>nautilus
+ list.</ulink></para>
+ </sect2>
+
+ </sect1>
+ <sect1 id="errors">
+ <title>Known Issues</title>
+ <para>
+ All software, when it is released, contains bugs the developers know
+ about but have elected, for a variety of reasons, not to fix before
+ releasing. Free software is no different in this regard from proprietary
+ software, except that with free software, we tell users about them.
+ </para>
+ <para>
+ We also encourage our users to report bugs so that they can be fixed. The
+ best way to report bugs found in &g2x; is to use the <ulink
+ url="http://bugzilla.gnome.org/simple-bug-guide.cgi";>Simple Bug
+ Guide</ulink>. The Simple Bug Guide will take you through the necessary
+ steps to file a quality bug report, and make sure that it is tagged
+ appropriately. If you're too advanced for anything with the word 'simple'
+ in it, there is also the <ulink
+ url="http://bugzilla.gnome.org/enter_bug.cgi";>traditional bug
+ form.</ulink> Please make sure to add the 'GNOME2' keyword to any bugs
+ reported that way.
+ </para>
+ <para>
+ More details on bugs already reported can be found at our <ulink
+ url="http://bugzilla.gnome.org/gnome-20-report.html";>Bugzilla</ulink>.
+ Among the most prominent &g2x; bugs:
+ </para>
+ <sect2>
+ <title>Internationalization of gnome-terminal is broken</title>
+ <para>Unfortunately, gnome-terminal is broken in many non-ASCII
+ locales. A fix for this was proposed but caused many other
+ problems and as a result, was withdrawn. The current progress
+ can be tracked in bugzilla number <ulink
+ url="http://bugzilla.gnome.org/show_bug.cgi?id=78007";>bug
+ 78007</ulink> or in the libzvt-i18n branch of the zvt module.
+ </para>
+ </sect2>
+ <sect2>
+ <title>Some features formerly provided by viewports no longer available
+ in Sawfish</title>
+ <para>
+ In order to simplify sawfish code and user interface, viewports have
+ been removed from Sawfish2. The current functionality replaces nearly
+ all viewport functionality, except two-dimensional workspace
+ navigation. This is bug number <ulink
+ url="http://bugzilla.gnome.org/show_bug.cgi?id=82337";>82337</ulink>.
+ <note>
+ <para>The following has been reported as a workaround when added to
+ <filename>.sawfishrc</filename>:
+ <programlisting>
+ ;; Get viewports back
+ (setq customize-command-classes '(default viewport))
+
+ ;; (setq viewport-dimensions '(NUMBER_OF_COLS . NUMBER_OF_ROWS))
+ (setq viewport-dimensions '(6 . 1)) ;; example
+ </programlisting>
+ </para>
+ </note>
+ </para>
+ </sect2>
+ </sect1>
+
+ <sect1 id="fixed">
+ <title>Fixed in this Release</title>
+ <para>
+ The GNOME 2.0.x Desktop releases are devoted to bugfixes, translations,
+ user interface consistency, and general polish of our major 2.0 Desktop
+ release. In &g2x;, you'll see the results of continued performance and
+ stability work, and plenty of bug fixes:
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://makeashorterlink.com/?A226621C1";>318 total</ulink> GNOME2 bugs marked fixed
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ <para>
+ Major bugs mentioned in the previous release notes have now been fixed and are listed here:
+ </para>
+
+ <sect2>
+ <title>Menu editing returns</title>
+ <para>
+ Menu editing returns in GNOME 2.0.2! Because a number of bugs existed
+ in the menu editing implementation, and the best fixes for some of them
+ were not reverse compatible, we did not include menu editing in
+ previous releases. Details on the menu architecture and tips for manual
+ editing of menus can be found in our <ulink
+ url="http://www.gnome.org/start/2.0/menuediting.html";>menu editing
+ guide</ulink>.
+ </para>
+ </sect2>
+
+ <sect2>
+ <title>New mime type handlers not always visible in nautilus</title>
+ <para>
+ When a new mime-type handler was installed, it did not show up
+ correctly in Nautilus right-click menus. Was fixed in GNOME 2.0.2.
+ </para>
+ </sect2>
+
+ <sect2>
+ <title>NFS-mounted $HOME directory</title>
+ <para>
+ For people with NFS-mounted <envar>$HOME</envar> directories, it was
+ not possible to drag files from the
+ <application>Nautilus</application> view windows to the
+ <guilabel>trashcan</guilabel> (it would generate an error about the
+ trash file not being a directory). This was fixed in GNOME 2.0.1 and
+ was <ulink url="http://bugzilla.gnome.org/show_bug.cgi?id=82644";>bug
+ 82644</ulink>.
+ </para>
+ </sect2>
+
+ <sect2 id="dotgnome">
+ <title>.gnome</title>
+ <para>
+ &g2; uses <filename>$HOME/.gnome2</filename> and
+ <filename>$HOME/.gnome2_private</filename> as directories for storing
+ stuff. However, you could not completely remove
+ <filename>$HOME/.gnome</filename>, since gnome-vfs needs it and did not
+ create it, so any modifications that gnome-vfs needs to save in the
+ user's directory would not be saved. Thus, users needed to create a
+ <filename>$HOME/.gnome</filename> directory before starting &g2;. This
+ was fixed in 2.0.1 and was <ulink
+ url="http://bugzilla.gnome.org/show_bug.cgi?id=84183";>bug
+ 84183</ulink>.
+ </para>
+ </sect2>
+ <sect2>
+ <title>Cannot drag and drop from Nautilus list view</title>
+ <para>
+ It wasn't possible to drag and drop files from the list view as you can
+ in the icon view. This was fixed in GNOME 2.0.1 and was <ulink
+ url="http://bugzilla.gnome.org/show_bug.cgi?id=74974";>bug
+ 74974</ulink>.
+ </para>
+ </sect2>
+ </sect1>
+
+ <sect1 id="gettinginvolved">
+ <title>Getting Involved</title>
+ <para>
+ The core of GNOME's success is its volunteers, both developers and users.
+ As a user, your contribution can be as simple as filing good bug reports.
+ GNOME's bugs are found at our <ulink
+ url="http://bugzilla.gnome.org/";>Bugzilla</ulink>. Bugmeister Luis Villa
+ has set up a <ulink
+ url="http://bugzilla.gnome.org/simple-bug-guide.cgi";>simple bug-filing
+ interface</ulink> to make it easier to file useful reports.
+ </para>
+ <para>
+ If you would like to take the next step, developers, documenters, web
+ developers, documenters and bug handlers are always welcome. More
+ information on getting involved can be found <ulink
+ url="http://developer.gnome.org/documents/joining-gnome/";>here</ulink>.
+ </para>
+ </sect1>
+
+</article>
Modified: branches/gnome-2-0/help/Makefile.am
==============================================================================
--- /branches/gnome-2-2/help/Makefile.am (original)
+++ branches/gnome-2-0/help/Makefile.am Mon Nov 3 11:07:03 2008
@@ -3,32 +3,8 @@
DOC_MODULE = release-notes
DOC_INCLUDES = \
- epiphany.xml \
release-notes.xml \
- rna11y.xml \
- rnapplets.xml \
- rncontrolcenter.xml \
- rndesktop.xml \
- rndocs.xml \
- rnepiphany.xml \
- rnfileroller.xml \
- rngames.xml \
- rngcalctool.xml \
- rngnomemeeting.xml \
- rngpdf.xml \
- rngucharmap.xml \
- rni18n.xml \
- rninstallation.xml \
- rnnewmaintainers.xml \
- rnplatform.xml \
- rnstandards.xml \
- rnthanks.xml \
- rnthemes.xml \
- rntoc.xml \
- rnwhy.xml \
- rnwm.xml \
- rnzenity.xml
-
+ menuediting.xml
DOC_FIGURES =
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
