Index: trunk/doc/design/07_devmap.html
===================================================================
--- trunk/doc/design/07_devmap.html	(revision 277)
+++ trunk/doc/design/07_devmap.html	(revision 278)
@@ -13,7 +13,7 @@
 	     footprint or simulation model (problem known as "slotting")
 </ul>
 
-<p>{des7:0}
+<p>{des7:1}
 These goals are achieved by using symbolic terminal names (instead
 of "pin numbers") in the schematic symbols and auxiliary data to translate
 the terminal names into port numbers. The following diagram demonstrates
@@ -21,7 +21,7 @@
 
 <p><img src="07_diag.svg">
 
-<p>{des7:0}
+<p>{des7:2}
 The device mapper has three major features: slotting name translation
 (red), device mapping (green) and pin mapping (blue). The slotting translation
 makes sure the resulting abstract component has the right amount of ports;
@@ -29,7 +29,7 @@
 attributes from a database; the pin mapper applies a pin numbers from
 a table (the table typically set up by the device mapper).
 
-<p>{des7:0}
+<p>{des7:3}
 The device mapper is an optional mechanism implemented in a plugin. The
 user may choose to use it or to:
 <ul>
@@ -43,17 +43,17 @@
 	     that would introduce a <i>pinmap</i> attribute
 </ul>
 
-<p>{des7:0}
+<p>{des7:4}
 It is possible to use features of this plugin selectively and/or replace
 some or all features using another plugin.
 
 <h2> 7.1. Slot prefixing </h2>
 
-<p>{des7:0}
+<p>{des7:5}
 Devmap registers for the <a href="02_data#des2:77">terminal-name-to-port-name
 translation</a>.
 
-<p>{des7:0}
+<p>{des7:6}
 If the <i>slot</i> attribute presents in a symbol, and the terminal does
 not have the "noslot" attribute, the translation is activated. The slot
 name is taken directly from the concrete symbol's <i>slot</i> attribute.
@@ -61,11 +61,11 @@
 attribute is then removed from the abstract component to avoid
 collisions.
 
-<p>{des7:0}
+<p>{des7:7}
 Typical example: common opamp symbol:
-<p>{des7:0}
+<p>{des7:8}
 <p><table border=1 cellspacing=0>
-<tr><th colspan=3 bgcolor="#aaaaaa"> {des7:0} example opamp terminal attributes
+<tr><th colspan=3 bgcolor="#aaaaaa"> {des7:9} example opamp terminal attributes
 <tr><th> name       <th> noslot                <th> terminal description
 <tr><td> in_plus    <td> (not present)         <td> positive input pin
 <tr><td> in_minus   <td> (not present)         <td> negative input pin
@@ -74,7 +74,7 @@
 <tr><td> v_minus    <td> "yes"                 <td> negative power rail
 </table>
 
-<p>{des7:0}
+<p>{des7:10}
 In the above example v_plus and v_minus are never prefixed with "slot/" because
 of their noslot attribute. In case the symbol is used with the slot attribute
 set, this means:
@@ -85,7 +85,7 @@
 	     exist in the abstract component
 </ul>
 
-<p>{des7:0}
+<p>{des7:11}
 Note: when the same symbol is used in a non-slotted use case, the symbol will
 not have the "slot" attribute; in this case no terminal name translation
 applied and the resulting abstract component will have the same port names
@@ -94,7 +94,7 @@
 
 <h2> 7.2. Pin mapping </h2>
 
-<p>{des7:0}
+<p>{des7:12}
 Pin mapping takes a map between the symbolic description  and emits the
 physical description (port numbers for a footprint or sim model). There
 shall be one such mapping per abstract component. If multiple symbols
@@ -102,7 +102,7 @@
 keep only one of the arrays.
 
 
-<p>{des7:0}
+<p>{des7:13}
 The input is a array is an unordered list of (terminal name + slot name)
 -&gt; (attribute_name + value) pairs, each specified in the following syntax:
 <pre>
@@ -109,17 +109,17 @@
 slot/termname -&gt; attribkey=value
 </pre>
 
-<p>{des7:0} E.g. "A/out -&gt; pcb/pin=1" means "terminal with 
+<p>{des7:14} E.g. "A/out -&gt; pcb/pin=1" means "terminal with 
 <i>name=out</i> in symbol tagged as <i>slot=A</i> shall get attribute
 <i>pcb/pin</i> set to <i>1</i>".
 
 
-<p>{des7:0}
+<p>{des7:15}
 If a slot/terminal pair is not found in the map, an error message is
 emitted. This happens when the schematics symbol uses a terminal that
 has no physical pin with the given device.
 
-<p>{des7:0}
+<p>{des7:16}
 If a slot/terminal pair of the map is not used in the mapping, no error
 is generated. A typical example when this happens is when a logic circuit
 has 4 identical slots but the schematics uses only 3. If this is considered
@@ -126,9 +126,9 @@
 an error, a DRC plugin shall check for it.
 
 
-<p>{des7:0}
+<p>{des7:17}
 <p><table border=1 cellspacing=0>
-<tr><th colspan=3 bgcolor="#aaaaaa"> {des7:0} pin mapping related symbol attributes
+<tr><th colspan=3 bgcolor="#aaaaaa"> {des7:18} pin mapping related symbol attributes
 <tr><th> attribute <th> value                <th> description
 <tr><td> pinmap    <td> array of map entries <td> the actual map, as described in TODO
 <tr><td> slot      <td> slot name            <td> textual name of the slot the symbol provides
@@ -136,24 +136,24 @@
 
 <h2> 7.3. Device mapping </h2>
 
-<p>{des7:0}
+<p>{des7:19}
 The device mapper takes the <i>devmap</i> attribute of a symbol and looks it up
 in a database for finding a device map file. If the devmap attribute is an
 array, each devmap file is looked up and applied, in order of appearance.
 
-<p>{des7:0}
+<p>{des7:20}
 A device map file is a simple list of cschem attributes. The device mapper
 takes each attribute from the device map file and apply it on the symbol that
 had the devmap attribute.
 
-<p>{des7:0}
+<p>{des7:21}
 A common device map file will usually have a pinmap attribute that will
 set at least one attributes on each terminal.
 
 
-<p>{des7:0}
+<p>{des7:22}
 <p><table border=1 cellspacing=0>
-<tr><th colspan=3 bgcolor="#aaaaaa"> {des7:0} device mapping related symbol attributes
+<tr><th colspan=3 bgcolor="#aaaaaa"> {des7:23} device mapping related symbol attributes
 <tr><th> attribute <th> value  <th> description
 <tr><td> devmap    <td> name   <td> name of the devmap file to use
 </table>
Index: trunk/doc/design/07_devmap_imp.html
===================================================================
--- trunk/doc/design/07_devmap_imp.html	(revision 277)
+++ trunk/doc/design/07_devmap_imp.html	(revision 278)
@@ -12,13 +12,13 @@
 is especially annoying when the same symbol is to be used with signal
 (sot23) and power (to220) transistors.
 
-<p>{imp7:0}
+<p>{imp7:1}
 Classic solution 'A' is simply having different, heavy symbols for each
 footprint. This approach has the obvious problem that replacing the
 footprint means replacing the symbol as well and that symbol needs
 to be copied for each footprint variant.
 
-<p>{imp7:0}
+<p>{imp7:2}
 A less obvious problem is that the symbol-&lt;pcb-footprint mapping is
 only one aspect, for one workflow (f1). If there's another flow (f2) that
 may also have different mappings for the same symbol, multiple
@@ -25,7 +25,7 @@
 combinations of f1+f2 mappings. This easily leads to an explosion of heavy
 symbols even for the very same device.
 
-<p>{imp7:0}
+<p>{imp7:3}
 Classic solution 'B' is to craft the footprint to match the symbol. This
 means there's no sot23 footprint, but a sot23-2n7002 footprint. In other
 words, the same sot23 footprint is copied over and over with only pin numbering
@@ -35,7 +35,7 @@
 the different requirements, this method requires 3 or 4 time clones of
 many footprint specific sot23 footprints.
 
-<p>{imp7:0}
+<p>{imp7:4}
 While both of the above solutions would work with cschem, it is recommended
 to use the devmap mechanism instead. For the 2n7002-in-sot23 example, the devmap
 would mean:
@@ -58,7 +58,7 @@
 
 <h3> 7.1.2 SPICE example </h2>
 
-<p>{imp7:0}
+<p>{imp7:5}
 The same example for SPICE simulation works the same way, except the devmap
 file would set <i>spice/model=M</i> and a different <i>pinmap<i> array:
 <pre>
@@ -66,7 +66,7 @@
 
 <h2> 7.3. Combining the two </h2>
 
-<p>{imp7:0}
+<p>{imp7:6}
 A schematics can be the source of multiple workflows, e.g. both simulation
 and PCB layout. An easy way to specify the device mapping for multiple flows is to
 include them all in the same devmap file. The resulting file would set all
@@ -80,7 +80,7 @@
 D->spice/pin=1
 </pre>
 
-<p>{imp7:0}
+<p>{imp7:7}
 However, this again creates bad coupling: for PCB, the devmap file name
 includes the footprint, because that makes the actual binding between the
 generic symbol and generic footprint. This mean there would be a different
@@ -87,7 +87,7 @@
 devmap file for the same MOSFET part coming in a to92 package. Yet, the spice
 model attribute and pin mapping would be copied into both.
 
-<p>{imp7:0}
+<p>{imp7:8}
 A better way is to have a pcb-only devmap file called "2n7002_sot23" and a
 SPICE specific devmap file called "2n7002_spice". The devmap attribute of
 the generic MOSFET symbol placed for the device can be an array, listing both
@@ -96,7 +96,7 @@
 
 <h2> 7.2. Slotting </h2>
 
-<p>{imp7:0}
+<p>{imp7:9}
 Slotting works by the <i>slot</i> slot attribute. Each entry of the <i>pinmap</i>
 attribute may contain a slot reference on the left side. When present, it
 limits the use of the entry to symbols with matching slot name. This allows
@@ -103,7 +103,7 @@
 assignment of the same terminal names multiple times, to different physical
 pin numbers, depending on the slot attribute.
 
-<p>{imp7:0}
+<p>{imp7:10}
 For example the PCB devmap for common (TODO: link) dual opamp in a 8 pin package, using
 slots 'A' and 'B':
 <pre>
@@ -117,7 +117,7 @@
 v_minus -&gt; pcb/pin=4
 </pre>
 
-<p>{imp7:0}
+<p>{imp7:11}
 When both slots are present, using this pinmap will produce the following
 port names in the resulting abstract model component: A/out, A/in_mius,
 A/in_plus, B/out, B/in_minus, B/in_plus, v_plus, v_minus. If slot A is
@@ -124,7 +124,7 @@
 missing from the schematics, only B/out, B/in_minus, B/in_plus, v_plus,
 v_minus are added in the abstract model.
 
-<p>{imp7:0}
+<p>{imp7:12}
 Note how v_plus and v_minus are specified to match universally, regardless
 of the slot. This allows a symbol where both instances have v_plus and v_minus
 terminals, but also allows a separate "opamp power" symbol with an arbitrary
@@ -132,7 +132,7 @@
 not prefixed with A/ or B/ because they had the noslot attribute (in the
 terminal).
 
-<p>{imp7:0}
+<p>{imp7:13}
 The resulting devmap file could be called "lm358_dip8", "lm358_so8" (and
 can set attribute <i>device=lm358</i> on the resulting component). But
 this pinout is a de-facto standard for dual ompamps in 8 pin packages, so
@@ -140,7 +140,7 @@
 "opamp2_any8" - but in this case the <i>device=lm358</i> can not be part
 of the devmap file.
 
-<p>{imp7:0}
+<p>{imp7:14}
 Note that this leads to the same heavy vs. light symbol consideration,
 applied to devmap files now. Cschem supports both approaches, it is up
 to the user to decide whether heavy or light devmap files should be used
@@ -150,13 +150,13 @@
 
 <h3> 7.3.1. Device map </h3>
 
-<p>{imp7:0}
+<p>{imp7:15}
 Option A: do the same as in gschem: manually set "pin numbers" and all
 attributes specific to footprints and simulation. This obviously reproduces
 the transistor problem, easily resulting in mismatched footprints. It also
 reproduces the heavy vs. light symbol problem.
 
-<p>{imp7:0}
+<p>{imp7:16}
 Option B: instead of filling in the footprint attribute, fill in the
 devmap attribute. Instead of saying it is a "footprint=sot23" (and maybe
 adding a device=2n7002 or value=2n7002), say it is a "devmap=2n7002_sot23".
@@ -166,24 +166,24 @@
 
 <h3> 7.3.2. Slotting </h3>
 
-<p>{imp7:0}
+<p>{imp7:17}
 Instead of the slotdef attribute, use the devmap attribute that is
 pointing to a slotted devmap file. Using the slot attribute is the same,
 except the value of the slot attribute doesn't have to be an integer
 but can be text, e.g. "power", "gpio", "i2c".
 
-<p>{imp7:0}
+<p>{imp7:18}
 Instead of the somewhat cryptic slotdef attribute, the devmap file contains
 a more readable table of pin assignment.
 
 <h2> 7.4. How it is displayed on the UI? </h2>
 
-<p>{imp7:0}
+<p>{imp7:19}
 After devmap or pinmap runs, the resulting attributes are available in the
 abstract model. Cschem can trace the connection between the concrete
 model's schematics symbol/terminal and the abstract model's component/port.
 
-<p>{imp7:0}
+<p>{imp7:20}
 Using this connection, a plugin in turn can take the resulting pcb/pin or
 spice/pin attribute from the abstract model and display it at any terminal
 on the schematics that contributed to it. Whether pcb/pin or spice/pin is
@@ -190,7 +190,7 @@
 displayed that way, depends on the plugin (or plugin parameters), which is
 configured in the view.
 
-<p>{imp7:0}
+<p>{imp7:21}
 In short: a view can be set up to display PCB pin numbers and another view
 can be set up to display SPICE pin numbers and the user can switch between
 views any time.