 | | 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)
|
