(2019-04-07, 12:05)Willy Tschager Wrote: I'd like to discuss the argument opened here:
The LDD ldraw.xml file has this structure:
<!-- Arch 3 x 6 x 5 30613.dat -->
<!-- PAVILION 6X3X5 19063 -->
<Brick ldraw="30613.dat" lego="19063"/>
<!-- PAVILION 6X3X5 30613 -->
<Brick ldraw="30613.dat" lego="30613"/>
<!-- Animal Dolphin 6228b.dat -->
<!-- DOLPHIN 9M 6228 -->
<Brick ldraw="6228b.dat" lego="6228"/>
How does it look like in Studio?
How would an information like this treated in an editor? Would it show also the alternate number or just jump to the right part is an element number is entered say in a search?
w.
I think this a fairly trivial problem to solve as long as the APIs to Rebrickable and Bricklink are robust. A simple script that runs every so often to update a database and then another script to pull info from the database to auto-generate a file in the format of choice (I think JSON is appropriate). Manual entries to the database would also be available to suppliment the API data. We could even do an initial population of the data by scraping already available KEYWORD data. Maybe a front end to allow searching. I'm super worried about it being 100% accuarate, just "good enough".