Mail Archives: geda-user/2016/03/26/23:45:00
On Sat, 26 Mar 2016, Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
> I'm not absolutely clear what you have in mind here, but far more
> useful than an interface to a local sql would be some graceful way to
> interface to these:
>
> https://www.snapeda.com
> http://madparts.org/
>
> So far as I'm aware these are the closest things to an effort to
> develop open parts libraries and creation.
>
I plan to have a web footprint plugin too, but I think I can handle that
(nonetheless, volunteers are welcome).
What I mean is that some users expressed in the past that they'd like to
keep their libraries in sql databases. We had the usual
"kilobytes-of-opinions-0-code" sessions about this on the list. A few
random examples:
http://archives.seul.org/geda/user/Oct-2007/msg00017.html
http://archives.seul.org/geda/user/Dec-2007/msg00485.html
http://permalink.gmane.org/gmane.comp.cad.geda.user/45086
https://www.mail-archive.com/geda-user AT moria DOT seul DOT org/msg07861.html
We have even a wiki page about a part manager:
http://wiki.geda-project.org/geda:gparts_dd
DJ also re-suggested the obvious solution in this mail:
http://permalink.gmane.org/gmane.comp.cad.geda.user/45102
This is what I have now, an API between pcb-rnd and random plugins that
can search/list/open footprints whatever way they want. I have the
original newlib (file system) footprint code in a plugin (the user can
even disable it; even, pcb-rnd can run without any code to
load footprits).
What I need is not more discussion about how things should/could be done,
but a volunteer who actually sits down and writes the code of a plugin
for keeping pcb footprint (library database, whatever) in a database
(probabyl sql). In whatever way the given volunteer likes. It's a smallish
project. It is easy to add new footprint plugins and the system is
designed that multiple alternative footprint plugins work together without
interference, so there's no risk in jumping on it.
no-flame DISCLAIMER:
although in some context sql/parts-database is related to
schematics, this mail has nothing to do with gschem (and toolkits,
languages, heavy-vs-light, etc). I am interested in the pcb-rnd side of
the story, so that if the user somehow already selected the right part,
pcb-rnd (and gsch2pcb-rnd) can fetch it from the database.
Regards,
Igor2
- Raw text -