wiki:PAGE_SCENE_IMPL_ALTERNATIVE_R0
Last modified 3 years ago Last modified on 02/10/09 06:39:17

Pages linking to PAGE_SCENE_IMPL_ALTERNATIVE_R0:
TASK_INDEX

Ticket Summary Owner Status Type Component Priority Effort Importance
#639 PAGE_SCENE_IMPL_ALTERNATIVE_R0 sriggins closed planned_task PAGE_WORK_AREA 3 2 19

Reported by Astea, 4 years ago.

Description

wiki page: PAGE_SCENE_IMPL_ALTERNATIVE_R0 - effort: 2d

Analysis_owners

sriggins

Analysis_reviewers

gogov, gogov

Analysis_score

4

Design_score

0

Imp._score

0

Test_score

0

Analysis

Overview

For this task, create an alternative page scene implementation that uses OpenGL for performance gains. This is done as a second engine so the main, stable engine can still be used until this faster engine is stable.

Task requirements

  • Build a faster page scene module
  • Investigate the use of JOGL and Java3D, which use OpenGL for performance gains
  • Explain and document which library was chosen and why
  • Consider and explain how native libraries (Native to Windows, OS X and Linux) might be used in Sophie

Task result

Result is another module that is optimized so we can continue to use main module while we tune this module

Implementation idea

  • Use the main implementation as a guide for this task
  • Java3D provides an object model that when used in conjunction with our scene model may prove useful
  • Make sure this R0 version at least works, specific performance gains are not required

PAGE_SCENE_IMPL_MAIN_R0

PAGE_SCENE_IMPL_COMMONS_R0

SCENE_COMMONS_R0

SCENE_COMMONS_R1

How to demo

Demo the speed and design differences between the main page scene engine and this one. Explain why you chose the library you decided upon using.

Design

(Describe your design here.)

Implementation

(Describe and link the implementation results here (from the wiki or the repository).)

Testing

(Place the testing results here.)

Comments