from donrob: jumper wires need pads and holes

[GoogleCodeExporter]

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

Please use labels and text to provide additional information.

Original issue reported on code.google.com by irasc...@gmail.com on 11 Mar 2009 at 4:16

[GoogleCodeExporter]

implement this as either a part with two footprints, where the footprints can 
be moved 
independently, or as a wire with ends and no middle.  During autorouting, as a 
last 
step, the autorouter finds a space to put the pads for the jumper, and connects 
each 
pad to the appropriate connector with a short trace wire.

Original comment by irasc...@gmail.com on 24 Aug 2009 at 11:04

[GoogleCodeExporter]

This is now implemented as a part with two independently movable footprints.  
The todo list is still large however, and there is 
one difficult issue that needs to be resolved:  when you drag a jumper from the 
parts bin and drop it into a sketch in PCB view, 
what, if anything, should happen in the other views? Where this becomes 
especially tricky is when the jumper ends are connected 
to other parts.  

One thought is that a jumper is essentially a bus on a breadboard, so that as 
parts become connected via jumper, we add 
connections (and a breadboard, if necessary) to a breadboard in breadboard 
view.  This is consistent with what we do now.  But it 
also gets us into a consistent kind of trouble, which is that it creates a mess 
in the other views.  

Possibly good news is that it may be clearer what happens in the other views 
when you delete a jumper in PCB view...

Original comment by irasc...@gmail.com on 21 Sep 2009 at 6:29

• Changed state: Started

[GoogleCodeExporter]

the rest of the todo list:

-- save, load, undo (tedious but straightforward)

-- jumperItems instead of jumper wires in the autorouter (tricky because we 
have to find space for the footprints)

-- replacing jumper wires with jumper parts throughout fritzing

Original comment by irasc...@gmail.com on 21 Sep 2009 at 6:33

[GoogleCodeExporter]

in terms of ui, what happens if the autorouter can't find room for jumper pads. 
Here 
are a couple of ideas:

1.  fall back to using a jumper wire.  The good news is that it already works.  
The bad 
news is that it complicates the code to have both JumperItems and Jumper wires 
(and may 
also confuse the user).

2.  place the pads somewhere and tell the user to move them manually.

Original comment by irasc...@gmail.com on 22 Sep 2009 at 6:50

[GoogleCodeExporter]

r3590: closing issue, and opening a new one for jumper wires

Original comment by irasc...@gmail.com on 22 Oct 2009 at 4:56

• Changed state: Fixed