 | | 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 (...) (16 years ago, 29-Jun-10, to lugnet.cad.ray)
| | | | | Re: L3P Warnings
|
| (...) As I understand it, nearly all of the fuss was about the fact that POV-Ray is a whole separate organism not under the control of the LSC, so any "official" additions to the LDraw library that contained inlined POV-Ray code would be at the (...) (16 years ago, 29-Jun-10, to lugnet.cad.ray)
| | | | | Re: L3P Warnings
|
| (...) A highly unpopular and controversial issue with LDRAW. You'd best create a working group to study the impact of creating your own sub-committee of an existing LDRAW committee for the purposes of resurrecting challenges to an asked-and-answered (...) (16 years ago, 28-Jun-10, to lugnet.cad.ray)
| | | | | Re: L3P Warnings
|
| (...) Let's initiate a list of signatures at once! :) /Tore (Another almost daily inlined POV-code user) (16 years ago, 28-Jun-10, to lugnet.cad.ray)
| | | | | Re: L3P Warnings
|
| (...) Wait a minute! I use L3P and inlined POV-Ray code almost daily--don't tell me that this is being phased out? Aaaaagghh! Dave! (16 years ago, 28-Jun-10, to lugnet.cad.ray)
|
|
