www.delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2015/06/29/16:38:06

X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-TCPREMOTEIP: 207.224.51.38
X-Authenticated-UID: jpd AT noqsi DOT com
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: [geda-user] gEDA/gschem still alive?
From: John Doty <jpd AT noqsi DOT com>
In-Reply-To: <20150629113018.GH19654@fi.muni.cz>
Date: Mon, 29 Jun 2015 14:37:53 -0600
Message-Id: <06F4FF36-28E4-421F-92D5-91535F982D72@noqsi.com>
References: <1435510363 DOT 682 DOT 26 DOT camel AT ssalewski DOT de> <55902AB9 DOT 9000004 AT neurotica DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1506281932040 DOT 6924 AT igor2priv> <20150629113018 DOT GH19654 AT fi DOT muni DOT cz>
To: geda-user AT delorie DOT com
X-Mailer: Apple Mail (2.1878.6)
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t5TKbx9v018673
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

On Jun 29, 2015, at 5:30 AM, Jan Kasprzak <kas AT fi DOT muni DOT cz> wrote:

> The barrier for using and enhancing thegedasymbols.org library should be
> lowered - the symbols should be searchable/usable from within
> gschem/gattrib/pcb,

Name conflicts would be a serious problem. It’s not safe to put the gedasymbols tree in your symbol search path, as an update by anybody could change your design.

> and the submission of new symbols should be made easier
> (no svn, for example). Maybe a plain old file upload with user feedback
> (like/dislike a particular symbol or footprint, which would then result
> in higher position in user searches, etc.). Maybe some support for
> autogenerated footprints (such as DIL with various number of pins).

One basic problem is that there are two symbol reference paradigms in geda-gaf, and neither is entirely satisfactory. The default is to refer to a symbol in the library search path. The other is to embed the symbol in the schematic file. Neither scales well to complex designs. The clean approach, easily implemented via command line, is to copy the symbol file to a project-specific repository. Clumsy up front, but much easier to deal with down the road. Implementing this approach in the symbol browser would make putting all of gedasymbols in the symbol browser’s search path (while forbidding library searches outside the browser) reasonably safe.

John Doty              Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com



- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019