| |
In lugnet.cad.dev, Don Heyse writes:
[snipped things down a bit]
> So it appears as if we agree that L3P-generated objects don't
> really belong in official LDRAW part files.
Generally, yeah. But mostly to the extent that I haven't thought it through
enough.
> 0 IFNDEF L3PPOV
> 0 normal LDRAW version of part 326bp04.dat
> ...
> 0 ELSE
> 0 INCLUDE l3ppov\326bp04.pov
> 0 ENDIF
That could work, but IMO only pushes the issue to the side. To some extent,
LDraw.org would still be blessing non-ldraw, non-pov-ray syntactic elements.
Steve
|
|
Message has 2 Replies:
 | | Re: Inline POV-Ray code?
|
| (...) Well, if thats how you really feel, then why even bother to "write up a spec/reference page on 0 IFDEF" at all. The instant you put the line: 0 IFDEF <code> in a part file you're blessing a non-ldraw extension. The <code> is by definition a (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
| | | Re: Inline POV-Ray code?
|
| (...) When I wrote this message, I was trying to figure some rational way to mix LDraw and L3P/POV-Ray code. Something like: 0 IFNDEF L3PPOV (ldraw code) 0 ELSE 0 #if (STUDS) 0 LDRAW 0 1 16 0 0 0 1 0 0 0 1 0 0 0 1 stud2.dat 0 LDRAW END 0 #end 0 (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
|
Message is in Reply To:
| | 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)
|
26 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
