 | | Change to existing policy on embedding POV-Ray code in Official Files —Orion Pobursky
|
| | | The LDraw.org Standards Committee (LSC) has recently discussed the issue of embedded POV-Ray code in Official Parts Library files. After careful consideration and with inputs from leading non-LSC members, most notably Lars Hassing and Chris Dee, we (...) (20 years ago, 19-Jan-04, to lugnet.cad.dev, lugnet.cad)
|
| | | |
| | | | | Re: Change to existing policy on embedding POV-Ray code in Official Files —Larry Pieniazek
|
| | | | | (...) Could you give a bit more info on the compatability issues (or a pointer to where they're discussed)? (20 years ago, 19-Jan-04, to lugnet.cad.dev)
|
| | | | | |
| | | | | | | Re: Change to existing policy on embedding POV-Ray code in Official Files —Orion Pobursky
|
| | | | | | (...) Basically, The POV team controls the syntax, functionality, and implementation of the POV-Ray Scene Description Language (P-R SDL) format. While the POV Team is very good at maintaining backwards compatibility, they have in the past change the (...) (20 years ago, 19-Jan-04, to lugnet.cad.dev)
|
| | | | | | |
| | | | | | | | Re: Change to existing policy on embedding POV-Ray code in Official Files —Larry Pieniazek
|
| | | | | | (...) OK, but whether or not the P-R SDL code was out of whack would not affect the usability of parts as parts within LDraw format programs themselves, right? (0)Only affect the accuracy or completeness or error state of transformation (by tools (...) (20 years ago, 19-Jan-04, to lugnet.cad.dev)
|
| | | | | | |
| | | | | | | | Re: Change to existing policy on embedding POV-Ray code in Official Files —Kevin L. Clague
|
| | | | | | | 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 (...) (20 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| | | | | | | |
| | | | | | | | | Re: Change to existing policy on embedding POV-Ray code in Official Files —Kevin L. Clague
|
| | | | | | | | 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 (...) (20 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| | | | | | | | |
| | | | | | | | Re: Change to existing policy on embedding POV-Ray code in Official Files —Steve Bliss
|
| | | | | | (...) True, but the 'embedded code' is still code we are effectively certifying as being good, whether it works strictly within LDraw, or in other GDL/SDL's. (...) Sorry, we never got around to making the list public. I'll work on that. Steve (20 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| | | | | | |
| | | | | | | | Re: Change to existing policy on embedding POV-Ray code in Official Files —Steve Bliss
|
| | | | | | (...) And now the archive is public (Thanks, Dan!). See the mailing-group list at the bottom of the page at (URL) (Thanks Orion for making the list!) Steve (20 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| | | | | | |
| | | | | Re: Change to existing policy on embedding POV-Ray code in Official Files —Don Heyse
|
| | | | | (...) Yay! The right place for POV code is in external libraries. Does this mean (URL) is going to be developed? Is a new L3P release in the works? It's been over a year and a half since this tantalizing message was posted. :^) (URL) Don (20 years ago, 19-Jan-04, to lugnet.cad.dev)
|
| | | | | |
| | | | | | | Re: Change to existing policy on embedding POV-Ray code in Official Files —Orion Pobursky
|
| | | | | | | (...) Yes, and if you want to join the project team let me know (this goes for anyone else as well). (...) -Orion (20 years ago, 19-Jan-04, to lugnet.cad.dev)
|
| | | | | | | |
| | | | | | | L3PPARTS (Was: Re: Change to existing policy on embedding POV-Ray code in Official Files) —Lars C. Hassing
|
| | | | | | (...) Yeah, well, it's been three years since the last L3P release, so I guess it's about time for another :-) The current v1.3 release has proven to be quite stable, so I have just collected and implemented a list of wishes from various users. (...) (20 years ago, 29-Jan-04, to lugnet.cad.dev)
|
| | | | | | |
| | | | | | | | Re: L3PPARTS (Was: Re: Change to existing policy on embedding POV-Ray code in Official Files) —Chuck Sommerville
|
| | | | | | | I Like it :) It is a great solution to a sticky problem. -Chuck (20 years ago, 29-Jan-04, to lugnet.cad.dev)
|
| | | | | | | |
| | | | | | | | | Re: L3PPARTS (Was: Re: Change to existing policy on embedding POV-Ray code in Official Files) —Niels Karsdorp
|
| | | | | | | | (...) Me, too. This also solves an issue for having .dat files not too detailed, like the rounded metal parts on 12V train conductor parts. Now the .dat files can contain a square box, which is fast drawn in construction programs and the .inc files (...) (20 years ago, 30-Jan-04, to lugnet.cad.dev)
|
| | | | | | | | |
| | | | | | | | Re: L3PPARTS (Was: Re: Change to existing policy on embedding POV-Ray code in Official Files) —Ross Crawford
|
| | | | | | (...) [snip] (...) I think it's a good idea! The only thing I think needs looking at is the naming - should it be dedicated to L3P or to the renderer, eg: RENDERPARTS\POVRAY RENDERPARTS\BRYCE etc. That way, people can provide their own program to do (...) (20 years ago, 30-Jan-04, to lugnet.cad.dev)
|
| | | | | | |
| | | | | Re: Change to existing policy on embedding POV-Ray code in Official Files —Tore Eriksson
|
| | | | | (...) Too sad. If I got that complicated language correcly, this means that the problem presented at (URL) and was solved by embedded POV-code has now regressed to be un-solved again. /Tore (20 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| | | | | |
| | | | | | | Re: Change to existing policy on embedding POV-Ray code in Official Files —Ross Crawford
|
| | | | | | | (...) Only until 3rd party libraries (like LGEO) become available. ROSCO (20 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| | | | | | | |
| | | | | | | Re: Change to existing policy on embedding POV-Ray code in Official Files —Orion Pobursky
|
| | | | | | (...) Actually, the only Official Library parts that have embedded P-R SDL are some of Paul Easter torus primitives. Since nothing was ever done in the first place, nothing is being undone now. If you're like me and frustrated that LGEO is (...) (20 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| | | | | | |
| | | | | | | | Re: Change to existing policy on embedding POV-Ray code in Official Files —Larry Pieniazek
|
| | | | | | | (...) What's entailed? Do you want participants who can test but not do much else? (20 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| | | | | | | |
| | | | | | | | | Re: Change to existing policy on embedding POV-Ray code in Official Files —Don Heyse
|
| | | | | | | | (...) 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 (...) (20 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| | | | | | | | |
| | | | | | | | Re: Change to existing policy on embedding POV-Ray code in Official Files —Tore Eriksson
|
| | | | | | | (...) 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 (...) (20 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| | | | | | | |
| | | | | | | | | Re: Change to existing policy on embedding POV-Ray code in Official Files —Steve Bliss
|
| | | | | | | | (...) Save that code! Once an LDraw/POV-Ray library is a going thing (and it looks like that won't take so long), those parts can be submitted there. Steve (20 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| | | | | | | | |
| | | | | | | | Re: Change to existing policy on embedding POV-Ray code in Official Files —Tore Eriksson
|
| | | | | | (...) Lars has already been implementing that support since... what year? 2004? Probably even longer. I may would have joined it, but it didn't work then and I still can't get it to work now, 3½ years later. (tried testdoc.pov) And, like I said, (...) (17 years ago, 1-Jul-07, to lugnet.cad.dev)
|
| | | | | | |
| | | | | | | | Re: Change to existing policy on embedding POV-Ray code in Official Files —Orion Pobursky
|
| | | | | | (...) At the risk of reigniting this argument, I still hold to the original reasons for disallowing EmPOV: - The POV-RAY SDL is not under the control of the LSC. This means that if the POV-Ray Team decides to depreciate a command (which they have (...) (17 years ago, 1-Jul-07, to lugnet.cad.dev)
|
| | | | | | |
| | | | | | | | Re: Change to existing policy on embedding POV-Ray code in Official Files —Timothy Gould
|
| | | | | | (...) I'd _like_ to see a meta-language for basic shapes defined in their primitives (the current naming system would be fine if it was consistent) as that could be used in converter software of all hues. I also realise this isn't likely to happen (...) (17 years ago, 1-Jul-07, to lugnet.cad.dev)
|
| | | | | | |
| | | | | Re: Change to existing policy on embedding POV-Ray code in Official Files —Willy Tschager
|
| | | | | (...) this is exactly what I was hoping for. w. (20 years ago, 27-Jan-04, to lugnet.cad.dev)
|
| | | | | |
| | | | | Re: Change to existing policy on embedding POV-Ray code in Official Files —Dave Schuler
|
| | | | | (...) Since I've contributed exactly two official parts to the LDraw library (neither of them with inlined POV-Ray code), I'm sure that my opinion carries more weight than anyone's on the subject... :) For some time it has been argued that the use (...) (17 years ago, 2-Jul-07, to lugnet.cad.dev)
|
| | | | | |
| | | | | Re: Change to existing policy on embedding POV-Ray code in Official Files —Roland Melkert
|
| | | | (...) Hello All, First I am no part designer but reading through this discussion I got an idea that might be interesting to share. First I think Orion is right with his stand to not allow povcode because of the 'why only pov-ray' argument. So I was (...) (17 years ago, 2-Jul-07, to lugnet.cad.dev)
|
| | | | |
