 | | Inline POV code in official parts?
|
|
What's the current plan for POV-Ray code in official parts? I have been out of the loop for a while, but my last understanding was that parts with inline POV-Ray code don't have any chance of getting certified on the parts tracker. Is this still the (...) (21 years ago, 28-Jul-03, to lugnet.cad.dev)
|
| |
| | 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: Inline POV code in official parts?
|
|
(...) I agree with Steve on this issue: no POV code in offical parts with the possible exception of primitves. I feel this way for a few reasons: - It could be construed the POV is the Official rendering program of the LDraw.org library. This can (...) (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: Inline POV code in official parts?
|
|
This is just my opinion since I started all this by suggesting to Lars to add POV support into L3P in the first place. By adding a few .dat primitives (not POV primitives) to the .dat definition, then you don't have to tie yourself to any renderer. (...) (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)
|
| |
| | Re: Inline POV code in official parts?
|
|
(...) That's a very heavy argument against EmbPOV. It would be a great thing if we could just have a very few basic features, say clipped by, pattern wrap and maybe one or two other and make it a generic syntax for alternative code. (...) Despite (...) (21 years ago, 13-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Inline POV code in official parts?
|
|
(...) More than three years have passed, the only thing that has happened is that the SteerCo and/or the Standard Committee has decided not to allow EmbPOV in the official Parts folder. A vauge discussion on creting yet another folder for Ldraw POV (...) (18 years ago, 1-May-07, to lugnet.cad.dev)
|
| |
| | Re: Inline POV code in official parts?
|
|
Why not make official POV-Ray Lego bricks and skip the whole LDraw to POV-Ray conversion? Use the same names, scale, and coordinates and all you need is a small script to convert the LDraw lines into POV- Ray lines using the same translations. Or (...) (18 years ago, 1-May-07, to lugnet.cad.dev)
|
| |
| | Re: Inline POV code in official parts?
|
|
(...) It doesn't really gain you much if you are just converting the LDraw parts directly - l3p does that just fine, and fairly fast. The only advantage of a POV-ray library is when you start adding POV-ray specific stuff, eg: replace the curve (...) (18 years ago, 1-May-07, to lugnet.cad.dev)
|
| |
| | Re: Inline POV code in official parts?
|
|
(...) The LDraw POV project ((URL) was created with the intention of someday becoming the de-facto, if not the actual, official LDraw compatible POV repository. I'll admit that it has languished for sometime (it's been almost 4 years sine I (...) (18 years ago, 2-May-07, to lugnet.cad.dev)
|
| |
| | Re: Inline POV code in official parts?
|
|
(...) Well, maybe others don't care about visible polys when it should be smooth, but it makes all the difference in the world to me. (...) Well, yeah. But that is better than everyone inventing their own POV- Ray code to make their own parts. How (...) (18 years ago, 2-May-07, to lugnet.cad.dev)
|
