Difference between revisions of "NURBS Editing Support"

m (Starseeker moved page Ayam Editor Feature Integration to NURBS Editing Support: This task will be reworked to be non-Ayam specific)
(Rework NURBS editing text to be less Ayam centric.)
Line 1: Line 1:
  
BRL-CAD has recently implemented support for raytracing of NURBS surfaces, but beyond basic operations such as rotation and translation it has no ability to edit them.  Ayam, although it uses a different format to store NURBS surfaces, does have the capability to edit them.  This project would examine the NURBS editing abilities of Ayam and map them to the corresponding openNURBS/Archer functionality, implementing at least a basic ability to alter NURBS surfaces.
+
BRL-CAD has recently implemented support for raytracing of NURBS surfaces, but beyond basic operations such as rotation and translation it has no ability to edit them.  This project would implement support for editing NURBS curves and surfaces in the new Archer modeling interface.
  
Note that editing NURBS in Archer/MGED should not assume OpenGL surface representations of NURBS are available - that would require the completion of the NURBS tessellation task and in any case not all editing environments provide working OpenGL.  Editing should be possible using wireframe representations of key features, and be mappable to more sophisticated OpenGL based visualization once it appears.
+
Note that editing NURBS in Archer should not assume OpenGL surface representations of NURBS are available.  Editing should be possible using wireframe representations of key features, and be mappable to more sophisticated OpenGL based visualization once it appears.
  
 
Main tasks would be:
 
Main tasks would be:
#Identifying key features used by Ayam to alter NURBS (knot insertion, etc) and mapping those operations to openNURBS calls (or identifying that the equivalent routine doesn't exist in openNURBS and will need to be ported/reimplemented from Ayam)  
+
#Identifying key editing operations (knot insertion, etc) and mapping those operations to openNURBS calls (or identifying that the equivalent routine doesn't exist in openNURBS and will need to be implemented)  
#Implementing librt/libged logic to allow those calls to be made  
+
#Implementing librt/libbrep/libged logic to allow those calls to be made  
#Implementing appropriate graphical controls and interface logic in Archer (other primitives will provide examples).
+
#Implementing appropriate graphical controls and interface logic in Archer (other primitive editing support code in Archer will provide relevant examples).
  
 
=References=
 
=References=
  
 
* http://ayam.sourceforge.net/
 
* http://ayam.sourceforge.net/
**The Ayam editor is a BSD licensed, Tcl/Tk based modeler for NURBS.  It's primary purpose is to serve as a modeler for the RenderMan interface, but at least some of the functionality it implements is of interest to BRL-CAD.
+
**The Ayam editor is a BSD licensed, Tcl/Tk based modeler for NURBS.  It's primary purpose is to serve as a modeler for the RenderMan interface, but at least some of the functionality it implements is of interest to BRL-CAD.  It's primary license is compatible with BRL-CAD's, but Ayam makes use of many third party components so be sure to check individual files for license information.
  
 
* src/librt/primitives/brep/brep.cpp
 
* src/librt/primitives/brep/brep.cpp
 +
* src/libbrep
 
* src/other/openNURBS
 
* src/other/openNURBS
 
* src/libtclcad
 
* src/libtclcad

Revision as of 21:20, 11 April 2013

BRL-CAD has recently implemented support for raytracing of NURBS surfaces, but beyond basic operations such as rotation and translation it has no ability to edit them. This project would implement support for editing NURBS curves and surfaces in the new Archer modeling interface.

Note that editing NURBS in Archer should not assume OpenGL surface representations of NURBS are available. Editing should be possible using wireframe representations of key features, and be mappable to more sophisticated OpenGL based visualization once it appears.

Main tasks would be:

  1. Identifying key editing operations (knot insertion, etc) and mapping those operations to openNURBS calls (or identifying that the equivalent routine doesn't exist in openNURBS and will need to be implemented)
  2. Implementing librt/libbrep/libged logic to allow those calls to be made
  3. Implementing appropriate graphical controls and interface logic in Archer (other primitive editing support code in Archer will provide relevant examples).

References

  • http://ayam.sourceforge.net/
    • The Ayam editor is a BSD licensed, Tcl/Tk based modeler for NURBS. It's primary purpose is to serve as a modeler for the RenderMan interface, but at least some of the functionality it implements is of interest to BRL-CAD. It's primary license is compatible with BRL-CAD's, but Ayam makes use of many third party components so be sure to check individual files for license information.
  • src/librt/primitives/brep/brep.cpp
  • src/libbrep
  • src/other/openNURBS
  • src/libtclcad

Requirements

  • Familiarity with C and C++
  • Familiarity with Tcl/Tk
  • Basic understanding of NURBS
  • (optional) openNURBS and/or Ayam experience