| | Re: pictures at tracker
|
| (...) What format are the current dependency files in, and when are they updated? ROSCO (23 years ago, 18-May-02, to lugnet.cad)
| | | | Re: pictures at tracker
|
| (...) They're in a tab-delimited text file, each line contains a super-to-subfile dependency, the status of the subfile - official, unofficial, or not found, and the title of the subfile. Like this: parts/3001.dat p/stud.dat official Stud The code (...) (23 years ago, 18-May-02, to lugnet.cad)
| | | | RE: pictures at tracker
|
| (...) Steve, I'm kinda busy here this morning, but I'd like to get going on the project soon. For now, I'll do the development offline on my machine, and when I think we're reasonably far along, I'll get acces to the box for testing. Can you send me (...) (23 years ago, 18-May-02, to lugnet.cad)
| | | | RE: pictures at tracker
|
| All, I have finally figured out what the essential character of the job of generating images for the parts tracker boils down to... Here's how I see it. 1. Official parts live in one actual, real file tree 2. Unofficial parts live in another actual, (...) (23 years ago, 19-May-02, to lugnet.cad)
| | | | Re: pictures at tracker
|
| (...) And when do they get generated? My point being, that's the obvious time to generate any images that depend on the part as well. So how I'd see it working is: 1. Author submits part / subpart / primitive. 2. Your script generates dependencies. (...) (23 years ago, 19-May-02, to lugnet.cad)
| | | | Re: pictures at tracker
|
| (...) I put a zip file containing the ldglite sources with the -MSfilepath patch on the sourceforge at: (URL) I had to tweak one line of code to get it to build with the old version of Mesa used on ldraw.org. It should work for Mesa 4.0 and above (...) (23 years ago, 19-May-02, to lugnet.cad)
| |