|
|
 | | Re: Partsref is Moving to LUGNET
|
| (...) Well, like it says on the page, "To reference a part image, when you already know the LDraw number for that part, use the following URL format. (URL).gif" In other words, linking directly to these images is OK in this case. (...) These are (...) (25 years ago, 1-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary)
| | | | | Re: Looking for pieces to trade at the meeting (November and Dece mber )
|
| Not to nit pick too much, but I feel we would be helped if we standardized the terms a bit. I think that there are some elements that are referred to differently than "industry standard" that I have commented on. If I can get to the Decemer meeting, (...) (25 years ago, 30-Nov-99, to lugnet.loc.us.ca.sf, lugnet.db.brictionary)
| | | | | Re: Best way to make parts images?
|
| (...) Quick and Dirty: - Install LDLite and LDraw Add-On - Point LDAO at LDLite for catalog-images (see (URL)). - Run the Make Catalog repeatedly, once for each color. - After running each color-batch, copy/convert all the files in ldraw\vec\ to a (...) (25 years ago, 29-Nov-99, to lugnet.db.brictionary, lugnet.cad)
| | | | | Re: Best way to make parts images?
|
| (...) I once wrote a program to create GIFs from the LeoCAD library for a person who wanted to build a database with all parts. If you're interested, just tell me how you want the files (size, color, command line options) and I'll recompile it (or (...) (25 years ago, 27-Nov-99, to lugnet.db.brictionary, lugnet.cad)
| | | | | Re: Best way to make parts images?
|
| (...) I don't think I agree. The images produced by LDLITE or something similar contain much more information, as they include the edge-lines in the parts. I tried to use raytraced images for instructions once, but I quickly came to the conclusion (...) (25 years ago, 27-Nov-99, to lugnet.db.brictionary, lugnet.cad)
|
|
