| |
In lugnet.cad.dev, Erik Olson writes:
>
> In a nutshell, 'namespaces'.
>
> Switching among parts libraries to get different versions (or different
> data) should be an application capability, not the individual part file.
I'm not following. Are you agreeing with the idea of using embedded POV-Ray
code, or having separate file libraries? I *think* you agree with the
second, am I right?
The one thing we gain by having embedded POV-Ray code is the ability to have
a portion of a part be done directly in POV-Ray, instead of doing the entire
file in POV-Ray.
Steve
|
|
Message has 2 Replies:
 | | Re: Inline POV-Ray code?
|
| (...) Right! I have always thought of the "0 IFNDEF L3PPOV" as a way to utilize most of the normal LDraw lines (that L3P can convert to equivalent POV code) and only replace a small tricky curvy section by some POV code that would look better. This (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
| | | Re: Inline POV-Ray code? [DAT]
|
| I see now that your problem is difficult to solve. Sorry I tried to put it into a nutshell, Steve. My preference would be to design an auxiliary file for each case, and markup the LDRAW part in a very general way, so that future programs could (...) (23 years ago, 1-Mar-02, to lugnet.cad.dev, lugnet.cad.ray)
|
Message is in Reply To:
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
|
|
|
|
