LDraw.org Discussion Forums

Full Version: Elimination of Physical_Colour parts from the library
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
(2019-04-03, 20:11)Gerald Lasser Wrote: [ -> ]Hi Willy,

In honestly never understood, why those parts are in the library anyway. I could not think of a reason to have them.

Actually I wanted to post this question since some time, so it is good you ask for opinions.

The only reason, is backwards compatibility of models in the wild...
But I think the colour hard coded parts are against the spirit of LDraw.

Gerald

They were introduced when LEGO started printing part number in the instructions to try to prevent too many 'why isn't this part number in LDraw' questions. But the concept never really got much traction.
(2019-04-04, 20:00)Roland Melkert Wrote: [ -> ]I would propose a generic index file structure in an existing format like json or xml.

And then include files for specific goals e.g. "LDraw2brickLink.json" or "LDraw2Lego.json" etc.

That would create a massive maintenance task. The translations would need to be managed at the granularity of the individual part number, with a mechanism to regenerate the json or xml (both of which would be quite byte-hungry for a simple translation file). Maybe something to build into Parts Tracker v2?

The authoring tools would need to support this new file, whereas the existing methods of hard-coded colour part files is automatiocally supported.
(2019-04-03, 22:24)Orion Pobursky Wrote: [ -> ]How are we going to allow cross reference between the hard coded color parts numbers and the actual part numbers? 

Well, what I would do is simply read the DAT file of the obsolete part, to see which DAT file is to be used in its place.  (If I correctly understand your question.)  

Thanks, 
Franklin
(2019-04-12, 20:31)Franklin W. Cain Wrote: [ -> ]Well, what I would do is simply read the DAT file of the obsolete part, to see which DAT file is to be used in its place.  (If I correctly understand your question.)  

Thanks, 
Franklin

I meant in the future. For the current parts, presumably an editor can update the reference much like a ~MovedTo but changing the color as well as the file.
While I'm working my way through the Physical_Color parts I'd like to know if we have a some sort of replacement, a list, anything ... editors can work with or I can add to the AIOI so that results pop up when people hit in a casual Physical_Color number into the search.

We started with this: https://forums.ldraw.org/thread-23337-po...l#pid31489

But I still don't see any outcome.

w.
(2019-08-19, 5:13)Willy Tschager Wrote: [ -> ]While I'm working my way through the Physical_Color parts I'd like to know if we have a some sort of replacement, a list, anything ... editors can work with or I can add to the AIOI so that results pop up when people hit in a casual Physical_Color number into the search.

We started with this: https://forums.ldraw.org/thread-23337-po...l#pid31489

But I still don't see any outcome.

w.

Yah. Because Brickset and Rebrickable have already solved this problem. You just search the number in the BIs and it spits you out the correct brick with an LDraw, Bricklink, Brickowl, etc ID.
(2019-08-19, 6:30)Orion Pobursky Wrote: [ -> ]Yah. Because Brickset and Rebrickable have already solved this problem. You just search the number in the BIs and it spits you out the correct brick with an LDraw, Bricklink, Brickowl, etc ID.

This means that I have to be online and use another prog. I was more thinking to offer a some sort of chart such as the LDConfig.ldr which progs use to do a search. Hitting into 123456 points you directly to our 1234.dat in main color.

w.
(2019-08-20, 16:36)Willy Tschager Wrote: [ -> ]This means that I have to be online and use another prog. I was more thinking to offer a some sort of chart such as the LDConfig.ldr which progs use to do a search. Hitting into 123456 points you directly to our 1234.dat in main color.

w.

I don't see a good way to do this with being online. There are literally thousands (probably 10,000s) of physical color numbers and no easily accessible central list of them. A user will have to type the BI number into a search engine to find out what LDraw number corresponds. Providing a master file would be huge sizewise and almost immediately out of date.
Pages: 1 2