Mail Archives: geda-user/2015/09/08/15:53:15
On Sep 8, 2015, at 12:53 PM, DJ Delorie <dj AT delorie DOT com> wrote:
>
>>> For me it seems like a problem to never be allowed to change an old symbol without breaking schematics using them.
>>
>> Or to be able to remove old rusting symbols from the distributed library.
>
> Perhaps we're finally seeing the dark side of a toolkit approach - the
> toolkit leaves too much of the management to the user?
It’s the cost of being able to do things that the developers never imagined. There’s a role for integrated tools. I’m typing this on a MacOSX Mail. I don’t need a mail client to do anything Mail can’t, so its integrated, rather totalitarian approach to the job is perfect for me. But when the job is more complicated, and I need more flexibility, a toolkit makes the job possible.
>
>> And then, ngspice users want an ngspice-oriented library, pcb users
>> want a pcb-oriented library, VHDL users want a VHDL-oriented
>> library, etc. It seems to me that a project library management tool
>> would be very useful.
>
> Yet another task that would fit into a proposed component database
> manager? Or is this something that the other tools need to know
> about?
It’s a little different. I see the component database manager as an automated editing/annotation tool between schematic capture and the downstream simulation/layout/documentation flow. But up front, you may want a tool to select the subset of symbols to use for the project in the first place.
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
- Raw text -