Mail Archives: geda-user/2013/09/08/18:08:45
> The geda.conf files are in a standard file format for which there are
> many parsers available
Er, not what I meant. I mean, a "library" could have symbols,
footprints, and models in it, and gnetlist/pcb/etc would resolve
conflicting names by searching the symbols' libraries before other
libraries. So if you have two "TO220" symbols in two different
libraries, you get the one from the "same" library when a symbol
requests it.
I'm thinking of Kai's library, which is already set up for this.
> > Also, it would be cool if the library "path" included cloud support,
> > like http:// and git:// paths.
>
> It would be cool, but I feel like that might be better implemented via
> helper daemons that just keep an on-disk library up-to-date. You
> wouldn't need any synchronisation with gschem; the library system would
> monitor the filesystem and DTRT when updates occurred (i.e. prompt the
> user, probably).
I really don't want something as big as, say, the Digikey database, on
my hard drive ;-)
But consider being able to search gedasymbols.org live, and
dynamically pull symbols from it... :-)
- Raw text -