Difference between revisions of "Plans for Merging X3D AR Proposals"

From Web3D.org
Jump to: navigation, search
Line 9: Line 9:
 
* General guidelines in Web3D consortium?
 
* General guidelines in Web3D consortium?
 
* From the scene writer's point of view, preferably less code for commonly/frequently used features, while detail control available for special cases.
 
* From the scene writer's point of view, preferably less code for commonly/frequently used features, while detail control available for special cases.
* From the user's (viewer's) point of view, the scene should be adopted to the hardware/software environment (tracker, camera device, browser, etc.) s/he has.
+
* From the user's (viewer's) point of view, the scene should be adopted to the hardware/software environment (tracker, camera device, browser, etc.) s/he has.  
  (i.e. scene writer should not specify hardware/software environment in the scene.)
+
  In other words, scene writer should not specify hardware/software environment in the scene, which is on the users' side.
  
 
2. Investigate each functional features stepwise
 
2. Investigate each functional features stepwise

Revision as of 18:21, 19 March 2012

This page is for discussing plans for merging X3D AR proposals, compared in Comparison of X3D AR Proposals.

Plan A: Yvonne

Plan B: Gerard Kim

Plan C: Gun Lee

1. Discuss general strategy/policy/guidelines

  • General guidelines in Web3D consortium?
  • From the scene writer's point of view, preferably less code for commonly/frequently used features, while detail control available for special cases.
  • From the user's (viewer's) point of view, the scene should be adopted to the hardware/software environment (tracker, camera device, browser, etc.) s/he has.
  In other words, scene writer should not specify hardware/software environment in the scene, which is on the users' side.

2. Investigate each functional features stepwise

  • Camera video stream image in the scene (texture and background)
  • Tracking (including support for general tracking devices)
  • Camera calibration (viewpoints)
  • Others (color-keying, depth occlusion)

3. Integration of functional features

  • Conflicts between individual components
  • Merging components

4. Specification writing

5. Review