kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

On 1/23/2018 2:18 PM, Vesa Solonen wrote:
> Matthijs Kooijman kirjoitti 23/01/18 klo 19:18:
>> Hi Wayne,
> 
>> I think upgrading the library list is the most important, since (in the
>> eyes of users) it is a fairly trivial change (in terms of what needs to
>> happen, not necessarily in terms of implementation) that is annoying to
>> do every time (remove all libraries and re-add all libraries, or compare
>> the list of libraries to the files to see if anything changes).
>>
>> Automatically updating existing schematics when one of its symbols moved
>> to a different library would of course be awesome if that could happen
>> as well. I also made a suggestion about that:
>>
>>> One way I can imagine this works is to also include a "rename"
>>> specification (perhaps similar to the current rename.json), which can be
>>> used by KiCad to automatically migrate older symbol references. Or
>>> perhaps the rescue dialog can be improved to look among other libraries
>>> for a symbol with the same name and let the user choose between
>>> relinking to such a symbol, or resueing one from the cache.
> 
> I've spent some time on this and it seems the way to go is using
> UUID/hash as object identifier. That takes care of versioning, provides
> fast and robust search, identification and archival (on object basis,
> independent of "library" or version control system). Please refer to
> Horizon EDA and LibrePCB implementation for details.
> 
> -Vesa
> 

I'm not opposed to this if we come up with a reasonable solution that
solves all of our requirements (project portability across platforms).
If we want to use hashes for symbol lookup, we need to make this
decision before I implement the new schematic and symbol library formats.