 | | Re: Inline POV code in official parts?
|
|
(...) Yes, it's pretty much still the case. I would really prefer to not have any POV code in the parts library at all. But if there must be some, I think it should stay in the primitive files. (...) I think a better solution is to work on POV (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Repository of .dat files with inline POV-Ray code... any interest?
|
|
(...) Okay... then I'd like to open this up to a question for the community: Is anyone interested in working on a single shared repository of ldraw-compatible parts with inlined POV-Ray code? How many authors out there are comfortable with both (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Repository of .dat files with inline POV-Ray code... any interest?
|
|
(...) Why not just a library of POV code only parts, ala LGEO/Raves, only compatible with the LDraw.org library? We could host this project on Sourceforge so anyone who was interested could develop. I think if we do it Pov only, LDraw.org is more (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Repository of .dat files with inline POV-Ray code... any interest? [DAT]
|
|
(...) Here is my $0.01.... This is how I have started handling Ldraw/PoV parts: The 3626bp6f.dat is availabe on the parts tracker here: (URL) is some line wrapping happening here, I will need to fix it later) 0 Minifig Head with Female Eyes with Red (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Repository of .dat files with inline POV-Ray code... any interest?
|
|
(...) Because parts with inline POV code work with the version of L3P that we have now. Why not start by building a library of modified official parts, but with the explicit goal of eventually converting them into POV only parts when L3P or some (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Repository of .dat files with inline POV-Ray code... any interest?
|
|
(...) I asked Lars a while back if he could wrap all the part definitions with IF NDEF statements so that someone could define the parts they wanted in an external include file and the rest would use the standard L3P code. Hopefully when a new (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Repository of .dat files with inline POV-Ray code... any interest?
|
|
(...) Now that would rock. For my personal use, this would almost entirely solve the problem. I could whip up a single file that contains all the parts I want to fix, run it through L3P, manually fix the parts in the resulting file, and then include (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Repository of .dat files with inline POV-Ray code... any interest?
|
|
(...) That's right, Don. Please see (URL) continued: (...) Yes, it will. Tony said: (...) Good initiative! If the file gets too big or unhandy for POV, I will reconsider the L3PARTS mentioned in (URL) (21 years ago, 3-Aug-03, to lugnet.cad.dev)
|
| |
| | Re: Repository of .dat files with inline POV-Ray code... any interest?
|
|
More this subject... I just registered a project with Soureforge for the purpose of creating a repository of POV include file describing the LDraw parts library. Once I recieve word back that my registration was approved or rejected, I'll post more. (...) (21 years ago, 19-Aug-03, to lugnet.cad.dev)
|
