Index: trunk/doc-rnd/intconn.html
===================================================================
--- trunk/doc-rnd/intconn.html (nonexistent)
+++ trunk/doc-rnd/intconn.html (revision 41)
@@ -0,0 +1,46 @@
+
+
+ pcb-rnd - the [intconn] patch
+
+There are parts with internal connections (e.g. pin 2 and 4 of a SO8
+package are internally connected). Vanilla PCB can not handle this,
+leaving the following options:
+
+ - connect both pins to the net from the schematics - this works if all the internally connected pins are required to connect to copper (common with GND or power pins) but is very inconvenient for signal pins where only one of them needs to be connected
+
- back-annotate which pin is connected - there's no easy back annotation
+
- one pin connected, the other is closer to the next target; PCB doesn't understand that they are alreayd connected internally; normally one shouldn't use the internal connection of a component instead of copper; except for the common practice to use 0 ohm SMD resistors for jumping wires
+
+
+The patch introduces a new pin flag intconn(g) which marks the pin
+to have internal connections in group g. If there
+are multiple pins using the same g value within a single element, they
+are internally connected. In other words, g is a group (or net name)
+within the element and pins can join to one of the numbered groups (or internal
+nets). The value of g shall be between 1 and 255, 0 means no internal
+connection (equivalent to the case when intconn(0) is omitted).
+
+When pin numbers are displayed (key 'd'), internal connection groups are
+written in square brackets, e.g. "2 [9]" means "pin 2, internally connected
+to group 9".
+
+
save/load and compatibility
+This patch introduces a new pin flag. In the following example
+pin 2 and 4 are connected internally as group 9, while pin 3
+does not have any internal connections:
+
+Pin[40000 60000 6000 3000 6600 2800 "2" "2" "square,intconn(9)"]
+Pin[40000 50000 6000 3000 6600 2800 "3" "3" "square"]
+Pin[40000 40000 6000 3000 6600 2800 "4" "4" "square,intconn(9)"]
+
+Vanilla PCB will load the design ignoring internal connections -
+this may introduce new rats.
+
+Vanilla PCB doesn't save intconn() and elements are embedded in the file -
+once the design is loaded and saved with vanilla PCB, internal connection
+info is lost.
+
+
plans
+No plans - this feature is fully implemented. There is no plan for implementing
+a gui, internal connections should be hand-edited into the element.
+
+
Index: trunk/doc-rnd/motivation.html
===================================================================
--- trunk/doc-rnd/motivation.html (revision 40)
+++ trunk/doc-rnd/motivation.html (revision 41)
@@ -23,6 +23,7 @@
communication requires web2.0
there are too many cycles of "please fix this and change that first"
with the chaos VCS, it's too likely that new feature patches would require ongoing maintenance to avoid that a large scale merge (or rebase, whatever) of another feature branch breaks it
+ there are too much pondering and too less prototyping; there are features that are being considered for years (for example back annotation, internal connections) with multiple concurrent ideas, but no code. Instead, I'd like to implement some code from the early phase of the idea, test it, and deprecate it if it didn't work out well.
I don't even dream about getting larger patches
no stable release for years; can't maintain a set of patches (like pcb-gpmi) and port them to new releases
@@ -48,7 +49,5 @@
merge pcb-gpmi; GPMI would be an optional addon, it'd probably stay a plugin, but there should not be a separate repo
-
-