From Fedora Project Wiki
(remove extra spacing + ready for FESCo)
Line 7: Line 7:
* [[SIGs/Desktop | Desktop SIG]]
* [[SIGs/Desktop | Desktop SIG]]
* Email: fedora-desktop-list@redhat.com
* Email: fedora-desktop-list@redhat.com


== Current status ==
== Current status ==
* Targeted release: [[Releases/15 | Fedora 15 ]]  
* Targeted release: [[Releases/15 | Fedora 15]]  
* Last updated: 2010-08-03
* Last updated: 2010-09-14
* Percentage of completion: 55%
* Percentage of completion: 55%


Line 21: Line 20:
== Detailed Description ==
== Detailed Description ==
GNOME 3 is the next major version of the GNOME desktop. After many years of a largely unchanged GNOME 2.x experience, GNOME 3 brings a fresh look and feel with gnome-shell. There are also many changes under the surfaces, like the move from CORBA-based technologies such as GConf, Bonobo, at-spi to dbus-based successors.
GNOME 3 is the next major version of the GNOME desktop. After many years of a largely unchanged GNOME 2.x experience, GNOME 3 brings a fresh look and feel with gnome-shell. There are also many changes under the surfaces, like the move from CORBA-based technologies such as GConf, Bonobo, at-spi to dbus-based successors.


== Benefit to Fedora ==
== Benefit to Fedora ==
Line 83: Line 81:


== How To Test ==
== How To Test ==
<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
A good "how to test" should answer these four questions:
0. What special hardware / data / etc. is needed (if any)?
1. How do I prepare my system to test this feature? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the feature is
working like it's supposed to?
3. What are the expected results of those actions?
-->
How to test the accessibility stack:
How to test the accessibility stack:
#. Make sure accessibility support is turned on
#. Make sure accessibility support is turned on
Line 123: Line 107:


== Dependencies ==
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
* gnome-shell uses clutter, which relies on 3D hardware and drivers. In F13, the shell is known to work ok with Intel and ATI graphics, and work somewhat with the nouveau driver for NVidia graphics. For F14, we want the shell to work well with all three of
* gnome-shell uses clutter, which relies on 3D hardware and drivers. In F13, the shell is known to work ok with Intel and ATI graphics, and work somewhat with the nouveau driver for NVidia graphics. For F14, we want the shell to work well with all three of
** xorg-x11-drv-ati
** xorg-x11-drv-ati
Line 137: Line 120:


Applications can be ported from GConf to dconf and from gtk2 to gtk3 one-by-one, so if the porting work is not complete (and it is very unlikely that it will be), we can just ship with some applications using the new technology, while others still use the old one.
Applications can be ported from GConf to dconf and from gtk2 to gtk3 one-by-one, so if the porting work is not complete (and it is very unlikely that it will be), we can just ship with some applications using the new technology, while others still use the old one.


== Documentation ==
== Documentation ==
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
* http://www.linuxfoundation.org/collaborate/workgroups/accessibility/atk/at-spi/at-spi_on_d-bus  
* http://www.linuxfoundation.org/collaborate/workgroups/accessibility/atk/at-spi/at-spi_on_d-bus  
* http://live.gnome.org/GnomeShell/
* http://live.gnome.org/GnomeShell/


== Release Notes ==
== Release Notes ==
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
* Fedora 14 includes GNOME3. It brings the first major overhaul of the GNOME user experience in 10 years.
* Fedora 14 includes GNOME3. It brings the first major overhaul of the GNOME user experience in 10 years.


== Comments and Discussion ==
== Comments and Discussion ==
* See [[Talk:Features/Gnome3]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->


[[Category:FeaturePageReadyForWrangler]]
[[Category:FeaturePageReadyForFesco]]
<!-- When your feature page is completed and ready for review -->
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->

Revision as of 16:43, 15 September 2010

GNOME 3

Summary

Include GNOME 3

Owner

Current status

  • Targeted release: Fedora 15
  • Last updated: 2010-09-14
  • Percentage of completion: 55%

GNOME has been mostly updated to 2.31.5 in rawhide. dconf, gnome-icon-theme-symbolic, gtk3 and yelp-xsl are in rawhide. The dbus a11y stack is now the default. gtk3 modules have been added for at-spi2-atk, PackageKit and gtk3-engines.

Detailed Description

GNOME 3 is the next major version of the GNOME desktop. After many years of a largely unchanged GNOME 2.x experience, GNOME 3 brings a fresh look and feel with gnome-shell. There are also many changes under the surfaces, like the move from CORBA-based technologies such as GConf, Bonobo, at-spi to dbus-based successors.

Benefit to Fedora

Fedora stays in sync with upstream, and gains a new user experience. Some long-standing problems with the CORBA-based accessibility stack will hopefully be solved as a side-effect of the move to D-Bus

Scope

  • Package new components
  • Build packages which provide gtk modules for gtk2 and gtk3 (tracked [upstream]):
    • librsvg2 (Done)
    • gtk2-engines [gtk3-engines review] (Done)
    • ibus-gtk [bug] (Done)
    • at-spi2-atk (Done)
    • PackageKit-gtk-module (Done)
  • Make GTK-using libraries parallel-installable, or port them to GTK3, or drop their GTK dependency:
    • libnotify (done, dependency now implicit)
    • gnome-desktop (done, parallel-installable gnome-desktop3)
    • libunique ([done], parallel-installable libunique3)
    • gtksourceview ([done], parallel-installable gtksourceview3)
    • webkitgtk ([done], parallel-installable webkitgtk3)
    • vte ([bug])
    • libwnck ([bug])
    • libmetacity-private ([bug])
    • clutter-gtk
    • libchamplain-gtk
    • gtkimageview
    • cheese-gtk
    • polkit-gtk
  • Switch to the dbus-based accessibility stack (Done)
  • Implement data migration for applications that are ported from GConf2 to dconf
    • done for evince
    • done for gedit
    • done for brasero
    • done for gnome-bluetooth
    • done for nautilus-sendto
    • done for gnome-color-manager
    • done for gnome-packagekit
    • done for gnome-power-manager
  • Implement fallback from the shell to 'classical GNOME' for unsupported hardware
  • All system status indicators must use symbolic icons, others are optional
    • power (Done)
    • updates (Done)
    • network
    • keyboard
    • sound
    • bluetooth
  • Make sure applications keep working and don't run into mixed linkage against both gtk2 and gtk3 via gtk-using libraries. Currently known problems:
    • rhythmbox (uses gtk2, but needs libbrasero-burn/media and gnome-media-profiles, which have moved to gtk3)
    • gthumb (uses gtk2, but needs libbrasero-burn which has moved to gtk3)
    • solang (uses gtk2, but needs libbrasero-burn/media which has moved to gtk3)
    • gnomeradio, nautilus-sound-converter also use gnome-media-profiles
  • Current mixed linkage problems that need to be addressed:
    • gnome-volume-control-applet

How To Test

How to test the accessibility stack:

  1. . Make sure accessibility support is turned on
  2. . Install at-spi2-core, at-spi2-atk, pyatspi
  3. . Set the GConf key /desktop/gnome/interface/at-spi-corba to false
  4. . Log in again
  5. . Verify that at-spi-registry is not running
  6. . Start orca
  7. . Verify that at-spi-registryd2 has been activated
  8. . Verify that speech support in orca works as it does with the old stack

Repeat these steps with other accessibility technologies

How to test fallback:

  1. . Use a system with supported graphics card
  2. . Log in to a GNOME session
  3. . Verify that you end up with gnome-shell
  4. . Switch to a system with a graphics card on which we don't have 3d support (e.g. a VM)
  5. . Log in to a GNOME session again
  6. . Verify that you end up with the 'classic GNOME' desktop

User Experience

The user experience (on supported hardware) will be defined by gnome-shell.

Accessibility tools will work as well as (or hopefully better than) they used to. The onscreen keyboard will no longer be gok, but caribou, which may offer a slightly different user experience.

Dependencies

  • gnome-shell uses clutter, which relies on 3D hardware and drivers. In F13, the shell is known to work ok with Intel and ATI graphics, and work somewhat with the nouveau driver for NVidia graphics. For F14, we want the shell to work well with all three of
    • xorg-x11-drv-ati
    • xorg-x11-drv-intel
    • xorg-x11-drv-nouveau
  • Any packages that install modules for gtk2 (such as image loaders, input methods or theme engines) need to do extra work to make their functionality available to gtk3 too

Contingency Plan

If gnome-shell is not complete or stable enough, keep it experimental and stay with 'classical GNOME' as the default. Users will still be able to try the shell manually, just like in F12 and F13.

If the dbus-based accessibility stack is not sufficiently functional, we switch back to the CORBA-based stack.

Applications can be ported from GConf to dconf and from gtk2 to gtk3 one-by-one, so if the porting work is not complete (and it is very unlikely that it will be), we can just ship with some applications using the new technology, while others still use the old one.

Documentation

Release Notes

  • Fedora 14 includes GNOME3. It brings the first major overhaul of the GNOME user experience in 10 years.

Comments and Discussion

Retrieved from "https://fedoraproject.org/w/index.php?title=Features/Gnome3&oldid=197395"