Search results

From BRL-CAD
  • currently defined in Lua would be moved to a C++ API accessible from the The API needs to be integrated in the command line and in the quick script
    7 KB (1,212 words) - 07:49, 6 May 2017
  • ...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
  • # [https://brlcad.org/docs/api API Documentation]
    1 KB (141 words) - 03:38, 8 February 2022
  • 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
  • ...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
  • *Constraints api is not mature thus not implemented.
    1 KB (178 words) - 05:01, 18 August 2014
  • For the first week, I’ll start working with the WikiBooks API, and write a code to get the text part extracted Next, I plan to work on the API:Styling content from wiki to present the docs with proper styling to
    2 KB (423 words) - 12:08, 20 July 2021
  • ...ures, already available public API's are used. However wherever needed new API's have also been created for this purpose.
    6 KB (959 words) - 10:48, 26 June 2014
  • Languages: C and OpenCL (or other GPGPU API)
    1 KB (219 words) - 06:03, 29 April 2021
  • ...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
  • ...been sent to the mailing list asking folks to submit the logs through the API and mail.
    3 KB (479 words) - 10:20, 22 August 2012
  • ...o I am not able to give a start to extend the object-oriented C++ Geometry API which includes the C++ '''coreInterface''' & '''LIBGED'''. ...ning to port '''Arbalest''' to '''MOOSE''' where Moose will become the new API of the BRL-CAD core in the future. Moose is based on the C++ '''coreInterfa
    4 KB (673 words) - 05:36, 13 March 2023
  • 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
  • ...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
  • ...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
  • LibreCAD Kernel Documentation/API Documentation for the usage with other softwares.
    2 KB (263 words) - 06:19, 20 March 2014
  • ...ork to be done is to put gecode's constraint solver "underneath" the libpc API in place of the existing solver and demonstrate successful soltions to prim
    2 KB (283 words) - 17:49, 14 March 2014
  • ...dges will be implemented... also, we may not want to implement some of the api functions that only create empty shells / regions for new models. models ca ...d800a7974a46a39e97?diff=split commit #1 for today]: added call to internal api for "Make Region, Shell, Vertex"
    12 KB (1,787 words) - 20:20, 30 June 2015
  • An API will be created to allow the framework to request data from the user. **Add the API to use them
    5 KB (783 words) - 16:28, 5 May 2016
  • ...oint, this task entails creating that (basic) client-server communications API using an OpenGL client front-end that leverages an existing scene graph and =Object-oriented geometry engine API=
    13 KB (2,013 words) - 19:07, 29 June 2011

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