Mail Archives: geda-user/2019/01/30/10:13:37
--Apple-Mail=_3338C1A7-BC50-4263-8F8E-EB6CA5EC3DEC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
> On Jan 30, 2019, at 8:27 AM, Roland Lutz <rlutz AT hedmen DOT org> wrote:
>=20
> I always wondered about this mechanic. As far as gEDA/gaf is =
concerned, only components which share a common refdes are part of one =
package, so U1a, U1b etc. are individual packages. Any logic that =
deviates from this would be specific to PCB and/or gsch2pcb.
Remember, pcb existed before gEDA, and Ales designed gEDA to support =
*any* downstream flow, not just pcb. This is a place where core gEDA =
conventions don=E2=80=99t quite match the conventions of the downstream =
tool. For other flows, the back end manages the mismatch, sometimes with =
the help of additional attributes. For example, the =E2=80=9Cpins=E2=80=9D=
attribute in some library symbols is there to support Allegro. The pcb =
flow didn=E2=80=99t get this kind of attention. It appears that nobody =
on the gEDA side anticipated the situation where pcb would become the =
most popular downstream tool, and nobody on the pcb side wanted to step =
up and do the Scheme coding at the interface.
So, we have a three way fork, with pcb-rnd centered on repairing the =
architecture of pcb, but with its own schematic capture, and gEDA =
becoming a pcb-centric tool, no longer much of a kit. Neither of these =
forks seems focused on maintaining the flexibility of gEDA as a primary =
goal: Lepton is keeping that dream alive.
John Doty Noqsi Aerospace, Ltd.
jpd AT noqsi DOT com
--Apple-Mail=_3338C1A7-BC50-4263-8F8E-EB6CA5EC3DEC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Jan 30, 2019, at 8:27 AM, Roland Lutz <<a =
href=3D"mailto:rlutz AT hedmen DOT org" class=3D"">rlutz AT hedmen DOT org</a>> =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">I always wondered about this =
mechanic. As far as gEDA/gaf is concerned, only components which =
share a common refdes are part of one package, so U1a, U1b etc. are =
individual packages. Any logic that deviates from this would be =
specific to PCB and/or gsch2pcb.</span></div></blockquote><br =
class=3D""></div><div>Remember, pcb existed before gEDA, and Ales =
designed gEDA to support *any* downstream flow, not just pcb. This is a =
place where core gEDA conventions don=E2=80=99t quite match the =
conventions of the downstream tool. For other flows, the back end =
manages the mismatch, sometimes with the help of additional attributes. =
For example, the =E2=80=9Cpins=E2=80=9D attribute in some library =
symbols is there to support Allegro. The pcb flow didn=E2=80=99t get =
this kind of attention. It appears that nobody on the gEDA side =
anticipated the situation where pcb would become the most popular =
downstream tool, and nobody on the pcb side wanted to step up and do the =
Scheme coding at the interface.</div><div class=3D""><br =
class=3D""></div>So, we have a three way fork, with pcb-rnd centered on =
repairing the architecture of pcb, but with its own schematic capture, =
and gEDA becoming a pcb-centric tool, no longer much of a kit. Neither =
of these forks seems focused on maintaining the flexibility of gEDA as a =
primary goal: Lepton is keeping that dream alive.<div class=3D""><br =
class=3D""><div class=3D"">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-caps: normal; font-variant-east-asian: normal; =
font-variant-position: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><div =
style=3D"word-wrap: break-word;" class=3D""><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-caps: normal; font-variant-east-asian: normal; =
font-variant-position: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><p =
style=3D"margin: 0px;" class=3D""><font face=3D"Helvetica" size=3D"3" =
style=3D"font-style: normal; font-variant-caps: normal; font-weight: =
normal; font-size: 12px; line-height: normal; font-family: Helvetica;" =
class=3D"">John Doty<span class=3D"Apple-converted-space"> =
<span =
class=3D"Apple-converted-space"> </span><span =
class=3D"Apple-converted-tab"> <span =
class=3D"Apple-converted-space"> </span></span></span>Noqsi =
Aerospace, Ltd.</font></p><p style=3D"margin: 0px;" class=3D""><a =
href=3D"mailto:jpd AT noqsi DOT com" class=3D"">jpd AT noqsi DOT com</a></p><br =
class=3D"Apple-interchange-newline"></span></div></span><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></body></html>=
--Apple-Mail=_3338C1A7-BC50-4263-8F8E-EB6CA5EC3DEC--
- Raw text -