Mail Archives: geda-user/2015/07/08/11:45:05
On 07/08/2015 02:41 AM, Gabriel Paubert (paubert AT iram DOT es) [via geda-user AT delorie DOT com] wrote:
> There are still subtle semantic details to discuss, but I see it
> basically as a front cache to the set of libraries (which may be defined
> by URLs as already suggested): if a symbol is in the cache you use it,
> otherwise you fetch the library item and copy it to the cache, where you
> can modify it to suit your need. You need an option in the GUI to update
> from the library (and resolve the case of several libraries defining
> the same symbol), but it has to be a deliberate act.
I like the idea of using a file based store for symbols/footprints even though it means
a library symbol gets copied needlessly and different versions with the same name can
happen. It's important for it to be easy to verify your design is correct, and
isolating it from outside libraries that change form day to day by actions of others
is necessary for that.
A database might be used to enable searching through one's design as he adds to it,
and yet, it would load up its state from the project directory files, (or schematic embedded
paragraphs) so the source of the symbols is certain and easy to confirm. A database
holding the design data chunks might even speed up creation of various kinds of netlists.
The way databases all have a "central control" attitude about them
is trouble for verifying correctness of designs though.
- Raw text -