LDraw.org Discussion Forums
Elimination of Physical_Colour parts from the library - Printable Version

+- LDraw.org Discussion Forums (https://forums.ldraw.org)
+-- Forum: General (https://forums.ldraw.org/forum-12.html)
+--- Forum: LDraw.org Announcements (https://forums.ldraw.org/forum-1.html)
+--- Thread: Elimination of Physical_Colour parts from the library (/thread-23323.html)

Pages: 1 2


Elimination of Physical_Colour parts from the library - Willy Tschager - 2019-04-03

Hi,

the LDraw SteerCo has unanimously decided to eliminate the current Physical_Colour parts from the official LDraw Parts Library via fasttrack. Physical_Colour parts are parts with hard coded colours, an unique part number and an underscore in front of the description. LEGO calls these "Element numbers". Following a few part numbers from the current library for comparison:

4277932.dat
4277933.dat
300321.dat
4116604.dat
...

But before they get "obsolated" by the Library Admin, we seek feedback and input from the community. Have your word.

Willy Tschager
on behalf of the LDraw Steering  Committee


RE: Elimination of Physical_Colour parts from the library - Gerald Lasser - 2019-04-03

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


RE: Elimination of Physical_Colour parts from the library - Orion Pobursky - 2019-04-03

(2019-04-03, 20:11)Gerald Lasser Wrote: 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.

This is my issue right now. I support the notion of removal but what are we going to do about models that use them


RE: Elimination of Physical_Colour parts from the library - Orion Pobursky - 2019-04-03

Aside from the concern I posted above I have one other thing I'd like discussed:

How are we going to allow cross reference between the hard coded color parts numbers and the actual part numbers? One suggestion is some sort of file that editors can reference to provide this data. If we choose this route we could expand it to include a Bricklink -> LDraw cross reference as well.


RE: Elimination of Physical_Colour parts from the library - Willy Tschager - 2019-04-04

(2019-04-03, 20:11)Gerald Lasser Wrote: 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.

It's not that we actually delete them from the library but HIDE them for the casual user like this:

http://www.ldraw.org/cgi-bin/ptdetail.cgi?f=parts/s/3626bs01.dat

w.


RE: Elimination of Physical_Colour parts from the library - Willy Tschager - 2019-04-04

(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? One suggestion is some sort of file that editors can reference to provide this data. If we choose this route we could expand it to include a Bricklink -> LDraw cross reference as well.

This was also my idea. I would be thankful for some suggestion from the code-people how to tackle this.

w.


RE: Elimination of Physical_Colour parts from the library - Roland Melkert - 2019-04-04

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.


RE: Elimination of Physical_Colour parts from the library - Gerald Lasser - 2019-04-04

(2019-04-04, 8:27)Willy Tschager Wrote: It's not that we actually delete them from the library but HIDE them for the casual user like this:

http://www.ldraw.org/cgi-bin/ptdetail.cgi?f=parts/s/3626bs01.dat

w.

Agreed, that's a good approach, hiding them. How many of those parts are actually in the library?


RE: Elimination of Physical_Colour parts from the library - Jaco van der Molen - 2019-04-05

(2019-04-03, 22:24)Orion Pobursky Wrote: Aside from the concern I posted above I have one other thing I'd like discussed:

How are we going to allow cross reference between the hard coded color parts numbers and the actual part numbers? One suggestion is some sort of file that editors can reference to provide this data. If we choose this route we could expand it to include a Bricklink -> LDraw cross reference as well.

That would make importing an LDraw file in an indexer like Brickstock (which uses the Bricklink database?) a lot easier too.
The most common problem here is all the variants with XXXa.dat, b, c...
We could tackle that too then.


RE: Elimination of Physical_Colour parts from the library - Chris Dee - 2019-04-07

(2019-04-03, 22:20)Orion Pobursky Wrote: This is my issue right now. I support the notion of removal but what are we going to do about models that use them

With a distrubtion as a zip archive it is not possible to delete files that users have already installed - unzip can't do that. Only option is to hide from the parts list. Fresh installs (with the AIOI) could supress them, but I don't like the idea of different install methods producing different libraries.