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=jQvMhadUzoNKzayv9pdHAOm+ZvYqWuA946+7yevDvIo=; b=klBsyu9RorCFJS8KuzmkeNkdgaWWrWk3YRAfml3lIEttCIYRD1X3lcm44qboPeKP9y 9m14gJBWq9wHUYfCd43LB4kigx2bV8vCKkjKT2XYSufrDJlhkXdyLeUFb7a05Ofm1oiH FmERSMVEaoApkB4FRBarYv9zvVJiaIdfKnLpMN1Et2IzyNmHq/vZCz9wXsEBIcvCo4Jb zL/0hMlRr3HAr0V4ZYr4yXzej4kceCYuzbYZa+DjSskUbeDFqnHde96AfQK0T6YHbYap zBfKXBN7ZwwhAHgfDUEQrAjmdGZKzDnb88RPWkXm9K8cBQW18+CX8QXlKJ0k6ZFsmzBF CYYw== X-Received: by 10.28.147.203 with SMTP id v194mr69428141wmd.16.1451495007817; Wed, 30 Dec 2015 09:03:27 -0800 (PST) Date: Wed, 30 Dec 2015 18:03:26 +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: <20151230180326.8c9492d84034c1709b136b6d@gmail.com> In-Reply-To: <5683FC71.5080904@ecosensory.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> <5683FC71 DOT 5080904 AT ecosensory 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 > On 12/29/2015 10:17 PM, gedau AT igor2 DOT repo DOT hu wrote: > > why gschem doesn't ask the netlist infra? Or why the netlist engine doesn't generate an ".lst" (staying with the object example) > > gschem can read? And why gschem tries to understand slotting in the first place, and doesn't leave it for the netlister? > > I think a superset netlist to be output along with the normal "bare" netlist would be the best kind of "patch" for annotating > forward and back. > > It is the kind of thing that will let you extract parasitic capacitances and stats about your design. > It could be a way to more easily and cleanly separate out chunks of schematic and layout for reuse -- when they did not start out > as a module, but now are wanted to be modular. It could be really good. I think possibility to feed back data as an annotation to the schematic might be a possibity. In such case it would be possible to visualize choices made later in the design flow without changing the original schematic but it may also add confusion. It would be useful for slotting, pin swapping, pin mapping and of course electrical parameters calculated from layout. Nicklas Karlsson