Elimination of Physical_Colour parts from the library

[Chris Dee]

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.