Hello!
Actually I've been working on this (not the shop part yet, that's the endgame).
I have a table of devices (loosely defined as "needs a power cable/source to operate normally" but there are exceptions like the expansion boards of the CLD-A100) where all connectivity details are kept.
=>
https://www.lddb.com/hardware.phpI treat DACs separately because they are attached to the audio output.
https://www.lddb.com/hardware/part/dac/We could imagine something similar with video processing chips (PAL, NTSC, MUSE, etc.).
I also have a table for parts that is, as of now, only brand/commercial ref/internal ref/description.
You can see it in this post:
admin @ Hardware DatabaseEx:
Pioneer / CU-CLD130 / VXX2364/ Remote Control Then I have a table for Device <-> Parts relationship/compatibility.
It can be 1 part compatible with N devices.
It can be 1 device compatible with N parts.
Or simply 1 part compatible with 1 device.
For CU-CLD130, it's 1 to 2 as it's listed as compatible with:
Pioneer CLD-K8VPioneer CLD-K99VHere is a crude display of the current draft table, manually being moved from
The REMOTE CONTROL definitive list:
https://www.lddb.com/part.phpWe could imagine the same thing for belt, m-holder, etc.
As for LDs before, the logical steps are database -> edit/submit -> collection -> wishlist -> shop.
I'm at the collection step right now.
Julien
PS: but dev is halted for a little while because.... September 19th was "
Talk like a Pirate Day" and the perfect timing to release another round of Guybrush Threepwood adventures!
=>
https://returntomonkeyisland.com/