https://brlcad.org/w/index.php?title=STEP_Multiple_Protocol_Parsing&feed=atom&action=historySTEP Multiple Protocol Parsing - Revision history2024-03-28T09:33:46ZRevision history for this page on the wikiMediaWiki 1.32.2https://brlcad.org/w/index.php?title=STEP_Multiple_Protocol_Parsing&diff=5158&oldid=prevSean: Created page with "STEP is the current standard for exchange of CAD data between different software packages. BRL-CAD makes use of the STEPcode project to implement its step-g importer, but cur..."2013-05-01T06:32:22Z<p>Created page with "STEP is the current standard for exchange of CAD data between different software packages. BRL-CAD makes use of the STEPcode project to implement its step-g importer, but cur..."</p>
<p><b>New page</b></p><div>STEP is the current standard for exchange of CAD data between different software packages. BRL-CAD makes use of the STEPcode project to implement its step-g importer, but currently our converter ends up hard-wired to a specific STEP application protocol (AP). There are numerous APs that are commonly encountered (e.g., AP203 and AP214), though, and we'd like to have one importer support multiple APs.<br />
<br />
For this project, you'd work to make our converter read at least AP203 and AP214 simultaneously. This will almost certainly involve extensive work directly in STEPcode to produce a parser properly encapsulated.<br />
<br />
=References=<br />
<br />
* src/other/step<br />
* src/conv/step<br />
<br />
=Requirements=<br />
<br />
* C++ Proficiency</div>Sean