Would need to be rewritten, but other than that we may be in a position In gcv that capability may be eclipsed, and the csg parser isn'tĪctive and is at a very early stage. wfobj uses it, but with the pending Asset Import Library support Stepcode project is considering a part11 parser rewrite not using * See if we can eliminate BRL-CAD use of re2c/lemon/perplex. Probably will need bounding boxīased tolerance defaults, as well as enabling one or more of the filters * Investigate OpenMesh decimation capabilities, identifying a good workingĭefault setup for a decimate command. The old librt API can be obsoleted cleanly. * move the rt_*_timer timing facilities to libbu and rework to allowĬontexts, allowing for more than one timer to be active. Unexpected warnings and duplicate line prints * mged> nirt -f fmt needs output cleanup. * heap unit test needs to actually compare performance against system Routines that need to autogenerate names to use the new * consolidate dbconcat, clone, make_name, and any other. Simplified tree traversal with cyclic awareness. Requires fullĬonsider implementing a corollary to FTS instead of dirent for Path - need to print a warning and stop walking. * tree command shouldn't infinite loop when encountering a cyclic * make sure we can run db_dirbuild() multiple times without creating * create boolweave+boolfinal unit tests to validate weaving behavior * OpenCL for enhanced performance boolweave sorting L/usr/brlcad/rel-7.18.0/lib -m64 -L/usr/local/lib64 -L/usr/local/lib -pipe -fno-strict-aliasing -fno-common -fexceptions -ggdb3 -D_FORTIFY_SOURCE=2 -O3 -w -L/usr/brlcad/rel-7.18.0/lib -lrt -lbn -lbu -ltcl8.5 -ldl -lm -lpng14 -lz -lc -lpthread -lregex -lsysv -lopenNURBS $ /usr/brlcad/rel-7.18.0/bin/brlcad-config rt L/usr/brlcad/rel-7.18.0/lib -m64 -L/usr/local/lib64 -L/usr/local/lib -pipe -fno-strict-aliasing -fno-common -fexceptions -ggdb3 -D_FORTIFY_SOURCE=2 -O3 -w -L/usr/brlcad/rel-7.18.0/lib -lbrlcad -lged -lwdb -lrt -lbn -lbu -ltcl8.5 -ldl -lm -lpng14 -lz -lc -lpthread -lregex -lsysv -lopenNURBS -lanalyze $ /usr/brlcad/rel-7.18.0/bin/brlcad-config brlcad llibs, reporting semicolon list for 'brlcad' lib). * brlcad-config build helper script is not working (not reporting * integrate gen-registered-attributes-html output into website * metaball in command input needs sanity checks and better validation. They want v2 (default) or previous v1 output format via a * readd support for vrml v1 to g-vrml so that users can select whether Rt_shootrays(), modify to pass all rays down through the spatial * bundle primary rays in rt front end into postage stamps, shoot via * add regression test for directional light sources Region creation - need to fix or back out * attribute normalization is drastically slowing down * fix pipe subtractions shaded display issue in archer g with all possible object types embedded. * modify libfb's default memory buffer allocation to be dynamic * implement uv-mapping callback so we can texture-map BoT, NMG, and Only as lower level settings when there are sensible defaults * The following will be removed from MGED's menu bar (unusedįeatures, can be accomplished another way, or will be exposed The comb and remove the 1_ and / on the entries. Invalid "1_/" to be created that result in error messagesĭuring any db listing (e.g., tops). * material infrastructure has regressions due to attr sync code that * re-enable regress-asc and regress-weight THESE TASKS SHOULD HAPPEN WITHIN TWO RELEASE ITERATIONS * race condition causing bus errors on exit THESE TASKS SHOULD HAPPEN BEFORE THE NEXT RELEASE At the beginning of each month,ĭevelopers add the tasks they expect to complete and then remove those It's more like a developer scratch pad for recording ideas andĬoordinating release tasks. This is not an official list of tasks that will be completed. Monthly development release iteration, tasks that will hopefully beĬompleted within two iterations, and a remaining "backlog" of Included is a list of the tasks expected for the current This document contains a collection of desirable BRL-CAD development
0 Comments
Leave a Reply. |