Symbol and footprint library table grouping

Bug #1764062 reported by Niki Guldbrand
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
KiCad
New
Unknown

Bug Description

While playing around with the 2 tables, I realised that it would be really handy if you could manage your libraries in a group, lets call it a "Collection" for the lack of a better term.

In https://github.com/KiCad/kicad-symbols there is a file called sym-lib-table, this file can be used as the "Collection List", then in the table editor you could "Include" a Collection by adding a reference to that file something like:

(sym_lib_table
  (lib (name xxx) ..... )
  (collection (name kicad) (type ....) (uri <some/path>/kicad-symbols/sym-lib-table) (descr "KiCAD Symbol library") (chksum....))
  (lib........))

Then in the table view it would be represented as 1 single row, but in general use it would behave as if the libraries were at that point in the system sym-lib-table.

In the component chooser you see it something like this:

Library name
-> Part name
-> Part name
KiCAD Symbol library
-> Library name
->-> Part name

Changed in kicad:
importance: Undecided → Wishlist
Revision history for this message
Wayne Stambaugh (stambaughw) wrote :

Symbol library tables can be linked so changes to the file formats are unnecessary. We would have to add some way to keep a list of library tables. The project file seems like the logical place for this list. We already have two "groups", global and project specific. I'm not sure how useful more groups would be but it is doable.

Changed in kicad:
status: New → Triaged
Jeff Young (jeyjey)
summary: - Symbol and footprint table editor grouping
+ Symbol and footprint library table grouping
tags: added: eeschema feature.request pcbnew
removed: wishlist
Revision history for this message
Seppe Stas (seppestas) wrote :

@Wayne what do you mean with "Symbol library tables can be linked" and how does this work? Could it be used to solve https://bugs.launchpad.net/kicad/+bug/1756735?

Revision history for this message
Wayne Stambaugh (stambaughw) wrote :

@Seppe, the design of the library table code allows any number of library tables to be linked together. Currently, the UI only supports global and project library tables but any number of library tables could be added.

Revision history for this message
Seppe Stas (seppestas) wrote :

I see, but if I understand correctly, a change to the UI would still be required in order to use this.

I agree that the changes to the file format of the library tables are unnecessary, but like you said there needs to be a place to store the list of used library tables.

I do not like the idea of using the project file for this, since this easily brakes when people in an organization e.g don't use the correct templates. It also doesn't support the use-case I described in my comment to issue +lp:1756735 since I explicitly want to have "local" as in "local to my PC" library tables.

I think an environmental variable makes sense and is somewhat in line with how the library locations get configured. Changing the library table format to allow "nested" library tables as described by Niki could work as well though.

Revision history for this message
KiCad Janitor (kicad-janitor) wrote :

KiCad bug tracker has moved to Gitlab. This report is now available here: https://gitlab.com/kicad/code/kicad/-/issues/2127

Changed in kicad:
status: Triaged → Expired
Changed in kicad:
importance: Wishlist → Unknown
status: Expired → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.