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 benefits of a toolkit
Date: Sun, 04 Oct 2015 04:09:04 +0200
Lines: 13
Message-ID: <muq1o0$5cu$1@ger.gmane.org>
References: <3719911A-C5F7-4603-B480-CA2542B6AE9A AT noqsi DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8Bit
X-Complaints-To: usenet AT ger DOT gmane DOT org
X-Gmane-NNTP-Posting-Host: a89-182-107-162.net-htp.de
User-Agent: KNode/4.14.1
Reply-To: geda-user AT delorie DOT com

John Doty wrote:

> But gEDA is a toolkit, not a tool, and it plays well with other
> toolkits. So, the answer I gave was “I generate the tables and the
> netlists automatically from the same design data.”

Your ability to do so is a consequence of the specific file format. 
This is not connected in any way to a tool vs tool kit dichotomy. 
These are orthogonal design decisions. A tool kit might save 
schematics in an impenetrable binary format. And an integrated EDA 
tool may save schematics in gschem format.

---<)kaimartin(>---