|
|
 | | Re: L3P Warnings
|
| (...) The decision not to include POV code in LDraw part files was made by the LSC - see (URL) for the rationale. Chris (14 years ago, 30-Jun-10, to lugnet.cad.ray)
| | | | | Re: L3P Warnings
|
| (...) I'm pretty sure the decision to disallow inline POV code in official parts was made prior to the creation of the LSC. On a side note, LDView's POV export functionality supports L3P's inline POV syntax. --Travis (14 years ago, 30-Jun-10, to lugnet.cad.ray)
| | | | | Re: L3P Warnings
|
| In lugnet.cad.ray, Tore Eriksson wrote: <snip> (...) I'm sorry I really don't, the 'if then' construction is pretty much the same only thing is the two versions are in the same file. So perhaps you are hinting on maintainability or mixed single (...) (14 years ago, 29-Jun-10, to lugnet.cad.ray)
| | | | | Re: L3P Warnings
|
| (...) After some tough discussion some years ago, I now agree on that (although so far, I've seen nothing that comes remotely close to L3P+POV-Ray. And I doubt there will be in a foreseeable future). (...) You don't??? Are you serious? I can (...) (14 years ago, 29-Jun-10, to lugnet.cad.ray)
| | | | | Re: L3P Warnings
|
| In lugnet.cad.ray, Dave Schuler wrote: <snip> (...) As far I understand it, the main reason the LSC don't want POV code in the parts themselves is because of the 'pollution'. Because another person might want blender code or maybe even something (...) (14 years ago, 29-Jun-10, to lugnet.cad.ray)
|
|
