Mail Archives: geda-user/2015/06/29/09:03:51
--089e0122a222896d330519a7b7a2
Content-Type: text/plain; charset=UTF-8
Experienced users can always roll their own footprints, but I feel that we
are likely to attract more new users if our footprint repositories runneth
over... otherwise I fear it will just be text editor wielding ascetics that
are tempted to take up gEDA/gaf.
My 2c worth.
Erich.
On Mon, Jun 29, 2015 at 10:02 PM, Stefan Salewski <mail AT ssalewski DOT de> wrote:
> On Mon, 2015-06-29 at 13:30 +0200, Jan Kasprzak wrote:
> > gedau AT igor2 DOT repo DOT hu wrote:
> > :
> >
> > It would be helpful to be able to denote attributes of the endpoints of
> nets,
> > such as "there would be high current flowing between these two
> endpoints",
> > so that in the PCB design phase I would know that some part of the net
> should
> > be drawn using thicker lines.
> >
>
> Yes -- we discussed that some years ago on this list. For gschem and my
> Peted clone we can already assign arbitrary attributes to net segments.
> For Peted I do intent to make that assignment "easy" -- maybe a special
> assignment mode where you simple click on a net segment and the
> corresponding attribute is assigned each. More difficult is inspection,
> we may want to see all nets with a assigned "power" attribute, but
> generally we do not want to pollute the schematic with hundreds of
> "power" text labels. Maybe we could have a list with all the attributes,
> and when we select an item in the list, all nets with that attribute are
> high lighted. Generally that net information should be transfered to
> PCB, so when we route a net manually in PCB, for power nets
> automatically a thick trace is used. I was told that old gnetlist did
> not transfer attributes to PCB unfortunately, but maybe the new python
> netlist generator may do it. Have you more concrete ideas how the whole
> process may work?
>
> > The barrier for using and enhancing the gedasymbols.org library should
> be
> > lowered
>
> OK, that is addressed to DJ and the other developers/maintainers. My
> personal impression is, that generally professional PCB developers
> hesitate to use symbols and footprints from foreign sources...
>
>
>
--089e0122a222896d330519a7b7a2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Experienced users can always roll their own footprint=
s, but I feel that we are likely to attract more new users if our footprint=
repositories runneth over... otherwise I fear it will just be text editor =
wielding ascetics that are tempted to take up gEDA/gaf.<br><br></div><div>M=
y 2c worth.<br><br></div><div>Erich.<br></div></div><div class=3D"gmail_ext=
ra"><br><div class=3D"gmail_quote">On Mon, Jun 29, 2015 at 10:02 PM, Stefan=
Salewski <span dir=3D"ltr"><<a href=3D"mailto:mail AT ssalewski DOT de" target=
=3D"_blank">mail AT ssalewski DOT de</a>></span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">On Mon, 2015-06-29 at 13:30 +0200, Jan Kasprzak wrote:<br>
> <a href=3D"mailto:gedau AT igor2 DOT repo DOT hu">gedau AT igor2 DOT repo DOT hu</a> wrote:<=
br>
> :<br>
<span class=3D"">><br>
> It would be helpful to be able to denote attributes of the endpoints o=
f nets,<br>
> such as "there would be high current flowing between these two en=
dpoints",<br>
> so that in the PCB design phase I would know that some part of the net=
should<br>
> be drawn using thicker lines.<br>
><br>
<br>
</span>Yes -- we discussed that some years ago on this list. For gschem and=
my<br>
Peted clone we can already assign arbitrary attributes to net segments.<br>
For Peted I do intent to make that assignment "easy" -- maybe a s=
pecial<br>
assignment mode where you simple click on a net segment and the<br>
corresponding attribute is assigned each. More difficult is inspection,<br>
we may want to see all nets with a assigned "power" attribute, bu=
t<br>
generally we do not want to pollute the schematic with hundreds of<br>
"power" text labels. Maybe we could have a list with all the attr=
ibutes,<br>
and when we select an item in the list, all nets with that attribute are<br=
>
high lighted. Generally that net information should be transfered to<br>
PCB, so when we route a net manually in PCB, for power nets<br>
automatically a thick trace is used. I was told that old gnetlist did<br>
not transfer attributes to PCB unfortunately, but maybe the new python<br>
netlist generator may do it. Have you more concrete ideas how the whole<br>
process may work?<br>
<span class=3D""><br>
> The barrier for using and enhancing the <a href=3D"http://gedasymbols.=
org" rel=3D"noreferrer" target=3D"_blank">gedasymbols.org</a> library shoul=
d be<br>
> lowered<br>
<br>
</span>OK, that is addressed to DJ and the other developers/maintainers. My=
<br>
personal impression is, that generally professional PCB developers<br>
hesitate to use symbols and footprints from foreign sources...<br>
<br>
<br>
</blockquote></div><br></div>
--089e0122a222896d330519a7b7a2--
- Raw text -