VR Juggler
Open Source
Virtual Reality


VRJ Wiki . VRJPlanning . FinishPlugInHandlingStory VRJ Wiki webs:
Juggler | VRJPlanning | Main | TWiki | Test
VRJPlanning . { Home | Changes | Index | Search | Go }

Wiki

· Home
· 2.0 Release
· 2.0 Beta 1
· 2.0 Alpha 4
· 2.0 Alpha 2
· 2.0 Alpha 1
· Development
· Direction
· Status

edit menu


Main
· About
· Documentation
· Publications
· Download
· HOWTO
· FAQ
· Discussion Area (Wiki)
· Status
· Contact

Projects
· VR Juggler
· Gadgeteer
· VPR
· Sonix
· JCCL
· Tweek
· PyJuggler
· VRJ.NET

Events
· SIGGRAPH 2004 BoF?
· SIGGRAPH 2003 BoF?
· Virtual Reality Course
· IEEE VR 2003 Course
· SC 2002 Exhibit

Site Search

Google

Sponsors
· Infiscape
· VRAC
· Iowa State University
· SourceForge

Link To Us


FinishPlugInHandlingStory

Story summary Get all the plug-ins building, loading, and working in the same manner
Iteration VrjTwoZeroAlphaFour
Development order 1
Customer  
Story Lead PatrickHartling
FEA  
Acceptance Criteria  
Passed acceptance test No

Full story

Our support for C++ plug-ins is relatively new, and we have learned things since we started. That knowledge needs to be applied to all the modules that handle plug-ins.

Implementation notes

The modules that have plug-ins are:

  1. Gadgeteer
    • Device drivers
    • ClusterJuggler plug-ins
  2. JCCL
    • Remote run-time reconfiguration
  3. Sonix
    • Audio implementations

All need to support the following:

  • Proper compilation
    • Plug-ins are built after the library upon which they depend
    • Plug-ins can be built separately from their dependent library
      • This makes it easier and faster to develop and test plug-ins
    • Plug-ins must be built to address different ABIs
      • Debug versus optimized (critical for Windows)
      • N32/64

Tasks in this story

Tasks Est Spent To do Risk Reviewer Developer Task Name
Task 2 2 0 Low     Build ClusterJuggler plug-ins separately from Gadgeteer
Task 2 2 0 Low     Handle ClusterJuggler plug-ins abstractly in configuration and code
Task 2 0 2 Low     Convert Sonix plug-ins to use vpr::Library
Task 2 0 2 Low     Build Sonix plug-ins separately from Sonix
Task 2 0 2 Low     Handle Sonix plug-ins abstractly in code

Task details:

Handling plug-ins "abstractly in code" means that the code operates on a platform- and ABI-independent level in terms of the plug-in name. The Gadgeteer device driver handling in gadget::InputManager and the remote run-time reconfiguration plug-in handling in jccl::ConfigManager demonstrate how to do this.

Build system adjustments should be based on the way that the Gadgeteer device drivers are compiled.


Topic FinishPlugInHandlingStory . { Edit | Attach | Ref-By | Printable | Diffs | r1.4 | > | r1.3 | > | r1.2 | More }

Copyright © 1999-2008 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding VRJ Wiki? Send feedback
Revision r1.4 - 11 Oct 2004 - 19:49 - PatrickHartling Copyright © 1999-2008 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding VRJ Wiki? Send feedback




VR Juggler Logo
Site contents © Copyright 1998–2005 Iowa State University and released under the GPL.
Harvesting email addresses from this page for commercial activities is prohibited.
Contact: Webmaster | Write Us
SOURCE REPOSITORY,
BUGS, FORUMS
HOSTED BY:		 SourceForge Home