 | | Re: Partsref is Moving to LUGNET
|
|
[should've snipped the ng list, but I didn't--couldn't decide which to keep/exclude] (...) So, as both the new Keeper of the LDraw Library and the Keeper of the Partsref Pages, I could build a make, and apply it everytime I get new candidate files (...) (25 years ago, 3-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
I haven't gotten any nibbles, can someone suggest a group better suited to answering this question? (...) <for one part> (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) This is kludgy but might work. Details left as an exercise. Your problem is that what you want is to know when a file is *new to YOU* not what it's timestamp is. Keep two complete sets of .dat files. One is an image of the state of files, but (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) You could try the version which comes with Cynwin32: (URL) used Beta 20.1; it seems pretty stable. If you're not too keen on using the Unix sub-layer (slow), try dmake: (URL) it seems to have gone commercial -- you have to *pay* for the (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) Yep, I'm familiar with make. I even went to look for one once. Do you know how hard it is to search the net for 'make'? I never could figure out a decent set of search-words... Oh, wait. I've got a make.exe with my old copy of Turbo Pascal. (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) Are you familiar with the make utility? It allows you to describe an arbitrary set of modules, with their associated interdependencies, and then re-build only the modules which have changed and modules dependant upon them. Of course, using (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) That's fine with me. The only downside is applying updates. When new parts are released for LDraw, I don't update individual partsref images and pages, I just regenerate the whole shebang. So any manual edits would probably get overwritten. (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) Yeah I was thinking that the third size should be a composite of four views top, left, bottom, and right. Should the floor be kept in this kind of view? Ie: Rotate Part over floor rather than 4 Cameras, nuking the floor only on the bottom (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
Excellent! After looking at them I think that other perspectives are more important than colors. Have you tried experimenting with the ambient light option in povray? I don't think l3p gives you that option but you can modify the pov files l3p (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) I Started this Several Weeks ago, I have already run Pov-Ray for the Thumbs and the Large Size. I have only the two sizes done so far. What would you call normal Size, I had not figured out a good third size any suggestions? All pngs, 128x96 (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) Speaking of which... I just posted my wants list. I want hundreds of most of the items on it. Someone pointed out to me that if I could tell of sets that had large quantities of the parts I might get better responses. Given the current state (...) (25 years ago, 1-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
One thing I noticed with the DAT explorer is that POV rendered images look _MUCH_ better with the lossless PNG format thatn with JPEG. Perhaps appropriate use of the JPEG smoothing function would help the the tests I did looked bad even at 100% (...) (25 years ago, 1-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) IMHO, the best thing is having both (a) super-quick-loading GIFs and (b) high-quality POV JPEGs, and then letting the user decide which one to view. A while back, someone even suggested having spinning/rotating POV-rendered images for each (...) (25 years ago, 1-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
Kevin Loch <kloch@opnsys.com> wrote in message news:FM32ur.BwF@lugnet.com... (...) I agree. Some parts--especially those with lots of rounded surfaces--can be hard to make out in LDraw. POVRAY works much better for these parts (and for decorated (...) (25 years ago, 1-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) Cool! (...) Is there any desire to have povray rendered images for each part? I still think that would be cool, even though the ldraw versions are more useful for some things. It would also be nice to be able to either: 1. have all parts (...) (25 years ago, 1-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary)
|
| |
| | 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)
|
