|
| | Re: Inline POV-Ray code?
|
| In lugnet.cad.dev, Don Heyse writes: [snipped things down a bit] (...) Generally, yeah. But mostly to the extent that I haven't thought it through enough. (...) That could work, but IMO only pushes the issue to the side. To some extent, LDraw.org (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
| | | | Re: Inline POV-Ray code?
|
| (...) So it appears as if we agree that L3P-generated objects don't really belong in official LDRAW part files. Once again this brings us back to the 0 INCLUDE suggestion. Imagine that ldraw.org (or someone else) distributes a separate set of part (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
| | | | Re: Inline POV-Ray code?
|
| (...) No, I meant the POVRay code referring to L3P-generated objects. By allowing this code in official part files, we'd be endorsing language that hasn't been generally discussed and reviewed. Not that I see any particular problem with the code. (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
| | | | Re: Inline POV-Ray code?
|
| (...) Which part of it aren't you keen about? Is it all the extra stuff in the dat file? If so, then perhaps this is a good time to dredge up my 0 INCLUDE suggestion yet again. ;) (URL) (23 years ago, 27-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
| | | | Re: Inline POV-Ray code?
|
| (...) OK. I'll write up a spec/reference page on 0 IFDEF. It will include the following metacommands: 0 IFDEF <code> 0 IFNDEF <code> 0 ELSE 0 ENDIF Should there be a 0 ELSEIFDEF and/or 0 ELSEIFNDEF? (...) Steve (23 years ago, 27-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
| |