Index: trunk/doc/use_cases/blockdiag.html
===================================================================
--- trunk/doc/use_cases/blockdiag.html (revision 5640)
+++ trunk/doc/use_cases/blockdiag.html (nonexistent)
@@ -1,19 +0,0 @@
-
-
-
- sch-rnd - use cases
-
- Block diagram
-
-Simulink style block diagrams, circuit boards, circuits
-with cables, hydraulics and maybe also VHDL. Features
-required:
-
- - Graphical symbols with pins.
-
- Possibility to connect pins or more abstract connection points.
-
- Buses to bunch together like wires in a cable.
-
- Possibility to assign values to objects.
-
- The connections will form nets.
-
-
-
Index: trunk/doc/use_cases/backannot.html
===================================================================
--- trunk/doc/use_cases/backannot.html (revision 5640)
+++ trunk/doc/use_cases/backannot.html (nonexistent)
@@ -1,20 +0,0 @@
-
-
-
- sch-rnd - use cases
-
- The "back annotation"
-
- Setup
-
- - any <-> sch flow
-
- in a later phase of the project, in a 3rd party software (e.g. PCB layout tool, simulation software) some change is made that has to be carried back to the schematics
-
-
- Problems
-
- - net change: multiple ways a network connection can be specified
-
- net change: hierarchy; what if a schematics is used in 4 instances and there's a change only in one instance?
-
- attribute change: attributes may be calculated by plugins (source shall be changed)
-
-
Index: trunk/doc/use_cases/plugin_gui.html
===================================================================
--- trunk/doc/use_cases/plugin_gui.html (revision 5640)
+++ trunk/doc/use_cases/plugin_gui.html (nonexistent)
@@ -1,14 +0,0 @@
-
-
-
- sch-rnd - use cases
-
- plugin highlight
-
-A plugin may want to:
-
- - modify attributes
-
- higlight/selection of symbols (and nets)
-
- drive the GUI (dialog boxes, "go there" on the schamtics)
-
-
Index: trunk/doc/use_cases/transistor.html
===================================================================
--- trunk/doc/use_cases/transistor.html (revision 5640)
+++ trunk/doc/use_cases/transistor.html (nonexistent)
@@ -1,22 +0,0 @@
-
-
-
- sch-rnd - use cases
-
- The "transistor" problem
-
- Setup
-
- - sch -> pcb flow
-
- generic (light) symbol in the schematics (e.g. a generic NPN)
-
- footprint attribute set to a generic footprint (e.g. a generic sot23)
-
-
- Problems
-
- - the pin numbering of the symbol is arbitrary
-
- the pin numbering of the footprint is arbitrary
-
- a footprint+NPN doesn't determine the pinout: there are various NPN devices with different pinouts with the same footprint
-
- number of logical pins may not match number of physical pins; unused pins, mutliple pins connected
-
-
Index: trunk/doc/use_cases/package.html
===================================================================
--- trunk/doc/use_cases/package.html (revision 5640)
+++ trunk/doc/use_cases/package.html (nonexistent)
@@ -1,24 +0,0 @@
-
-
-
- sch-rnd - use cases
-
- The Packaging problem
-
- Setup
-
- - sch -> pcb flow
-
- generic (light) symbol in the schematics (e.g. a generic IC)
-
- footprint attribute set to a generic package (e.g. a generic BGA256)
-
-
- Problems
-
- - the pin numbering of the IC is arbitrary
-
- the pin numbering of the Package is arbitrary
-
- a Package+IC doesn't determine the pinout: there are various IC devices with different pinouts with the same footprint
-
- number of logical pins may not match number of physical pins; unused pins, multiple pins connected, power and ground rings,passive componnents
-
- Package designers will also use cschem to design the package
-
- IC designers will also use cschem to design the bonding diagram
-
-
Index: trunk/doc/Autostyle.html
===================================================================
--- trunk/doc/Autostyle.html (revision 5640)
+++ trunk/doc/Autostyle.html (revision 5641)
@@ -8,7 +8,6 @@
About
| Knowledge pool | Tutorial
| Current state
- | Use cases
| Design
Index: trunk/doc/contact.html
===================================================================
--- trunk/doc/contact.html (revision 5640)
+++ trunk/doc/contact.html (revision 5641)
@@ -15,7 +15,6 @@
| About
| Knowledge pool | Tutorial
| Current state
- | Use cases
| Design
Index: trunk/doc/developer/archive/use_cases/backannot.html
===================================================================
--- trunk/doc/developer/archive/use_cases/backannot.html (nonexistent)
+++ trunk/doc/developer/archive/use_cases/backannot.html (revision 5641)
@@ -0,0 +1,20 @@
+
+
+
+ sch-rnd - use cases
+
+ The "back annotation"
+
+ Setup
+
+ - any <-> sch flow
+
- in a later phase of the project, in a 3rd party software (e.g. PCB layout tool, simulation software) some change is made that has to be carried back to the schematics
+
+
+ Problems
+
+ - net change: multiple ways a network connection can be specified
+
- net change: hierarchy; what if a schematics is used in 4 instances and there's a change only in one instance?
+
- attribute change: attributes may be calculated by plugins (source shall be changed)
+
+
Index: trunk/doc/developer/archive/use_cases/blockdiag.html
===================================================================
--- trunk/doc/developer/archive/use_cases/blockdiag.html (nonexistent)
+++ trunk/doc/developer/archive/use_cases/blockdiag.html (revision 5641)
@@ -0,0 +1,19 @@
+
+
+
+ sch-rnd - use cases
+
+ Block diagram
+
+Simulink style block diagrams, circuit boards, circuits
+with cables, hydraulics and maybe also VHDL. Features
+required:
+
+ - Graphical symbols with pins.
+
- Possibility to connect pins or more abstract connection points.
+
- Buses to bunch together like wires in a cable.
+
- Possibility to assign values to objects.
+
- The connections will form nets.
+
+
+
Index: trunk/doc/developer/archive/use_cases/package.html
===================================================================
--- trunk/doc/developer/archive/use_cases/package.html (nonexistent)
+++ trunk/doc/developer/archive/use_cases/package.html (revision 5641)
@@ -0,0 +1,24 @@
+
+
+
+ sch-rnd - use cases
+
+ The Packaging problem
+
+ Setup
+
+ - sch -> pcb flow
+
- generic (light) symbol in the schematics (e.g. a generic IC)
+
- footprint attribute set to a generic package (e.g. a generic BGA256)
+
+
+ Problems
+
+ - the pin numbering of the IC is arbitrary
+
- the pin numbering of the Package is arbitrary
+
- a Package+IC doesn't determine the pinout: there are various IC devices with different pinouts with the same footprint
+
- number of logical pins may not match number of physical pins; unused pins, multiple pins connected, power and ground rings,passive componnents
+
- Package designers will also use cschem to design the package
+
- IC designers will also use cschem to design the bonding diagram
+
+
Index: trunk/doc/developer/archive/use_cases/plugin_gui.html
===================================================================
--- trunk/doc/developer/archive/use_cases/plugin_gui.html (nonexistent)
+++ trunk/doc/developer/archive/use_cases/plugin_gui.html (revision 5641)
@@ -0,0 +1,14 @@
+
+
+
+ sch-rnd - use cases
+
+ plugin highlight
+
+A plugin may want to:
+
+ - modify attributes
+
- higlight/selection of symbols (and nets)
+
- drive the GUI (dialog boxes, "go there" on the schamtics)
+
+
Index: trunk/doc/developer/archive/use_cases/transistor.html
===================================================================
--- trunk/doc/developer/archive/use_cases/transistor.html (nonexistent)
+++ trunk/doc/developer/archive/use_cases/transistor.html (revision 5641)
@@ -0,0 +1,22 @@
+
+
+
+ sch-rnd - use cases
+
+ The "transistor" problem
+
+ Setup
+
+ - sch -> pcb flow
+
- generic (light) symbol in the schematics (e.g. a generic NPN)
+
- footprint attribute set to a generic footprint (e.g. a generic sot23)
+
+
+ Problems
+
+ - the pin numbering of the symbol is arbitrary
+
- the pin numbering of the footprint is arbitrary
+
- a footprint+NPN doesn't determine the pinout: there are various NPN devices with different pinouts with the same footprint
+
- number of logical pins may not match number of physical pins; unused pins, mutliple pins connected
+
+
Index: trunk/doc/help.html
===================================================================
--- trunk/doc/help.html (revision 5640)
+++ trunk/doc/help.html (revision 5641)
@@ -15,7 +15,6 @@
| About
| Knowledge pool | Tutorial
| Current state
- | Use cases
| Design
Index: trunk/doc/index.html
===================================================================
--- trunk/doc/index.html (revision 5640)
+++ trunk/doc/index.html (revision 5641)
@@ -15,7 +15,6 @@
| About
| Knowledge pool | Tutorial
| Current state
- | Use cases
| Design
Index: trunk/doc/irc.html
===================================================================
--- trunk/doc/irc.html (revision 5640)
+++ trunk/doc/irc.html (revision 5641)
@@ -15,7 +15,6 @@
| About
| Knowledge pool | Tutorial
| Current state
- | Use cases
| Design
Index: trunk/doc/mirrors.html
===================================================================
--- trunk/doc/mirrors.html (revision 5640)
+++ trunk/doc/mirrors.html (revision 5641)
@@ -15,7 +15,6 @@
| About
| Knowledge pool | Tutorial
| Current state
- | Use cases
| Design
Index: trunk/doc/state.html
===================================================================
--- trunk/doc/state.html (revision 5640)
+++ trunk/doc/state.html (revision 5641)
@@ -15,7 +15,6 @@
| About
| Knowledge pool | Tutorial
| Current state
- | Use cases
| Design
Index: trunk/doc/tutorial/index.html
===================================================================
--- trunk/doc/tutorial/index.html (revision 5640)
+++ trunk/doc/tutorial/index.html (revision 5641)
@@ -15,7 +15,6 @@
| About
| Knowledge pool | Tutorial
| Current state
- | Use cases
| Design
|