| 03:05.53 | *** join/#brlcad infobot (ibot@208.53.50.136) |
| 03:05.53 | *** topic/#brlcad is BRL-CAD and open source CAx discussion ! Also @ http://brlcad.zulipchat.com ! Logs @ http://infobot.rikers.org/%23brlcad/ |
| 03:25.41 | brlcad | teepee: it's 'alive' in the sense that it's in use by a handful of folks, but nobody is actively working on the code right now |
| 03:26.45 | brlcad | we work on it when we need to and effectively have a more stable / older fork of the github code that we use in our ap203 parser |
| 03:31.03 | teepee | hmm |
| 03:44.14 | brlcad | the domain was let go by mpictor (a young guy that was maintaining the website) |
| 03:44.20 | brlcad | guess he didn't update all of the refs |
| 03:59.24 | brlcad | I think part of it is that we've had a perception that it's "done enough" for what we needed it for in our 203 parser, and a fairly comprehensive spec implementation for most APs |
| 04:03.32 | brlcad | there's some new concepts in ap242 that probably won't parse well without some ap21 changes in the stepcode side, but it should handle 203 and 214 just fine |
| 04:03.55 | brlcad | most of the effort when implementing a parser is on the app side, not on the parsing side |
| 04:04.20 | brlcad | you can see our glue in src/conv/step in the brlcad repo |
| 05:58.28 | teepee | what I've seen the use cases are probably 214 (e.g. generating models for kicad) |
| 06:00.05 | teepee | I'm mostly worried as it not being in any distribution, produces huge amounts of make install errors and I'm not able to find out in an hour how to even build the ap203min example |
| 08:48.23 | *** join/#brlcad Sound (~Sound@unaffiliated/sound) |
| 11:54.13 | *** join/#brlcad Sound (~Sound@unaffiliated/sound) |
| 22:27.59 | *** join/#brlcad merzo (~merzo@151-55-133-95.pool.ukrtel.net) |