06:18 <houkime> ooook... played with eeshow again today

06:18 <houkime> kicad again surprised me

06:19 <houkime> the thing i discovered is that there's a symlib table in .config/kicad

06:19 <houkime> and it actually holds the info about libs' whereabouts

06:20 <houkime> now the fun part

06:20 <houkime> how is someone supposed to view sch files on the other computer?

06:21 <houkime> there's a <projectname>-cache.lib generated inside the folder

06:22 <houkime> and it is sort of supposed to maintain viewability in cases wherethere's nothing except the project folder itself

06:24 <houkime> + there's a symlib table inside the project folder, but the trick is - it is incomplete

06:24 <houkime> for some REASON

09:29 <Joerg-Neo900> the fun part starts where eeshow joggles with multiple git commit project versions which all have their very specific lib stuff they work with

09:29 <houkime> it's not really a problem

09:29 <Joerg-Neo900> lib and cache*

09:30 <houkime> it does all operations independently for each commit

09:30 <Joerg-Neo900> not as long as you keep ALL lib elements localy inside the project and save them in your git commit

09:34 <houkime> which is exactly why having sym-lib-table in .config is extremely git-unfriendly. I'm not sure what devs are thinking about and probably will need to tap into kicad code itself.

09:36 <houkime> it seems like git and shareability in general is not on the checlistt for them.

09:36 <houkime> *checklist

09:39 <houkime> which makes me wish goodluck to horizon, librepcb etc.

10:43 <Joerg-Neo900> hmmm

10:47 <Joerg-Neo900> aiui the sym-table been there in kicad4 already, and eeshow works with it. No need to mess up kicad itself. Actually if we had planned to modify kicad to integrate eeshow functions, the whole system design would look vasty different and would provide a lot of additional opportunities

11:02 <Joerg-Neo900> kicad4 code is such a hair spaghetti ball that neither Werner nor anybody else dared to cope with it to integrate eeshow into kicad. In fact even kicad devels themselves see it exactly that way: "Beginning developer guide <https://i.imgur.com/miVHGTP.gifv" (and they had a Spaghetti_Bolognese based one, a year or two ago)

14:19 <houkime> nope. there was a fp-lib-table. But not sym-lib table. just searched in the eeshow to be sure. the only symlib table functional is the one introduced by me (in my fork).

14:23 <houkime> it doesn't seem that eeshow did sth with fp-lib-tables either

14:24 <houkime> would be convenient since they are also stored in .config and have the same problem

14:24 <houkime> *could have been

14:28 <houkime> current state is: it does work semi-ok if using cachelib (wpwrak says cache is not reliable enough), it successfully utilizes sym-lib-table that is inside project folder, it's just the file itself is not complete for some reason.

14:30 <houkime> so the simplest fix would be to force kicad to store full symlib-table inside the project folder instead of a partial one

14:31 <houkime> should work then and also makes a lot of sense.

14:33 <houkime> one also could try tocheck .config folder also with eeshow, but this will result in bugs with git versioning since .config isnot in svc

21:07 <Joerg-Neo900> the old "official" kicad developer starting guide video: https://www.youtube.com/watch?v=UerBCXHKJ5s

21:10 <Joerg-Neo900> zhere are project-wide and system(user)-wide lib lists, for footprints and for symnols

21:10 <Joerg-Neo900> project overrides user-global overrides defaults