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=20161025;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
        bh=Fj2XhjR19zeR3GMTCwIwBFLwOvvVcbvEbLckp/G/oZA=;
        b=CFcrPJrafoqD006ANpVv4GaYgRMwgeUlnGLeofK/wvAGeM+52cvDik25MAsijHp2LU
         1e3VwbBMlYj3A8tD1XwqcQvW5TR/DgOunbzdO2FmxKh6E7n6esLD3ugwH+GQquF+AX3T
         sNtP9SrcwCZwz8QrJJbNBykh1E621Md7mRePpPYLDn0Mpe60ndqS6cd1tQ6ceeiyxhfO
         rWWeZJIs79zVZbfX48SxT6wTc8HlidAaWt0O3UgMafN0s1RVk8WED+8EM0zhp1hYzP//
         bkpSrCPkcbUSatlN2ONIk1KXIgUu3oZUkShKb2SzwK2OaMRv6Lv4ZVKLEtJXlFUqtwft
         waRg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to;
        bh=Fj2XhjR19zeR3GMTCwIwBFLwOvvVcbvEbLckp/G/oZA=;
        b=auf26FsijyjBgQwuN6FvIeFkMnUtOVlrptKUY6fTNEhCknlAtPA8f1vwPnqt/xdQbZ
         Ibf+krxnsbra1Kuwrofv6gQZaTPOlLZSFZ5ozVCV5HZL28RhJ4tccTBMEUT9zciYlx8h
         eT/7rWcxd7eqh/fPhByZtt6Pv3EHbwRAO3Sb+nJFXN7gdqZf56A+3KxIawsPam/vXPBL
         suBEZOizEx80Z8nvK6+hvEOXqNPy3BkR3aO11vD/So/fgEqrgupn1Gz2RUlR8PkePWuA
         U9jbGqYMq0+MgZa+vjFWZjAWYIL+7e7+6Ds6OA2f479sr6opwSfzsMFFl9pfd28AheiY
         Spaw==
X-Gm-Message-State: AOAM531vVnmnKQWkV1U3XdIFGt+aRG//BY/zFXBpGNXLXyEaqnLeIQKU
	OFhwiGOcVI9LGcyiRHCk7rzQGO6uhAkdFPmsV3GRPWlG
X-Google-Smtp-Source: ABdhPJzsGErmppbE6D80EN2xjazyiN71LN+YBVVSNuxFiOS1ung3JOG/eq9xS//ULV00MS7b9KUfOJy7E7IeyokP7NA=
X-Received: by 2002:a05:651c:1ac:: with SMTP id c12mr9052463ljn.179.1626265433151;
 Wed, 14 Jul 2021 05:23:53 -0700 (PDT)
MIME-Version: 1.0
References: <9f6960b4-e3e7-7a99-7617-77e51e6bee4c AT xs4all DOT nl> <b2eb7bb5-4682-3c34-3d25-8caaa34e4a75 AT xs4all DOT nl>
In-Reply-To: <b2eb7bb5-4682-3c34-3d25-8caaa34e4a75@xs4all.nl>
From: "Erich Heinzle (a1039181 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Date: Wed, 14 Jul 2021 21:53:39 +0930
Message-ID: <CAHUm0tMHrKT33JfQ7KjmcgZUcCesg+y9LW5m5PSm=KijgUbybQ@mail.gmail.com>
Subject: Re: [geda-user] file format cooperation
To: geda-user <geda-user AT delorie DOT com>
Content-Type: multipart/alternative; boundary="000000000000741d6e05c7146dca"
Reply-To: geda-user AT delorie DOT com

--000000000000741d6e05c7146dca
Content-Type: text/plain; charset="UTF-8"

It should be noted that pcb-rnd can import and export in gEDA PCB format
(and kicad XML, eagle xml, eagle binary, protel autotrax...), it's just
that you inevitably lose features by exporting like this because PCB's (and
kicad's, protel's, eagle's) data model(s) is(are) a subset of pcb-rnd's.

I have two separate exporters in inkscape2pcb for this reason, one that
exports to gEDA PCB .fp format, and the other to pcb-rnd .lht format, which
natively allows polygons within footprints, arcs, and text, along with any
other feature you find on a layout.

I think the lesson is that you need a save file format that can adequately
express the feature set being used on a board, rather than having the
feature set used on the board being constrained by the save file format.

My two cents worth.

Erich


> pcb has spawned a clone (2014-ish) with an entirely different native
> file format, I won't call that a "vendor lock" in though, it's
> effectively preventing users to swap applications "on the fly", and we
> can learn from this.
>
>
>
>

--000000000000741d6e05c7146dca
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div class=3D"gmail_quote" dir=3D"auto"><div dir=3D"ltr" =
class=3D"gmail_attr">It should be noted that pcb-rnd can import and export =
in gEDA PCB format (and kicad XML, eagle xml, eagle binary, protel autotrax=
...), it&#39;s just that you inevitably lose features by exporting like thi=
s because PCB&#39;s (and kicad&#39;s, protel&#39;s, eagle&#39;s) data model=
(s) is(are) a subset of pcb-rnd&#39;s.</div><div dir=3D"ltr" class=3D"gmail=
_attr"><br></div><div dir=3D"ltr" class=3D"gmail_attr">I have two separate =
exporters in inkscape2pcb for this reason, one that exports to gEDA PCB .fp=
 format, and the other to pcb-rnd .lht format, which natively allows polygo=
ns within footprints, arcs, and text, along with any other feature you find=
 on a layout.</div><div dir=3D"ltr" class=3D"gmail_attr"><br></div><div dir=
=3D"ltr" class=3D"gmail_attr">I think the lesson is that you need a save fi=
le format that can adequately express the feature set being used on a board=
, rather than having the feature set used on the board being constrained by=
 the save file format.</div><div dir=3D"ltr" class=3D"gmail_attr"><br></div=
><div dir=3D"ltr" class=3D"gmail_attr">My two cents worth.</div><div dir=3D=
"ltr" class=3D"gmail_attr"><br></div><div dir=3D"ltr" class=3D"gmail_attr">=
Erich</div><div dir=3D"ltr" class=3D"gmail_attr"><br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">
<br>
pcb has spawned a clone (2014-ish) with an entirely different native <br>
file format, I won&#39;t call that a &quot;vendor lock&quot; in though, it&=
#39;s <br>
effectively preventing users to swap applications &quot;on the fly&quot;, a=
nd we <br>
can learn from this.<br>
<br>
</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><br></blockquote><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex"><br></blockquote></div></div>

--000000000000741d6e05c7146dca--