Peter Clifton wrote:
On Fri, 2007-03-16 at 10:18 -0500, John Griessen wrote:
You could put an attribute in your schematic
such that symbols must be from the central database
[jg]Nevermind me thinking versioning meant part symbols from database on a
date...
I'm conceptually looking at
front end stuff similar to Tomaz Solc's "GTK interface to
gedasymbols.org", but hopefully with much more "database" knowledge
relating to "parts".
Keeping all the files and embedded symbols in sync with the database versions
might cost more time than it's worth,
but to have a database for relating to all the non symbol data about parts
we use is a great thing.
Finding part info gets into how people run businesses, so I think it is best
to let them use databases they already use -- like SQL ones. How about TinyERP
for a database?
Bob Paddock is trying it out, I'm going to give it a whirl. To be able to put engineering data into the same system you put
receipts and invoices and marketing work in would be great.
From it's project page -- "Tiny ERP is a free ERP and CRM solution. The main technical features are: a GTK2 client, a distributed
server, flexible workflows, an object database (on top of PostgreSQL), dynamic GUIs, customizable reports, SOAP and XML-RPC
interfaces, ..."
John Griessen
_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
