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=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=15YBb5EKF/FLqUM6ocD5SIJidonR95hD1u2c/Vqy8u4=; b=sb3p7nYId/okzD+JNML6YXMCA+MPr01ABFQ1hOMTSaeelGOA53oQBcr22Uhs4Hr2l5 i9ZS9TQibdQR5UHXkclrRJ/BYZzoUS4T2F6DkJthbaNNdWVO0wL/eTHVp4C9H18uUgwQ gHs/ThxcLNuL5PY6rfCnttr6xuW7gOJWra2MwrsDTcB+O67buoLCQfUDPn34GBkUC3Ol J88YgF6LYQFlyHry+Z+hAPNcafzSvZ8KQ4aBVzni4dTlEPJYWp2MlTpq8x/mk4m4nh6R vnVbwQUriMHXbuONaOv6PR3miz8WIZy5FRpCn4tOJUXRQ8iG8TmNepRuXGFOXJfspLnK J/5w== MIME-Version: 1.0 X-Received: by 10.194.6.98 with SMTP id z2mr108962504wjz.101.1452127280360; Wed, 06 Jan 2016 16:41:20 -0800 (PST) In-Reply-To: References: <1512221837 DOT AA25291 AT ivan DOT Harhan DOT ORG> <20160105182120 DOT 3237F809D79B AT turkos DOT aspodata DOT se> <8E0210CD-0694-4717-A7B1-3224E39691DA AT sbcglobal DOT net> <20160106095351 DOT 410e3f2407176052d835251e AT gmail DOT com> <20160107004041 DOT 8812ea2779c265f6d827d39a AT gmail DOT com> Date: Wed, 6 Jan 2016 15:41:20 -0900 Message-ID: Subject: Re: [geda-user] A fileformat library From: "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=047d7b5d3e64b6f63d0528b3ba2a 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 --047d7b5d3e64b6f63d0528b3ba2a Content-Type: text/plain; charset=UTF-8 On Wed, Jan 6, 2016 at 12:10 AM, wrote: > Britton: > > The last time we discussed this, there was some semblance of a consensus > > that we could use YAML or JSON as a text format, with possible > translation > > to sqlite for a binary format. > > There is much discussion on this list that amounts to "talk but no > code". > True. I think what happened is no one took it seriously so there was no objection at the time. I did mention my intentions back then though, and Lev also. > It is not interesting to participate in all thoose threads, sorry. > Understandable. > And even if you shows us the code, it's no free ride either. > Example e.g. pcb-rnd and xorn. > So to be blunt, the healthy route is to code what you need yourself. > Given the discussion yesterday this is pretty much what I've concluded. My new plan is to just add export in a format the script languages can pick up (probably YAML), and probably the ability to read it when I start needing that. It won't be god's chosen file format for pcb and no one should have any big reason to care. Britton --047d7b5d3e64b6f63d0528b3ba2a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Wed, Jan 6, 2016 at 12:10 AM, <karl AT aspodata DOT se> wrot= e:
Britton:
> The last time we discussed this, there was some semblance of a consens= us
> that we could use YAML or JSON as a text format, with possible transla= tion
> to sqlite for a binary format.

There is much discussion on this list that amounts to "talk but no
code".

True.=C2=A0 I think what ha= ppened is no one took it seriously so there was no objection at the time.= =C2=A0 I did mention my intentions back then though, and Lev also.
=C2=A0
It is not interesting to participate in all thoose threads, sorry.

Understandable.
=C2=A0
And even if you shows us the code, it's no free ride either.
Example e.g. pcb-rnd and xorn.=C2=A0

So to be blunt, the healthy route is to code what you need yourself.

Given the discussion yesterday this is pretty= much what I've concluded.=C2=A0 My new plan is to just add export in a= format the script languages can pick up (probably YAML), and probably the = ability to read it when I start needing that.=C2=A0 It won't be god'= ;s chosen file format for pcb and no one should have any big reason to care= .
=C2=A0
Britton

--047d7b5d3e64b6f63d0528b3ba2a--