| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
In lugnet.cad.dev, Kevin L. Clague wrote: [much snippage] (...) The above example parallel directory structure is just an example. I see that there are many possible alternate solutions... POV directory as sigbling of LDRAW subdirectory, where the (...) (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
|
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) One thing the project clearly needs right now is a small homepage to tell what it's all about, and outline what people can do to help. That might help pull in more active participants than a lone CVS archive. I've seen your pages, Larry. I bet (...) (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
|
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
In lugnet.cad.dev, Larry Pieniazek wrote: <much snippage> (...) As Orion described, we'd rather put the ability of using POV or whatever other renderer you choose outside the LDraw file format, and outside the LDraw format parts library. If we (...) (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
|
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) The relatively easy solution on how to make the wrench tool and, even more obvious, the (unofficial) patterned maxifig heads - that solution has become undone. (...) The only thing that ever has frustrated me about LGEO is that I never ever (...) (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
|
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) What's entailed? Do you want participants who can test but not do much else? (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|