I was thinking about the recent Parts DB discussion and I would like to see some form of feature like this added to the geda tools. My main problem is that the task is too large to implement in a reasonable amount of time. It is also very controversial because of database backend integration and the added dependences that this would lead too.
So my idea is to try adding a storage and referencing mechanism which would allow a project specific customized components to be referenced from multiple schematic files. The customized components would be stored in a special type of sch file; a separate components would exist for each type of component used in a project and have all the suitable attributes set (value, footprint, etc.); the component would have a suitable text reference value defined. The existing sch file format would be extended to store a reference to the special sch file(s) or through a config file, and a new component reference type would be used to link to the customized component using the text reference value. Suitable GUI changes would be needed to allow component selection and customization, but I would see these as extensions to the existing dialog. Code changes would hopefully be limited to the component processing, with significant refactoring to support these abstract component references. Though I think the changes could be implemented incrementally, possibly providing suitable hooks for database backed plugins. Does this make sense? Within the context of making file format/library code changes, we might also want to talk about embedded symbols, hierarchal schematics, and proper bus support. Robert P.S. Separately I like to see some features which would allow Design Rule Check's to be preformed on schematic files. _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
