 | | Re: LDraw-to-Raves (was: POV in Part) —Steve Bliss
|
| | | (...) I'm torn - using a single file in POV-Ray is definitely more convenient, and 750 definitions don't seem to be too much overhead for the parsing engine to chew on. But for (later) updates to the wrapper library, individual files would work (...) (21 years ago, 16-Jul-03, to lugnet.cad.dat.parts)
|
| | | |
| | | | | Re: LDraw-to-Raves (was: POV in Part) —Paul Easter
|
| | | | (...) I think the 1:1 aproach would be better. Using one main include file might be convienient, but makes it difficult for many authors to contribute to. (...) Something like this? (URL) do not use the part files from there, most of them have been (...) (21 years ago, 17-Jul-03, to lugnet.cad.dat.parts)
|
| | | | |
| | | | | | Re: LDraw-to-Raves (was: POV in Part) —Michael Horvath
|
| | | | | (...) That's it. Do you think you could add to that? I guess a POV file could be made that would automatically generate a gallery. I'll have to look into that. -Mike (21 years ago, 17-Jul-03, to lugnet.cad.dat.parts)
|
| | | | | |
| | | | | | Re: LDraw-to-Raves (was: POV in Part) —Steve Bliss
|
| | | | | (...) Hmm, thinking more about this, it could be done with individual files, and then a single master file that includes all the individual wrapper files. The master file could be auto-generated whenever the wrapper-library is updated. That would be (...) (21 years ago, 17-Jul-03, to lugnet.cad.dat.parts)
|
| | | | | |
| | | | | | | Re: LDraw-to-Raves (was: POV in Part) —Larry Pieniazek
|
| | | | | | (...) Do files have to be named explicitly or is there a notion of includepath or classpath like searching in POV? If so... Would it be possible to combine approaches? Have the base parts all in one file but each release of revs is in another, and (...) (21 years ago, 20-Jul-03, to lugnet.cad.dat.parts)
|
| | | | | | |
| | | | | | | | Re: LDraw-to-Raves (was: POV in Part) —Steve Bliss
|
| | | | | | (...) AFAIK, they have to be explicitly included. (...) Not really, because then there'd be an issue of search order order, too much complication. (...) I prefer to keep it simple -- either one big file with everything in it, or one master file that (...) (21 years ago, 24-Jul-03, to lugnet.cad.dat.parts)
|
| | | | | | |
| | | | | | Re: LDraw-to-Raves (was: POV in Part) —Jeroen de Haan
|
| | | | (...) YES YES YES! Cool stuff, Paul. C'mon guys open your eyes and look at this: (URL) helmet (very good part writing I must say, I couldn't have done it) 500+ lines. And by adding (just) 36 lines of POV code one gets a real rounded helmet. Now, (...) (21 years ago, 20-Jul-03, to lugnet.cad.dat.parts)
|
| | | | |
| | | | | | Re: LDraw-to-Raves (was: POV in Part) —Michael Horvath
|
| | | | | (...) Jeroen, GeoCities doesn't allow deep links to files. You'll have to link to an html page with the image on it. I've had the same problem. -Mike (21 years ago, 20-Jul-03, to lugnet.cad.dat.parts)
|
| | | | | |
| | | | | | Re: LDraw-to-Raves (was: POV in Part) —Steve Bliss
|
| | | | | (...) For one, I'm not keen on putting POV-Ray code in LDraw part files. Besides complicating the review/certification process, it also ties the LDraw library to one specific renderer, in an official way. Steve (21 years ago, 24-Jul-03, to lugnet.cad.dat.parts)
|
| | | | | |
| | | | | | Re: LDraw-to-Raves (was: POV in Part) —Ryan Farrington
|
| | | | (...) Perhaps things like this could be included in the category/list of other .dat libraries that will some day be on LDraw.org. People could go to the respective sites to download POV enhanced parts. Just my $0.02 --Ryan (URL) (21 years ago, 25-Jul-03, to lugnet.cad.dat.parts)
|
| | | | |
