 | | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) I think that the word slope should be in there, along with the degrees of the slope. Those two slopes would then be "1x2 45 degree end cap slope" and "2x2 45 degree peak slope junction". Although, "half-pyramid" fits the "end cap" best, as (...) (25 years ago, 7-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
|
| |
| | Re: LDAO Suggestion Mark 3
|
|
I just keep a 0view.dat file in my /models directory ("0" so it's always at the top), and when I want to view .dats from the newsreader I launch the 0view.dat into LDAO's Editor, then with one cut-and-paste I can view a model. One more cut-and-paste (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev)
|
| |
| | Re: Parts Database (Was: Idea: ... Lego piece naming convention?) [DAT]
|
|
Ah, yet another promising database variant! This is great, and fast! I only see one problem with it is it only includes official LDraw elements. Isn't there any way we could make .DAT files for not yet rendered parts, too? Just for database (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) Why not add some new meta-commands? Either: 0 DEAFULTS COLOUR=15 ZOOM=150 (or 1.5) Or: 0 DEFAULT COLOUR 15 0 DEFAULT ZOOM 1.5 ... In fact, parts of the database could be hosted in the parts' .DAT files (to be continued in my posting subjected (...) (25 years ago, 7-Jul-99, to lugnet.general, lugnet.cad.dev)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) Would the plan be to include images for each part in each known colour? For the decorated parts, at least, I would prefer that the image uses a real life background colour rather than the default grey. As a reference for parts sales, etc it (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) Speaking of which, that 3002peye is one of those early mistakes that needs to be fixed. -- Terry K -- (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| |
| | Re: LDraw Parts Update 9905
|
|
(...) I have no problem with LEdit using the installed version of piece 30359. That is the piece you mean, right? Email me the part file you have and I will check to see if it causes a problem. -- Terry K -- (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.cad)
|
| |
| | Re: LDraw Parts Update 9905
|
|
(...) there is a serious bug in 9905. using the laser piece in ledit crashes ledit. someone want to take a look at the problem??? ldlite gives a syntax error on line 126 for the part but there is nothing wrong with line 126 that i can see. (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.cad)
|
| |
| | (canceled)
|
|
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
Simon Robinson wrote in message ... (...) and (...) Hey, those aren't "hollow space wheels", they're "podracer jet engines"... Frank (25 years ago, 7-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
Todd Lehman wrote in message ... (...) problem... in the above database, part 3002 is a 2x3 brick, part 3002PEYE is a 2x2 brick with printing of an eye). Frank (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) I'd agree. In principle, where bricks do have obvious uses you'd need to keep that use in the name for simplicity. After all, I'm sure it wouldn't be too hard to find some exotic uses for wheels, but is anyone seriously going to suggest that (...) (25 years ago, 7-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
John Matthews wrote in message ... (...) different (...) I think parts descriptions have to assume a "top/up" of a part, otherwise, we'll have really long names" "5x5x2 rectangular piece with one stud centered on one 5x5 face with hollow on (...) (25 years ago, 7-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) Correction: it would be bad to put each image *only* on a separate web page. Right? It really needs both (or multiple) types of displays. Here are a couple of crude, semi-working examples... * One piece: (URL) A bunch of pieces in a numeric (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) Words can't be copyrighted (well, maybe supercalifrigilistic...alidocious can be :-) but trademark searches are free at the USPTO (but they're delayed by 2 months so that they can charge fees for up-to-date searches). USPTO search of their (...) (25 years ago, 7-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) It would be bad to put each image on a seperate web page. Right now I depend on printed parts catalogs, and having all the images on one page allows me to print them out quickly. If the parts were each on their own page it would make the site (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) Just my .02 Sterling: This word might already be copyrighted and / or trademarked. How cheap is a copyright search? Also -- I kinda prefer the one without the "k". I guess it boosts our class if we're building with fancy Lego "bric"s rather (...) (25 years ago, 7-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
|
| |
| | Re: can parts authors try to finish what they have started?
|
|
(...) i remember that steve bliss made it and the part that was posted was close to being finished. what i was saying is that someone should finish the part because it is probobly 90% complete, not like the canoe and quarter saucer hill that are (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) Darnit, I can't spell today. :-) That should be "Bricktionary." --Todd (25 years ago, 6-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) As they say in Canada, Minnesota, and Maine, "O-ya, it's been parta da plan since day one." :-) Lots of little prototypes and mock-ups and discussions here and there. Sill a ways off from fruition, though. But I think it's one of the very most (...) (25 years ago, 6-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
|
