I'd be interested, even with the ocean liner in place this information would be helpful.
I was thinking about something similar like this a while back but decided to push it to the next next LDCad version thinking it's part of connectivity which I'm planning for a later version.
You could probably collect some information from scanning the headers of the library, most companion parts use a identity matrix anyway and share similar descriptions or !help lines.
For example the wheel and tyre parts usually have the same diameter in their description (you could setup regex rules for this in the cfg file). The list would then automatically assimilate new parts in new library's and you only have to add information about less obvious parts to the config file.
I was also thinking about a self learning feature at some point using grouping.
I was thinking about something similar like this a while back but decided to push it to the next next LDCad version thinking it's part of connectivity which I'm planning for a later version.
You could probably collect some information from scanning the headers of the library, most companion parts use a identity matrix anyway and share similar descriptions or !help lines.
For example the wheel and tyre parts usually have the same diameter in their description (you could setup regex rules for this in the cfg file). The list would then automatically assimilate new parts in new library's and you only have to add information about less obvious parts to the config file.
I was also thinking about a self learning feature at some point using grouping.