Mail Archives: geda-user/2012/12/17/04:16:50
--bcaec54d47667a1eb204d108d1b1
Content-Type: text/plain; charset=ISO-8859-1
On Sat, Dec 15, 2012 at 2:12 PM, Richard Barlow <richard AT richardbarlow DOT co DOT uk
> wrote:
> On Fri, 2012-12-14 at 10:29 +0100, Levente wrote:
> > I lost track of this thread, but I have an idea. I've seen this
> > implementation in Zuzken CR5000 Board designer. Each copper object had
> > an attribute called "net". When you place a track you could click on
> > an object to connect to. This way, there is no need to do any graphs,
> > etc. Just compare touching copper objects net attribute. If it is not
> > the same emit warning.
>
> A few weeks ago I had to layout a board using Eagle, due to the project
> already using Eagle. From my experience Eagle uses this method and I
> found it to be extremely annoying to use. For the most part it was fine,
> but the one thing that was very hard to do was place vias and then route
> traces to/from them. It's fine if you're placing a trace and switch
> layers; Eagle places a via and all the net attributes are correct.
> However this isn't that great a work-flow if you're laying out a very
> dense board, where you have to jiggle things around to get an wide bus
> onto another layer. Eagle complains continuously about nets being
> shorted.
>
> I also encountered other annoying situations caused by this manual
> assignment of net attributes to everything, where I found myself
> effectively managing the EDA's state for it, rather than getting on with
> the task in hand.
>
> I find PCB's method of tracking connectivity to be less constraining and
> allows for more varied work-flows. It's also closer to reality in that
> ultimately what matters is the actual connection between things, the
> copper doesn't care what net it belongs to. The only bad thing with
> PCB's method is the highlighting of shorts and it seems that it should
> be possible to preserve PCB's current behaviour while vastly improving
> this using some graph theory. If at all possible I think we should
> strive to keep the notion of copper being 'free' in PCB.
>
>
I find annoying PCB's method when you place a VIA. You are not allowed
connect wire to a newly placed VIA.
If only you could connect a floating object to any net, that would be some
advantage.
Levente
--bcaec54d47667a1eb204d108d1b1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<br><br><div class=3D"gmail_quote">On Sat, Dec 15, 2012 at 2:12 PM, Richard=
Barlow <span dir=3D"ltr"><<a href=3D"mailto:richard AT richardbarlow DOT co DOT uk=
" target=3D"_blank">richard AT richardbarlow DOT co DOT uk</a>></span> wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">
On Fri, 2012-12-14 at 10:29 +0100, Levente wrote:<br>
> I lost track of this thread, but I have an idea. I've seen this<br=
>
> implementation in Zuzken CR5000 Board designer. Each copper object had=
<br>
> an attribute called "net". When you place a track you could =
click on<br>
> an object to connect to. This way, there is no need to do any graphs,<=
br>
> etc. Just compare touching copper objects net attribute. If it is not<=
br>
> the same emit warning.<br>
<br>
A few weeks ago I had to layout a board using Eagle, due to the project<br>
already using Eagle. From my experience Eagle uses this method and I<br>
found it to be extremely annoying to use. For the most part it was fine,<br=
>
but the one thing that was very hard to do was place vias and then route<br=
>
traces to/from them. It's fine if you're placing a trace and switch=
<br>
layers; Eagle places a via and all the net attributes are correct.<br>
However this isn't that great a work-flow if you're laying out a ve=
ry<br>
dense board, where you have to jiggle things around to get an wide bus<br>
onto another layer. Eagle complains continuously about nets being<br>
shorted.<br>
<br>
I also encountered other annoying situations caused by this manual<br>
assignment of net attributes to everything, where I found myself<br>
effectively managing the EDA's state for it, rather than getting on wit=
h<br>
the task in hand.<br>
<br>
I find PCB's method of tracking connectivity to be less constraining an=
d<br>
allows for more varied work-flows. It's also closer to reality in that<=
br>
ultimately what matters is the actual connection between things, the<br>
copper doesn't care what net it belongs to. The only bad thing with<br>
PCB's method is the highlighting of shorts and it seems that it should<=
br>
be possible to preserve PCB's current behaviour while vastly improving<=
br>
this using some graph theory. If at all possible I think we should<br>
strive to keep the notion of copper being 'free' in PCB.<br>
<br></blockquote><div><br>I find annoying PCB's
method when you place a VIA. You are not allowed connect wire to a=20
newly placed VIA.<br><br>If only you could connect a floating object to any=
=20
net, that would be some advantage.<br><br>Levente<br>=A0</div><br></div><br=
>
--bcaec54d47667a1eb204d108d1b1--
- Raw text -