| www.delorie.com/archives/browse.cgi | search |
| X-Authentication-Warning: | delorie.com: mail set sender to geda-user-bounces using -f |
| X-Recipient: | geda-user AT delorie DOT com |
| X-IPAS-Result: | =?us-ascii?q?A2CBCACa06VY/wv01pZeHQEFAQsBg1FhgQmDC5xmlTOCDCq?= |
| =?us-ascii?q?FeAKCDEAXAQIBAQEBAQEBYihCEAGEHgEFJwsBOxsLGAkaCw8FGESJaw+yVDqLO?= | |
| =?us-ascii?q?wELASWLO4JbgVUHAQFngmiCMQWJB4Y/gUiKcYZwixqCCFOOOIgtimsgATaBACA?= | |
| =?us-ascii?q?UCCo9gg6CboFJPzWGdoEEDxeCFwEBAQ?= | |
| X-IronPort-AV: | E=Sophos;i="5.35,169,1484002800"; |
| d="scan'208";a="28685507" | |
| Date: | Thu, 16 Feb 2017 17:38:23 +0100 |
| From: | "Gabriel Paubert (paubert AT iram DOT es) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> |
| To: | geda-user AT delorie DOT com |
| Subject: | Re: tEDAx (was: Re: [geda-user] RFC: edacore - should we reboot it? |
| the EDA ecosystem) + help needed | |
| Message-ID: | <20170216163823.GA31909@visitor2.iram.es> |
| References: | <alpine DOT DEB DOT 2 DOT 00 DOT 1702130818300 DOT 7286 AT igor2priv> |
| <alpine DOT DEB DOT 2 DOT 00 DOT 1702160811400 DOT 7286 AT igor2priv> | |
| MIME-Version: | 1.0 |
| In-Reply-To: | <alpine.DEB.2.00.1702160811400.7286@igor2priv> |
| User-Agent: | Mutt/1.5.21 (2010-09-15) |
| 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 |
On Thu, Feb 16, 2017 at 08:22:38AM +0100, gedau AT igor2 DOT repo DOT hu wrote:
> Hi all,
>
> status update:
>
> On Mon, 13 Feb 2017, gedau AT igor2 DOT repo DOT hu wrote:
>
> >2. what's the minimum we'd need to do for a working "edacore" setup:
> >
> >http://repo.hu/projects/pcb-rnd/devlog/20170213_edacore1.html
>
> people have downloaded these docs from 40 unique IPs, but I got 0
> feedback - sort of "as expected".
>
> I contacted the edacore project, but it seems our vision totally
> differs, so we should just do two different projects.
>
> I also seeked some of the gEDA project leaders, hoping we could do
> this together, but I failed.
>
> So I started to do it alone, hoping that it would be useful and/or
> adapted by other projects (including, but _not_ limited to gEDA
> members). The cost was so low that even if it ends up just "yet
> another file format" only one tool uses, it's still not a big loss.
>
>
> The name is tEDAx - Trivial EDA eXchange. Focusing on
> trivial-to-implement file exchange for the common-minimum data.
> Project page and specificaitons: http://repo.hu/projects/tedax
>
>
> A hint on costs of adoption: I wrote the reference parser and a
> tEDAx netlist (schematics) importer plugin in pcb-rnd in about 70
> minutes total.
>
> Why should we care: short term I believe tEDAx can solve a serious
> design falw in our gschem* -> pcb* flow that I will describe in
> another mail in another thread.
Here TEDAX means: "Técnico Especialista en Desactivación de Artefactos
Explosivos". These are the people which are called for example when a
bomb from a previous war is found.
In English the more or less equivalent term is EOD (explosive ordnance
disposal).
What kind of bomb are you trying to prevent from exploding? :-)
[Yes, I deliberately refrained from entering the recent flamewars^W
discussions on this mailing list.]
Gabriel
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |