Mike Crowe wrote: > I have used some of the comercial schematic packages that allow > integration of attribute information into a database. It provides > significant improvements for tasks such as; generating purchasing > requests, inventory management, and bill of materials management, and > component obsolescence. When viewing the attributes on the schematic, > one is looking at the latest component information.
The function of "schematic viewed with latest data" can be had with a files-as-database system too, just by using a different project definition file, or ini files, however you call it. Could database driven apps get their data from gschem running this way? That might have to be done with another full project dir, but that can be had easily with a git branch. The work flow I am imagining is: Werner's files-as-database system used to create a version, git create a branch later for analyzing new parts used, update project file to use newest libraries, connect database apps to that project dir somehow, (probably with Peter Brett's libgeda database-connector. John Griessen -- Ecosensory Austin TX _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
