X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Sun, 12 Feb 2017 04:36:08 +0100 (CET)
X-X-Sender: igor2 AT igor2priv
To: "Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From: gedau AT igor2 DOT repo DOT hu
Subject: Re: [geda-user] Announcement - openaltium release + edacore
In-Reply-To: <CAJXU7q_h9+g4FzQYGH1xgUzJtG=++fFgeA851DVX2b5xo9zM8A@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1702120424560.7286@igor2priv>
References: <CAJXU7q-VqAGYeheVBON8+TdwsM84rq1z2bKoi_S-0Sax49W-Zw AT mail DOT gmail DOT com> <20170211174559 DOT GM21523 AT foo DOT stuge DOT se> <CAJXU7q_h9+g4FzQYGH1xgUzJtG=++fFgeA851DVX2b5xo9zM8A AT mail DOT gmail DOT com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="0-436087724-1486870568=:7286"
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

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-436087724-1486870568=:7286
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE



On Sat, 11 Feb 2017, Peter Clifton (petercjclifton AT googlemail DOT com) [via ged=
a-user AT delorie DOT com] wrote:

>
>On 11 February 2017 at 17:45, Peter Stuge (peter AT stuge DOT se) [via
>geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
>=C2=A0
>      > I don't have a huge amount of time to work on this - so I'm
>      putting it
>      > out there as is in the hope it is useful to others.
>
>      Are you saying that you don't really have time and/or desire to
>      actually maintain this library and are primarily publishing a
>      code drop for others to potentially do further work with?
>
>
>Sadly, that is probably a fair characterization. Time is real limiting
>factor at the moment.
>
>I know there are people looking into file translation - and I released it =
in
>the hope it would be useful. If anyone wants to contribute, that would als=
o
>be cool.

Thank you, it will become relevant for pcb-rnd soon, maybe even this year.=
=20
We are working EDA interoperability happen by implementing importers and=20
exporters to other EDA tools.

>
>Something you can use in edacore?

Reminds me, we could write pcb-rnd import/export code to edacore formats=20
too, but I couldn't find any documentation on that. Is that project still=
=20
alive?

If yes, can someone please post an URL to file format specs?

If not, is there still developer interest behind edacore? Could we=20
rethink/reroute the project a bit? I have some ideas that could make some=
=20
parts work, and could yield some result even short term. (Yes, this=20
means I may also be offering some of my development time if the ideas=20
are accepted and I see it triggering other developers to activate too.)

Regards,

Igor2

--0-436087724-1486870568=:7286--