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-type:content-transfer-encoding; bh=42/dcBP5z5dlQG656i10PIcUfYDC6HjoyMRjxtAibN0=; b=JqrH6DkEZzZvYpehYopg0qghjLYIjSWT6x8zBCf71ITkeVM3Wj2MqDP5+KPc8IZIzu 6cKdPr0MGp7rU+sFyi6KvqEaapyTOnws5e8S0e/OsWaZLJc2ya+6uXPVKz8KzG3B78Rm 6ib/qhMOsMoU/xNxLWnCua6rjuCWNrsohZQ/KDGnAx9THcY4j7zwOF9kW1DTH3/ZClhu V/DBNUI7/gJBr0rVOgqpjOrd9Gywr4XBMT8/Ser7/cEsOQAv4sD1QmVOVXadirsDN4tK ZGmsKbP2Dq+k7GiT4ei+4qgQ9WpERN2LPZ/HpXvS0CvfRI81RKmmLCS3csyyyXP8Mxyz tEnw== X-Received: by 10.194.175.232 with SMTP id cd8mr38414465wjc.45.1445289378977; Mon, 19 Oct 2015 14:16:18 -0700 (PDT) Date: Mon, 19 Oct 2015 23:16:17 +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] Pin mapping (separate symbols from mappings) Message-Id: <20151019231617.a326768ce3d85ec86a39e81f@gmail.com> In-Reply-To: <201510192106.t9JL6PAx006922@envy.delorie.com> References: <20151018204010 DOT 9cce6a231dcc296256e187bd AT gmail DOT com> <201510181843 DOT t9IIhmWo025346 AT envy DOT delorie DOT com> <20151018233004 DOT 78db1f9df1b1e68325c8639e AT gmail DOT com> <201510192106 DOT t9JL6PAx006922 AT envy DOT delorie 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 > > By default, the schematic references the package and stores the picks of > > the author. > > My idea allows for "something" to choose the package based on whatever > else the user might have provided. For example, if I specify SOT-23 > and my library only has one SOT-23 option, that's enough to specify > the package without having to explicitly specify the package. > > That way you can reduce the set of matching parts a little at a time > instead of having to pick a final package up front. > > > This sounds a lot like the "package" scenario I described above. > > Yup :-) > > My way of using it would be to have symbols keep their symbolic pin > "numbers" like A,B,Y or B,C,E. Footprints would have numeric pin > numbers as usual. The "package" would include a mapping from symbolic > to numeric pins for that package. The netlister would apply the > conversion based on which "package" was chosen. Symbolic pin "numbers", footprint pin numbers as usual and a mapping applied by netlister would also be my way. Nicklas Karlsson