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 Subject: Re: [geda-user] New experimental netlist features Date: Sat, 05 Sep 2015 22:35:22 +0200 Lines: 50 Message-ID: References: <55E8773B DOT 9000902 AT jump-ing DOT de> <55E8831A DOT 8050307 AT jump-ing DOT de> <55E891FA DOT 2010509 AT jump-ing DOT de> <201509032030 DOT t83KU1Yq017045 AT envy DOT delorie DOT com> <55E97A3E DOT 2070402 AT jump-ing DOT de> <69B8B3F4-A6E4-43E9-9055-C63A5D6A3707 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-102-147.net-htp.de User-Agent: KNode/4.14.1 Reply-To: geda-user AT delorie DOT com John Doty wrote: > Why would they want gEDA over kiCAD? > Shouldn’t we be promoting our strengths? Unfortunately, strengths don't make a deal if there are show stopping weaknesses. Quick reminder (in no particular order): * the out-of-the-box library of symbols is barely usable * the out of the box library of footprints is quite frugal * user documentation is in a sad state * developer documentation is patchy at best * there is no windows install available from the projects website * there is no straight forward way to do simple simulations * there is no way to do blind and buried vias * there is no interaction with 3D CAD applications Traditionally, the other competitors in the low cost segment of EDA applications had similar, or even worse issues. But with kicad development gaining quite some momentum in recent years this has changed. > Gnetlist is the unique, powerful, core of gEDA. "unique" → now, that xorn arrived, gnetlist is obviously not unique anymore. (Well, it is unique in that it is probably the only scheme based netlister in the universe) "core" → a collection of tools contains no singular core (almost by definition). People successfully use geda without touching gnetlist at all. Not every work-flow is driven by schematics. "powerful" → buses are purely graphical → no way to pass parameters to sub sheets → no variables (think $AUTHOR, $DATE, $REVISION, ...) → no infrastructure to do back annotation > Why hide it away? What do you mean by "hide away"? This thread is not about hiding anything but to essentially replace a component with something that does the same job in a more clean way minus some of the above issues. And yes, the traditional netlister should stay in the project if only for the peace of mind. ---<)kaimartin(>---