Search results

• NURBS Optimization and Cleanup
  ...the Rhino3D folks) and implements many of the most useful portions of the API that they removed. Our rendering support was based on research in 2006 tha ...clean non-reusable way. Ideally, our mods and extensions to the OpenNURBS API should be consolidated together, refactored, and made into a proper overlay
  2 KB (291 words) - 17:43, 26 March 2012
• Analysis Library
  ...rtcheck uses one grid that fires from the "view plane" in MGED - a logical API for this would be to use librt's ray bundle abilities (or enhance them if i ** the design of this library's API must be carefully considered
  1 KB (243 words) - 14:07, 24 March 2011
• Mesh library cleanup
  ...ions to make sure they do exactly what they are supposed to do by creating API unit tests. Test-driven development is a must here. * Ability to write API unit tests
  2 KB (352 words) - 10:05, 9 February 2017
• Generalized abstracted spacial partitioning capability
  ...ce partitioning - with a successful implementation of a space partitioning API the problem is reduced to implementing calls to test whether nodes satisfy ...list or IRC to make sure they understand what the requirements for such an API are.
  1 KB (218 words) - 14:02, 24 March 2011
• Level of Detail Wireframes
  #Design a callback API for librt primitives to provide on request a view dependent wireframe #Implement and test the API and wireframe schemes.
  2 KB (341 words) - 10:13, 24 March 2011
• Google Summer of Code/2015
  == Object-Oriented C++ Geometry API ==
  5 KB (638 words) - 21:53, 28 April 2016
• Geometry Selection Functionality
  ...nction as part of the filtering criteria. The target product would be a C api in librt (possibly an extension of the existing search code filter types, i
  2 KB (322 words) - 13:38, 24 March 2011
• GED Transactions
  ...me libged transactions the inverse transaction may not be obvious, and the API details and design for implementation also need careful consideration. A s
  2 KB (357 words) - 13:36, 24 March 2011
• Google Summer of Code/2014
  ==Object-oriented C++ Geometry API==
  6 KB (771 words) - 23:34, 4 May 2016
• STEP Coverage Test
  * Familiarity with being able to link against a 3rd party C/C++ API
  774 bytes (129 words) - 02:28, 1 May 2013
• OpenCL GPGPU Raytracing
  Languages: C and OpenCL (or other GPGPU API)
  909 bytes (145 words) - 06:07, 29 April 2021
• Consolidate image processing
  ...y (LIBICV), and convert all existing image conversion tools to use the new API. Correctness and robustness testing should be part of the process (what ha
  1 KB (171 words) - 12:57, 24 March 2011
• Documentation
  # [https://brlcad.org/docs/api API Documentation]
  1 KB (141 words) - 03:38, 8 February 2022
• Object-oriented interfaces
  With that, the C++ interface would be a canonical API for external applications, interfaces to other programming languages, etc..
  1 KB (161 words) - 10:45, 28 February 2014
• Package Library Extensions
  ...performance bottlenecks and to eliminate the assumption of globals in the API by adding user callbacks.
  1 KB (185 words) - 18:35, 26 March 2012
• OpenCL GPGPU Complex Raytracing
  Languages: C and OpenCL (or other GPGPU API)
  1 KB (219 words) - 06:03, 29 April 2021
• Bending light
  ...Any implementation of ray bending should be consistent with the existing API and will need to be maintainable within BRL-CAD's sources.
  1 KB (204 words) - 18:12, 5 December 2017
• BRL-CAD's core C++ interface
  The C++ interface is a object oriented API to BRL-CAD's core libraries around librt.
  2 KB (236 words) - 10:31, 22 June 2009
• Geometry Conversion Library
  ...project would work on a conversion library (LIBGCV) that provides a clean API for converting to and from different formats.
  2 KB (253 words) - 13:14, 24 March 2011
• Google Season of Docs/Project Ideas
  ...ction. The primary goal of this project is to make sure all of the public API has a Doxygen comment, has parameters tagged appropriately, grouped accordi
  7 KB (1,049 words) - 10:00, 26 March 2021

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)