##(see the SpecSpec for an explanation)

''Please check the status of this specification in Launchpad before editing it.  If it is Approved, contact the Assignee or another knowledgeable person before making changes.''

 * '''Launchpad Entry''': UbuntuSpec:redirected-direct-rendering
 * '''Packages affected''': xserver-xorg-core

== Summary ==

Currently opengl apps do not work correctly when composite is running. This is a BIG bug and annoyance for desktop users, especially as composite-by-default is set to be included for gutsy. This should be fixed via redirected direct rendering. It is especially important as modern applications use opengl interfaces, such as blender and google earth, but also for smaller opengl parts, such as the visualisations in amarok.

== Rationale ==

Users of ubuntu, both advanced users and novices, find it annoying to have to disable the compositioning window manager whenever they want to run an opengl accelerated application. Solving this requires deep changes to the structure of the X server and the display drivers, and is a future plan for the Xorg devs: http://dri.freedesktop.org/wiki/DirectRenderingToRedirectedWindows (A prototype for this has been developed by Kristian Hogsberg: http://hoegsberg.blogspot.com/2007/08/redirected-direct-rendering.html). However, it is a big job, so I believe that the Ubuntu devs should help out.

I'm sure many people know more about this than me, so feel free to add details.

##== Use Cases ==

##== Assumptions ==

##== Design ==

##You can have subsections that better describe specific parts of the issue.

##== Implementation ==

##This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

##=== UI Changes  ===

##Should cover changes required to the UI, or specific UI that is required to implement this

##=== Code Changes ===

##Code changes should include an overview of what needs to change, and in some cases even the specific details.

##=== Migration ===

##Include
##data migration, if any
##redirects from old URLs to new ones, if any
##how users will be pointed to the new way of doing things, if necessary.

##== Test/Demo Plan ==

##It's important that we are able to test new features, and demonstrate them to users.  Use this section to ##describe a short plan that anybody can follow that demonstrates the feature is working.  This can then be used ##during CD testing, and to show off after release.

##This need not be added or completed until the specification is nearing beta.

##== Outstanding Issues ==

##This should highlight any issues that should be addressed in further specifications, and not problems with the ##specification itself; since any specification with problems cannot be approved.

##== BoF agenda and discussion ==

##Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what ##was discussed and note any options that were rejected.

----
CategorySpec CategorySpec