 | | 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)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) Sybrand, Since you're looking at an incredibly huge undertaking, be sure to seek out and make the most of every last bit of info you can find on the net about anything related to this. (But don't give up! :-) Here are some related things which (...) (25 years ago, 6-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
|
| |
| | Re: Parts Database (Was: Idea: ... Lego piece naming convention?)
|
|
Tim Courtney skrev i meddelandet <4.2.0.58.1999070617...mm.com>... (...) Don't forget LDLIST, (URL) can search the LDRAW parts on any text in the description, CATEGORY and KEYWORDS, and show a picture of the parts found. (And I can modify it if (...) (25 years ago, 6-Jul-99, to lugnet.general, lugnet.cad.dev)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
I think that it would be unwise to use words such as vertical clip or gable in part nomenclatures. The gable end piece was designed to be used to complete the gable of a roof, yet it might be used for an entirely different purpose. A 1 x 1 with (...) (25 years ago, 6-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
|
| |
| | Re: Parts Database (Was: Idea: ... Lego piece naming convention?)
|
|
(...) EXCELLENT IDEA, Tore! Having that searchable would help a lot. Though it seems an odd characteristic to include, and no one would permanently categorize a piece by number of studs ('cept bricks, plates, and tiles), it is very helpful in (...) (25 years ago, 6-Jul-99, to lugnet.general, lugnet.cad.dev)
|
| |
| | Re: Parts Database (Was: Idea: ... Lego piece naming convention?)
|
|
(...) Hi all A standard naming convention is defenetively a must, weither Ldraw or Aucxilla or what ever it is, my self, I build a db for part inventory giving my own Part Number, Description and it is confusing with all the part auction around. In (...) (25 years ago, 6-Jul-99, to lugnet.general, lugnet.cad.dev)
|
| |
| | Parts Database (Was: Idea: ... Lego piece naming convention?)
|
|
So far, I've only used LDraw's partlist and Lutz's, but I must say Steve's looks very promising. When it comes to Lego databases, there is an infinite amount of data we all wish to enter or seek on. Here's my two ideas to make Mission Impossible a (...) (25 years ago, 6-Jul-99, to lugnet.general, lugnet.cad.dev)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) Actually it was Lutz Uhlmann's Part Reference (at (URL) Frank Filz ---...--- Work: mailto:ffilz@us.ibm.com Home: mailto:ffilz@mindspring.com (25 years ago, 6-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) Are you having problems with the pages I put up at (URL)? Do you have any suggestions on ways the pages could be restructured to be smaller, but still usable as a tool to locate a specific part by looking at images of a bunch of parts? Some (...) (25 years ago, 6-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) To start with the second point you mention: I don't think anyone should be obliged to used the `standard' nomenclature. As you say, for different applications the best name to use can vary for a piece. Even, if one wants to call a 1x1 brick a (...) (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?
|
|
(...) areas (...) I've (...) Do (...) which I (...) what (...) among (...) lot of (...) Another one which would be good to have a concise name for are the various "connector" pieces, especially for the 1x1 plate with side clip. I could see the one (...) (25 years ago, 6-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?
|
|
(...) That would be nice. Too bad it's not a perfect world. At least there's a record that the part has been worked on. If someone else wants to work on the part, they can contact the first author, and maybe avoid some duplicate effort. (...) Is (...) (25 years ago, 6-Jul-99, to lugnet.cad.dev)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) For a lot of basic bricks, plates, tiles, etc, we seem to do OK. But other areas we seem to have trouble with the piece names. One area in particular that I've seen some problems are sloped brick peaks or apex bricks. Let's start there. Do we (...) (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?
|
|
(...) My feeling is that it would be good to have a standard set of names for auctions and inventories. It would be nice if LDraw could use these names also, but sounds like there is good reason for it to use a different set of names. Two sets of (...) (25 years ago, 6-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?
|
|
Jonathan Wilson <wilsonj@xoommail.com> wrote in message news:37809C77.94BD19...ail.com... (...) No. A part catches your fancy, you work on it. You get bored or frustrated, you drop it. Maybe you pick it up later, maybe you don't. (...) That (...) (25 years ago, 6-Jul-99, to lugnet.cad.dev)
|
| |
| | Re: [LDAO] New beta version available
|
|
(...) Yep. That has been fixed for the next release. Steve (25 years ago, 6-Jul-99, to lugnet.cad.dev)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
Sybrand Bonsma <bonsma@phys.chem.ethz.ch> wrote in message news:FEG10M.DFB@lugnet.com... (...) clear (...) maybe (...) LDraw, (...) should (...) The problem is that there are different needs for different applications using piece names. LDraw piece (...) (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?
|
|
(...) I think this is a good idea. If such database is hosted on Lugnet, or a clear link to another place everybody can use the same names when they want to auction/buy/sell/trade pieces. If there are pictures shown of the pieces it would even be (...) (25 years ago, 6-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
|
| |
| | Idea: How starting to work for a unique Lego piece naming convention?
|
|
Actually subject line says all. How about making a move about it? Many efforts ongoing around the community requires this. The first examples that come to mind are piece auctions, set inventory database and Lego CAD studies. We have already several (...) (25 years ago, 6-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
|
| |
| | Re: LDraw Parts Update 9905
|
|
(...) OK, it is fixed. And the problem was much worse than I thought. I didn't omit one part from the gif image - I left off *seven*. Turns out PSP's browser would not load seven of the images. I tried repeatedly. And it wouldn't view other things (...) (25 years ago, 6-Jul-99, to lugnet.cad.dev, lugnet.cad)
|
| |
| | Re: LDraw Parts Update 9905
|
|
(...) Thanks, Tamy. But you make it sound like I gave birth. It wasn't _that_ painful. :-) -- Terry K -- (25 years ago, 6-Jul-99, to lugnet.cad.dev, lugnet.cad)
|
