DOPΣ - isnt kicad mod supported? or how does it...

isnt kicad mod supported? or how does it work any working example?
No description
10 Replies
Rishabh
Rishabh3w ago
It is supported, there is a change in architecture it seems currently. This should be resolved in sometime. I am waiting for @Seve response
DOPΣ
DOPΣOP3w ago
is this handled by core or footprinter/?
No description
Rishabh
Rishabh3w ago
No, this wouldn't work in the footprinter repo. The fetch is done in the eval
DOPΣ
DOPΣOP3w ago
eval is saying this? is it implemented or not
No description
Rishabh
Rishabh3w ago
I know, it is implemented 😂. The platformConfig is being over writen in runframe
DOPΣ
DOPΣOP3w ago
too much complex 😢 , im trying this7
No description
Rishabh
Rishabh3w ago
What is the issue you are trying to solve?
DOPΣ
DOPΣOP3w ago
GitHub
Support direct import of kicad_mod files · Issue #768 · tscircuit...
We could theoretically support direct import of kicad_mod files for people who have local kicad libraries. Figure out how to make bun have a custom import handler for a kicad_mod file Modify tscirc...
DOPΣ
DOPΣOP3w ago
i need example or something that is expected so i can test if my implementations are correct
Seve
Seve3w ago
You can get kicad mod files from the official kicad repo or the kicad-mod-cache.tscircuit.com RE: Your approach with converting the kicad_mod to circuit json inside eval. This would work but I'd like to not build in too much kicad-specific functionality especially at that stage where it's hard to catch errors (you're doing it at a sort of import resolution stage) Instead, i think your should introduce something to props/eval's platformConfig like footprintFileParserMap: { kicad_mod: { parserFn: ... } } } Inside core, we can then call the footprintFileParserMap.kicad_mod.parserFn when we get a URL (all static file imports are converted to URLs) hopefully that makes sense @DOPΣ , what i've proposed will make tscircuit more extensible for other types of footprint files

Did you find this page helpful?