X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Injected-Via-Gmane: http://gmane.org/
To: geda-user AT delorie DOT com
From: Kai-Martin Knaak <kmk AT familieknaak DOT de>
Subject: Re: [geda-user] The new to do
Date: Mon, 20 Jul 2015 02:18:02 +0200
Lines: 21
Message-ID: <mohenr$bj9$1@ger.gmane.org>
References: <CAM2RGhQ70Pex5aNeQ86vKHc7sKf_Vpws69__CPb2QKg6fJTeHg AT mail DOT gmail DOT com> <mnv04v$if0$1 AT ger DOT gmane DOT org> <0A5D410F-D1EF-4FC6-AF0F-BB13218B1615 AT icloud DOT com> <mo1uus$cmb$1 AT ger DOT gmane DOT org> <201507140318 DOT t6E3IElw031504 AT envy DOT delorie DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7Bit
X-Complaints-To: usenet AT ger DOT gmane DOT org
X-Gmane-NNTP-Posting-Host: a89-182-11-108.net-htp.de
User-Agent: KNode/4.14.1
Reply-To: geda-user AT delorie DOT com

DJ Delorie wrote:

>> In particular, the many-to-many-many relation between symbols,
>> footprints and values must be managed in the head of the user.
> 
> IMHO the many-to-many relation is probably one of the most complex
> problems we still need to solve.
> 
A sufficiently versatile package format would provide a solution to 
this problem. A package can be viewed as a way to integrate the 
knowledge about the various aspects of components. 

A package can be as simple as a set of symbols and footprints. In this 
case the knowledge would be the implicit statement that these symbols 
and footprints are compatible. But it can also provide a list of 
footprints which can be combined with a specific symbol. It can also 
provide the information that a component needs to be represented by a 
set of symbols (e.g. a opamp could be represented by a triangle symbol 
and a separate supply symbol)

---<)kaimartin(>---