On Fri, 2007-03-16 at 10:18 -0500, John Griessen wrote: [snip]
> Probably some kind of checksum signature put in symbols > would let their version be verified by "unlimited" systems like you envision. > That would keep the file based symbols embedded in designs or saved in users > home directories in sync with ones chosen from a > central database. > > You could put an attribute in your schematic > such that symbols must be from the central database as of such and such a > date. > That would get you stuck in a big-corp/big-education IT world of hassles and > update work > that everybody else could skip! > > John Griessen I had hoped to avoid big nasty IT hastles. 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". Such a database could grow to be large. I'm unclear why using server(s) as data-sources for the parts manager would cause lots more update work. Are you just referring to selecting symbols by date? I'd imagined either a file version number (like CVS), or a SHA1 hash (like git) could identify a particular version of a symbol (or the specific symbol in the later case). I presume most users will use the system without wanting a server, so perhaps it will be possible to mirror repositories like gedasymbols.org as download packages.. e.g. "All symbols from author X", or "The 74xx series". I never intended to completely replace local file based storage. Regards, -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
