X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-transfer-encoding; bh=zjBsXSLZEzEYdx7jAh4C4GukeyARSyn48E6nYB6DMw0=; b=uw2nM7Om2qIrg4cYy/sYjLPJdJ3m9IA4kUehr3Vba0Gj8dWRZOllLimczAxTOoBR/g oKzBtGK+jgIEb8pb9my+7jpQayV59gxAcpfPU5VgrH/Cs+x/tudreU0vPJA4lRMnhGt6 oZwRH8/Rpsk3ZQZkeDjj6RHOKdRj/OK1yHJOziM44oreI/OnSEf17Yz2WuXcsMSYxwLB enJDkGBB90xChGp9n4wezm0HlsjtSkCRory2qI+HUsocY3GoizcsOlzvj0J+966AA7Lb oWyM9273s0sqO7EBkBtHd4kWATpZHBpr0bJ2qx6ANfbKs1j6nqI432xotHFLh7zzwHkc vIEg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=zjBsXSLZEzEYdx7jAh4C4GukeyARSyn48E6nYB6DMw0=; b=H8X5734b5XvvF0sxjDtNcJyKNATcM+8O4Rxect7aqG9R9aHSc4zNLCi+iz/npDDCOb Twhy04ub7zioXmWIiJlDxsRTyYQvnf6SO9J3g3T8RAgHlA8U0z5YpU7am/TgB8L1rGqW Soon5PdYGYWiD6BnReTMmpSokJEnIrTi3I0aKxZWFBl+ybjMV1PHjy3metpIZ7RO4OV4 YAcP1ylAz+dCWf7JSt6djgPO2Y7rFpyaNwMX8SijkqZYT4FRr3MHbPplqrfJKlwcR/8n tr11bW3MqvBMFLsN9ioNX22nEs66gyOMFUExd8fGNXjzHY+so/VSJuDVgqD1XFGMr/Sa MaBg== X-Gm-Message-State: AD7BkJKKsXxrquSL3laLwCFEkESP7k/i77XpGml/5ypXo9Ys8E7s3MEeWY4zVuW1kHz/yg== X-Received: by 10.112.64.6 with SMTP id k6mr6619668lbs.50.1460291315626; Sun, 10 Apr 2016 05:28:35 -0700 (PDT) Date: Sun, 10 Apr 2016 14:28:31 +0200 From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] gschem attribute list, value list Message-Id: <20160410142831.7688d5fbb14856453051c459@gmail.com> In-Reply-To: References: <20160324143854 DOT 1a1535a687a8c9fc7ff0bd01 AT gmail DOT com> X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 Precedence: bulk > > For symbol attributes there is a list of attributes to chose from > > then selecting an attribute, although manual entering is also > > possible. It would be good with list of attribute values also. > > First > > step would be possibility to store information in symbol. It is > > useful for values for in particular: resistors, capacitors and > > inductors but also for comparators, operational amplifiers and > > others. > > Ack. > The symbols of my gschem libraries include an attribute "footprints" > with a comma separated list of suggested footprints. Similarly, > they may contain an attribute "values" with a list of preferred > values. The GUI could present these list attributes as a drop-down > list for the user to choose from. Didn't think about that possibility, Great! > See > http://www.gedasymbols.org/user/kaimartin_knaak/essential/essential.html > section "List attributes" > > > > Some attribute values depend on downstream tools like footprint and > > maybe device so they be harder to get into gschem, ideally maybe > > they should be generated by downstream tool? > > Ideally, the allocation of footprints should be driven by, or at least > aided by some sort of library. The advantage of a library over a generic > data base type of approach would be the ability to share. It is much more > straightforward to distribute items of a library than to clone parts of > a relational data base. To read information from symbol is simple, get information from a database or other tool and use them in symbol is more complicated. Nicklas Karlsson