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=b8qJXt5dlqd++X+G8bRWYrfHNf1VjONBTvKzLn5XWvw=; b=XRuaZkQIFYuqYI5QRxvXO2L62d7y2u55MSPQHK3VpE0NoC5ESakEamA4sT6aaG8/Tf lMG+zi+0XuteMbi5Z6t5EVg1GQPQ3FmBP/Fvn0W8UBkzhfJjLRtGEZzGqUDXoO23caIq hvX5aWHHtRJKumH+mBlUTk+og6QWbydmsGyXVUPWmaDt2vohleW97Iffvn3jNhhRIEyv 8e75yIQjfszpzY+2R+wkfCXojSQLgl3ngkLO1GdlMypMC/5sqNKQq4sf3oDKGdFZrhcI 78qjEcsrUCHRFdkC9i9SqFR0uIXvjzSGkyNtwSTr2/AIBnNDly1ODBpksJSV3lR1rZCQ FXHQ== X-Received: by 10.25.20.32 with SMTP id k32mr5115911lfi.58.1451500001775; Wed, 30 Dec 2015 10:26:41 -0800 (PST) Date: Wed, 30 Dec 2015 19:26:36 +0100 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] Project leadership (design error in the core of gschem) Message-Id: <20151230192636.fc377052d1b3314ceb5fd4c7@gmail.com> In-Reply-To: <7C27D3F4-9CC2-46DB-BE88-77564F3FC0FC@noqsi.com> References: <43CC8F96-6452-40FA-9DFB-E0983721C19C AT noqsi DOT com> <20151229094603 DOT 782092b57563336883546bfd AT gmail DOT com> <449C2A4A-814E-4858-ACB3-82807A80BE8A AT noqsi DOT com> <7C27D3F4-9CC2-46DB-BE88-77564F3FC0FC AT noqsi 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=UTF-8 Content-Transfer-Encoding: 8bit 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 > > And why gschem tries to understand slotting in the first place, and doesn't leave it for the netlister? > > I think that’s because the concept of forward annotation to an as-built schematic was not on the table when it was implemented. The developers thought that users would need to see pin numbers in the source schematics. I suppose there are many who will still want this even after we construct a good way to make as-built schematics. > > John Doty Noqsi Aerospace, Ltd. > http://www.noqsi.com/ > jpd AT noqsi DOT com I have been thinking about an annotation mechanism so that it possible to annotate decisions made later during design flow without changing the original schematics but it may also add confusion. Nicklas Karlsson