| | Re: Part naming/organization [was: Re: More inventories on peeron.com!]
|
|
(...) You're absolutely right. I keep planning on updating those parts. Basically, the Castle, Space, and Town categories should go away. Train will stay, because there are many train-specific pieces. Ditto for any other theme-like categories. Steve (23 years ago, 29-Jun-01, to lugnet.db.brictionary)
|
|
| | Re: Part naming/organization [was: Re: More inventories on peeron.com!]
|
|
(...) Are you letting me fight my own battles, or throwing me to the wolves? ;) Partsref using LDraw names is no defense for me... (...) And my stance is that partsref uses the data from ldraw. My advantage is that when LDraw changes, it's very easy (...) (23 years ago, 29-Jun-01, to lugnet.db.inv, lugnet.db.brictionary)
|
|
| | Re: Part naming/organization [was: Re: More inventories on peeron.com!]
|
|
(...) heh, I agree - except that I can't think of a way to group headgear together... not without using keywords or something... (which is planned, I'll admit). (...) heh, no, not really - just we got tired of the huge pile of sets waiting to be (...) (23 years ago, 29-Jun-01, to lugnet.db.inv, lugnet.db.brictionary)
|
|
| | Re: Part naming/organization [was: Re: More inventories on peeron.com!]
|
|
(...) I'll let Steve fight his own battle - but I will point out that partref uses %100 ldraw names... :) (...) Tell me about it. Our current stance on peeron is that we won't create new names for pieces that already have names via ldraw/partsref... (...) (23 years ago, 29-Jun-01, to lugnet.db.inv, lugnet.db.brictionary)
|
|
| | Part naming/organization [was: Re: More inventories on peeron.com!]
|
|
(...) And I must mention that, although it is in some ways convenient to be able to find pieces by theme, things get messy when themes are used in the hierarchy. For example, consider the Castle section of Partsref, and these "Castle *" parts. There (...) (23 years ago, 29-Jun-01, to lugnet.db.inv, lugnet.db.brictionary)
|