Difference between revisions of "Impress: OpenGL rendered transitions"

From Apache OpenOffice Wiki
Jump to: navigation, search
(Current Status: no longer in school)
(Student Task List: added more tasks, and marked completed tasks.)
Line 20: Line 20:
 
* Successfully build OOo. Done.
 
* Successfully build OOo. Done.
 
* Verify the newly built version of OOo can be installed and run. Done
 
* Verify the newly built version of OOo can be installed and run. Done
* Successfully make a minor hack to OOo, preferably to Impress. In Progress.
+
* Successfully make a minor hack to OOo, preferably to Impress. Done.
* Successfully debug the minor hack.
+
* Verify the hacked version of OOo can be run to verify it works correctly. Done.
* Verify the hacked version of OOo can be run to verify it works correctly.
+
* Successfully debug the minor hack. In Progress.
 +
* Create Technical Design Document (naively).
 +
* Assess and edit parts of TDD so it would integrate correctly into OOo.
 +
* Begin Implementation described in TDD.
  
 
== Items to do if time permits (Backlog) ==
 
== Items to do if time permits (Backlog) ==

Revision as of 20:03, 8 May 2007

This is the wiki page for the Google Summer_of_Code_2007 proposal by Shane M Mathews and mentored by Thorsten Behrens and Radek Doulik.

Proposal

To add 3D transitions to the Impress application. Transition is an animation where one page is visible in the beginning and another in the end. It is used during presentation slideshow to switch pages.

In the process of implementing OpenGL transitions an UNO API should be added to slideshow code, so that OpenGL transitions engine might be created as standalone UNO component. Current transitions should be refactored to another UNO component.

The engine will get the previous and next pages and should render the transition at given speed.

The participant should also implement at least 5 OpenGL transitions, rendered by the UNO component.

Current Status

The student is learning how to build, code, and compile OOo before May 28th, the official beginning of the project.

Student Blog

Student Task List

  • subscribe to openoffice.org wiki. Done.
  • Submit a filled-out copy of the Joint Copyright Assignment form (JCA). Done.
  • Successfully build OOo. Done.
  • Verify the newly built version of OOo can be installed and run. Done
  • Successfully make a minor hack to OOo, preferably to Impress. Done.
  • Verify the hacked version of OOo can be run to verify it works correctly. Done.
  • Successfully debug the minor hack. In Progress.
  • Create Technical Design Document (naively).
  • Assess and edit parts of TDD so it would integrate correctly into OOo.
  • Begin Implementation described in TDD.

Items to do if time permits (Backlog)

Write suggestions for the student here!

  • Detect the use of a video card to do advanced graphical effects, such as generating a height map based on the colors of the current slide, and casting shadows using steep parallax mapping. Suggested by the student.
  • Press tab to Zoom out "exposé-style" to give a view of all slides. Suggested by John Spray.
Personal tools