[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
gEDA-cvs: gaf.git: branch: stable-1.6 updated (1.6.0-20091004-53-g0a2711c)
The branch, stable-1.6 has been updated
via 0a2711ce62dd3f19ae81ecdfd893231de390da9a (commit)
via 1b200e957de912ec369124a2efebe16ec4e6b531 (commit)
via 19e4de650dad95977bc07bae4f897ab6b9d7b110 (commit)
from bd34cfde2450790b357e574281f9562adce64303 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
=========
Summary
=========
docs/scripts/Makefile.am | 3 +-
docs/scripts/copygitignores.sh | 8 +-
docs/scripts/copywip.sh | 28 -
docs/scripts/populatemkfiles.sh | 4 +-
docs/scripts/postproc.sh | 52 -
docs/scripts/removedups.sh | 22 -
docs/scripts/wikicommit.sh | 17 -
docs/scripts/wikifetch.sh | 40 -
docs/wiki/Makefile.am | 2 +-
docs/wiki/geda-documentation.fr.html | 2 +-
docs/wiki/geda-documentation.html | 48 +-
docs/wiki/geda-faq-gschem.html | 27 +-
docs/wiki/geda-file_format_spec.html | 42 +-
docs/wiki/geda-gnetlist_scheme_tutorial.html | 290 ++++
docs/wiki/geda-gparts_dd.html | 1457 ++++++++++++++++++++
docs/wiki/geda-gsch2pcb_tutorial.html | 35 +-
docs/wiki/geda-gschem2pcb_readme.html | 154 --
docs/wiki/geda-gschem_symbol_creation.html | 407 ++++++
docs/wiki/geda-guile_scripting.html | 26 +-
.../geda-pcb_footprint_naming_conventions.html | 231 ++++
docs/wiki/geda-pcb_footprints.html | 32 +-
docs/wiki/geda-pcb_funding_sow-fwdann_ideas.html | 1 -
docs/wiki/geda-pcb_funding_sow-gui_ideas.html | 1 -
docs/wiki/geda-pcb_tips.html | 152 ++-
docs/wiki/geda-release_engineering.html | 14 +-
docs/wiki/geda-scg.html | 586 +--------
docs/wiki/geda-todos.html | 144 +--
docs/wiki/geda-todos_historical.html | 95 ++-
docs/wiki/images/Makefile.am | 4 +-
docs/wiki/images/interwiki/Makefile.am | 2 +-
docs/wiki/images/smileys/Makefile.am | 2 +-
docs/wiki/index.html | 30 +-
docs/wiki/media/Makefile.am | 7 +-
docs/wiki/media/geda/Makefile.am | 2 +-
docs/wiki/media/geda/gparts-flow-2.png | Bin 0 -> 21085 bytes
docs/wiki/media/geda/gparts-ss-companies.png | Bin 0 -> 26023 bytes
docs/wiki/media/geda/gparts-ss-devices.png | Bin 0 -> 40736 bytes
docs/wiki/media/geda/gparts-ss-documentation.png | Bin 0 -> 26160 bytes
docs/wiki/media/geda/gparts-ss-footprints.png | Bin 0 -> 22485 bytes
docs/wiki/media/geda/gparts-ss-packages.png | Bin 0 -> 60292 bytes
docs/wiki/media/geda/gparts-ss-parts-2.png | Bin 0 -> 141064 bytes
docs/wiki/media/geda/gparts-ss-parts.png | Bin 0 -> 127507 bytes
docs/wiki/media/geda/gparts-ss-symbols-2.png | Bin 0 -> 84138 bytes
docs/wiki/media/geda/gparts-ss-symbols.png | Bin 0 -> 74655 bytes
docs/wiki/media/geda/gparts_erd_main.png | Bin 0 -> 33931 bytes
docs/wiki/media/geda/gparts_flow.png | Bin 0 -> 18562 bytes
docs/wiki/media/tragesym/Makefile.am | 2 +-
docs/wiki/playground-playground.html | 99 --
docs/wiki/playground-transistor_guide.html | 129 --
docs/wiki/start.html | 30 +-
docs/wiki/start_es.html | 10 +-
docs/wiki/wiki-syntax.html | 2 +-
52 files changed, 2789 insertions(+), 1450 deletions(-)
delete mode 100755 docs/scripts/copywip.sh
delete mode 100755 docs/scripts/postproc.sh
delete mode 100755 docs/scripts/removedups.sh
delete mode 100755 docs/scripts/wikicommit.sh
delete mode 100755 docs/scripts/wikifetch.sh
create mode 100644 docs/wiki/geda-gnetlist_scheme_tutorial.html
create mode 100644 docs/wiki/geda-gparts_dd.html
delete mode 100644 docs/wiki/geda-gschem2pcb_readme.html
create mode 100644 docs/wiki/geda-gschem_symbol_creation.html
create mode 100644 docs/wiki/geda-pcb_footprint_naming_conventions.html
create mode 100644 docs/wiki/media/geda/gparts-flow-2.png
create mode 100644 docs/wiki/media/geda/gparts-ss-companies.png
create mode 100644 docs/wiki/media/geda/gparts-ss-devices.png
create mode 100644 docs/wiki/media/geda/gparts-ss-documentation.png
create mode 100644 docs/wiki/media/geda/gparts-ss-footprints.png
create mode 100644 docs/wiki/media/geda/gparts-ss-packages.png
create mode 100644 docs/wiki/media/geda/gparts-ss-parts-2.png
create mode 100644 docs/wiki/media/geda/gparts-ss-parts.png
create mode 100644 docs/wiki/media/geda/gparts-ss-symbols-2.png
create mode 100644 docs/wiki/media/geda/gparts-ss-symbols.png
create mode 100644 docs/wiki/media/geda/gparts_erd_main.png
create mode 100644 docs/wiki/media/geda/gparts_flow.png
delete mode 100644 docs/wiki/playground-playground.html
delete mode 100644 docs/wiki/playground-transistor_guide.html
=================
Commit Messages
=================
commit 0a2711ce62dd3f19ae81ecdfd893231de390da9a
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Commit: Ales Hvezda <ahvezda@xxxxxxxx>
Removed a bunch of obsolete wiki snapshot creation/cleanup scripts
:100644 100644 3de66cc... 2a9ed40... M docs/scripts/Makefile.am
:100755 000000 04ad48b... 0000000... D docs/scripts/copywip.sh
:100755 000000 6d229d3... 0000000... D docs/scripts/postproc.sh
:100755 000000 84ab613... 0000000... D docs/scripts/removedups.sh
:100755 000000 c9f81f9... 0000000... D docs/scripts/wikicommit.sh
:100755 000000 2c850ce... 0000000... D docs/scripts/wikifetch.sh
commit 1b200e957de912ec369124a2efebe16ec4e6b531
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Commit: Ales Hvezda <ahvezda@xxxxxxxx>
Updated the wiki snapshot from the official wiki
:100644 100644 5aff050... 59b3563... M docs/wiki/Makefile.am
:100644 100644 cc0b8e6... 013d4a3... M docs/wiki/geda-documentation.fr.html
:100644 100644 146071f... 51965f0... M docs/wiki/geda-documentation.html
:100644 100644 996d53b... bc95071... M docs/wiki/geda-faq-gschem.html
:100644 100644 779c5cd... e408185... M docs/wiki/geda-file_format_spec.html
:000000 100644 0000000... 33306cf... A docs/wiki/geda-gnetlist_scheme_tutorial.html
:000000 100644 0000000... fbba04f... A docs/wiki/geda-gparts_dd.html
:100644 100644 5283402... c03a9a4... M docs/wiki/geda-gsch2pcb_tutorial.html
:100644 000000 8d4f38d... 0000000... D docs/wiki/geda-gschem2pcb_readme.html
:000000 100644 0000000... 3eefee0... A docs/wiki/geda-gschem_symbol_creation.html
:100644 100644 4d97dfd... f807ac3... M docs/wiki/geda-guile_scripting.html
:000000 100644 0000000... 983826d... A docs/wiki/geda-pcb_footprint_naming_conventions.html
:100644 100644 d2339a6... 85352ff... M docs/wiki/geda-pcb_footprints.html
:100644 100644 e15c265... f0072a4... M docs/wiki/geda-pcb_funding_sow-fwdann_ideas.html
:100644 100644 7fc3e5e... 326c2b3... M docs/wiki/geda-pcb_funding_sow-gui_ideas.html
:100644 100644 6d473df... 998095a... M docs/wiki/geda-pcb_tips.html
:100644 100644 011a9a4... bde39e2... M docs/wiki/geda-release_engineering.html
:100644 100644 83d058e... 3da3c56... M docs/wiki/geda-scg.html
:100644 100644 a21fb9e... ae00cd4... M docs/wiki/geda-todos.html
:100644 100644 d759dab... 967cb5b... M docs/wiki/geda-todos_historical.html
:100644 100644 b8db727... c971ff5... M docs/wiki/images/Makefile.am
:100644 100644 a294f2c... 0723035... M docs/wiki/images/interwiki/Makefile.am
:100644 100644 2e01243... 77e5024... M docs/wiki/images/smileys/Makefile.am
:100644 100644 d876a26... 19d0714... M docs/wiki/index.html
:100644 100644 8ce7d79... 943c93a... M docs/wiki/media/Makefile.am
:100644 100644 ab3fb70... 64ae657... M docs/wiki/media/geda/Makefile.am
:000000 100644 0000000... 734a40e... A docs/wiki/media/geda/gparts-flow-2.png
:000000 100644 0000000... 8e5bff5... A docs/wiki/media/geda/gparts-ss-companies.png
:000000 100644 0000000... e2265db... A docs/wiki/media/geda/gparts-ss-devices.png
:000000 100644 0000000... 463a717... A docs/wiki/media/geda/gparts-ss-documentation.png
:000000 100644 0000000... 59238b1... A docs/wiki/media/geda/gparts-ss-footprints.png
:000000 100644 0000000... 961ce68... A docs/wiki/media/geda/gparts-ss-packages.png
:000000 100644 0000000... 95a8530... A docs/wiki/media/geda/gparts-ss-parts-2.png
:000000 100644 0000000... b878536... A docs/wiki/media/geda/gparts-ss-parts.png
:000000 100644 0000000... d51ffa4... A docs/wiki/media/geda/gparts-ss-symbols-2.png
:000000 100644 0000000... 389dfd7... A docs/wiki/media/geda/gparts-ss-symbols.png
:000000 100644 0000000... 2f45297... A docs/wiki/media/geda/gparts_erd_main.png
:000000 100644 0000000... 384fd60... A docs/wiki/media/geda/gparts_flow.png
:100644 100644 857988c... fd88f56... M docs/wiki/media/tragesym/Makefile.am
:100644 000000 4f6c787... 0000000... D docs/wiki/playground-playground.html
:100644 000000 f13fe82... 0000000... D docs/wiki/playground-transistor_guide.html
:100644 100644 d876a26... 19d0714... M docs/wiki/start.html
:100644 100644 540ce33... 4408be8... M docs/wiki/start_es.html
:100644 100644 17b47f2... 156e0c2... M docs/wiki/wiki-syntax.html
commit 19e4de650dad95977bc07bae4f897ab6b9d7b110
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Commit: Ales Hvezda <ahvezda@xxxxxxxx>
Tweaked scripts with updated paths
Eventually these scripts should be fixed or rewritten so that they
do not have any hardcoded paths.
:100755 100755 e7da5a1... d43aa67... M docs/scripts/copygitignores.sh
:100755 100755 8553471... 3f8ed9a... M docs/scripts/populatemkfiles.sh
=========
Changes
=========
commit 0a2711ce62dd3f19ae81ecdfd893231de390da9a
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Commit: Ales Hvezda <ahvezda@xxxxxxxx>
Removed a bunch of obsolete wiki snapshot creation/cleanup scripts
diff --git a/docs/scripts/Makefile.am b/docs/scripts/Makefile.am
index 3de66cc..2a9ed40 100644
--- a/docs/scripts/Makefile.am
+++ b/docs/scripts/Makefile.am
@@ -1,8 +1,7 @@
## $Id$
##
-EXTRA_DIST = postproc.sh wikifetch.sh wikicommit.sh populatemkfiles.sh \
- copywip.sh removedups.sh copygitignores.sh
+EXTRA_DIST = populatemkfiles.sh copygitignores.sh
MOSTLYCLEANFILES = *.log *~
CLEANFILES = *.log *~
diff --git a/docs/scripts/copywip.sh b/docs/scripts/copywip.sh
deleted file mode 100755
index 04ad48b..0000000
--- a/docs/scripts/copywip.sh
+++ /dev/null
@@ -1,28 +0,0 @@
-#!/bin/sh
-
-# Handle changed files
-diff -r -q wip wiki | grep Files | sed "s/Files/cp -f/" | sed "s/ and / /" | sed "s/ differ//" > tmp$$.sh
-sh ./tmp$$.sh
-rm -f tmp$$.sh
-
-
-# Handle new files (still buggy but works for at least two levels)
-diff -r -q wip wiki | grep "Only in wip" | sed "s/Only in//" | sed "s/: /:/" > filelist.$$
-
-for i in `cat filelist.$$`
-do
- directory=`echo $i | awk -F: '{print $1}'`
- file=`echo $i | awk -F: '{print $2}'`
- basedir=`basename $directory`
-
- echo Processing: $directory $file
- if [ "$basedir" = "wip" ]
- then
- cp -f $basedir/$file wiki/
- else
- mkdir -p wiki/$basedir > /dev/null 2>&1
- cp -f wip/$basedir/$file wiki/$basedir
- fi
-done
-
-rm -f filelist.$$
diff --git a/docs/scripts/postproc.sh b/docs/scripts/postproc.sh
deleted file mode 100755
index 6d229d3..0000000
--- a/docs/scripts/postproc.sh
+++ /dev/null
@@ -1,52 +0,0 @@
-#!/bin/sh
-
-if [ ! -e "geda_faq.html" ]
-then
- echo "You must start this program in the toplevel wiki directory"
- echo "wherever geda_faq.html lives."
- exit 1
-fi
-
-if [ ! -e "../scripts/removedups.sh" ]
-then
- echo "../scripts/removedups.sh must exist"
- exit 1
-fi
-
-files=`find . -name \*.html -print`
-
-for i in $files
-do
- echo $i
- mv -f $i $i.old
- cat $i.old | sed '/\<script type/d' > $i
-
- rm -f $i.old
-
- mv -f $i $i.old2
- isdetail=`echo $i | grep _detail`
- if [ "$isdetail" = "" ]
- then
- cat $i.old2 | \
- sed 's%media="all" type="text/css" href="http://geda.seul.org/wiki/lib/exe/css.php?s=all"%media="all"; type="text/css" href="lib/exe/css"%g' | \
- sed 's%media="screen" type="text/css" href="http://geda.seul.org/wiki/lib/exe/css.php"%media="screen"; type="text/css" href="lib/exe/001css"%g' | \
- sed 's%media="print" type="text/css" href="http://geda.seul.org/wiki/lib/exe/css.php?s=print"%media="print"; type="text/css" href="lib/exe/002css"%g' \
- > $i
- else
- cat $i.old2 | \
- sed 's%media="all" type="text/css" href="http://geda.seul.org/wiki/lib/exe/css.php?s=all"%media="all"; type="text/css" href="../lib/exe/css"%g' | \
- sed 's%media="screen" type="text/css" href="http://geda.seul.org/wiki/lib/exe/css.php"%media="screen"; type="text/css" href="../lib/exe/001css"%g' | \
- sed 's%media="print" type="text/css" href="http://geda.seul.org/wiki/lib/exe/css.php?s=print"%media="print"; type="text/css" href="../lib/exe/002css"%g' \
- > $i
- fi
-
-
- rm -f $i.old2
-
-done
-
-# Remove duplicate images from _detail
-../scripts/removedups.sh 001
-../scripts/removedups.sh 002
-rm -f _media/001*.png _media/001*.jpg _media/002*.png _media/002*.jpg
-
diff --git a/docs/scripts/removedups.sh b/docs/scripts/removedups.sh
deleted file mode 100755
index 84ab613..0000000
--- a/docs/scripts/removedups.sh
+++ /dev/null
@@ -1,22 +0,0 @@
-#!/bin/sh
-
-prefix=$1
-
-cd _media
-files=`ls -1 ${prefix}*`
-
-cd ../_detail
-
-for i in $files
-do
- oldname=$i
- newname=`echo $i | sed "s/$prefix//g"`
- htmlfiles=`grep -l $oldname *.html`
- for j in $htmlfiles
- do
- echo Patching $j : $oldname to $newname
- mv $j $j.orig
- cat $j.orig | sed "s/$oldname/$newname/g" > $j
- done
-done
-
diff --git a/docs/scripts/wikicommit.sh b/docs/scripts/wikicommit.sh
deleted file mode 100755
index c9f81f9..0000000
--- a/docs/scripts/wikicommit.sh
+++ /dev/null
@@ -1,17 +0,0 @@
-#!/bin/sh
-
-files=`find . -name \* -print | grep -v CVS | grep -v Makefile | sed "s%^\./%%" | sed "s%^\.%%"`
-
-for i in $files
-do
- image=`file $i | grep -i image`
-
- if [ "$image" != "" ]
- then
- echo Adding image: $i
- cvs add -kb $i
- else
- echo Adding regular file: $i
- cvs add $i
- fi
-done
diff --git a/docs/scripts/wikifetch.sh b/docs/scripts/wikifetch.sh
deleted file mode 100755
index 2c850ce..0000000
--- a/docs/scripts/wikifetch.sh
+++ /dev/null
@@ -1,40 +0,0 @@
-#!/bin/bash
-
-#
-# Retrieve wiki pages as html pages, creating a local tree of documents
-# mirroring the original wiki structure. Wiki URLs are converted to local
-# directories/filenames based on namespace/wiki-page naming conventions.
-#
-# Check calling arguments.
-
-# website to fetch
-site=http://geda.seul.org/wiki
-
-if [ ! -d ../wip ]
-then
- mkdir ../wip
-fi
-
-if [ ! -d ../wip ]
-then
- echo "cannot create wip directory"
- exit 1
-fi
-
-#
-pavuk -logfile ../wip/pavuk_logfile.txt \
- -slogfile ../wip/pavuk_slogfile.txt \
- -cdir ../wip \
- -dont_leave_site \
- -noRobots \
- -index_name "index.html" \
- -httpad "+X_DOKUWIKI_DO: export_xhtml" \
- -cookie_file ../wip/cookies.txt \
- -cookie_send \
- -url_pattern http://geda.seul.org/wiki/\* \
- -skip_rpattern "(.*\?do=(_export|diff|revisions|backlink|index|export_.*))|_export|feed\.php.*" \
- -tr_chr_chr "?&*:" _ \
- -post_update \
- -sleep 1 \
- -fnrules F "*" "%h/%d/%b%E" "$site"
-
commit 1b200e957de912ec369124a2efebe16ec4e6b531
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Commit: Ales Hvezda <ahvezda@xxxxxxxx>
Updated the wiki snapshot from the official wiki
diff --git a/docs/wiki/Makefile.am b/docs/wiki/Makefile.am
index 5aff050..59b3563 100644
--- a/docs/wiki/Makefile.am
+++ b/docs/wiki/Makefile.am
@@ -4,7 +4,7 @@ docsdir = $(docdir)/$(docname)/
SUBDIRS = images media
-docs_DATA = geda-gtkwave_tex2vcd_mp.html geda-na_howto.html geda-wip-clipboard.html geda-icarus_vpi_mp.html geda-debian.html geda-grcsan.html geda-devmacosx.html geda-mcalc_readme.html geda-format_translation.html geda-scg.html gerbv-projects.html geda-csygas.html geda-todos_historical.html geda-icarus_extensions.html libgeda3_object_based_design.html playground-transistor_guide.html geda-igarus_fpga_lcg.html geda-icarus_xnf.html playground-playground.html geda-icarus_vvp_runtime.html geda-gschem_ug.fr.html geda-faq-attribs.fr.html geda-wcalc_readme.html geda-gsch2pcb_tutorial.html geda-gtkwave_vcd2lxt2_mp.html geda-pcb_funding_sow.html geda-bom_readme.html geda-design_flow_roadmap.html geda-gerbv_pnp_readme.html geda-faq-attribs.html geda-fbabgapp.html geda-faq-simulation.fr.html geda-gtkwave_vztminer_mp.html geda-documentation.html geda-scm.html geda-icarus_ieee1364.html geda-pcb-quick_reference.html geda-pcb-quick_reference.fr.html index.html geda-sn_readme.html geda-faq-gnetlist.html geda-documentation.fr.html geda-eagle_pcb_netlister_readme.html geda-faq.fr.html geda-tragesym_tutorial.fr.html geda-faq-gnetlist.fr.html geda-example_usbjtag.html geda-suse_10.1.html start_es.html geda-todos.html geda-icarus_opcodes.html geda-gschem_warmup.html geda-suse_rpm_installation.html geda-pcb_tips.fr.html geda-gtkwave_mvl2lxt_mp.html style.css geda-cygwin.html gsoc2007.html geda-gfdl.html geda-gtkwave_vcd2lxt_mp.html geda-start.html geda-pcb_funding_sow-gui_ideas.html geda-ngspice_mp.html geda-ssan.html geda-faq.html geda-faq-gsch2pcb.fr.html geda-gattrib_readme.html geda-gschem2pcb_readme.html geda-xml_file_formats.html geda-example_hsm.html geda-ngsconvert_mp.html gsoc2008.html geda-glossary.fr.html geda-grenum_mp.html geda-tragesym_readme.html geda-icarus_readme.html geda-icarus_anc.html geda-gtkwave_mp.html start.html geda-ngspice_and_gschem.html start_fr.html geda-file_format_spec.html geda-data_structure_design_discussion.html geda-installation.html geda-wcalc_stdio_mp.html geda-gschem_mp.html geda-pcb_mp.html gsoc2007_projects.html gsoc2009_projects.html geda-hse_howto.html geda-icarus_quick_start.html geda-style_guide.html geda-circuit_simulation_improvements.html geda-pcb_footprints.html geda-ubuntu.html geda-fedora_rpm_installation.html glue-projects.html geda-spice_improvements.html print.css geda-gtkwave_mvl2vcd_mp.html geda-glossary.html geda-data_plotting_improvements.html geda-wcalc_mp.html geda-gnetlist_ug.html gsoc2008_projects.html geda-usage.fr.html geda-gtkwave_lxt2miner_mp.html geda-faq-simulation.html geda-suse_10.0.html gwave-projects.html geda-gsch2pcb_tutorial_releasenotes.html geda-usage.html best_practices.html geda-installed_plugins.html geda-glossaire.fr.html pcb-projects.html geda-covered_mp.html geda-icarus_glossary.html geda-pcb_tips.html geda-debian.fr.html geda-gsymcheck_mp.html gschem-projects.html geda-syntax_features.html libgeda3.html design.css geda-fc3.html geda-ngnutmeg_mp.html gtkwave-projects.html geda-gtkwave_lxt2vcd_mp.html geda-gnetlist_mp.html geda-gtkwave_vzt2vcd_mp.html geda-devel-tips.html geda-gtkwave_tla2vcd_mp.html geda-guile_scripting.html geda-olib_readme.html geda-gerbv_mp.html geda-master_attributes_list.html geda-kig_howto.html geda-version_control_migration.html geda-fc1.html geda-gsch2pcb_readme.html geda-design_flow_and_hierarchy_roadmap.html geda-faq-gschem.fr.html geda-gschem_ug.html geda-fc2.html geda-icarus_xilinx_hints.html geda-transistor_guide.html geda-verilog_netlister_readme.html geda-icarus_vpi_within_vvp.html wiki-syntax.html geda-scg.fr.html geda-faq-gsch2pcb.html wiki-dokuwiki.html geda-tragesym_tutorial.html geda-gedasuite_installation.html geda-faq-gschem.html geda-release_engineering.html geda-experiences.html geda-fc4.html gsoc2009.html geda-systemc_netlister_readme.html geda-pcb_funding_sow-fwdann_ideas.html geda-faq-pcb.html geda-installation.fr.html geda-icarus_vvp_simulation.html geda-vhdl_netlister_readme.html geda-gtkwave_vcd2vzt_mp.html geda-tasks.html geda-suse_9.3.html geda-sdb_howto.html geda-vams_netlister_readme.html geda-icarus_mp.html
+docs_DATA = geda-faq-gschem.html geda-experiences.html geda-icarus_xnf.html geda-verilog_netlister_readme.html geda-tragesym_tutorial.fr.html geda-ngnutmeg_mp.html wiki-syntax.html geda-ssan.html geda-example_usbjtag.html geda-gnetlist_scheme_tutorial.html geda-faq-gsch2pcb.fr.html geda-icarus_readme.html geda-gsch2pcb_tutorial.html geda-na_howto.html gsoc2009.html geda-example_hsm.html libgeda3_object_based_design.html geda-fc3.html geda-glossary.html geda-kig_howto.html geda-icarus_vvp_simulation.html geda-pcb_footprints.html geda-wip-clipboard.html geda-faq.html geda-faq-gsch2pcb.html geda-todos_historical.html geda-covered_mp.html geda-pcb_tips.html gsoc2009_projects.html geda-wcalc_mp.html best_practices.html index.html geda-syntax_features.html geda-icarus_opcodes.html geda-gparts_dd.html geda-gtkwave_vztminer_mp.html geda-grcsan.html geda-scg.fr.html geda-gsch2pcb_readme.html geda-debian.fr.html geda-gtkwave_vcd2vzt_mp.html geda-installation.fr.html geda-gtkwave_mp.html geda-format_translation.html geda-glossary.fr.html geda-ngsconvert_mp.html geda-documentation.fr.html geda-glossaire.fr.html geda-icarus_mp.html geda-icarus_vpi_mp.html geda-devel-tips.html geda-gschem_warmup.html geda-style_guide.html geda-fc1.html geda-transistor_guide.html geda-icarus_vvp_runtime.html geda-tragesym_tutorial.html start_fr.html geda-release_engineering.html gsoc2007_projects.html gsoc2007.html geda-gsymcheck_mp.html geda-gtkwave_mvl2vcd_mp.html design.css geda-ngspice_and_gschem.html gsoc2008_projects.html geda-data_plotting_improvements.html geda-tragesym_readme.html geda-suse_10.1.html geda-hse_howto.html style.css geda-eagle_pcb_netlister_readme.html geda-gattrib_readme.html geda-systemc_netlister_readme.html geda-spice_improvements.html geda-pcb_funding_sow-fwdann_ideas.html geda-faq-gschem.fr.html geda-ngspice_mp.html geda-version_control_migration.html geda-usage.fr.html geda-pcb-quick_reference.fr.html geda-olib_readme.html geda-wcalc_readme.html geda-sn_readme.html libgeda3.html geda-fedora_rpm_installation.html geda-gnetlist_ug.html wiki-dokuwiki.html geda-debian.html geda-gschem_ug.html geda-faq-attribs.fr.html geda-gtkwave_lxt2miner_mp.html geda-suse_10.0.html geda-design_flow_roadmap.html geda-faq-simulation.html geda-gtkwave_vcd2lxt_mp.html geda-master_attributes_list.html geda-pcb_tips.fr.html geda-gschem_ug.fr.html geda-icarus_vpi_within_vvp.html geda-gschem_mp.html geda-suse_rpm_installation.html geda-gnetlist_mp.html gsoc2008.html geda-installation.html geda-gerbv_pnp_readme.html geda-mcalc_readme.html geda-icarus_xilinx_hints.html geda-ubuntu.html geda-pcb_funding_sow-gui_ideas.html geda-todos.html geda-fbabgapp.html geda-fc4.html geda-pcb_footprint_naming_conventions.html geda-gtkwave_vcd2lxt2_mp.html geda-faq-attribs.html geda-pcb-quick_reference.html geda-xml_file_formats.html geda-icarus_extensions.html geda-pcb_funding_sow.html geda-scm.html geda-gtkwave_lxt2vcd_mp.html geda-faq-pcb.html geda-faq-simulation.fr.html geda-icarus_ieee1364.html geda-gtkwave_vzt2vcd_mp.html geda-grenum_mp.html geda-guile_scripting.html start_es.html geda-bom_readme.html geda-vhdl_netlister_readme.html geda-usage.html geda-gschem_symbol_creation.html geda-vams_netlister_readme.html geda-csygas.html geda-gfdl.html geda-devmacosx.html glue-projects.html geda-wcalc_stdio_mp.html geda-gerbv_mp.html geda-fc2.html geda-gedasuite_installation.html geda-igarus_fpga_lcg.html geda-installed_plugins.html geda-suse_9.3.html geda-faq-gnetlist.html gwave-projects.html geda-faq.fr.html gtkwave-projects.html geda-file_format_spec.html geda-faq-gnetlist.fr.html geda-icarus_anc.html print.css geda-gtkwave_tla2vcd_mp.html gschem-projects.html geda-gtkwave_mvl2lxt_mp.html start.html geda-design_flow_and_hierarchy_roadmap.html geda-start.html geda-tasks.html geda-gsch2pcb_tutorial_releasenotes.html geda-icarus_quick_start.html geda-data_structure_design_discussion.html geda-documentation.html geda-sdb_howto.html gerbv-projects.html geda-circuit_simulation_improvements.html pcb-projects.html geda-gtkwave_tex2vcd_mp.html geda-icarus_glossary.html geda-pcb_mp.html geda-cygwin.html geda-scg.html
EXTRA_DIST = $(docs_DATA)
diff --git a/docs/wiki/geda-documentation.fr.html b/docs/wiki/geda-documentation.fr.html
index cc0b8e6..013d4a3 100644
--- a/docs/wiki/geda-documentation.fr.html
+++ b/docs/wiki/geda-documentation.fr.html
@@ -103,7 +103,7 @@ New features are available for document authors:
</li>
<li class="level1"><div class="li"> <a href="geda-bom_readme.html" class="wikilink1" title="geda-bom_readme.html">Bill of Material netlister README</a></div>
</li>
-<li class="level1"><div class="li"> <a href="geda-gschem2pcb_readme.html" class="wikilink1" title="geda-gschem2pcb_readme.html">gschem2pcb README</a></div>
+<li class="level1"><div class="li"> <a href="geda-gschem2pcb_readme.html" class="wikilink2" title="geda-gschem2pcb_readme.html">gschem2pcb README</a></div>
</li>
<li class="level1"><div class="li"> <a href="geda-verilog_netlister_readme.html" class="wikilink1" title="geda-verilog_netlister_readme.html">Verilog netlister README</a></div>
</li>
diff --git a/docs/wiki/geda-documentation.html b/docs/wiki/geda-documentation.html
index 146071f..51965f0 100644
--- a/docs/wiki/geda-documentation.html
+++ b/docs/wiki/geda-documentation.html
@@ -48,7 +48,7 @@
<div class="level1">
</div>
-<!-- SECTION "gEDA Tool Suite on-line documentation" [1-55] -->
+<!-- SECTION "gEDA Tool Suite on-line documentation" [1-56] -->
<h2><a name="tutorials" id="tutorials">Tutorials</a></h2>
<div class="level2">
<ul>
@@ -64,10 +64,12 @@
</li>
<li class="level1"><div class="li"> <a href="geda-tragesym_tutorial.html" class="wikilink1" title="geda-tragesym_tutorial.html">tragesym tutorial</a> on how to create symbols with the tragesym script.</div>
</li>
+<li class="level1"><div class="li"> <a href="geda-gnetlist_scheme_tutorial.html" class="wikilink1" title="geda-gnetlist_scheme_tutorial.html">Scripting a gnetlist backend in scheme</a> by John Doty.</div>
+</li>
</ul>
</div>
-<!-- SECTION "Tutorials" [56-511] -->
+<!-- SECTION "Tutorials" [57-600] -->
<h2><a name="gschem_-_schematic_capture" id="gschem_-_schematic_capture">gschem - Schematic Capture</a></h2>
<div class="level2">
<ul>
@@ -75,7 +77,7 @@
</li>
<li class="level1"><div class="li"> <a href="geda-gschem_mp.html" class="wikilink1" title="geda-gschem_mp.html">gschem man-page</a></div>
</li>
-<li class="level1"><div class="li"> <a href="geda-scg.html" class="wikilink1" title="geda-scg.html">Symbol Creation Guide</a></div>
+<li class="level1"><div class="li"> <a href="geda-gschem_symbol_creation.html" class="wikilink1" title="geda-gschem_symbol_creation.html">Symbol Creation Guide</a></div>
</li>
<li class="level1"><div class="li"> <a href="geda-hse_howto.html" class="wikilink1" title="geda-hse_howto.html">Hooks/Scheme Extension HOWTO</a></div>
</li>
@@ -84,7 +86,7 @@
</ul>
</div>
-<!-- SECTION "gschem - Schematic Capture" [512-812] -->
+<!-- SECTION "gschem - Schematic Capture" [601-920] -->
<h2><a name="gnetlist_-_netlister" id="gnetlist_-_netlister">gnetlist - Netlister</a></h2>
<div class="level2">
<ul>
@@ -106,8 +108,6 @@
</li>
<li class="level1"><div class="li"> <a href="geda-bom_readme.html" class="wikilink1" title="geda-bom_readme.html">Bill of Material netlister README</a></div>
</li>
-<li class="level1"><div class="li"> <a href="geda-gschem2pcb_readme.html" class="wikilink1" title="geda-gschem2pcb_readme.html">gschem2pcb README</a></div>
-</li>
<li class="level1"><div class="li"> <a href="geda-verilog_netlister_readme.html" class="wikilink1" title="geda-verilog_netlister_readme.html">Verilog netlister README</a></div>
</li>
<li class="level1"><div class="li"> <a href="geda-vhdl_netlister_readme.html" class="wikilink1" title="geda-vhdl_netlister_readme.html">VHDL netlister README</a></div>
@@ -121,7 +121,7 @@
</ul>
</div>
-<!-- SECTION "gnetlist - Netlister" [813-1685] -->
+<!-- SECTION "gnetlist - Netlister" [921-1744] -->
<h2><a name="gsymcheck_-_symbol_checker" id="gsymcheck_-_symbol_checker">gsymcheck - Symbol Checker</a></h2>
<div class="level2">
<ul>
@@ -130,7 +130,7 @@
</ul>
</div>
-<!-- SECTION "gsymcheck - Symbol Checker" [1686-1771] -->
+<!-- SECTION "gsymcheck - Symbol Checker" [1745-1830] -->
<h2><a name="utils_-_geda_utilities" id="utils_-_geda_utilities">utils - gEDA Utilities</a></h2>
<div class="level2">
<ul>
@@ -151,7 +151,7 @@
</ul>
</div>
-<!-- SECTION "utils - gEDA Utilities" [1772-2188] -->
+<!-- SECTION "utils - gEDA Utilities" [1831-2247] -->
<h2><a name="examples" id="examples">Examples</a></h2>
<div class="level2">
<ul>
@@ -162,7 +162,7 @@
</ul>
</div>
-<!-- SECTION "Examples" [2189-2338] -->
+<!-- SECTION "Examples" [2248-2397] -->
<h2><a name="attribute_file_format_details" id="attribute_file_format_details">Attribute/File Format Details</a></h2>
<div class="level2">
<ul>
@@ -173,7 +173,7 @@
</ul>
</div>
-<!-- SECTION "Attribute/File Format Details" [2339-2504] -->
+<!-- SECTION "Attribute/File Format Details" [2398-2563] -->
<h1><a name="spice" id="spice">SPICE</a></h1>
<div class="level1">
<ul>
@@ -198,7 +198,7 @@
</ul>
</div>
-<!-- SECTION "SPICE" [2505-3238] -->
+<!-- SECTION "SPICE" [2564-3297] -->
<h1><a name="ngspice" id="ngspice">ngspice</a></h1>
<div class="level1">
<ul>
@@ -214,7 +214,7 @@
</ul>
</div>
-<!-- SECTION "ngspice" [3239-3661] -->
+<!-- SECTION "ngspice" [3298-3720] -->
<h1><a name="gnucap" id="gnucap">gnucap</a></h1>
<div class="level1">
<ul>
@@ -225,7 +225,7 @@
</ul>
</div>
-<!-- SECTION "gnucap" [3662-3890] -->
+<!-- SECTION "gnucap" [3721-3949] -->
<h1><a name="gspiceui" id="gspiceui">gSpiceUI</a></h1>
<div class="level1">
<ul>
@@ -234,7 +234,7 @@
</ul>
</div>
-<!-- SECTION "gSpiceUI" [3891-3976] -->
+<!-- SECTION "gSpiceUI" [3950-4035] -->
<h1><a name="pcb" id="pcb">PCB</a></h1>
<div class="level1">
<ul>
@@ -249,7 +249,7 @@
</ul>
</div>
-<!-- SECTION "PCB" [3977-4381] -->
+<!-- SECTION "PCB" [4036-4440] -->
<h1><a name="gerbv" id="gerbv">gerbv</a></h1>
<div class="level1">
<ul>
@@ -260,7 +260,7 @@
</ul>
</div>
-<!-- SECTION "gerbv" [4382-4527] -->
+<!-- SECTION "gerbv" [4441-4586] -->
<h1><a name="icarus_verilog" id="icarus_verilog">Icarus Verilog</a></h1>
<div class="level1">
<ul>
@@ -299,7 +299,7 @@
</ul>
</div>
-<!-- SECTION "Icarus Verilog" [4528-5522] -->
+<!-- SECTION "Icarus Verilog" [4587-5581] -->
<h1><a name="gtkwave" id="gtkwave">GTKWave</a></h1>
<div class="level1">
<ul>
@@ -333,10 +333,12 @@
</ul>
</div>
-<!-- SECTION "GTKWave" [5523-6554] -->
+<!-- SECTION "GTKWave" [5582-6614] -->
<h1><a name="wcalc" id="wcalc">Wcalc</a></h1>
<div class="level1">
<ul>
+<li class="level1"><div class="li"> <a href="http://wcalc.sourceforge.net/"; class="urlextern" title="http://wcalc.sourceforge.net/"; rel="nofollow">wcalc Home Page</a></div>
+</li>
<li class="level1"><div class="li"> <a href="geda-wcalc_readme.html" class="wikilink1" title="geda-wcalc_readme.html">Wcalc README</a></div>
</li>
<li class="level1"><div class="li"> <a href="geda-wcalc_mp.html" class="wikilink1" title="geda-wcalc_mp.html">Wcalc man-page</a></div>
@@ -346,7 +348,7 @@
</ul>
</div>
-<!-- SECTION "Wcalc" [6555-6701] -->
+<!-- SECTION "Wcalc" [6615-6815] -->
<h1><a name="mcalc" id="mcalc">mcalc</a></h1>
<div class="level1">
<ul>
@@ -357,7 +359,7 @@
</ul>
</div>
-<!-- SECTION "mcalc" [6702-6881] -->
+<!-- SECTION "mcalc" [6816-6995] -->
<h1><a name="covered" id="covered">covered</a></h1>
<div class="level1">
<ul>
@@ -370,7 +372,7 @@
</ul>
</div>
-<!-- SECTION "covered" [6882-7179] -->
+<!-- SECTION "covered" [6996-7293] -->
<h1><a name="for_document_authors" id="for_document_authors">For document authors</a></h1>
<div class="level1">
@@ -387,5 +389,5 @@ New features are available for document authors:
</ul>
</div>
-<!-- SECTION "For document authors" [7180-] --></body>
+<!-- SECTION "For document authors" [7294-] --></body>
</html>
diff --git a/docs/wiki/geda-faq-gschem.html b/docs/wiki/geda-faq-gschem.html
index 996d53b..bc95071 100644
--- a/docs/wiki/geda-faq-gschem.html
+++ b/docs/wiki/geda-faq-gschem.html
@@ -798,7 +798,7 @@ The default printing size is used when printing from the command line. To set th
</p>
</div>
-<!-- SECTION "How do I print schematics from the command line?" [25153-26443] -->
+<!-- SECTION "How do I print schematics from the command line?" [25153-26444] -->
<h2><a name="how_can_i_get_color_postscript_png_output" id="how_can_i_get_color_postscript_png_output">How can I get color postscript/PNG output?</a></h2>
<div class="level2">
@@ -826,8 +826,13 @@ To control the background of the <acronym title="Portable Network Graphics">PNG<
The 255 255 255 are the RGB components for the background color of the <acronym title="Portable Network Graphics">PNG</acronym> image.
</p>
+<p>
+From version 1.5.2 onwards, print and display color maps are separate. In order to get postscript output with a light background, add the following to your gschemrc:
+</p>
+<pre class="code">(load (build-path geda-rc-path "print-colormap-lightbg"))</pre>
+
</div>
-<!-- SECTION "How can I get color postscript/PNG output?" [26444-27576] -->
+<!-- SECTION "How can I get color postscript/PNG output?" [26445-27815] -->
<h2><a name="how_can_i_get_black_and_white_postscript_png_output" id="how_can_i_get_black_and_white_postscript_png_output">How can I get black and white postscript/PNG output?</a></h2>
<div class="level2">
@@ -842,7 +847,7 @@ For black and white <acronym title="Portable Network Graphics">PNG</acronym> ima
<pre class="code">(image-color "disabled") ; for monochromoe PNG output</pre>
</div>
-<!-- SECTION "How can I get black and white postscript/PNG output?" [27577-27942] -->
+<!-- SECTION "How can I get black and white postscript/PNG output?" [27816-28181] -->
<h2><a name="how_can_i_produce_pdf_output" id="how_can_i_produce_pdf_output">How can I produce PDF output?</a></h2>
<div class="level2">
@@ -875,7 +880,7 @@ In a KDE environment the print command is â??kprinterâ?? with the output option
<pre class="code">(print-command "kprinter")</pre>
</div>
-<!-- SECTION "How can I produce PDF output?" [27943-28915] -->
+<!-- SECTION "How can I produce PDF output?" [28182-29154] -->
<h2><a name="how_can_i_insert_schematics_into_my_latex_document" id="how_can_i_insert_schematics_into_my_latex_document">How can I insert schematics into my LaTex document?</a></h2>
<div class="level2">
<ol>
@@ -899,7 +904,7 @@ In a KDE environment the print command is â??kprinterâ?? with the output option
\end{document}</pre>
</div>
-<!-- SECTION "How can I insert schematics into my LaTex document?" [28916-29484] -->
+<!-- SECTION "How can I insert schematics into my LaTex document?" [29155-29723] -->
<h2><a name="how_can_i_split_postscript_output_over_multiple_pages" id="how_can_i_split_postscript_output_over_multiple_pages">How can I split Postscript output over multiple pages?</a></h2>
<div class="level2">
@@ -908,12 +913,12 @@ gschem does not provide this functionality internally, however there is a progra
</p>
</div>
-<!-- SECTION "How can I split Postscript output over multiple pages?" [29485-29828] -->
+<!-- SECTION "How can I split Postscript output over multiple pages?" [29724-30067] -->
<h1><a name="gschem_installation_run-time_problems" id="gschem_installation_run-time_problems">Gschem installation/run-time problems</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Gschem installation/run-time problems" [29829-29881] -->
+<!-- SECTION "Gschem installation/run-time problems" [30068-30120] -->
<h2><a name="gschem_segfaults_when_i_delete_components_on_fc5_and_other_linux_distributions_is_there_a_work-around" id="gschem_segfaults_when_i_delete_components_on_fc5_and_other_linux_distributions_is_there_a_work-around">Gschem segfaults when I delete components on FC5 (and other Linux distributions)! Is there a work-around?</a></h2>
<div class="level2">
@@ -936,7 +941,7 @@ csh:
<pre class="code">setenv G_SLICE always-malloc</pre>
</div>
-<!-- SECTION "Gschem segfaults when I delete components on FC5 (and other Linux distributions)! Is there a work-around?" [29882-30536] -->
+<!-- SECTION "Gschem segfaults when I delete components on FC5 (and other Linux distributions)! Is there a work-around?" [30121-30775] -->
<h2><a name="after_installation_gschem_does_not_work_what_could_be_wrong" id="after_installation_gschem_does_not_work_what_could_be_wrong">After installation gschem does not work!? What could be wrong?</a></h2>
<div class="level2">
@@ -974,7 +979,7 @@ Also, some older releases of gEDA/gaf had some bugs when the rc files were insta
</p>
</div>
-<!-- SECTION "After installation gschem does not work!? What could be wrong?" [30537-32461] -->
+<!-- SECTION "After installation gschem does not work!? What could be wrong?" [30776-32700] -->
<h2><a name="add_components_offers_no_symbols_what_can_i_do_about_it" id="add_components_offers_no_symbols_what_can_i_do_about_it">"Add Components" offers no symbols! What can I do about it?</a></h2>
<div class="level2">
@@ -1008,7 +1013,7 @@ All of these config files may or may not append paths to the library search list
</p>
</div>
-<!-- SECTION "Add Components offers no symbols! What can I do about it?" [32462-33420] -->
+<!-- SECTION "Add Components offers no symbols! What can I do about it?" [32701-33659] -->
<h2><a name="i_m_using_gschem_gaf_through_a_ssh_connection_and_i_get_an_error_likexlibextension_render_missing_on_display_localhost10.0" id="i_m_using_gschem_gaf_through_a_ssh_connection_and_i_get_an_error_likexlibextension_render_missing_on_display_localhost10.0">I'm using gschem/gaf through a SSH connection and I get an error like: 'Xlib: extension "RENDER" missing on display "localhost:10.0".'</a></h2>
<div class="level2">
@@ -1027,5 +1032,5 @@ The latter enables trusted X11 forwarding.
</p>
</div>
-<!-- SECTION "I'm using gschem/gaf through a SSH connection and I get an error like: 'Xlib: extension RENDER missing on display localhost:10.0.'" [33421-] --></body>
+<!-- SECTION "I'm using gschem/gaf through a SSH connection and I get an error like: 'Xlib: extension RENDER missing on display localhost:10.0.'" [33660-] --></body>
</html>
diff --git a/docs/wiki/geda-file_format_spec.html b/docs/wiki/geda-file_format_spec.html
index 779c5cd..e408185 100644
--- a/docs/wiki/geda-file_format_spec.html
+++ b/docs/wiki/geda-file_format_spec.html
@@ -145,7 +145,7 @@ A schematic/symbol file for gEDA/gaf consists of:
</p>
</div>
-<!-- SECTION "Object types" [2247-3517] -->
+<!-- SECTION "Object types" [2247-3519] -->
<h3><a name="version" id="version">version</a></h3>
<div class="level3">
@@ -186,9 +186,9 @@ Valid in: Schematic and Symbol files<br/>
</li>
<li class="level1"><div class="li"> fileformat version is just an integer with no minor number.</div>
</li>
-<li class="level1"><div class="li"> Development versions include: 19990601, 19990610, 19990705, 19990829, 19990919, 19991011, 20000220, 20000704, 20001006, 20001217, 20010304, 20010708, 20010722, 20020209, 20020414, 20020527, 20020825, 20021103, 20030223, 20030525, 20030901, 20040111, 20040710, 20041228, 20050313, 20050820, 20060123, 20060824, 20060906, 20061020, 20070216, 20070705, 20070708, 20070818, 20071229, 20080110</div>
+<li class="level1"><div class="li"> Development versions include: 19990601, 19990610, 19990705, 19990829, 19990919, 19991011, 20000220, 20000704, 20001006, 20001217, 20010304, 20010708, 20010722, 20020209, 20020414, 20020527, 20020825, 20021103, 20030223, 20030525, 20030901, 20040111, 20040710, 20041228, 20050313, 20050820, 20060123, 20060824, 20060906, 20061020, 20070216, 20070705, 20070708, 20070818, 20071229, 20080110, 20080127, 20080706, 20081220, 20081221, 20090328, 20090829, 20090830</div>
</li>
-<li class="level1"><div class="li"> Stable versions include: 20070526, 20070626, 20070902, 20071231, 20080127</div>
+<li class="level1"><div class="li"> Stable versions include: 20070526, 20070626, 20070902, 20071231, 20080127, 20080929, 20081220, 20081231, 20091004, 20100214</div>
</li>
<li class="level1"><div class="li"> <acronym title="Concurrent Versions System">CVS</acronym> or test versions (should not be used): 20030921, 20031004, 20031019, 20031231, 20050814</div>
</li>
@@ -203,7 +203,7 @@ Valid in: Schematic and Symbol files<br/>
<pre class="code">v 20040111 1</pre>
</div>
-<!-- SECTION "version" [3518-5475] -->
+<!-- SECTION "version" [3520-5597] -->
<h3><a name="line" id="line">line</a></h3>
<div class="level3">
@@ -291,7 +291,7 @@ A line segment from (23000, 69000) to (28000, 69000) with color index 3, 40 mils
</p>
</div>
-<!-- SECTION "line" [5476-6710] -->
+<!-- SECTION "line" [5598-6832] -->
<h3><a name="picture" id="picture">picture</a></h3>
<div class="level3">
@@ -401,7 +401,7 @@ A picture object with the lower left corner at (16900, 35800). The width of the
</p>
</div>
-<!-- SECTION "picture" [6711-9504] -->
+<!-- SECTION "picture" [6833-9626] -->
<h3><a name="box" id="box">box</a></h3>
<div class="level3">
@@ -530,7 +530,7 @@ A box with the lower left hand corner at (33000, 67300) and a width and height o
</p>
</div>
-<!-- SECTION "box" [9505-11711] -->
+<!-- SECTION "box" [9627-11833] -->
<h3><a name="circle" id="circle">circle</a></h3>
<div class="level3">
@@ -646,7 +646,7 @@ A circle with the center at (38000, 67000) and a radius of 900 mils, color index
</p>
</div>
-<!-- SECTION "circle" [11712-13837] -->
+<!-- SECTION "circle" [11834-13959] -->
<h3><a name="arc" id="arc">arc</a></h3>
<div class="level3">
@@ -742,7 +742,7 @@ dashlength dashspace</code></strong>
</p>
</div>
-<!-- SECTION "arc" [13838-15354] -->
+<!-- SECTION "arc" [13960-15476] -->
<h3><a name="text" id="text">text</a></h3>
<div class="level3">
@@ -889,7 +889,7 @@ A text object with the origin at (10000, 20000), color index 3, 10 points in siz
</p>
</div>
-<!-- SECTION "text" [15355-18509] -->
+<!-- SECTION "text" [15477-18631] -->
<h3><a name="net" id="net">net</a></h3>
<div class="level3">
@@ -938,7 +938,7 @@ A net segment from (12700, 29400) to (32900, 29400) with color index 4.
</p>
</div>
-<!-- SECTION "net" [18510-19035] -->
+<!-- SECTION "net" [18632-19157] -->
<h3><a name="bus" id="bus">bus</a></h3>
<div class="level3">
@@ -994,7 +994,7 @@ A bus segment from (27300, 37400) to (27300, 35300) with color index 3 and no ne
</p>
</div>
-<!-- SECTION "bus" [19036-19967] -->
+<!-- SECTION "bus" [19158-20089] -->
<h3><a name="pin" id="pin">pin</a></h3>
<div class="level3">
@@ -1061,7 +1061,7 @@ A pin from (0, 200) to (200, 200) with color index 1, a regular pin, and the fir
</p>
</div>
-<!-- SECTION "pin" [19968-20964] -->
+<!-- SECTION "pin" [20090-21086] -->
<h3><a name="component" id="component">component</a></h3>
<div class="level3">
@@ -1123,7 +1123,7 @@ A component whoâ??s origin is at (18600,19900), is selectable, not rotated, not
</p>
</div>
-<!-- SECTION "component" [20965-21969] -->
+<!-- SECTION "component" [21087-22091] -->
<h3><a name="path" id="path">path</a></h3>
<div class="level3">
@@ -1274,7 +1274,7 @@ A path starting at (410,240) with lines drawn from there, and joining points (50
</p>
</div>
-<!-- SECTION "path" [21970-24820] -->
+<!-- SECTION "path" [22092-24942] -->
<h3><a name="font" id="font">font</a></h3>
<div class="level3">
@@ -1317,7 +1317,7 @@ The above font definition is for the space character.
</p>
</div>
-<!-- SECTION "font" [24821-25342] -->
+<!-- SECTION "font" [24943-25464] -->
<h2><a name="colors" id="colors">Colors</a></h2>
<div class="level2">
@@ -1407,7 +1407,7 @@ In the gEDA/gaf schematic and symbol file format colors are specified via an int
</p>
</div>
-<!-- SECTION "Colors" [25343-26381] -->
+<!-- SECTION "Colors" [25465-26503] -->
<h2><a name="attributes" id="attributes">Attributes</a></h2>
<div class="level2">
@@ -1429,7 +1429,7 @@ The object is a pin which has an attribute pinnumber=3 and pinseq=3 (name=value)
</p>
</div>
-<!-- SECTION "Attributes" [26382-27369] -->
+<!-- SECTION "Attributes" [26504-27491] -->
<h2><a name="embedded_components" id="embedded_components">Embedded Components</a></h2>
<div class="level2">
@@ -1448,7 +1448,7 @@ In the example above, <strong>555-1.sym</strong> is the component. The EMBEDDED
</p>
</div>
-<!-- SECTION "Embedded Components" [27370-28134] -->
+<!-- SECTION "Embedded Components" [27492-28256] -->
<h2><a name="path_data" id="path_data">Path data</a></h2>
<div class="level2">
@@ -1537,7 +1537,7 @@ The resulting path (with control points drawn on to illustrate their positions)
</p>
</div>
-<!-- SECTION "Path data" [28135-31563] -->
+<!-- SECTION "Path data" [28257-31685] -->
<h2><a name="document_revision_history" id="document_revision_history">Document Revision History</a></h2>
<div class="level2">
<table class="inline">
@@ -1559,5 +1559,5 @@ The resulting path (with control points drawn on to illustrate their positions)
</table>
</div>
-<!-- SECTION "Document Revision History" [31564-] --></body>
+<!-- SECTION "Document Revision History" [31686-] --></body>
</html>
diff --git a/docs/wiki/geda-gnetlist_scheme_tutorial.html b/docs/wiki/geda-gnetlist_scheme_tutorial.html
new file mode 100644
index 0000000..33306cf
--- /dev/null
+++ b/docs/wiki/geda-gnetlist_scheme_tutorial.html
@@ -0,0 +1,290 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+
+
+
+<h1><a name="scripting_a_gnetlist_backend_in_scheme" id="scripting_a_gnetlist_backend_in_scheme">Scripting a gnetlist backend in Scheme</a></h1>
+<div class="level1">
+
+<p>
+ <strong>by John Doty</strong>
+</p>
+
+<p>
+(this was <a href="http://archives.seul.org/geda/user/Jul-2009/msg00235.html"; class="urlextern" title="http://archives.seul.org/geda/user/Jul-2009/msg00235.html"; rel="nofollow">originally posted</a> to the gEDA-user mailing list in July 2009)
+</p>
+
+<p>
+Donâ??t Panic!
+</p>
+
+<p>
+If youâ??ve never written a program in Lisp, it looks daunting. But itâ??s a lot easier than it looks. Wrap a little bit of â??syntactic sugarâ?? around Lisp, and it becomes Logo, which elementary school children can learn.
+</p>
+
+<p>
+And, just to make it clear what some of the funny words mean, <a href="http://en.wikipedia.org/wiki/Lisp_%28programming_language%29"; class="interwiki iw_wp" title="http://en.wikipedia.org/wiki/Lisp_%28programming_language%29";>Lisp</a> is a computer language, <a href="http://en.wikipedia.org/wiki/Scheme_%28programming_language%29"; class="interwiki iw_wp" title="http://en.wikipedia.org/wiki/Scheme_%28programming_language%29";>Scheme</a> is a dialect of Lisp, and <a href="http://en.wikipedia.org/wiki/GNU_Guile"; class="interwiki iw_wp" title="http://en.wikipedia.org/wiki/GNU_Guile";>Guile</a> is an implementation of Scheme. Guile is used for â??scriptingâ?? gEDA. In particular, the gnetlist front end, written in C, extracts topology and attribute information from schematics, and then presents that data to â??back endâ?? Guile scripts for processing and output.
+</p>
+
+<p>
+This tutorial is specifically about programming gnetlist back ends in Scheme. If you donâ??t already know Scheme, you should probably look at other material too, such as:
+</p>
+
+<p>
+<a href="http://www.ccs.neu.edu/home/dorai/t-y-scheme/t-y-scheme.html"; class="urlextern" title="http://www.ccs.neu.edu/home/dorai/t-y-scheme/t-y-scheme.html"; rel="nofollow">http://www.ccs.neu.edu/home/dorai/t-y-scheme/t-y-scheme.html</a>
+</p>
+
+<p>
+Or look up â??Scheme tutorialâ?? with your favorite engine: there are many.
+</p>
+
+<p>
+The reference document at:
+</p>
+
+<p>
+<a href="http://www.gnu.org/software/guile/manual/html_node/index.html"; class="urlextern" title="http://www.gnu.org/software/guile/manual/html_node/index.html"; rel="nofollow">http://www.gnu.org/software/guile/manual/html_node/index.html</a>
+</p>
+
+<p>
+may also be useful.
+</p>
+
+<p>
+OK, letâ??s get started. Hereâ??s a particularly simple back end:
+</p>
+<pre class="code scheme"><span class="co1">;; gnetlist development playground</span>
+
+<span class="br0">(</span>use-modules <span class="br0">(</span>ice<span class="nu0">-9</span> readline<span class="br0">)</span><span class="br0">)</span>
+<span class="br0">(</span>activate-readline<span class="br0">)</span>
+
+<span class="br0">(</span><span class="kw1">define</span> <span class="br0">(</span>devel output-filename<span class="br0">)</span>
+ <span class="br0">(</span>scm-style-repl<span class="br0">)</span>
+<span class="br0">)</span></pre>
+<p>
+To use this, put it in a file called <code>gnet-devel.scm</code>. Copy this file to wherever gnetlist Scheme files are kept on your system. On the machine Iâ??m using today, the command is:
+</p>
+<pre class="code bash">$ sudo cp gnet-devel.scm /sw/share/gEDA/scheme/</pre>
+<p>
+The <code>â??/sw/"</code> will be <code>â??/usr/"</code> for most Linux package installations, maybe <code>â??/usr/localâ??</code> or <code>â??~/mygeda/"</code> for a tarball installation. Youâ??ll have to figure that out. If the target location is writable by you without superuser privileges, you wonâ??t need the <code>â??sudoâ??</code>.
+</p>
+
+<p>
+Now, translating <code>â??/sw/"</code> as needed, type:
+</p>
+<pre class="code bash">$ gnetlist -g devel /sw/share/gEDA/examples/lightning_detector/lightning.sch</pre>
+<p>
+You should see the usual gnetlist boiler plate, followed by:
+</p>
+<pre class="code">
+guile>
+</pre>
+
+<p>
+Try:
+</p>
+<pre class="code">
+guile> packages
+</pre>
+
+<p>
+You should see:
+</p>
+<pre class="code scheme"><span class="br0">(</span><span class="st0">"Q3"</span> <span class="st0">"R5"</span> <span class="st0">"Q2"</span> <span class="st0">"R4"</span> <span class="st0">"Q1"</span> <span class="st0">"C6"</span> <span class="st0">"R3"</span> <span class="st0">"L2"</span> <span class="st0">"A1"</span> <span class="st0">"bat(+3v)"</span> <span class="st0">"lamp(1)"</span> <span class="st0">"R2"</span> <span class="st0">"C5"</span> <span class="st0">"L1"</span> <span class="st0">"R1"</span> <span class="st0">"C4"</span> <span class="st0">"lamp(2)"</span> <span class="st0">"C3"</span> <span class="st0">"C2"</span> <span class="st0">"C1"</span> <span class="st0">"D1"</span> <span class="st0">"bat(0v)"</span> <span class="st0">"R7"</span> <span class="st0">"Q4"</span> <span class="st0">"R6"</span><span class="br0">)</span></pre>
+<p>
+<code>â??packagesâ??</code> is a handy variable, containing a list of all unique <code>â??refdes="</code> attribute values. By typing it, you fed it to the â??REPLâ??, the Read, Evaluate, Print Loop. So, the REPL read it, evaluated it (getting a list), and printed it.
+</p>
+
+<p>
+Now try:
+</p>
+<pre class="code">
+guile> (length packages)
+25
+</pre>
+
+<p>
+What happened here? Here, the REPL evaluated the list
+</p>
+<pre class="code scheme"><span class="br0">(</span><span class="kw1">length</span> packages<span class="br0">)</span></pre>
+<p>
+In most programming languages, youâ??d write this expression in more traditional functional notation as <code>â??length( packages )"</code>. <code>â??lengthâ??</code> is a function, which tells you the length of a list.
+</p>
+
+<p>
+Use the same notation to do arithmetic. For example, calculate â??2+3â?? as:
+</p>
+<pre class="code">
+guile> (+ 2 3)
+5
+</pre>
+
+<p>
+Note that the procedure "+" can be used to add any number of quantities, including none at all:
+</p>
+<pre class="code">
+guile> (+)
+0
+guile> (+ 1 2 3)
+6
+</pre>
+
+<p>
+Weâ??ll make use of this later on.
+</p>
+
+<p>
+The readline stuff in our <code>gnet-devel.scm</code> back end allows you to use the cursor keys on your keyboard to move around through the history and edit input. Very handy when interacting. Try it.
+</p>
+
+<p>
+Another useful variable gnetlist defines is <code>â??all-unique-netsâ??</code> (type it). Just as <code>â??(length packages)"</code> tells you how many packages you have, <code>â??(length all-unique-nets)"</code> will tell you how many nets you have.
+</p>
+
+<p>
+Then thereâ??s <code>all-pins</code>:
+</p>
+<pre class="code">
+guile> all-pins
+(("1" "2" "3") ("2" "3" "1") ("2" "1") ("1" "2") ("1" "2") ("1" "2") ("1" "2") ("1" "2") ("1" "2") ("2" "1") ("2" "1") ("2" "1") ("1" "2") ("2" "1") ("1") ("1") ("2" "1") ("2" "3" "1") ("2" "3" "1") ("1") ("2" "1") ("2" "3" "1") ("1" "2") ("1") ("1"))
+</pre>
+
+<p>
+Note that this is a little more complicated than the previous examples: itâ??s a list of lists, not just a list of strings. Each of the lists corresponds to the pins on one package. One thing we might want to extract from this is a count of the number of pins. We canâ??t just take the length of <code>all-pins</code> to get this: that gives us the number of lists it contains, which is the number of packages:
+</p>
+<pre class="code">
+guile> (length all-pins)
+25
+</pre>
+
+<p>
+To get the pin count, first get the individual pin counts for each package:
+</p>
+<pre class="code">
+guile> (map length all-pins)
+(3 3 2 2 2 2 2 2 2 2 2 2 2 2 1 1 2 3 3 1 2 3 2 1 1)
+</pre>
+
+<p>
+This is one of the easy ways to do a â??loopâ?? in Scheme; <code>(map p x)</code> yields a list of the results of calling procedure <code>p</code> individually for each element of <code>x</code>. Then we can add them up with a slightly different kind of â??loopâ??:
+</p>
+<pre class="code">
+guile> (apply + (map length all-pins))
+50
+</pre>
+
+<p>
+(apply p x) calls procedure p once, with all of the elements of x as arguments. So the expression above winds up evaluating:
+</p>
+<pre class="code scheme"><span class="br0">(</span>+ <span class="nu0">3</span> <span class="nu0">3</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">2</span> <span class="nu0">1</span> <span class="nu0">1</span> <span class="nu0">2</span> <span class="nu0">3</span> <span class="nu0">3</span> <span class="nu0">1</span> <span class="nu0">2</span> <span class="nu0">3</span> <span class="nu0">2</span> <span class="nu0">1</span> <span class="nu0">1</span><span class="br0">)</span></pre>
+<p>
+Thus far weâ??ve been using predefined variables and procedures. Weâ??ll want to be able to define our own. Itâ??s easy:
+</p>
+<pre class="code">
+guile> (define the-answer 42)
+guile> the-answer
+42
+</pre>
+
+<p>
+This defines a variable, <code>the-answer</code>, and gives it the value 42.
+</p>
+
+<p>
+We can also define procedures:
+</p>
+<pre class="code">
+guile> (define add1 (lambda (x) (+ x 1)))
+guile> (add1 100)
+101
+</pre>
+
+<p>
+When you see <code>â??lambdaâ??</code> think â??procedureâ??. The first thing (the technical term is â??formâ??) following <code>â??lambdaâ??</code> is a list of the arguments of the procedure, in this case <code>â??(x)"</code>. When the the procedure is called, Guile evaluates the remaining forms, in this case just one, <code>â??(+ x 1)"</code>, with actual arguments substituted. The result of the procedure is the result of evaluating the last form. So, <code>â??(add1 100)"</code> becomes <code>â??(+ 100 1)"</code>, which evaluates to 101.
+</p>
+
+<p>
+Now we can put our statistics collection together into a back end. First, define a procedure to write a line of output:
+</p>
+<pre class="code scheme"><span class="br0">(</span><span class="kw1">define</span> format-line
+ <span class="br0">(</span><span class="kw1">lambda</span> <span class="br0">(</span>name value<span class="br0">)</span>
+ <span class="br0">(</span><span class="kw1">display</span> name<span class="br0">)</span>
+ <span class="br0">(</span><span class="kw1">display</span> value<span class="br0">)</span>
+ <span class="br0">(</span><span class="kw1">newline</span><span class="br0">)</span>
+ <span class="br0">)</span>
+<span class="br0">)</span></pre>
+<p>
+Weâ??re using two new builtin procedures here, <code>â??displayâ??</code> and <code>â??newlineâ??</code>, which should be self-explanatory. Now:
+</p>
+<pre class="code scheme"><span class="br0">(</span><span class="kw1">define</span> display-stats
+ <span class="br0">(</span><span class="kw1">lambda</span> <span class="br0">(</span><span class="br0">)</span> <span class="co1">; no arguments</span>
+ <span class="br0">(</span>format-line <span class="st0">"pins: "</span> <span class="br0">(</span>apply + <span class="br0">(</span><span class="kw1">map</span> <span class="kw1">length</span> all-pins<span class="br0">)</span><span class="br0">)</span><span class="br0">)</span>
+ <span class="br0">(</span>format-line <span class="st0">"packages: "</span> <span class="br0">(</span><span class="kw1">length</span> packages<span class="br0">)</span><span class="br0">)</span>
+ <span class="br0">(</span>format-line <span class="st0">"nets: "</span> <span class="br0">(</span><span class="kw1">length</span> all-unique-nets<span class="br0">)</span><span class="br0">)</span>
+ <span class="br0">)</span>
+<span class="br0">)</span></pre><pre class="code">
+guile> (display-stats)
+pins: 50
+packages: 25
+nets: 13
+</pre>
+
+<p>
+To finish off a back end, we need a â??main programâ??. By convention, that has the name of the back end. It has the responsibility of opening the output file, too. So, for a â??statsâ?? back end for collecting the stats, the entire file looks like:
+</p>
+<pre class="code scheme"><span class="co1">;; gnetlist back end for extracting design statistics</span>
+<span class="co1">;;</span>
+<span class="co1">;; Legal boilerplate here as needed</span>
+
+<span class="br0">(</span><span class="kw1">define</span> stats
+ <span class="br0">(</span><span class="kw1">lambda</span> <span class="br0">(</span>filename<span class="br0">)</span>
+ <span class="br0">(</span>set-<span class="kw1">current-output-port</span> <span class="br0">(</span><span class="kw1">open-output-file</span> filename<span class="br0">)</span><span class="br0">)</span>
+ <span class="br0">(</span>display-stats<span class="br0">)</span>
+ <span class="br0">)</span>
+<span class="br0">)</span>
+
+<span class="co1">;; Collect and output the statistics</span>
+
+<span class="br0">(</span><span class="kw1">define</span> display-stats
+ <span class="br0">(</span><span class="kw1">lambda</span> <span class="br0">(</span><span class="br0">)</span> <span class="co1">; no arguments</span>
+ <span class="br0">(</span>format-line <span class="st0">"pins: "</span> <span class="br0">(</span>apply + <span class="br0">(</span><span class="kw1">map</span> <span class="kw1">length</span> all-pins<span class="br0">)</span><span class="br0">)</span><span class="br0">)</span>
+ <span class="br0">(</span>format-line <span class="st0">"packages: "</span> <span class="br0">(</span><span class="kw1">length</span> packages<span class="br0">)</span><span class="br0">)</span>
+ <span class="br0">(</span>format-line <span class="st0">"nets: "</span> <span class="br0">(</span><span class="kw1">length</span> all-unique-nets<span class="br0">)</span><span class="br0">)</span>
+ <span class="br0">)</span>
+<span class="br0">)</span>
+
+<span class="co1">;; Simple output format</span>
+
+<span class="br0">(</span><span class="kw1">define</span> format-line
+ <span class="br0">(</span><span class="kw1">lambda</span> <span class="br0">(</span>name value<span class="br0">)</span>
+ <span class="br0">(</span><span class="kw1">display</span> name<span class="br0">)</span>
+ <span class="br0">(</span><span class="kw1">display</span> value<span class="br0">)</span>
+ <span class="br0">(</span><span class="kw1">newline</span><span class="br0">)</span>
+ <span class="br0">)</span>
+<span class="br0">)</span></pre>
+<p>
+Put this in a file named <code>gnet-stats.scm</code>, copy it to where it belongs with something like
+</p>
+<pre class="code bash">$ sudo cp gnet-stats.scm /sw/share/gEDA/scheme/</pre>
+<p>
+ and then <code>â??gnetlist -g statsâ??</code> followed by the usual other arguments and schematic pathnames will put your designâ??s statistics in the output file (default <code>output.net</code>).
+</p>
+
+<p>
+Pretty easy, huh? Useful, too. Lately Iâ??ve been designing systems that consist of stacks of boards: statistics like these are helpful in figuring out which subsystems I should combine on each board.
+</p>
+
+</div>
+</body>
+</html>
diff --git a/docs/wiki/geda-gparts_dd.html b/docs/wiki/geda-gparts_dd.html
new file mode 100644
index 0000000..fbba04f
--- /dev/null
+++ b/docs/wiki/geda-gparts_dd.html
@@ -0,0 +1,1457 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<div class="toc">
+<div class="tocheader toctoggle" id="toc__header">Table of Contents</div>
+<div id="toc__inside">
+
+<ul class="toc">
+<li class="level1"><div class="li"><span class="li"><a href="#part_manager" class="toc">Part Manager</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#part_database" class="toc">Part Database</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#entities" class="toc">Entities</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#part_categories" class="toc">Part Categories</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#part_hierarchy" class="toc">Part Hierarchy</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#part_manager_gui" class="toc">Part Manager GUI</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#use_cases" class="toc">Use Cases</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#ui_design" class="toc">UI Design</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#configuration" class="toc">Configuration</a></span></div></li></ul>
+</li></ul>
+</li></ul>
+</div>
+</div>
+
+<p>
+This page serves as a working document for the design of a parts manager for gEDA. Please submit feedback to the geda-dev or geda-user mailing lists.
+</p>
+
+
+
+<h1><a name="part_manager" id="part_manager">Part Manager</a></h1>
+<div class="level1">
+
+<p>
+ The part manager uses a relational database to store parts used in the development of electronic assemblies. The part manager also stores attributes for these parts and can place these attributes into a component or symbol for placement into schematics.
+</p>
+
+<p>
+The part manager provides a <acronym title="Graphical User Interface">GUI</acronym> that allows the user to browse and edit the data in the part database. The user can select parts in the <acronym title="Graphical User Interface">GUI</acronym>, then cut and paste them into their schematic.
+</p>
+
+<p>
+The following figure shows the relationship between the parts manager and other applications in the gEDA suite.
+</p>
+
+<p>
+<a href="media/geda/gparts-flow-2.png" class="media" target="_blank" title="geda:gparts-flow-2.png"><img src="media/geda/gparts-flow-2.png" class="media" title="" alt="" /></a>
+</p>
+
+<p>
+The part database can be configured as either local or remote. In the remote configuration, many users can access the part database concurrently.
+</p>
+
+</div>
+<!-- SECTION "Part Manager" [152-914] -->
+<h2><a name="part_database" id="part_database">Part Database</a></h2>
+<div class="level2">
+
+<p>
+ The following figure shows the entity relationships for a part in the resistor category. The category does not reference any tables in the resistor category, but only contains the view name and stored procedures to manipulate a part within the resistor category. This mechanism allows the tables and relationships to vary by category.
+</p>
+
+<p>
+<a href="media/geda/gparts_erd_main.png" class="media" target="_blank" title="geda:gparts_erd_main.png"><img src="media/geda/gparts_erd_main.png" class="media" title="" alt="" /></a>
+</p>
+
+</div>
+<!-- SECTION "Part Database" [915-1308] -->
+<h3><a name="entities" id="entities">Entities</a></h3>
+<div class="level3">
+
+<p>
+ The database always contains tables to store the following entities. The database contains additional tables to store specific categories of parts (e.g. a capacitor table, a diode table, a resistor table, etc…). This list excludes junction tables and metadata tables.
+</p>
+
+</div>
+
+<h4><a name="category" id="category">Category</a></h4>
+<div class="level4">
+
+<p>
+ A class of parts (e.g. capacitors, diodes, resistors, transistors, etc…). A category can contain sub-categories (e.g. small-signal diodes, TVS diodes, zener diodes, etc…) Sub-categories can include additional sub-categories. All parts within a category or sub-category share the same set of attributes (e.g. forward voltage, maximum current, power dissipation, etc…). Sub-categories do not need to inherit the attributes of their parent.
+</p>
+
+<p>
+The category stores metadata for mapping the partâ??s database columns to the component attributes. For numeric attributes, the category stores the columnâ??s unit of measure (e.g. amps, farads, ohms, volts, etc…).
+</p>
+
+<p>
+The category also stores the names of database views and stored procedures to access and manipulate the tables of parts within the category.
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th class="leftalign"> Description </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> CategoryID </td><td class="rightalign"> </td><td class="leftalign"> Surrogate key </td>
+ </tr>
+ <tr>
+ <td> CategoryName </td><td> String </td><td> The unique name of the category </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> ParentID </td><td class="rightalign"> </td><td class="leftalign"> Foreign key to Category </td>
+ </tr>
+</table>
+
+</div>
+
+<h4><a name="company" id="company">Company</a></h4>
+<div class="level4">
+
+<p>
+ Currently, a company represents a partâ??s manufacturer.
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th class="leftalign"> Description </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> CompanyID </td><td class="rightalign"> </td><td class="leftalign"> Surrogate key </td>
+ </tr>
+ <tr>
+ <td> CompanyName </td><td> String </td><td> The unique name of the company </td>
+ </tr>
+</table>
+
+</div>
+
+<h4><a name="device" id="device">Device</a></h4>
+<div class="level4">
+
+<p>
+ A type of part. The device name only provides a mechanism to map parts to symbols. A part in the library of device resistor can use all the symbols in the library where device is resistor. Similarly, a symbol where device is resistor can represent any part of device resistor. When importing a symbol, the database uses the value of the symbol attribute DEVICE as the initial value for the device field. The user can change the device field after import using the part manager <acronym title="Graphical User Interface">GUI</acronym>.
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th class="leftalign"> Description </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> DeviceID </td><td class="rightalign"> </td><td class="leftalign"> Surrogate key </td>
+ </tr>
+ <tr>
+ <td> DeviceName </td><td> String </td><td> The unique name of the device </td>
+ </tr>
+</table>
+
+</div>
+
+<h4><a name="document" id="document">Document</a></h4>
+<div class="level4">
+
+<p>
+ Any file associated with a part. Documents can include datasheets, erata, user manuals, etc… This entity stores a path to the actual document file. The path could either be local or network. The path stored in the database is relative to the base path stored in the configuration file.
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th class="leftalign"> Description </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> DocumentID </td><td class="rightalign"> </td><td class="leftalign"> Surrogate key </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Category </td><td> String </td><td> The documentâ??s category (e.g. â??Datasheetâ??, â??Erataâ??, â??User Manualâ??) </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Title </td><td> String </td><td class="leftalign"> The documentâ??s title </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> SourceURL </td><td> String </td><td class="leftalign"> The <acronym title="Uniform Resource Locator">URL</acronym> where the document can be obtained on the Internet </td>
+ </tr>
+ <tr>
+ <td> FileLocation </td><td> String </td><td class="leftalign"> The location of the locally stored document </td>
+ </tr>
+</table>
+
+</div>
+
+<h4><a name="footprint" id="footprint">Footprint</a></h4>
+<div class="level4">
+
+<p>
+ The PCB artwork associated with a package. This entity stores a path to the actual PCB footprint file. The path could either be local or network. The path stored in the database is relative to the base path stored in the configuration file.
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th class="leftalign"> Description </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> FootprintID </td><td class="rightalign"> </td><td class="leftalign"> Surrogate key </td>
+ </tr>
+ <tr>
+ <td> FootprintName </td><td> String </td><td> The unique name of the footprint </td>
+ </tr>
+</table>
+
+</div>
+
+<h4><a name="model" id="model">Model</a></h4>
+<div class="level4">
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th class="leftalign"> Description </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> ModelID </td><td class="rightalign"> </td><td class="leftalign"> Surrogate key </td>
+ </tr>
+ <tr>
+ <td> ModelName </td><td> String </td><td class="leftalign"> The name of the MODEL within the model file. </td>
+ </tr>
+ <tr>
+ <td> ModelPath </td><td> String </td><td class="leftalign"> Absolute path to the model file. </td>
+ </tr>
+ <tr>
+ <td> ModelType </td><td> String </td><td class="leftalign"> The model type: IBIS, PSPICE, etc… </td>
+ </tr>
+</table>
+
+</div>
+
+<h5><a name="spice" id="spice">Spice</a></h5>
+<div class="level5">
+
+<p>
+ When instantiating a component or creating a heavy symbol that uses a Spice model, the following database columns map to the following attributes.
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Column </th><th class="leftalign"> Attribute </th><th class="leftalign"> Notes </th>
+ </tr>
+ <tr>
+ <td> Model.ModelName </td><td> MODEL-NAME </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td> Model.ModelPath </td><td class="leftalign"> FILE </td><td> Should use absolute path. </td>
+ </tr>
+</table>
+
+</div>
+
+<h4><a name="part_flat" id="part_flat">Part (Flat)</a></h4>
+<div class="level4">
+
+<p>
+ A part represents a class of components. The database uses this version of the part table when configured to use a flat part table. The flat and hierarchical parts tables are mutually exclusive. The database uses one or the other.
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Field </th><th> Type </th><th class="leftalign"> Description </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> PartID </td><td class="rightalign"> </td><td class="leftalign"> Surrogate key </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> CompanyID </td><td class="rightalign"> </td><td> Foreign key to company specifies manufacturer </td>
+ </tr>
+ <tr>
+ <td> PartNumber </td><td> String </td><td class="leftalign"> The manufacturersâ??s part number </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> DeviceID </td><td class="rightalign"> </td><td class="leftalign"> Foreign key to Device </td>
+ </tr>
+</table>
+
+<p>
+ Other columns TBD.
+</p>
+
+</div>
+
+<h4><a name="part_hierarchical" id="part_hierarchical">Part (Hierarchical)</a></h4>
+<div class="level4">
+
+<p>
+ A part represents a class of components. The database uses this version of the part table when configured to use hierarchical part tables. The flat and hierarchical parts tables are mutually exclusive. The database uses one or the other.
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Field </th><th> Type </th><th class="leftalign"> Description </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> PartID </td><td class="rightalign"> </td><td class="leftalign"> Surrogate key </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> CompanyID </td><td class="rightalign"> </td><td> Foreign key to company specifies manufacturer </td>
+ </tr>
+ <tr>
+ <td> PartNumber </td><td> String </td><td class="leftalign"> The manufacturersâ??s part number </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> DeviceID </td><td class="rightalign"> </td><td class="leftalign"> Foreign key to Device </td>
+ </tr>
+</table>
+
+</div>
+
+<h4><a name="package" id="package">Package</a></h4>
+<div class="level4">
+
+<p>
+ The physical structure, or form-factor, of a part (i.e. 0603, SOT-23, PDIP16). Each package can associate with zero or more footprints. Also, each footprint could represent zero or more packages.
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th class="leftalign"> Description </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> PackageID </td><td class="rightalign"> </td><td class="leftalign"> Surrogate key </td>
+ </tr>
+ <tr>
+ <td> PackageName </td><td> String </td><td class="leftalign"> The unique name of the package </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Technology </td><td> String </td><td> The type of package. Either â??SMTâ?? or â??THâ?? </td>
+ </tr>
+</table>
+
+</div>
+
+<h4><a name="symbol" id="symbol">Symbol</a></h4>
+<div class="level4">
+
+<p>
+ The graphical representation of a part. This entity uses the symbol base filename as the unique name of the symbol. This base filename is relative to one of the component libraries found in the configuration files. The component library paths can either be local or network.
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th class="leftalign"> Description </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> SymbolID </td><td class="rightalign"> </td><td class="leftalign"> Surrogate key </td>
+ </tr>
+ <tr>
+ <td> SymbolName </td><td> String </td><td> The unique name of the symbol. This field contains the base filename of the symbol. </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> DeviceID </td><td class="rightalign"> </td><td class="leftalign"> Foreign key to Device </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "Entities" [1309-8103] -->
+<h3><a name="part_categories" id="part_categories">Part Categories</a></h3>
+<div class="level3">
+
+<p>
+ Part categories break down classes of parts hierarchically. The category hierarchy exists separately than the part hierarchy. The category hierarchy only provides the user with a system to locate parts quickly. A child in the category hierarchy does not need to inherit the attributes of a parent.
+</p>
+
+<p>
+The parts manager uses categories to keep the lists of parts manageable. If the list of parts in a particular category grows large, the category can be subdivided into sub-categories.
+</p>
+
+<p>
+It may be difficult to change the categories, using a <acronym title="Graphical User Interface">GUI</acronym>, because of the part table abstraction through database views and stored procedures. It may be better to distribute the parts manager with a default configuration that works for most.
+</p>
+
+<div class="noteclassic">Help is needed with the taxonomy of parts. Please send feedback to the geda-dev or geda-user mailing lists.
+</div>
+
+<p>
+The default hierarchy of parts follow:
+</p>
+<ul>
+<li class="level1"><div class="li"> Discretes</div>
+<ul>
+<li class="level2"><div class="li"> Diodes</div>
+<ul>
+<li class="level3"><div class="li"> Small-signal</div>
+</li>
+<li class="level3"><div class="li"> TVS</div>
+</li>
+<li class="level3"><div class="li"> Zeners</div>
+</li>
+</ul>
+</li>
+</ul>
+</li>
+<li class="level1"><div class="li"> Passives</div>
+<ul>
+<li class="level2"><div class="li"> Capacitors</div>
+</li>
+<li class="level2"><div class="li"> Inductors</div>
+</li>
+<li class="level2"><div class="li"> Resistors</div>
+</li>
+</ul>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Part Categories" [8104-9162] -->
+<h3><a name="part_hierarchy" id="part_hierarchy">Part Hierarchy</a></h3>
+<div class="level3">
+
+<p>
+ The part hierarchy allows the database to attach additional attributes to a class of parts. These attributes provide a faster means to locate and select parts, especially commodity parts. The database only provides these additional attributes when configured to use hierarchical part tables.
+</p>
+
+<p>
+These additional attributes, stored in numeric format, allow <acronym title="Structured Query Language">SQL</acronym> to select parts. For example, to locate diodes with reverse voltage greater than 60 volts, use the following <acronym title="Structured Query Language">SQL</acronym> statement.
+</p>
+<pre class="code sql"><span class="kw1">SELECT</span> * <span class="kw1">FROM</span> DiodeV
+ <span class="kw1">WHERE</span> VR > <span class="nu0">60</span>;</pre>
+<p>
+The intent of the part hierarchy does not include exhaustively classifying all electronic parts or fully parameterizing any class of electronic part. The part hierarchy simply intends to allow the user to quickly locate a part, such as a 4.75 kΩ 1% 0603.
+</p>
+
+<p>
+<em class="u">TODO: Develop guidelines for subclassing part.</em>
+</p>
+
+<p>
+Proposed guidelines for including attributes:
+</p>
+<ul>
+<li class="level1"><div class="li"> Include attributes that are encoded in the manufacturer part number.</div>
+</li>
+<li class="level1"><div class="li"> Exclude attributes that are inconsistently characterized between manufacturers.</div>
+</li>
+<li class="level1"><div class="li"> Exclude attributes that must be either read from graphs, or calculated. </div>
+</li>
+</ul>
+
+<p>
+ These attributes may not work for everyone, so the database allows the user to customize these part tables.
+</p>
+
+</div>
+
+<h4><a name="capacitors" id="capacitors">Capacitors</a></h4>
+<div class="level4">
+
+<p>
+ Capacitors extend part with one additional table of attributes.
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th class="leftalign"> Units </th><th class="leftalign"> Description </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> PartID </td><td class="rightalign"> </td><td class="rightalign"> </td><td class="leftalign"> Foreign key to Part </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> PackageID </td><td class="rightalign"> </td><td class="rightalign"> </td><td> Foreign key to Package </td>
+ </tr>
+ <tr>
+ <td> Capacitance </td><td> Physical </td><td class="leftalign"> FARADS </td><td class="leftalign"> Capacitance </td>
+ </tr>
+</table>
+
+<p>
+ When instantiating a component or creating a heavy symbol, the following database columns map to the following attributes.
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Column </th><th> Attribute </th><th class="leftalign"> Notes </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> Device.DeviceName </td><td class="leftalign"> DEVICE </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td> Capacitor.Capacitance </td><td class="leftalign"> VALUE </td><td class="rightalign"> </td>
+ </tr>
+</table>
+
+</div>
+
+<h4><a name="inductors" id="inductors">Inductors</a></h4>
+<div class="level4">
+
+<p>
+ Inductors extend part with one additional table of attributes.
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th class="leftalign"> Units </th><th class="leftalign"> Description </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> PartID </td><td class="rightalign"> </td><td class="rightalign"> </td><td class="leftalign"> Foreign key to Part </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> PackageID </td><td class="rightalign"> </td><td class="rightalign"> </td><td> Foreign key to Package </td>
+ </tr>
+ <tr>
+ <td> Inductance </td><td> Physical </td><td class="leftalign"> HENRYS </td><td class="leftalign"> Inductance </td>
+ </tr>
+</table>
+
+<p>
+ When instantiating a component or creating a heavy symbol, the following database columns map to the following attributes.
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Column </th><th> Attribute </th><th class="leftalign"> Notes </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> Device.DeviceName </td><td class="leftalign"> DEVICE </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td> Inductor.Inductance </td><td class="leftalign"> VALUE </td><td class="rightalign"> </td>
+ </tr>
+</table>
+
+</div>
+
+<h4><a name="rectifier_and_switching_diodes" id="rectifier_and_switching_diodes">Rectifier and Switching Diodes</a></h4>
+<div class="level4">
+
+<p>
+ Rectifier and switching diodes extend part with one additional table of attributes. Most diodes can be placed into this table.
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th> Units </th><th class="leftalign"> Description </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> PartID </td><td class="rightalign"> </td><td class="rightalign"> </td><td class="leftalign"> Foreign key to Part </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> PackageID </td><td class="rightalign"> </td><td class="rightalign"> </td><td class="leftalign"> Foreign key to Package </td>
+ </tr>
+ <tr>
+ <td> MaxReverseVoltage </td><td> Physical </td><td> VOLTS </td><td> Maximum reverse voltage (Absolute maximum rating) </td>
+ </tr>
+ <tr>
+ <td> MaxForwardCurrent </td><td> Physical </td><td class="leftalign"> AMPS </td><td> Maximum forward current (Absolute maximum rating) </td>
+ </tr>
+ <tr>
+ <td> TypForwardVoltage </td><td> Physical </td><td> VOLTS </td><td class="leftalign"> Typical forward voltage </td>
+ </tr>
+ <tr>
+ <td> AveForwardCurrent </td><td> Physical </td><td class="leftalign"> AMPS </td><td class="leftalign"> Average forward current </td>
+ </tr>
+</table>
+
+</div>
+
+<h4><a name="resistors" id="resistors">Resistors</a></h4>
+<div class="level4">
+
+<p>
+ Resistors extend part with one additional table of attributes.
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th class="leftalign"> Units </th><th class="leftalign"> Description </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> PartID </td><td class="rightalign"> </td><td class="rightalign"> </td><td class="leftalign"> Foreign key to Part </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> PackageID </td><td class="rightalign"> </td><td class="rightalign"> </td><td> Foreign key to Package </td>
+ </tr>
+ <tr>
+ <td> Resistance </td><td> Physical </td><td class="leftalign"> OHMS </td><td class="leftalign"> Resistance </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Tolerance </td><td> Physical </td><td> PERCENT </td><td class="leftalign"> Tolerance </td>
+ </tr>
+</table>
+
+<p>
+ When instantiating a component or creating a heavy symbol, the following database columns map to the following attributes.
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Column </th><th> Attribute </th><th class="leftalign"> Notes </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> Device.DeviceName </td><td class="leftalign"> DEVICE </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td> Resistor.Resistance </td><td class="leftalign"> VALUE </td><td class="rightalign"> </td>
+ </tr>
+</table>
+
+</div>
+
+<h4><a name="tvs_diodes" id="tvs_diodes">TVS Diodes</a></h4>
+<div class="level4">
+
+<p>
+ TVS diodes extend part with one additional table of attributes.
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th> Units </th><th class="leftalign"> Description </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> PartID </td><td class="rightalign"> </td><td class="rightalign"> </td><td class="leftalign"> Foreign key to Part </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> PackageID </td><td class="rightalign"> </td><td class="rightalign"> </td><td> Foreign key to Package </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> WorkingVoltage </td><td> Physical </td><td> VOLTS </td><td class="leftalign"> Working voltage </td>
+ </tr>
+ <tr>
+ <td> BreakdownVoltage </td><td> Physical </td><td> VOLTS </td><td class="leftalign"> Breakdown voltage </td>
+ </tr>
+</table>
+
+</div>
+
+<h4><a name="zener_diodes" id="zener_diodes">Zener Diodes</a></h4>
+<div class="level4">
+
+<p>
+ Zener diodes extend part with one additional table of attributes.
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Field </th><th class="leftalign"> Type </th><th> Units </th><th class="leftalign"> Description </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> PartID </td><td class="rightalign"> </td><td class="rightalign"> </td><td class="leftalign"> Foreign key to Part </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> PackageID </td><td class="rightalign"> </td><td class="rightalign"> </td><td> Foreign key to Package </td>
+ </tr>
+ <tr>
+ <td> ZenerVoltage </td><td> Physical </td><td> VOLTS </td><td class="leftalign"> Zener voltage </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "Part Hierarchy" [9163-13953] -->
+<h2><a name="part_manager_gui" id="part_manager_gui">Part Manager GUI</a></h2>
+<div class="level2">
+
+<p>
+ The part manager <acronym title="Graphical User Interface">GUI</acronym> is the main component of the part management system. The part manager <acronym title="Graphical User Interface">GUI</acronym> allows the user to browse and manipulate the part database and to cut and paste symbols into the schematic editor.
+</p>
+
+</div>
+<!-- SECTION "Part Manager GUI" [13954-14195] -->
+<h3><a name="use_cases" id="use_cases">Use Cases</a></h3>
+<div class="level3">
+
+</div>
+
+<h4><a name="uc.component.copy.clipboard" id="uc.component.copy.clipboard">uc.component.copy.clipboard</a></h4>
+<div class="level4">
+
+<p>
+ Copy a part to the clipboard as a component (light symbol).
+</p>
+<ol>
+<li class="level1"><div class="li"> The user selects a part in the database.</div>
+</li>
+<li class="level1"><div class="li"> The user selects a symbol to represent the part.</div>
+</li>
+<li class="level1"><div class="li"> The <acronym title="Graphical User Interface">GUI</acronym> instantiates a component and overrides attributes.</div>
+</li>
+<li class="level1"><div class="li"> The user previews the component to ensure the graphic looks correct.</div>
+</li>
+<li class="level1"><div class="li"> The user selects the copy action.</div>
+</li>
+<li class="level1"><div class="li"> The <acronym title="Graphical User Interface">GUI</acronym> copies the component to the clipboard.</div>
+</li>
+<li class="level1"><div class="li"> The user pastes the component in gschem.</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.component.export.file" id="uc.component.export.file">uc.component.export.file</a></h4>
+<div class="level4">
+
+<p>
+ Export a part to a file as a heavy symbol.
+</p>
+<ol>
+<li class="level1"><div class="li"> The user selects a part in the database.</div>
+</li>
+<li class="level1"><div class="li"> The user selects a symbol to represent the part.</div>
+</li>
+<li class="level1"><div class="li"> The <acronym title="Graphical User Interface">GUI</acronym> clones the symbol and substitutes attributes.</div>
+</li>
+<li class="level1"><div class="li"> The user previews the symbol to ensure the graphic looks correct.</div>
+</li>
+<li class="level1"><div class="li"> The user selects the export action.</div>
+</li>
+<li class="level1"><div class="li"> The <acronym title="Graphical User Interface">GUI</acronym> prompts the user for a filename and location.</div>
+</li>
+<li class="level1"><div class="li"> The <acronym title="Graphical User Interface">GUI</acronym> writes the symbol to the given file.</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.database.create" id="uc.database.create">uc.database.create</a></h4>
+<div class="level4">
+
+<p>
+ Create a new part database.
+</p>
+<ol>
+<li class="level1"><div class="li"> TBD</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.database.destroy" id="uc.database.destroy">uc.database.destroy</a></h4>
+<div class="level4">
+
+<p>
+ Destroy an existing database.
+</p>
+<ol>
+<li class="level1"><div class="li"> The user selects the destroy database action.</div>
+</li>
+<li class="level1"><div class="li"> The <acronym title="Graphical User Interface">GUI</acronym> prompts the user for confirmation.</div>
+</li>
+<li class="level1"><div class="li"> The application drops the database.</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.document.add" id="uc.document.add">uc.document.add</a></h4>
+<div class="level4">
+
+<p>
+ Add a new document to the database.
+</p>
+<ol>
+<li class="level1"><div class="li"> The user selects the add document action.</div>
+</li>
+<li class="level1"><div class="li"> The <acronym title="Graphical User Interface">GUI</acronym> prompts the user for a filename and location.</div>
+</li>
+<li class="level1"><div class="li"> The application adds the document to the database.</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.document.attach" id="uc.document.attach">uc.document.attach</a></h4>
+<div class="level4">
+
+<p>
+ Associate a document(s) with a part(s).
+</p>
+<ol>
+<li class="level1"><div class="li"> The user selects one or more parts from the database.</div>
+</li>
+<li class="level1"><div class="li"> The user selects the attach document action.</div>
+</li>
+<li class="level1"><div class="li"> The <acronym title="Graphical User Interface">GUI</acronym> prompts the user with a list of all the documents in the database.</div>
+</li>
+<li class="level1"><div class="li"> The user selects one or more documents from the list.</div>
+</li>
+<li class="level1"><div class="li"> The application attaches the given documents to the given parts.</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.document.delete" id="uc.document.delete">uc.document.delete</a></h4>
+<div class="level4">
+
+<p>
+ Delete a document(s) from the database. Remove all references.
+</p>
+<ol>
+<li class="level1"><div class="li"> The user selects one or more documents in the database.</div>
+</li>
+<li class="level1"><div class="li"> The user selects the delete action.</div>
+</li>
+<li class="level1"><div class="li"> The <acronym title="Graphical User Interface">GUI</acronym> prompts the user for confirmation.</div>
+</li>
+<li class="level1"><div class="li"> The application deletes the selected documents from the database.</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.document.detach" id="uc.document.detach">uc.document.detach</a></h4>
+<div class="level4">
+
+<p>
+ Disassociate a document(s) from a part(s). All parts and documents remain in the database. Only the relationship is removed.
+</p>
+<ol>
+<li class="level1"><div class="li"> The user selects one or more parts from the database.</div>
+</li>
+<li class="level1"><div class="li"> The user selects the detach document action.</div>
+</li>
+<li class="level1"><div class="li"> The <acronym title="Graphical User Interface">GUI</acronym> prompts the user with a list of all the documents attached to the given parts.</div>
+</li>
+<li class="level1"><div class="li"> The user selects one or more documents from the list.</div>
+</li>
+<li class="level1"><div class="li"> The <acronym title="Graphical User Interface">GUI</acronym> prompts the user for confirmation.</div>
+</li>
+<li class="level1"><div class="li"> The application detaches the given documents from the given parts, if attached.</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.document.edit" id="uc.document.edit">uc.document.edit</a></h4>
+<div class="level4">
+
+<p>
+ Edit the metadata associated with a document.
+</p>
+<ol>
+<li class="level1"><div class="li"> TBD</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.document.view" id="uc.document.view">uc.document.view</a></h4>
+<div class="level4">
+
+<p>
+ View a document.
+</p>
+<ol>
+<li class="level1"><div class="li"> TBD</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.footprint.delete" id="uc.footprint.delete">uc.footprint.delete</a></h4>
+<div class="level4">
+
+<p>
+ Delete a footprint(s) from the database. Remove all references.
+</p>
+<ol>
+<li class="level1"><div class="li"> The user selects one or more footprints in the database.</div>
+</li>
+<li class="level1"><div class="li"> The user selects the delete action.</div>
+</li>
+<li class="level1"><div class="li"> The <acronym title="Graphical User Interface">GUI</acronym> prompts the user for confirmation.</div>
+</li>
+<li class="level1"><div class="li"> The application deletes the selected footprints from the database.</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.footprint.edit" id="uc.footprint.edit">uc.footprint.edit</a></h4>
+<div class="level4">
+
+<p>
+ Edit the metadata associated with a footprint.
+</p>
+
+</div>
+
+<h4><a name="uc.footprint.import.file" id="uc.footprint.import.file">uc.footprint.import.file</a></h4>
+<div class="level4">
+
+<p>
+ Import a single footprint file into the database.
+</p>
+<ol>
+<li class="level1"><div class="li"> The user selects the import footprint file action.</div>
+</li>
+<li class="level1"><div class="li"> The <acronym title="Graphical User Interface">GUI</acronym> prompts the user for a footprint file.</div>
+</li>
+<li class="level1"><div class="li"> The application creates a footprint in the database for a new footprint file.</div>
+</li>
+<li class="level1"><div class="li"> The application updates a footprint in the database for an old footprint file.</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.footprint.import.library" id="uc.footprint.import.library">uc.footprint.import.library</a></h4>
+<div class="level4">
+
+<p>
+ Import all footprint files from the library into the database.
+</p>
+<ol>
+<li class="level1"><div class="li"> The user selects the import footprint library action.</div>
+</li>
+<li class="level1"><div class="li"> The application searches all footprint libraries.</div>
+</li>
+<li class="level1"><div class="li"> The application creates footprints in the database for new footprint files in the library.</div>
+</li>
+<li class="level1"><div class="li"> The application updates footprints in the database for old footprint files in the library. </div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.model.add" id="uc.model.add">uc.model.add</a></h4>
+<div class="level4">
+
+<p>
+ Add a new model to the database.
+</p>
+<ol>
+<li class="level1"><div class="li"> The user selects the add model action.</div>
+</li>
+<li class="level1"><div class="li"> The <acronym title="Graphical User Interface">GUI</acronym> prompts the user for a model type, name, and filename.</div>
+</li>
+<li class="level1"><div class="li"> The application adds the model to the database.</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.model.attach" id="uc.model.attach">uc.model.attach</a></h4>
+<div class="level4">
+
+<p>
+ Associate a model(s) with a part(s).
+</p>
+<ol>
+<li class="level1"><div class="li"> The user selects one or more parts from the database.</div>
+</li>
+<li class="level1"><div class="li"> The user selects the attach model action.</div>
+</li>
+<li class="level1"><div class="li"> The <acronym title="Graphical User Interface">GUI</acronym> prompts the user with a list of all the models in the database.</div>
+</li>
+<li class="level1"><div class="li"> The user selects one or more models from the list.</div>
+</li>
+<li class="level1"><div class="li"> The application attaches the given models to the given parts.</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.model.delete" id="uc.model.delete">uc.model.delete</a></h4>
+<div class="level4">
+
+<p>
+ Delete a model(s) from the database. Remove all references.
+</p>
+<ol>
+<li class="level1"><div class="li"> The user selects one or more models in the database.</div>
+</li>
+<li class="level1"><div class="li"> The user selects the delete action.</div>
+</li>
+<li class="level1"><div class="li"> The <acronym title="Graphical User Interface">GUI</acronym> prompts the user for confirmation.</div>
+</li>
+<li class="level1"><div class="li"> The application deletes the selected models from the database.</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.model.detach" id="uc.model.detach">uc.model.detach</a></h4>
+<div class="level4">
+
+<p>
+ Disassociate a model(s) from a part(s). All parts and models remain in the database. Only the relationship is removed.
+</p>
+<ol>
+<li class="level1"><div class="li"> The user selects one or more parts from the database.</div>
+</li>
+<li class="level1"><div class="li"> The user selects the detach model action.</div>
+</li>
+<li class="level1"><div class="li"> The <acronym title="Graphical User Interface">GUI</acronym> prompts the user with a list of all the models attached to the given parts.</div>
+</li>
+<li class="level1"><div class="li"> The user selects one or more models from the list.</div>
+</li>
+<li class="level1"><div class="li"> The <acronym title="Graphical User Interface">GUI</acronym> prompts the user for confirmation.</div>
+</li>
+<li class="level1"><div class="li"> The application detaches the given models from the given parts, if attached.</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.model.import.library.spice" id="uc.model.import.library.spice">uc.model.import.library.spice</a></h4>
+<div class="level4">
+
+<p>
+ Import all Spice files from the library into the database.
+</p>
+<ol>
+<li class="level1"><div class="li"> The user selects the import Spice library action.</div>
+</li>
+<li class="level1"><div class="li"> The application searches all Spice library directories for files.</div>
+</li>
+<li class="level1"><div class="li"> The application parses files to extract model names.</div>
+</li>
+<li class="level1"><div class="li"> The application creates Spice models in the database for new models in the library.</div>
+</li>
+<li class="level1"><div class="li"> The application updates Spice models in the database for old models in the library.</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.model.view" id="uc.model.view">uc.model.view</a></h4>
+<div class="level4">
+
+<p>
+ TBD
+</p>
+
+</div>
+
+<h4><a name="uc.package.add" id="uc.package.add">uc.package.add</a></h4>
+<div class="level4">
+
+<p>
+ Add a new package to the database.
+</p>
+<ol>
+<li class="level1"><div class="li"> TBD</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.package.delete" id="uc.package.delete">uc.package.delete</a></h4>
+<div class="level4">
+
+<p>
+ Delete a package(s) from the database. Remove all references.
+</p>
+<ol>
+<li class="level1"><div class="li"> The user selects one or more packages in the database.</div>
+</li>
+<li class="level1"><div class="li"> The user selects the delete action.</div>
+</li>
+<li class="level1"><div class="li"> The <acronym title="Graphical User Interface">GUI</acronym> prompts the user for confirmation.</div>
+</li>
+<li class="level1"><div class="li"> The application deletes the selected packages from the database.</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.package.edit" id="uc.package.edit">uc.package.edit</a></h4>
+<div class="level4">
+
+<p>
+ Edit the package data.
+</p>
+<ol>
+<li class="level1"><div class="li"> TBD</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.part.add" id="uc.part.add">uc.part.add</a></h4>
+<div class="level4">
+
+<p>
+ Add a new part to the database.
+</p>
+<ol>
+<li class="level1"><div class="li"> TBD</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.part.delete" id="uc.part.delete">uc.part.delete</a></h4>
+<div class="level4">
+
+<p>
+ Delete a part(s) from the database. Remove all references.
+</p>
+<ol>
+<li class="level1"><div class="li"> The user selects one or more parts in the database.</div>
+</li>
+<li class="level1"><div class="li"> The user selects the delete action.</div>
+</li>
+<li class="level1"><div class="li"> The <acronym title="Graphical User Interface">GUI</acronym> prompts the user for confirmation.</div>
+</li>
+<li class="level1"><div class="li"> The application deletes the selected parts from the database.</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.part.edit" id="uc.part.edit">uc.part.edit</a></h4>
+<div class="level4">
+
+<p>
+ Edit the part data.
+</p>
+<ol>
+<li class="level1"><div class="li"> TBD</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.part.search" id="uc.part.search">uc.part.search</a></h4>
+<div class="level4">
+
+<p>
+ Search for a part in the database using the manufacturer part number.
+</p>
+
+</div>
+
+<h4><a name="uc.symbol.delete" id="uc.symbol.delete">uc.symbol.delete</a></h4>
+<div class="level4">
+
+<p>
+ Delete a symbol(s) from the database. Remove all references.
+</p>
+<ol>
+<li class="level1"><div class="li"> The user selects one or more symbols in the database.</div>
+</li>
+<li class="level1"><div class="li"> The user selects the delete action.</div>
+</li>
+<li class="level1"><div class="li"> The <acronym title="Graphical User Interface">GUI</acronym> prompts the user for confirmation.</div>
+</li>
+<li class="level1"><div class="li"> The application deletes the selected symbols from the database.</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.symbol.edit" id="uc.symbol.edit">uc.symbol.edit</a></h4>
+<div class="level4">
+
+<p>
+ Edit the metadata associated with a symbol.
+</p>
+<ol>
+<li class="level1"><div class="li"> TBD</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.symbol.import.file" id="uc.symbol.import.file">uc.symbol.import.file</a></h4>
+<div class="level4">
+
+<p>
+ Import a single symbol file into the database.
+</p>
+<ol>
+<li class="level1"><div class="li"> The user selects the import symbol file action.</div>
+</li>
+<li class="level1"><div class="li"> The <acronym title="Graphical User Interface">GUI</acronym> prompts the user for a symbol file.</div>
+</li>
+<li class="level1"><div class="li"> The application creates a symbol in the database for a new symbol file.</div>
+</li>
+<li class="level1"><div class="li"> The application updates a symbol in the database for an old symbol file.</div>
+</li>
+</ol>
+
+</div>
+
+<h4><a name="uc.symbol.import.library" id="uc.symbol.import.library">uc.symbol.import.library</a></h4>
+<div class="level4">
+
+<p>
+ Import the contents of the component library into the database.
+</p>
+<ol>
+<li class="level1"><div class="li"> The user selects the import symbol library action.</div>
+</li>
+<li class="level1"><div class="li"> The application searches all component libraries specified in the configuration file for symbol files.</div>
+</li>
+<li class="level1"><div class="li"> The application creates symbols in the database for new symbol files in the library.</div>
+</li>
+<li class="level1"><div class="li"> The application updates symbols in the database for old symbol files in the library.</div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Use Cases" [14196-22131] -->
+<h3><a name="ui_design" id="ui_design">UI Design</a></h3>
+<div class="level3">
+
+</div>
+
+<h4><a name="company_view" id="company_view">Company View</a></h4>
+<div class="level4">
+
+<p>
+ The company view lists all the companies in the database.
+</p>
+
+<p>
+<a href="media/geda/gparts-ss-companies.png" class="media" target="_blank" title="geda:gparts-ss-companies.png"><img src="media/geda/gparts-ss-companies.png" class="media" title="" alt="" /></a>
+</p>
+
+</div>
+
+<h4><a name="device_view" id="device_view">Device View</a></h4>
+<div class="level4">
+
+<p>
+ The device view lists all the devices stored in the database.
+</p>
+
+<p>
+<a href="media/geda/gparts-ss-devices.png" class="media" target="_blank" title="geda:gparts-ss-devices.png"><img src="media/geda/gparts-ss-devices.png" class="media" title="" alt="" /></a>
+</p>
+
+</div>
+
+<h4><a name="documentation_view" id="documentation_view">Documentation View</a></h4>
+<div class="level4">
+
+<p>
+ The documentation view shows all the documents stored in the database.
+</p>
+
+<p>
+<a href="media/geda/gparts-ss-documentation.png" class="media" target="_blank" title="geda:gparts-ss-documentation.png"><img src="media/geda/gparts-ss-documentation.png" class="media" title="" alt="" /></a>
+</p>
+
+</div>
+
+<h4><a name="footprint_view" id="footprint_view">Footprint View</a></h4>
+<div class="level4">
+
+<p>
+ The footprint view shows all the footprints stored in the database.
+</p>
+
+<p>
+<a href="media/geda/gparts-ss-footprints.png" class="media" target="_blank" title="geda:gparts-ss-footprints.png"><img src="media/geda/gparts-ss-footprints.png" class="media" title="" alt="" /></a>
+</p>
+
+</div>
+
+<h4><a name="package_view" id="package_view">Package View</a></h4>
+<div class="level4">
+
+<p>
+ The package view shows all the packages stored in the database.
+</p>
+
+<p>
+<a href="media/geda/gparts-ss-packages.png" class="media" target="_blank" title="geda:gparts-ss-packages.png"><img src="media/geda/gparts-ss-packages.png" class="media" title="" alt="" /></a>
+</p>
+
+</div>
+
+<h4><a name="part_view" id="part_view">Part View</a></h4>
+<div class="level4">
+
+<p>
+ The part view shows parts stored in the database. The user selects the category from the left pane. The parts within the given category show in the middle pane. After selecting a part from the middle pane, the symbols available for that part show in the lower right pane. The upper right pane shows the symbol preview.
+</p>
+
+<p>
+<a href="media/geda/gparts-ss-parts-2.png" class="media" target="_blank" title="geda:gparts-ss-parts-2.png"><img src="media/geda/gparts-ss-parts-2.png" class="media" title="" alt="" /></a>
+</p>
+
+</div>
+
+<h4><a name="symbol_view" id="symbol_view">Symbol View</a></h4>
+<div class="level4">
+
+<p>
+ The symbol view shows all the symbols stored in the database. The upper right pane shows the symbol preview.
+</p>
+
+<p>
+<a href="media/geda/gparts-ss-symbols-2.png" class="media" target="_blank" title="geda:gparts-ss-symbols-2.png"><img src="media/geda/gparts-ss-symbols-2.png" class="media" title="" alt="" /></a>
+</p>
+
+</div>
+<!-- SECTION "UI Design" [22132-23316] -->
+<h3><a name="configuration" id="configuration">Configuration</a></h3>
+<div class="level3">
+
+<p>
+ The parts manager reads gafâ??s Scheme configuration files using Guile-1.8. The parts manager reads the following configuration files in order. The parts manager attempts reading the file in each of the given paths in order.
+</p>
+<ol>
+<li class="level1"><div class="li"> system-gafrc</div>
+<ol>
+<li class="level2"><div class="li"> the path specified in the environment variable GEDADATARC</div>
+</li>
+<li class="level2"><div class="li"> the paths retrieved from g_get_system_config_dirs() + â??gEDAâ??</div>
+</li>
+<li class="level2"><div class="li"> the paths retrieved from g_get_system_data_dirs() + â??gEDAâ??</div>
+</li>
+</ol>
+</li>
+<li class="level1"><div class="li"> gafrc</div>
+<ol>
+<li class="level2"><div class="li"> the path specified in the environment variable HOME</div>
+</li>
+<li class="level2"><div class="li"> ~/.gEDA</div>
+</li>
+</ol>
+</li>
+<li class="level1"><div class="li"> gafrc</div>
+<ol>
+<li class="level2"><div class="li"> .</div>
+</li>
+</ol>
+</li>
+<li class="level1"><div class="li"> system-gpartsrc</div>
+<ol>
+<li class="level2"><div class="li"> the path specified in the environment variable GPARTSDATARC</div>
+</li>
+<li class="level2"><div class="li"> the paths retrieved from g_get_system_config_dirs() + â??gpartsâ??</div>
+</li>
+<li class="level2"><div class="li"> the paths retrieved from g_get_system_data_dirs() + â??gpartsâ??</div>
+</li>
+</ol>
+</li>
+<li class="level1"><div class="li"> gpartsrc</div>
+<ol>
+<li class="level2"><div class="li"> the path specified in the environment variable HOME</div>
+</li>
+<li class="level2"><div class="li"> ~/.gEDA</div>
+</li>
+</ol>
+</li>
+<li class="level1"><div class="li"> gpartsrc</div>
+<ol>
+<li class="level2"><div class="li"> .</div>
+</li>
+</ol>
+</li>
+</ol>
+
+<p>
+ The parts manager supports the following configuration items from gaf.
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Item </th><th class="leftalign"> Parser </th><th> Description </th>
+ </tr>
+ <tr>
+ <td> always-promote-attributes </td><td> libgeda </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> attribute-promotion </td><td> libgeda </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> bitmap-directory </td><td> libgeda </td><td class="leftalign"> Specifies the directory for bitmap images </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> bus-style </td><td class="leftalign"> gschem </td><td class="leftalign"> Specifies the line thickness for busses </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> component-library </td><td> libgeda </td><td class="leftalign"> Adds a directory to the component library </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> display-color-map </td><td class="leftalign"> gschem </td><td class="leftalign"> Specifies schematic colors for display </td>
+ </tr>
+ <tr>
+ <td> display-outline-color-map </td><td class="leftalign"> gschem </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> eval-protected </td><td> libgeda </td><td class="leftalign"> For the parts manager, simply â??evalâ?? </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> keep-invisible </td><td> libgeda </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> net-style </td><td class="leftalign"> gschem </td><td class="leftalign"> Specifies the line thickness for nets </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> postscript-prolog </td><td> libgeda </td><td class="leftalign"> Ignored by the parts manager </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> print-color-map </td><td> libgeda </td><td class="leftalign"> Specifies schematic colors for printing </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> promote-invisible </td><td> libgeda </td><td class="rightalign"> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> scheme-directory </td><td> libgeda </td><td> Specifies the directory for additional scheme files </td>
+ </tr>
+</table>
+
+<p>
+ The parts manager supports the following private configuration items.
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Item </th><th> Parser </th><th> Description </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> database-interface </td><td> gparts </td><td class="leftalign"> Adds a database interface module </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> document-library </td><td> gparts </td><td class="leftalign"> Adds a directory to the document library </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> footprint-library </td><td> gparts </td><td> Adds a directory to the footprint library </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> spice-library </td><td> gparts </td><td class="leftalign"> Adds a directory to the spice library </td>
+ </tr>
+</table>
+
+</div>
+
+<h4><a name="database-interface" id="database-interface">database-interface</a></h4>
+<div class="level4">
+
+<p>
+ The parts manager uses dynamically loadable modules to support the various database engines. The parts manager uses a separate module to support each database engine.
+</p>
+<ul>
+<li class="level1"><div class="li"> MySQL</div>
+</li>
+<li class="level1"><div class="li"> PostgreSQL</div>
+</li>
+<li class="level1"><div class="li"> SQLite</div>
+</li>
+</ul>
+
+</div>
+
+<h4><a name="document-library" id="document-library">document-library</a></h4>
+<div class="level4">
+
+<p>
+ Adds a directory to the list of directories where documentation is stored.
+</p>
+
+</div>
+
+<h4><a name="footprint-library" id="footprint-library">footprint-library</a></h4>
+<div class="level4">
+
+<p>
+ Adds a directory to the list of directories where footprints are stored. The parts manager can import newlib footprints from these directories.
+</p>
+
+</div>
+
+<h4><a name="spice-library" id="spice-library">spice-library</a></h4>
+<div class="level4">
+
+<p>
+ Adds a directory to the list of directories where SPICE models are stored. The parts manager can import these models from these directories.
+</p>
+
+</div>
+<!-- SECTION "Configuration" [23317-] --></body>
+</html>
diff --git a/docs/wiki/geda-gsch2pcb_tutorial.html b/docs/wiki/geda-gsch2pcb_tutorial.html
index 5283402..c03a9a4 100644
--- a/docs/wiki/geda-gsch2pcb_tutorial.html
+++ b/docs/wiki/geda-gsch2pcb_tutorial.html
@@ -78,7 +78,7 @@ The gschem <strong>value</strong> attribute value is the particular component va
</p>
</div>
-<!-- SECTION "Terminology" [948-3251] -->
+<!-- SECTION "Terminology" [948-3252] -->
<h2><a name="setup" id="setup">Setup</a></h2>
<div class="level2">
@@ -138,7 +138,7 @@ or, in each project directory there could be a <strong>gafrc</strong> file with
</ul>
<pre class="code">ln -s ../pcb-elements packages</pre>
<ul>
-<li class="level1"><div class="li"> <strong> gsch2pcb setup: </strong> In each of your project directories, create a gsch2pcb project file which can be named anything that does not end in <em>.sch</em>. A poject file will be created in the example below.</div>
+<li class="level1"><div class="li"> <strong> gsch2pcb setup: </strong> In each of your project directories, create a gsch2pcb project file which can be named anything that does not end in <em>.sch</em>. A project file will be created in the example below.</div>
</li>
</ul>
@@ -147,7 +147,7 @@ or, in each project directory there could be a <strong>gafrc</strong> file with
</p>
</div>
-<!-- SECTION "Setup" [3252-7825] -->
+<!-- SECTION "Setup" [3253-7827] -->
<h2><a name="simple_example" id="simple_example">Simple Example</a></h2>
<div class="level2">
@@ -163,7 +163,7 @@ output-name board
</pre>
</div>
-<!-- SECTION "Simple Example" [7826-8301] -->
+<!-- SECTION "Simple Example" [7828-8303] -->
<h3><a name="create_schematicone.sch" id="create_schematicone.sch">Create schematic: one.sch</a></h3>
<div class="level3">
@@ -200,7 +200,7 @@ output-name board
</p>
</div>
-<!-- SECTION "Create schematic: one.sch" [8302-9703] -->
+<!-- SECTION "Create schematic: one.sch" [8304-9705] -->
<h3><a name="edit_the_attributes_of_the_components_on_the_schematic" id="edit_the_attributes_of_the_components_on_the_schematic">Edit the attributes of the components on the schematic.</a></h3>
<div class="level3">
@@ -228,7 +228,7 @@ Anyway, weâ??re done for now with <strong>one.sch</strong>, so save it with the
</p>
</div>
-<!-- SECTION "Edit the attributes of the components on the schematic." [9704-11653] -->
+<!-- SECTION "Edit the attributes of the components on the schematic." [9706-11656] -->
<h3><a name="create_schematictwo.sch" id="create_schematictwo.sch">Create schematic: two.sch</a></h3>
<div class="level3">
@@ -240,7 +240,7 @@ This will be really trivial and stupid since weâ??re doing it only to demonstrat
</li>
<li class="level1"><div class="li"> Add components:</div>
<ul>
-<li class="level2"><div class="li"> From the <strong>Iput/Output</strong> library one <strong>input-2.sym</strong>.</div>
+<li class="level2"><div class="li"> From the <strong>Input/Output</strong> library one <strong>input-2.sym</strong>.</div>
</li>
<li class="level2"><div class="li"> From the <strong>Basic Devices</strong> library one <strong>resistor-1.sym</strong>.</div>
</li>
@@ -283,7 +283,7 @@ Now we are done with the schematics except for assigning <strong>refdes</strong>
</p>
</div>
-<!-- SECTION "Create schematic: two.sch" [11654-15281] -->
+<!-- SECTION "Create schematic: two.sch" [11657-15285] -->
<h3><a name="generate_pcb_files_from_schematics" id="generate_pcb_files_from_schematics">Generate PCB Files from Schematics</a></h3>
<div class="level3">
@@ -311,7 +311,7 @@ If you get output from gsch2pcb like: <em>2 unknown elements added to board.pcb.
</p>
</div>
-<!-- SECTION "Generate PCB Files from Schematics" [15282-17519] -->
+<!-- SECTION "Generate PCB Files from Schematics" [15286-17524] -->
<h3><a name="layout_pcb_files" id="layout_pcb_files">Layout PCB Files</a></h3>
<div class="level3">
@@ -378,7 +378,8 @@ Or, you can let PCB spread out the elements with <strong>Select→Disperse al
</p>
<p>
-Note: you can use the PCB auto placement feature instead of manually placing (or dispersing with the <strong>Select→Disperse …</strong> commands) the components as described above. To do this, you would load the netlist, select the components you want to be autoplaced (if this is the first PCB run, just <b>Select→Select all objects</b>) then do <strong>Select→Auto place selected elements</strong>. Then you can again manually tune the PCB generated placements. The auto place function should place elements more intelligently than the disperse function, but it is also much slower as layouts get larger.
+Note: you can use the PCB auto placement feature instead of manually placing (or dispersing with the <strong>Select→Disperse …</strong> commands) the components as described above. To do this, you would load the netlist, select the components you want to be autoplaced (if this is the first PCB run, just <strong>Select→Select all
+objects</strong>) then do <strong>Select→Auto place selected elements</strong>. Then you can again manually tune the PCB generated placements. The auto place function should place elements more intelligently than the disperse function, but it is also much slower as layouts get larger.
</p>
</div>
@@ -422,7 +423,7 @@ In some layouts it is important to put components on either side of the board,
</p>
</div>
-<!-- SECTION "Layout PCB Files" [17520-25954] -->
+<!-- SECTION "Layout PCB Files" [17525-25956] -->
<h2><a name="modifying_schematics" id="modifying_schematics">Modifying Schematics</a></h2>
<div class="level2">
@@ -479,7 +480,7 @@ board.pcb is backed up as board.pcb.bak1.
</p>
</div>
-<!-- SECTION "Modifying Schematics" [25955-29760] -->
+<!-- SECTION "Modifying Schematics" [25957-29762] -->
<h2><a name="custom_gschem_symbols" id="custom_gschem_symbols">Custom gschem Symbols</a></h2>
<div class="level2">
@@ -578,7 +579,7 @@ For complete details on making symbols, read through the <a href="geda-scg.html"
</p>
</div>
-<!-- SECTION "Custom gschem Symbols" [29761-34014] -->
+<!-- SECTION "Custom gschem Symbols" [29763-34016] -->
<h2><a name="custom_file_elements" id="custom_file_elements">Custom file elements</a></h2>
<div class="level2">
@@ -659,7 +660,7 @@ Pin(0 0 70 20 70 42 "" "1" 0x00000101)
</p>
</div>
-<!-- SECTION "Custom file elements" [34015-40476] -->
+<!-- SECTION "Custom file elements" [34017-40478] -->
<h2><a name="custom_m4_elements_requires_gsch2pcb_1.0" id="custom_m4_elements_requires_gsch2pcb_1.0">Custom m4 elements (Requires gsch2pcb >= 1.0)</a></h2>
<div class="level2">
@@ -798,7 +799,7 @@ Mark(50 50)
</p>
</div>
-<!-- SECTION "Custom m4 elements (Requires gsch2pcb >= 1.0)" [40477-48164] -->
+<!-- SECTION "Custom m4 elements (Requires gsch2pcb >= 1.0)" [40479-48166] -->
<h2><a name="multi-user_setup_requires_gsch2pcb_1.0" id="multi-user_setup_requires_gsch2pcb_1.0">Multi-user Setup (requires gsch2pcb >= 1.0)</a></h2>
<div class="level2">
@@ -839,7 +840,7 @@ With the above, users will have access to site wide libraries and only need to p
</p>
</div>
-<!-- SECTION "Multi-user Setup (requires gsch2pcb >= 1.0)" [48165-49802] -->
+<!-- SECTION "Multi-user Setup (requires gsch2pcb >= 1.0)" [48167-49804] -->
<h2><a name="pc_board_fabrication" id="pc_board_fabrication">PC Board Fabrication</a></h2>
<div class="level2">
@@ -874,5 +875,5 @@ If you find that your pads and traces donâ??t print on the same page, or are pla
</p>
</div>
-<!-- SECTION "PC Board Fabrication" [49803-] --></body>
+<!-- SECTION "PC Board Fabrication" [49805-] --></body>
</html>
diff --git a/docs/wiki/geda-gschem2pcb_readme.html b/docs/wiki/geda-gschem2pcb_readme.html
deleted file mode 100644
index 8d4f38d..0000000
--- a/docs/wiki/geda-gschem2pcb_readme.html
+++ /dev/null
@@ -1,154 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
-<html>
-<head>
- <title></title>
- <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
- <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
- <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
-
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-</head>
-<body>
-
-
-
-
-<h1><a name="gschem2pcb_readme" id="gschem2pcb_readme">gschem2pcb README</a></h1>
-<div class="level1">
-<pre class="code">------------------------------------------------------------------
-JM Routoure. routoure@xxxxxxxxxxxxxx
-17/01/2000
-
-I would like to thank Stefan Petersen for debuging the scheme program.
-
--------------------------------------------------------------------
-
-
-This document describes how to install (section I) and use (section II) the
-gschem2pcb package. Section III describes some of the footprints
-available in pcb
-
-The purpose of this package is to interface gschem with pcb. It uses a scheme
-program and a script.
-
-
-Section I : Installation.
-
-1. Untar the gschem2pcb.tar. You must obtain 3 files gschem2pcb.sh,
-GNET-PCBboard.scm and the README file.
-
-2. Move gschem2pcb.sh in a directory which is in your PATH (/usr/local/bin for
-instance ). Be sure that gschem2pcb.sh can be executed (chmod 755 gschem2pcb.sh)
-
-3. Move GNET-PCBboard.scm in the share directory of your gEDA distribution.
-Normally, it should be /usr/local/share/gEDA/scheme.
-
-4. Modify the common.m4 file of the pcb program (should be found in
-/usr/X11R6/lib/X11/pcb/m4/) like this : the include keywords at the end of the
-file must be replace by
-
-include(/usr/X11R6/lib/X11/pcb/m4/connector.inc)
-include(/usr/X11R6/lib/X11/pcb/m4/dil.inc)
-include(/usr/X11R6/lib/X11/pcb/m4/misc.inc)
-include(/usr/X11R6/lib/X11/pcb/m4/plcc.inc)
-include(/usr/X11R6/lib/X11/pcb/m4/to.inc)
-include(/usr/X11R6/lib/X11/pcb/m4/qfp.inc)
-
-5. Edit the ~/.gEDA/gschemrc file and be sure that the following line exists :
-(attribute-name "footprint")
-
-
-6. Be sure that grep, sed and gawk are installed. That's all..
-
-
-Section II : using gschem2pcb.
-
-1. With gschem, create a schematic. All the device you want to have in pcb must
-have a Uref attribute. The footprint that you want to use in pcb are indicated
-by the footprint attribute (see section III for the description of the footprint
-in pcb)
-
-Be careful that the attributes Uref, name, value and device must not contain
-space char.
---------------------------------------------------------
-
-2. Save your work (ultralownoise.sch for instance -ambitious design!) and type in a shell
-
- gschem2pcb.sh ultralownoise.sch.
-
-note : the gschem file must end by .sch
-
-Error messages will appear if some space characters are found in the
-attributes Uref, name, value and device and if the name of the footprint was not
-found. Warning, pcb files are created even if errors occur!
-
-- if ultralownoise.pcb does not exist, it will be created. A netlist file
-ultralownoise.net will also be created. In pcb, load the pcb (load layout). All
-the footprints will appears at the top-left corner of the windows. Load the
-netlist (load netlist file) and type the key "w". Place the footprints and type
-"o" to optimize the rastnet. See the pcb documentation for details.
-
-- if ultralownoise.pcb exists, a ultralownoise.new.pcb file should be
-created. It should contain only the new device that have been added in the
-schematic since the last save of the ultralownoise.pcb file. Use "load layout
-data to paste buffer" to include the new footprints in the pcb file. The nestlist
-file is also updated so read it again.
-
-
-Section III. Description of the name of the footprint in pcb.
-pcb uses macro to define the footprints. For DIL packages, for instance, 2
-arguments are used to indicate the number of pins and the width in mil of the
-footprint. In gschem the footprint attribute of a 300 mil width and 8 pins DIL
-is:
-DIL 8 300.
-Warning, for that attribute, you have to included the space char!
-
-In the following. I describe the footprint attribute that are to be used in
-gschem for the footprint avalaible in pcb. N stands
-for the number of pins, W the width in mil, L the length in mil and D the
-diameter in mil
-CONNECTOR ROWS COLS # single connector
-DIN41_651LAY N # DIN 41.651 laying
-DIN41_651STAND N # DIN 41.651 standing
-SUBD_LAY_BASE N # SUB-D connector laying
-SUBD_MALE_LAY_BASE N # SUB-D connector male laying
-SUBD_FEMALE_LAY_BASE N # SUB-D connector female laying
-DIL N W # dual-inline standard
-D N # dual inline with W=244
-DW N # dual inline with W=419
-SD N # SD (ZIP)
-MULTIWATT15 # 15 pins multiwatt footprint
-R025 # standard 1/4W resistor !now attributes
-SIL N # SIL
-CSIL # SIL package with a common pin
-QFP132 # QFP132 flat pack
-LED D # standing LED
-DIODE_LAY L # laying diode
-AXIAL_LAY L # standard axial footprint
-CRYSTAL W # crystal package
-OSC # a can oscillator
-ISA8 # 8 bit ISA Slot card
-OVEN_OSC # ovenized-oscillator package
-RADIAL_CAN W # a radial capcitor package
-PLCC N # pllc
-PLCC N add # pllc with additionnal border add
-QFP N add # qfp with additionnal border add
-No additional parameters for the to footprints
-TO3_90
-TO3_45
-TO5
-TO92
-TO126
-TO126LAY-WIDE
-TO126STAND-WIDE
-TO220
-TO220LAY-WIDE
-TO220STAND
-TO220STAND-WIDE
-
-</pre>
-
-</div>
-</body>
-</html>
diff --git a/docs/wiki/geda-gschem_symbol_creation.html b/docs/wiki/geda-gschem_symbol_creation.html
new file mode 100644
index 0000000..3eefee0
--- /dev/null
+++ b/docs/wiki/geda-gschem_symbol_creation.html
@@ -0,0 +1,407 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<div class="toc">
+<div class="tocheader toctoggle" id="toc__header">Table of Contents</div>
+<div id="toc__inside">
+
+<ul class="toc">
+<li class="level1"><div class="li"><span class="li"><a href="#geda_gaf_symbol_creation_document" class="toc">gEDA/gaf Symbol Creation Document</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#component_symbol_creation" class="toc">Component symbol creation</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#requirements" class="toc">Requirements</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#style" class="toc">Style</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#text" class="toc">Text</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#attributes" class="toc">Attributes</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#graphics" class="toc">Graphics</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#pins" class="toc">Pins</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#electrical" class="toc">Electrical</a></span></div></li>
+</ul>
+</li>
+<li class="level2"><div class="li"><span class="li"><a href="#hints_and_tips" class="toc">Hints and Tips</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#example" class="toc">Example</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#document_revision_history" class="toc">Document Revision History</a></span></div></li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h1><a name="geda_gaf_symbol_creation_document" id="geda_gaf_symbol_creation_document">gEDA/gaf Symbol Creation Document</a></h1>
+<div class="level1">
+
+<p>
+by: Ales V. Hvezda / July 6th, 2004<br/>
+ The latest version of this document may be found at: <a href="http://geda.seul.org/wiki/geda:gschem_symbol_creation"; class="urlextern" title="http://geda.seul.org/wiki/geda:gschem_symbol_creation"; rel="nofollow">http://geda.seul.org/wiki/geda:gschem_symbol_creation</a><br/>
+ This document is released under the <a href="geda-gfdl.html" class="wikilink1" title="geda-gfdl.html">GNU Free Documentation License (GFDL)</a>.<br/>
+
+</p>
+
+</div>
+<!-- SECTION "gEDA/gaf Symbol Creation Document" [1-294] -->
+<h2><a name="overview" id="overview">Overview</a></h2>
+<div class="level2">
+
+<p>
+This document describes the creation of component symbols, including style conventions, and hints/tips and things to look out for when drawing symbols for the gEDA/gaf system.
+</p>
+
+</div>
+<!-- SECTION "Overview" [295-494] -->
+<h2><a name="component_symbol_creation" id="component_symbol_creation">Component symbol creation</a></h2>
+<div class="level2">
+
+<p>
+Component symbols (from here on known as â??symbolsâ??) are drawn using gschem. You can start with a blank page or a known-to-be good symbol that is similar to the one you want to create.
+</p>
+
+<p>
+1. Run gschem and find a blank page or run: gschem filename-1.sym<br/>
+ 2. Draw the symbol (see the style guide below for some conventions).<br/>
+ 3. Translate the symbol to the origin using Edit/Symbol Translate…<br/>
+
+</p>
+<ul>
+<li class="level1"><div class="li"> Zoom in at least one step.</div>
+</li>
+<li class="level1"><div class="li"> Make sure the snap is ON (this is critical).</div>
+</li>
+<li class="level1"><div class="li"> Make sure grid snap size is set to 100 (this is critical).</div>
+</li>
+<li class="level1"><div class="li"> Select â??Symbol Translate…â?? or the press equivalent hotkey.</div>
+</li>
+<li class="level1"><div class="li"> Enter 0 into the entry field and press OK.<br/>
+</div>
+</li>
+</ul>
+
+<p>
+Translating the symbol to the origin is a required step. To translate a symbol elsewhere, enter a offset (in mils) which is a even multiple of 100. Make sure all pins are snapped to a 100 mil grid point.
+</p>
+
+<p>
+4. Save the symbol using Save or SaveAs… Here are some symbol naming conventions:<br/>
+
+</p>
+<ul>
+<li class="level1"><div class="li"> Symbols are named: symbolname-#.sym</div>
+</li>
+<li class="level1"><div class="li"> Symbols end with a .sym extension.</div>
+</li>
+<li class="level1"><div class="li"> Symbols have a -# where # is a number. Typically # is 1 but if there are multiple symbols for a device then this number simply increments.</div>
+</li>
+<li class="level1"><div class="li"> Symbol names are typically lowercase but letters which are part of a part number are uppercase.</div>
+</li>
+<li class="level1"><div class="li"> The above case rule can be broken if the filename looks incorrect or wrong.</div>
+</li>
+</ul>
+
+<p>
+ 5. Place the symbol in one of the directories specified by the componentlibrary keyword in the system-gafrc file. Once this is done, the symbol should be visible immediately and can be selected and placed with the â??Add/Select Component…â?? menu item.
+</p>
+
+</div>
+<!-- SECTION "Component symbol creation" [495-2132] -->
+<h2><a name="requirements" id="requirements">Requirements</a></h2>
+<div class="level2">
+
+<p>
+This section describes the various requirements which must be met in order to create a valid symbol which will display and netlist in the gEDA/gaf system. Most of the requirements center around having certain attributes attached or inside the symbol.<br/>
+ Running gsymcheck will check that all of these requirements are met. gsymcheck will output fatal errors which are quite serious and must be corrected. gsymcheck will also output warnings on things which should be fixed but are not fatal.<br/>
+ For more information on the attributes presented here, please see the <a href="geda-master_attributes_list.html" class="wikilink1" title="geda-master_attributes_list.html">Master
+Attribute Document</a>.
+</p>
+<ul>
+<li class="level1"><div class="li"> device=DEVICENAME should be placed somewhere in the symbol and made invisible. device= is the device name and is required. Typically the devicename is in all caps (capital letters). This attribute should not be used as a label. Use a separate text object for the label. If the object is a graphic then device= should be set to none (device=none). It is no longer required to attach this attribute anything; just having it exist as device=DEVICENAME is good enough.</div>
+</li>
+<li class="level1"><div class="li"> graphical=1 should exist somewhere in a symbol which is purely graphical (such as a title block or decon symbol). Symbols which have this attribute have no electrical or circuit significance. Donâ??t forget to set device=none.</div>
+</li>
+<li class="level1"><div class="li"> description=text should exist somewhere in the symbol. This attribute provides an one line description of the symbol.</div>
+</li>
+<li class="level1"><div class="li"> All pins should have a pair of attributes attached to them: pinseq=# and pinnumber=#. The first attribute, pinseq=# is just a sequence number and increments sequentially starting at 1. The second attribute pinnumber=# is the number of the pin. When a symbol is netlisted, the pin numbers are output in order of pin sequence. The pin number can be alphanumeric (i.e. like E or C).</div>
+</li>
+<li class="level1"><div class="li"> All pins should also have pinlabel=value attached to them. This attribute is the name or label of the pin (vs the pin number). This attribute is also used when a symbol is used in a hierarchical schematic. Please make this attribute green (instead of the default attribute yellow).</div>
+</li>
+<li class="level1"><div class="li"> All pins should also have pintype=value attached to them. This attribute describes the kind of a pin. Possible values are: in, out, io, oc, oe, pas, tp, tri, clk, pwr. Please see the <a href="geda-master_attributes_list.html" class="wikilink1" title="geda-master_attributes_list.html">Master Attribute Document</a> for more info.</div>
+</li>
+<li class="level1"><div class="li"> If a component has multiple slots in a package (such as a 7400 (NAND) which has 4 NANDs per package) then you need a numslots=# attribute. The # is the number of slots the device has. numslots= should be exist somewhere in the symbol and made invisible. Additional slot related required attributes are described below.</div>
+</li>
+<li class="level1"><div class="li"> If a component has multiple slots in a physical package then you also need to include a slotdef=#:#,#,#… for every slot. The first # corresponds to the slot number. If a device has 4 slots then there should be slotdef=1:…, slotdef=2:…, slotdef=3:…, and slotdef=4:…, attributes existing somewhere in the symbol and made invisible. The subsequent # have a one-to-one correspondence to pinseq=# attributes and specify what corresponding pinnumber=# should be when that slot is set. See The attached 7400-1.sym as an example of how this should all work.</div>
+</li>
+<li class="level1"><div class="li"> It is recommended that all symbols which have slots have a slot=1 attribute inside the symbol.</div>
+</li>
+<li class="level1"><div class="li"> footprint=PACKAGENAME should exist somewhere in the symbol which might be used with the PCB netlister. PACKAGENAME is the PCB footprint or package type like DIP14 or DIP40. Please see the Footprint naming conventions chapter for further detail. See also the PCB documentation and gnetlist/docs/README.pcb for more info on this attribute.</div>
+</li>
+<li class="level1"><div class="li"> You should put a refdes=U? attribute inside the symbol. Make only the value visible and it will be promoted (attached to the outside of the symbol (so it can be edited) when the symbol is placed in a schematic.</div>
+</li>
+<li class="level1"><div class="li"> The label= attribute should not be attached anywhere in the symbol. It is obsolete.</div>
+</li>
+<li class="level1"><div class="li"> The name= attribute should not be attached anywhere in the symbol.</div>
+</li>
+<li class="level1"><div class="li"> The netname= attribute should not be attached anywhere in the symbol. It is only used in schematics.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Requirements" [2133-6327] -->
+<h2><a name="style" id="style">Style</a></h2>
+<div class="level2">
+
+<p>
+This section describes the style in which is used in the standard gEDA/gaf symbol library.
+</p>
+
+</div>
+<!-- SECTION "Style" [6328-6438] -->
+<h3><a name="text" id="text">Text</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> All Text labels should all be 10 pt in size.</div>
+</li>
+<li class="level1"><div class="li"> Text (labels not attributes) should be color number 9 (text | green).</div>
+</li>
+<li class="level1"><div class="li"> Use the special overbar encoding (e.g. â??pinlabel=\_Reset\_â??) to express inverse logic levels</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Text" [6439-6675] -->
+<h3><a name="attributes" id="attributes">Attributes</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Pin numbers (which are attributes) should all be 8 pt in size.</div>
+</li>
+<li class="level1"><div class="li"> pinnumber (the attribute) should be displayed for pins (not pinseq).</div>
+</li>
+<li class="level1"><div class="li"> Attached attributes should be yellow. The color is set automatically to yellow if the text item is attached.</div>
+</li>
+<li class="level1"><div class="li"> The only exception to this is pinlabel= attributes, those should be color number 9 (text | green). If every text item within a symbol is yellow, the symbol looks too yellow.</div>
+</li>
+<li class="level1"><div class="li"> Attributes can be attached to some part of the symbol. Toplevel attributes (like the device= or net= attributes) used to be required to be attached to something to be attributes, but now they just have to exist in the symbol file as name=value.</div>
+</li>
+<li class="level1"><div class="li"> Expanding a bit on the last sentence, as long as the text item has the format name=value, it is considered an attribute. Attributes inside a symbol do not have to be attached to anything. In order to see hidden attributes in gschem select Edit/Show/Hide Inv Text.</div>
+</li>
+<li class="level1"><div class="li"> There is a symbol content versioning system in libgeda which is based on the symversion= attribute. Please see the Master Attribute Document for more information on using this versioning scheme.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Attributes" [6676-7845] -->
+<h3><a name="graphics" id="graphics">Graphics</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Lines, boxes, arcs, and any other graphics should be color number 3 (graphic | green).</div>
+</li>
+<li class="level1"><div class="li"> Polarity bubbles should be color number 6 (logic bubble | cyan)</div>
+</li>
+<li class="level1"><div class="li"> If you are unsure on how to make a new symbol look or how big to make a new symbol, look at the existing symbols to get a feel for the appropriate appearance and size.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Graphics" [7846-8196] -->
+<h3><a name="pins" id="pins">Pins</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Pins should all be 300 mils (3 grid spaces) long.</div>
+</li>
+<li class="level1"><div class="li"> For pins which are next to a logic bubble, make the pins 200 mils (2 grid spaces) long and then make the logic bubble 100 mils in diameter. In order to draw a 100 mil diameter circle, you will need to change the snap spacing to 50.</div>
+</li>
+<li class="level1"><div class="li"> A pin has two ends: one end has a red endpoint and one end that does not. The red endpoint is where nets can be connected. You can either rotate the pin so that this active end is in the right place or manually edit the symbol file changing the â??whichendâ?? parameter on the pin object. See the File Format document for more info.</div>
+</li>
+<li class="level1"><div class="li"> Be that all endpoints of pins which are meant to be connected to are on the 100 mil grid. The endpoint which is not active can be off the grid if necessary.</div>
+</li>
+<li class="level1"><div class="li"> Pins should be color number 1 (pins | white).</div>
+</li>
+<li class="level1"><div class="li"> Leave 400 mils (4 grid spaces) between (vertically) pins, unless you are drawing a special symbol, then just try to make it look good.</div>
+</li>
+<li class="level1"><div class="li"> Pin number attributes should be 50 mils above (or below; which ever makes the most sense) the pin which they are attached to.</div>
+</li>
+<li class="level1"><div class="li"> Input pins belong on the left and output pins belong on the right of the symbol.</div>
+</li>
+<li class="level1"><div class="li"> Please do not mix inputs and outputs on the same side of the symbol, unless absolutely necessary.</div>
+</li>
+<li class="level1"><div class="li"> You can have pins on the top or bottom of a symbol.</div>
+</li>
+<li class="level1"><div class="li"> The order for rows of pins (buses) should be LSB (least significant bit) to MSB (most significant bit). When drawing pins which are part of a bus, make sure the LSB of the bus is at the top (or for pins on top/bottom of a symbol, left of the rest of the other pins). Look at 74/74181-1.sym for a correct example of this order (A0 on top through A3 and B0 on top through B3). Violating this rule will make connecting buses much more diffcult.</div>
+</li>
+<li class="level1"><div class="li"> When placing pins on logic gates, be sure to place the smallest pin numbers toward the top (or left) and then increment going down (or across).</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Pins" [8197-10152] -->
+<h3><a name="electrical" id="electrical">Electrical</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Do not draw power and ground pins. That information will be conveyed using attributes (see the netattrib document).</div>
+</li>
+<li class="level1"><div class="li"> The above rule can be broken if necessary, but keep in mind most of the standard library does not have power pins showing.</div>
+</li>
+<li class="level1"><div class="li"> Keep in mind, symbols are supposed to be symbolic, they do not represent the physical package that the device comes in.</div>
+</li>
+<li class="level1"><div class="li"> There is some disagreement on above, so this is okay too: Arrange the pins on a symbol logically so that they promote an uncluttered schematic. Note that this is frequently not the same pin arrangement as the physical device.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Electrical" [10153-10777] -->
+<h2><a name="hints_and_tips" id="hints_and_tips">Hints and Tips</a></h2>
+<div class="level2">
+
+<p>
+This section describes some hints and tips which will make your symbol creation experience easier.<br/>
+
+</p>
+<ul>
+<li class="level1"><div class="li"> Pins MUST be snapped on the 100-spaced grid.</div>
+</li>
+<li class="level1"><div class="li"> Avoid drawing things off of the grid. If you do, you cannot move the object(s) using the move command (if the grid is on) since the object will be snapped to the grid. [This was an old bug, which I think has been fixed, but avoid doing this anyway]. Use the symbol translate command instead (or move the object with grid snap off)</div>
+</li>
+<li class="level1"><div class="li"> It is okay to set the grid finer than 100 (say 10 or 25) when creating symbols, just remember to set this back to 100 once you are ready to translate the symbol to the origin.</div>
+</li>
+<li class="level1"><div class="li"> If you want to translate a symbol from the origin to elsewhere, then use the â??Symbol translateâ?? command and enter a non zero number. Make sure this number is a multiple of 100 (ie 1000, or 1100).</div>
+</li>
+<li class="level1"><div class="li"> Remember that pins are special objects; if you want to add a pin, make sure it is a pin and not a line or net. Use the Add/Pin command to place a pin.</div>
+</li>
+<li class="level1"><div class="li"> Donâ??t include nets or buses inside symbols. That is not supported and doesnâ??t make much sense anyway.</div>
+</li>
+<li class="level1"><div class="li"> Pinnumber should be the visible attribute for pins, along with pinlabel if any.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Hints and Tips" [10778-12015] -->
+<h2><a name="example" id="example">Example</a></h2>
+<div class="level2">
+
+<p>
+This section provides a simple example which tries to follow all of the above rules. This symbol is of a 7400 (NAND gate).<br/>
+
+</p>
+
+<p>
+<pre STYLE="background : LightGreen;
+margin-left : 2em"><font size="+0">v 20031231 1
+L 300 200 300 800 3 0 0 0 -1 -1
+T 300 0 9 8 1 0 0 0 1
+7400
+L 300 800 700 800 3 0 0 0 -1 -1
+T 500 900 5 10 0 0 0 0 1
+device=7400
+T 500 1100 5 10 0 0 0 0 1
+slot=1
+T 500 1300 5 10 0 0 0 0 1
+numslots=4
+T 500 1500 5 10 0 0 0 0 1
+slotdef=1:1,2,3
+T 500 1700 5 10 0 0 0 0 1
+slotdef=2:4,5,6
+T 500 1900 5 10 0 0 0 0 1
+slotdef=3:9,10,8
+T 500 2100 5 10 0 0 0 0 1
+slotdef=4:12,13,11
+L 300 200 700 200 3 0 0 0 -1 -1
+A 700 500 300 270 180 3 0 0 0 -1 -1
+V 1050 500 50 6 0 0 0 -1 -1 0 -1 -1 -1 -1 -1
+P 1100 500 1300 500 1 0 1
+{
+T 1100 550 5 8 1 1 0 0 1
+pinnumber=3
+T 1100 450 5 8 0 1 0 2 1
+pinseq=3
+T 950 500 9 8 0 1 0 6 1
+pinlabel=Y
+T 950 500 5 8 0 1 0 8 1
+pintype=out
+}
+P 300 300 0 300 1 0 1
+{
+T 200 350 5 8 1 1 0 6 1
+pinnumber=2
+T 200 250 5 8 0 1 0 8 1
+pinseq=2
+T 350 300 9 8 0 1 0 0 1
+pinlabel=B
+T 350 300 5 8 0 1 0 2 1
+pintype=in
+}
+P 300 700 0 700 1 0 1
+{
+T 200 750 5 8 1 1 0 6 1
+pinnumber=1
+T 200 650 5 8 0 1 0 8 1
+pinseq=1
+T 350 700 9 8 0 1 0 0 1
+pinlabel=A
+T 350 700 5 8 0 1 0 2 1
+pintype=in
+}
+T 300 900 8 10 1 1 0 0 1
+refdes=U?
+T 500 2250 5 10 0 0 0 0 1
+footprint=DIP14
+T 500 2450 5 10 0 0 0 0 1
+description=4 NAND gates with 2 inputs
+T 500 2850 5 10 0 0 0 0 1
+net=Vcc:14
+T 500 3050 5 10 0 0 0 0 1
+net=GND:7
+T 500 2650 5 10 0 0 0 0 1
+documentation=http://www-s.ti.com/sc/ds/sn74hc00.pdf
+</font></pre>
+</p>
+
+<p>
+This example produces the following (using gschem):
+</p>
+
+<p>
+<a href="media/geda/symbol_7400-1_hidden.png" class="media" target="_blank" title="geda:symbol_7400-1_hidden.png"><img src="media/geda/symbol_7400-1_hidden.png" class="media" title=":geda:symbol_7400-1_hidden.png" alt=":geda:symbol_7400-1_hidden.png" /></a>
+</p>
+
+<p>
+This is the same symbol with all the hidden text visible (via Edit/Show/Hide Inv Text):
+</p>
+
+<p>
+<a href="media/geda/symbol_7400-1.png" class="media" target="_blank" title="geda:symbol_7400-1.png"><img src="media/geda/symbol_7400-1.png" class="media" title=":geda:symbol_7400-1.png" alt=":geda:symbol_7400-1.png" /></a>
+</p>
+
+</div>
+<!-- SECTION "Example" [12016-13732] -->
+<h2><a name="document_revision_history" id="document_revision_history">Document Revision History</a></h2>
+<div class="level2">
+<table class="inline">
+ <tr>
+ <td> September 14th, 2002</td><td>Created symbol.tex from symbols.html </td>
+ </tr>
+ <tr>
+ <td> October 31st, 2002</td><td>Fixed bad example symbol </td>
+ </tr>
+ <tr>
+ <td> February 11th, 2003</td><td>Footprint naming conventions added </td>
+ </tr>
+ <tr>
+ <td> September 27th, 2003</td><td>Applied Dan McMahillâ??s QFP and QFN patch </td>
+ </tr>
+ <tr>
+ <td> July 6th, 2004</td><td>Added a bunch more details/hints to the pin section </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "Document Revision History" [13733-] --></body>
+</html>
diff --git a/docs/wiki/geda-guile_scripting.html b/docs/wiki/geda-guile_scripting.html
index 4d97dfd..f807ac3 100644
--- a/docs/wiki/geda-guile_scripting.html
+++ b/docs/wiki/geda-guile_scripting.html
@@ -19,9 +19,10 @@
<li class="clear">
<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#guile_scripting_reference" class="toc">Guile scripting reference</a></span></div>
+<li class="level2"><div class="li"><span class="li"><a href="#guile_scripting" class="toc">Guile scripting</a></span></div>
<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#libgeda_c_library" class="toc">libgeda C library</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#tutorials" class="toc">Tutorials</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#libgeda_c_library_reference" class="toc">libgeda C library reference</a></span></div></li>
<li class="level3"><div class="li"><span class="li"><a href="#libgeda_geda.scm" class="toc">libgeda geda.scm</a></span></div></li></ul>
</li></ul>
</li></ul>
@@ -30,12 +31,23 @@
-<h2><a name="guile_scripting_reference" id="guile_scripting_reference">Guile scripting reference</a></h2>
+<h2><a name="guile_scripting" id="guile_scripting">Guile scripting</a></h2>
<div class="level2">
</div>
-<!-- SECTION "Guile scripting reference" [1-40] -->
-<h3><a name="libgeda_c_library" id="libgeda_c_library">libgeda C library</a></h3>
+<!-- SECTION "Guile scripting" [1-31] -->
+<h3><a name="tutorials" id="tutorials">Tutorials</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> <a href="geda-gnetlist_scheme_tutorial.html" class="wikilink1" title="geda-gnetlist_scheme_tutorial.html">Scripting a gnetlist backend in scheme</a> (John Doty)</div>
+</li>
+<li class="level1"><div class="li"> See also the <a href="geda-gnetlist_ug.html#scheme_backend_api" class="wikilink1" title="geda-gnetlist_ug.html">Scheme Backend API</a> section of the gnetlist User Guide</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Tutorials" [32-249] -->
+<h3><a name="libgeda_c_library_reference" id="libgeda_c_library_reference">libgeda C library reference</a></h3>
<div class="level3">
<p>
@@ -192,7 +204,7 @@
</ul>
</div>
-<!-- SECTION "libgeda C library" [41-1481] -->
+<!-- SECTION "libgeda C library reference" [250-1700] -->
<h3><a name="libgeda_geda.scm" id="libgeda_geda.scm">libgeda geda.scm</a></h3>
<div class="level3">
@@ -218,5 +230,5 @@
</ul>
</div>
-<!-- SECTION "libgeda geda.scm" [1482-] --></body>
+<!-- SECTION "libgeda geda.scm" [1701-] --></body>
</html>
diff --git a/docs/wiki/geda-pcb_footprint_naming_conventions.html b/docs/wiki/geda-pcb_footprint_naming_conventions.html
new file mode 100644
index 0000000..983826d
--- /dev/null
+++ b/docs/wiki/geda-pcb_footprint_naming_conventions.html
@@ -0,0 +1,231 @@
+
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html>
+<head>
+ <title></title>
+ <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
+ <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
+ <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
+
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+</head>
+<body>
+
+<div class="toc">
+<div class="tocheader toctoggle" id="toc__header">Table of Contents</div>
+<div id="toc__inside">
+
+<ul class="toc">
+<li class="clear">
+
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#footprint_naming_conventions" class="toc">Footprint naming conventions</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#notes" class="toc">Notes</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#integrated_circuit_packages" class="toc">Integrated circuit packages</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#integrated_circuit_smt_packages" class="toc">Integrated circuit SMT packages</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#basic_semiconductors" class="toc">Basic semiconductors</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#basic_smt_semiconductors" class="toc">Basic SMT semiconductors</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#passive_components" class="toc">Passive components</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#passive_smt_components" class="toc">Passive SMT components</a></span></div></li></ul>
+</li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h2><a name="footprint_naming_conventions" id="footprint_naming_conventions">Footprint naming conventions</a></h2>
+<div class="level2">
+
+<p>
+This section describes the conventions for naming of footprints used in PCB (and gEDA/gaf).<br/>
+ The purpose of the naming convention is to establish a standard to maintain the same naming convention through the different phases of the CAD chain. This helps in ensuring that the collaborative effort of gEDA/gaf is not lost.
+</p>
+
+</div>
+<!-- SECTION "Footprint naming conventions" [1-364] -->
+<h3><a name="notes" id="notes">Notes</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Unless otherwise noted, numerical pin names will be used, starting from 1.</div>
+</li>
+<li class="level1"><div class="li"> n is for the pin count.</div>
+</li>
+<li class="level1"><div class="li"> m is for the pin spacing in mils.</div>
+</li>
+<li class="level1"><div class="li"> x is for the x dimension of the package (excluding pins). In particular this is used for the QFP package family.</div>
+</li>
+<li class="level1"><div class="li"> SMT means surface mount, other components are through-hole.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Notes" [365-707] -->
+<h3><a name="integrated_circuit_packages" id="integrated_circuit_packages">Integrated circuit packages</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Dual in line packages with up to 22 100 mil spaced pins and 300 mil row spacing are called DIPn.</div>
+</li>
+<li class="level1"><div class="li"> Dual in line packages with 24 or more 100 mil spaced pins and 300 mil row spacing are called DIPnN.</div>
+</li>
+<li class="level1"><div class="li"> Dual in line packages with 100 mil spaced pins and 400 mil row spacing are called DIPnH.</div>
+</li>
+<li class="level1"><div class="li"> Dual in line packages with 24 or more 100 mil spaced pins and 600 mil row spacing are called DIPn.</div>
+</li>
+<li class="level1"><div class="li"> Shrink dual in line packages with up to 24 70 mil spaced pins and 300 mil row spacing are called SDIPn.</div>
+</li>
+<li class="level1"><div class="li"> Shrink dual in line packages with more than 24 70 mil spaced pins and 400 mil row spacing are called SDIPn.</div>
+</li>
+<li class="level1"><div class="li"> Single in line packages with 100 mil spaced pins are called SIPnN. See also JUMPER, below.</div>
+</li>
+<li class="level1"><div class="li"> Zig-zag in-line package are called ZIPn.</div>
+</li>
+<li class="level1"><div class="li"> Plastic leadless chip carrier with pin socket are called PLCCnX.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Integrated circuit packages" [708-1576] -->
+<h3><a name="integrated_circuit_smt_packages" id="integrated_circuit_smt_packages">Integrated circuit SMT packages</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Small outline SMT packages with up to 16 50 mil spaced pins and 150 mil total width are called SOn.</div>
+</li>
+<li class="level1"><div class="li"> Small outline SMT packages with more than 16 50 mil spaced pins and 150 mil total width are called SOnN.</div>
+</li>
+<li class="level1"><div class="li"> Small outline SMT packages with 50 mil spaced pins and 200 mil total width are called SOnM.</div>
+</li>
+<li class="level1"><div class="li"> Small outline SMT packages with up to 20 50 mil spaced pins and 300 mil total width are called SOnW.</div>
+</li>
+<li class="level1"><div class="li"> Small outline SMT packages with more than 20 50 mil spaced pins and 300 mil total width are called SOn.</div>
+</li>
+<li class="level1"><div class="li"> Small outline SMT packages with 44 or more 50 mil spaced pins and 525 mil total width are called SOn.</div>
+</li>
+<li class="level1"><div class="li"> Metric shrink small outline SMT packages with 0.65 mm spaced pins and 323 mil total width are called MSSOPn. NOTE: To be confirmed.</div>
+</li>
+<li class="level1"><div class="li"> Metric shrink small outline SMT packages with up to 44 0.65 mm spaced pins and 420 mil total width are called MSSOPnW.</div>
+</li>
+<li class="level1"><div class="li"> Metric shrink small outline SMT packages with over 44 0.65 mm spaced pins and 545 mil total width are called MSSOPnW.</div>
+</li>
+<li class="level1"><div class="li"> Shrink small outline SMT packages with 25 mil spaced pins and 420 mil total width are called SSOPnW.</div>
+</li>
+<li class="level1"><div class="li"> Quarter size small outline SMT packages with 25 mil spaced pins and 244 mil total width are called SSOPn.</div>
+</li>
+<li class="level1"><div class="li"> Thin small outline SMT packages with 21.65 mil spaced pins and 535 mil total width are called TSOPn.</div>
+</li>
+<li class="level1"><div class="li"> Thin small outline SMT packages with 20 mil spaced pins and 795 mil total width are called TSOPnA.</div>
+</li>
+<li class="level1"><div class="li"> Thin small outline SMT packages with 20 mil spaced pins and 559 mil total width are called TSOPnB.</div>
+</li>
+<li class="level1"><div class="li"> Thin shrink small outline SMT packages with up to 28 26 mil spaced pins and 260 mil total width are called TSSOPn.</div>
+</li>
+<li class="level1"><div class="li"> Thin shrink small outline SMT packages with over 28 20 mil spaced pins and 319 mil total width are called TSSOPn.</div>
+</li>
+<li class="level1"><div class="li"> Ultra Super Mini SMT packages with up to 16 0.5 mm spaced pins are called USn.</div>
+</li>
+<li class="level1"><div class="li"> Plastic leadless chip carrier SMT are called PLCCn.</div>
+</li>
+<li class="level1"><div class="li"> Square quad-side at pack SMT are called QFPn x.</div>
+</li>
+<li class="level1"><div class="li"> Rectangular quad-side at pack SMT are called QFPn R.</div>
+</li>
+<li class="level1"><div class="li"> Square low profile quad-side at pack SMT are called LQFPn x.</div>
+</li>
+<li class="level1"><div class="li"> Square thin quad-side at pack SMT are called TQFPn x.</div>
+</li>
+<li class="level1"><div class="li"> Square Quad-side at no-lead SMT without exposed paddle (back side contact) are called QFNn x. Pin count is n and package size is x mm.</div>
+</li>
+<li class="level1"><div class="li"> Square Quad-side at no-lead SMT with exposed paddle (back side contact) are called QFNn x EP. Pin count is n and package size is x mm.</div>
+</li>
+<li class="level1"><div class="li"> Thin profile square Quad-side at no-lead SMT without exposed paddle (back side contact) are called TQFNn x. Pin count is n and package size is x mm.</div>
+</li>
+<li class="level1"><div class="li"> Thin profile square Quad-side at no-lead SMT with exposed paddle (back side contact) are called TQFNn x EP. Pin count is n and package size is x mm.</div>
+</li>
+<li class="level1"><div class="li"> Dual in line style crystal oscillators are OSC8 and OSC14.</div>
+</li>
+<li class="level1"><div class="li"> 5 pin SOT SMT packages are SOT25 and SOT325.</div>
+</li>
+<li class="level1"><div class="li"> 6 pin SOT SMT packages are SOT26 and SOT326.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Integrated circuit SMT packages" [1577-4507] -->
+<h3><a name="basic_semiconductors" id="basic_semiconductors">Basic semiconductors</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Axial diodes are called ALFm. Pin 1 is the cathode.</div>
+</li>
+<li class="level1"><div class="li"> Conventional through hole LED is LED3 and LED5 for 3 and 5 mm respectively. Pin 1 is plus. NOTE: Should probably be changed to be in line with diode convention.</div>
+</li>
+<li class="level1"><div class="li"> TO transistors are TO5, TO92, TO126, TO220 etc. Suxes may apply, e.g. TO126W is for wide, TO126S is for standing, TO126SW is for standing, wide.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Basic semiconductors" [4508-4910] -->
+<h3><a name="basic_smt_semiconductors" id="basic_smt_semiconductors">Basic SMT semiconductors</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> SOD diode SMT packages use their standard package name, e.g. SOD80, SOD87, SOD106A, SOD110. There are also SOD123, SOD323 with narrow pads.</div>
+</li>
+<li class="level1"><div class="li"> SOT transistor SMT packages use their standard package name, e.g. SOT23, SOT323. There is also an SC90.</div>
+</li>
+<li class="level1"><div class="li"> SOT transistor SMT packages with numbering as for diodes (pin 1 is cathode, pin 2 anode) are SOT23D, SOT323D.</div>
+</li>
+<li class="level1"><div class="li"> 4 pin SOT SMT packages are SOT89, SOT143, SOT223.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Basic SMT semiconductors" [4911-5366] -->
+<h3><a name="passive_components" id="passive_components">Passive components</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Axial non-polar components (typically resistor, capacitor) are called ACYm.</div>
+</li>
+<li class="level1"><div class="li"> Bottom lead (radial) non-polar circular component (typically capacitor) is RCYm.</div>
+</li>
+<li class="level1"><div class="li"> Bottom lead non-polar rectangular component (typically capacitor) is BREm.</div>
+</li>
+<li class="level1"><div class="li"> A standard crystal is HC49, or other HC designations as required.</div>
+</li>
+<li class="level1"><div class="li"> Single row 100 mil pin spacing jumpers are JUMPERn. The main difference compared to single in line package is the hole size.</div>
+</li>
+<li class="level1"><div class="li"> Dual row 100 mil spacing headers with DIP pin numbering are HEADERn 1. Note that n is an even number.</div>
+</li>
+<li class="level1"><div class="li"> Dual row 100 mil spacing headers with ribbon cable numbering are HEADERn 2. Note that n is an even number.</div>
+</li>
+<li class="level1"><div class="li"> Angled full header connectors with latches are DIN41651 n.</div>
+</li>
+<li class="level1"><div class="li"> Standing full header connectors with latches are DIN41651 nS.</div>
+</li>
+<li class="level1"><div class="li"> DSUB connectors female are DBnF.</div>
+</li>
+<li class="level1"><div class="li"> DSUB connectors male are DBnM.</div>
+</li>
+<li class="level1"><div class="li"> Female DIN card-to-card connectors are DIN41612CnF. Add S suffix for standing.</div>
+</li>
+<li class="level1"><div class="li"> Male DIN card-to-card connectors are DIN41612CnM. Add S suffix for standing.</div>
+</li>
+<li class="level1"><div class="li"> AMP modular RJ connectors with screen are RJ11, RJ12 and RJ45.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Passive components" [5367-6488] -->
+<h3><a name="passive_smt_components" id="passive_smt_components">Passive SMT components</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> Standard SMT resistors, inductors, capacitors etc are 0201, 0402, 0603, 0805, 1206, 1210, 1806, 1812, 1825, 2020, 2706.</div>
+</li>
+<li class="level1"><div class="li"> Tantalum SMT capacitors are EIA3216, EIA3528, EIA6032, and EIA7343. Pin 1 is plus.</div>
+</li>
+<li class="level1"><div class="li"> SMT electrolytics are designated by can diameter in 1/10 mm: SME33, SME43, SME53, SME66, SME84, SME104.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Passive SMT components" [6489-] --></body>
+</html>
diff --git a/docs/wiki/geda-pcb_footprints.html b/docs/wiki/geda-pcb_footprints.html
index d2339a6..85352ff 100644
--- a/docs/wiki/geda-pcb_footprints.html
+++ b/docs/wiki/geda-pcb_footprints.html
@@ -18,8 +18,8 @@
<ul class="toc">
<li class="level1"><div class="li"><span class="li"><a href="#pcb_footprint_guide" class="toc">PCB Footprint Guide</a></span></div>
<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#using_pcb_footprints" class="toc">Using PCB Footprints</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#creating_pcb_footprints" class="toc">Creating PCB Footprints</a></span></div>
+<li class="clear">
+
<ul class="toc">
<li class="level3"><div class="li"><span class="li"><a href="#footprint_basics" class="toc">Footprint basics</a></span></div></li>
<li class="level3"><div class="li"><span class="li"><a href="#pcb_footprint_faq" class="toc">PCB Footprint FAQ</a></span></div></li>
@@ -34,23 +34,15 @@
<h1><a name="pcb_footprint_guide" id="pcb_footprint_guide">PCB Footprint Guide</a></h1>
<div class="level1">
+<ul>
+<li class="level1"><div class="li"> The PCB <acronym title="Frequently Asked Questions">FAQ</acronym>: <a href="geda-pcb_tips.html" class="wikilink1" title="geda-pcb_tips.html">pcb_tips</a>. </div>
+</li>
+<li class="level1"><div class="li"> <a href="geda-pcb_footprint_naming_conventions.html" class="wikilink1" title="geda-pcb_footprint_naming_conventions.html">PCB Footprint Naming Conventions</a> : read this to learn how to <em>name</em> your footprint files.</div>
+</li>
+</ul>
</div>
-<!-- SECTION "PCB Footprint Guide" [3-37] -->
-<h2><a name="using_pcb_footprints" id="using_pcb_footprints">Using PCB Footprints</a></h2>
-<div class="level2">
-
-</div>
-<!-- SECTION "Using PCB Footprints" [38-71] -->
-<h2><a name="creating_pcb_footprints" id="creating_pcb_footprints">Creating PCB Footprints</a></h2>
-<div class="level2">
-
-<p>
-<strong>This page is redundant!!! see <a href="geda-pcb_tips.html" class="wikilink1" title="geda-pcb_tips.html">pcb_tips</a>. Furthermore, there is no better way to understand the inner workings of footprints than the pdf <em>Footprint Creation for the Open-Source Layout Program â??PCBâ??</em></strong><a href="http://brorson.com/gEDA/land_patterns_20070818.pdf"; class="urlextern" title="http://brorson.com/gEDA/land_patterns_20070818.pdf"; rel="nofollow">http://brorson.com/gEDA/land_patterns_20070818.pdf</a>
-</p>
-
-</div>
-<!-- SECTION "Creating PCB Footprints" [72-375] -->
+<!-- SECTION "PCB Footprint Guide" [4-183] -->
<h3><a name="footprint_basics" id="footprint_basics">Footprint basics</a></h3>
<div class="level3">
<ul>
@@ -69,7 +61,7 @@
</ul>
</div>
-<!-- SECTION "Footprint basics" [376-906] -->
+<!-- SECTION "Footprint basics" [184-713] -->
<h3><a name="pcb_footprint_faq" id="pcb_footprint_faq">PCB Footprint FAQ</a></h3>
<div class="level3">
@@ -138,7 +130,7 @@ Simply add a pad on top of your pin and give them the same pin-number. If the s
</p>
</div>
-<!-- SECTION "PCB Footprint FAQ" [907-2204] -->
+<!-- SECTION "PCB Footprint FAQ" [714-2011] -->
<h2><a name="sharing_pcb_footprints" id="sharing_pcb_footprints">Sharing PCB Footprints</a></h2>
<div class="level2">
@@ -160,5 +152,5 @@ Simply add a pad on top of your pin and give them the same pin-number. If the s
</p>
</div>
-<!-- SECTION "Sharing PCB Footprints" [2205-] --></body>
+<!-- SECTION "Sharing PCB Footprints" [2012-] --></body>
</html>
diff --git a/docs/wiki/geda-pcb_funding_sow-fwdann_ideas.html b/docs/wiki/geda-pcb_funding_sow-fwdann_ideas.html
index e15c265..f0072a4 100644
--- a/docs/wiki/geda-pcb_funding_sow-fwdann_ideas.html
+++ b/docs/wiki/geda-pcb_funding_sow-fwdann_ideas.html
@@ -10,7 +10,6 @@
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
</head>
<body>
-<a href=.>start</a> => <a href=geda-pcb_funding_sow.html>pcb_funding_sow</a></br>
diff --git a/docs/wiki/geda-pcb_funding_sow-gui_ideas.html b/docs/wiki/geda-pcb_funding_sow-gui_ideas.html
index 7fc3e5e..326c2b3 100644
--- a/docs/wiki/geda-pcb_funding_sow-gui_ideas.html
+++ b/docs/wiki/geda-pcb_funding_sow-gui_ideas.html
@@ -10,7 +10,6 @@
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
</head>
<body>
-<a href=.>start</a> => <a href=geda-pcb_funding_sow.html>pcb_funding_sow</a></br>
diff --git a/docs/wiki/geda-pcb_tips.html b/docs/wiki/geda-pcb_tips.html
index 6d473df..998095a 100644
--- a/docs/wiki/geda-pcb_tips.html
+++ b/docs/wiki/geda-pcb_tips.html
@@ -48,6 +48,7 @@
<li class="level2"><div class="li"><span class="li"><a href="#what_is_the_recommended_way_to_deal_with_different_footprints_for_the_same_sort_of_device" class="toc">What is the recommended way to deal with different footprints for the same sort of device?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_draw_a_new_footprint" class="toc">How do I draw a new footprint?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_edit_change_an_existing_footprint" class="toc">How do I edit/change an existing footprint?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#pcb_does_not_save_silk_when_i_try_to_make_a_footprint" class="toc">pcb does not save silk when I try to make a footprint</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#what_is_the_proper_way_to_make_a_double-sided_footprint" class="toc">What is the proper way to make a double-sided footprint?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_add_a_footprint_library_to_pcb" class="toc">How do I add a footprint library to PCB?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_update_a_footprint_in_my_layout" class="toc">How do I update a footprint in my layout?</a></span></div></li>
@@ -396,7 +397,7 @@ Everybody does this a little differently. Some people draw the footprint entirel
</ul>
</div>
-<!-- SECTION "How do I draw a new footprint?" [11969-13166] -->
+<!-- SECTION "How do I draw a new footprint?" [11969-13167] -->
<h2><a name="how_do_i_edit_change_an_existing_footprint" id="how_do_i_edit_change_an_existing_footprint">How do I edit/change an existing footprint?</a></h2>
<div class="level2">
@@ -437,7 +438,16 @@ Alternatively, you can use your favorite text editor and edit the source code of
</p>
</div>
-<!-- SECTION "How do I edit/change an existing footprint?" [13167-14134] -->
+<!-- SECTION "How do I edit/change an existing footprint?" [13168-14135] -->
+<h2><a name="pcb_does_not_save_silk_when_i_try_to_make_a_footprint" id="pcb_does_not_save_silk_when_i_try_to_make_a_footprint">pcb does not save silk when I try to make a footprint</a></h2>
+<div class="level2">
+
+<p>
+The silk of footprints can only deal with lines and arcs. All the other objects like polygons, rectangles and text are silently omitted during <code>Convert buffer to element</code>. If you need text in footprints you have to literary draw the letters with the line tool.
+</p>
+
+</div>
+<!-- SECTION "pcb does not save silk when I try to make a footprint" [14136-14465] -->
<h2><a name="what_is_the_proper_way_to_make_a_double-sided_footprint" id="what_is_the_proper_way_to_make_a_double-sided_footprint">What is the proper way to make a double-sided footprint?</a></h2>
<div class="level2">
@@ -455,7 +465,7 @@ If you draw the footprint with pcb-<acronym title="Graphical User Interface">GUI
</p>
</div>
-<!-- SECTION "What is the proper way to make a double-sided footprint?" [14135-14704] -->
+<!-- SECTION "What is the proper way to make a double-sided footprint?" [14466-15035] -->
<h2><a name="how_do_i_add_a_footprint_library_to_pcb" id="how_do_i_add_a_footprint_library_to_pcb">How do I add a footprint library to PCB?</a></h2>
<div class="level2">
@@ -466,7 +476,7 @@ Adding footprint libraries can be done from the <acronym title="Graphical User I
</p>
</div>
-<!-- SECTION "How do I add a footprint library to PCB?" [14705-15210] -->
+<!-- SECTION "How do I add a footprint library to PCB?" [15036-15541] -->
<h2><a name="how_do_i_update_a_footprint_in_my_layout" id="how_do_i_update_a_footprint_in_my_layout">How do I update a footprint in my layout?</a></h2>
<div class="level2">
@@ -476,7 +486,7 @@ There is no way to automatically replace all instances of a footprint with the n
</p>
</div>
-<!-- SECTION "How do I update a footprint in my layout?" [15211-15933] -->
+<!-- SECTION "How do I update a footprint in my layout?" [15542-16264] -->
<h2><a name="pcb_is_not_finding_my_footprints._why" id="pcb_is_not_finding_my_footprints._why">PCB is not finding my footprints. Why?</a></h2>
<div class="level2">
@@ -485,7 +495,7 @@ The footprint path that PCB uses is defined using the <strong><code>Pcb.elementP
</p>
</div>
-<!-- SECTION "PCB is not finding my footprints. Why?" [15934-16282] -->
+<!-- SECTION "PCB is not finding my footprints. Why?" [16265-16613] -->
<h2><a name="now_that_i_have_all_of_these_footprints_where_do_i_put_them" id="now_that_i_have_all_of_these_footprints_where_do_i_put_them">Now that I have all of these footprints where do I put them?</a></h2>
<div class="level2">
@@ -532,7 +542,7 @@ gsch2pcb myproject
</pre>
</div>
-<!-- SECTION "Now that I have all of these footprints where do I put them?" [16283-17830] -->
+<!-- SECTION "Now that I have all of these footprints where do I put them?" [16614-18161] -->
<h2><a name="what_s_this_business_about_flashed_pads" id="what_s_this_business_about_flashed_pads">What's this business about flashed pads?</a></h2>
<div class="level2">
@@ -549,12 +559,12 @@ Now the plotters I believe are all laser plotters and the concept of flashed vs
</p>
</div>
-<!-- SECTION "What's this business about flashed pads?" [17831-19490] -->
+<!-- SECTION "What's this business about flashed pads?" [18162-19821] -->
<h1><a name="component_placement" id="component_placement">Component placement</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Component placement" [19491-19525] -->
+<!-- SECTION "Component placement" [19822-19856] -->
<h2><a name="how_do_i_rotate_a_selection_i.e._of_more_than_one_item" id="how_do_i_rotate_a_selection_i.e._of_more_than_one_item">How do I rotate a selection (i.e. of more than one item)?</a></h2>
<div class="level2">
<ol>
@@ -573,7 +583,7 @@ Now the plotters I believe are all laser plotters and the concept of flashed vs
</p>
</div>
-<!-- SECTION "How do I rotate a selection (i.e. of more than one item)?" [19526-19969] -->
+<!-- SECTION "How do I rotate a selection (i.e. of more than one item)?" [19857-20300] -->
<h2><a name="how_do_i_rotate_objects_by_an_arbitrary_angle" id="how_do_i_rotate_objects_by_an_arbitrary_angle">How do I rotate objects by an arbitrary angle?</a></h2>
<div class="level2">
<ol>
@@ -590,7 +600,7 @@ Now the plotters I believe are all laser plotters and the concept of flashed vs
</p>
</div>
-<!-- SECTION "How do I rotate objects by an arbitrary angle?" [19970-20382] -->
+<!-- SECTION "How do I rotate objects by an arbitrary angle?" [20301-20713] -->
<h2><a name="how_do_i_move_objects_by_an_arbitrary_distance" id="how_do_i_move_objects_by_an_arbitrary_distance">How do I move objects by an arbitrary distance?</a></h2>
<div class="level2">
<ol>
@@ -607,7 +617,7 @@ If both coordinates are prefixed with a "+", or "-" the move
</p>
</div>
-<!-- SECTION "How do I move objects by an arbitrary distance?" [20383-20824] -->
+<!-- SECTION "How do I move objects by an arbitrary distance?" [20714-21155] -->
<h2><a name="how_do_i_move_objects_to_an_absolute_location" id="how_do_i_move_objects_to_an_absolute_location">How do I move objects to an absolute location?</a></h2>
<div class="level2">
@@ -616,7 +626,7 @@ Use the command â??MoveObject()" as described above.
</p>
</div>
-<!-- SECTION "How do I move objects to an absolute location?" [20825-20935] -->
+<!-- SECTION "How do I move objects to an absolute location?" [21156-21266] -->
<h2><a name="how_do_i_change_the_size_of_a_graphical_object_such_as_text_silkscreen_lines_etc" id="how_do_i_change_the_size_of_a_graphical_object_such_as_text_silkscreen_lines_etc">How do I change the size of a graphical object (such as text, silkscreen lines, etc)?</a></h2>
<div class="level2">
<ul>
@@ -631,7 +641,7 @@ Use the command â??MoveObject()" as described above.
</p>
</div>
-<!-- SECTION "How do I change the size of a graphical object (such as text, silkscreen lines, etc)?" [20936-21387] -->
+<!-- SECTION "How do I change the size of a graphical object (such as text, silkscreen lines, etc)?" [21267-21718] -->
<h2><a name="how_do_i_put_components_on_both_faces_in_pcb" id="how_do_i_put_components_on_both_faces_in_pcb">How do I put components on both faces in PCB?</a></h2>
<div class="level2">
@@ -646,7 +656,7 @@ There are two ways to do it:
</ul>
</div>
-<!-- SECTION "How do I put components on both faces in PCB?" [21388-21856] -->
+<!-- SECTION "How do I put components on both faces in PCB?" [21719-22187] -->
<h2><a name="i_cant_t_move_the_components_on_the_other_side_of_the_board" id="i_cant_t_move_the_components_on_the_other_side_of_the_board">I cant't move the components on the other side of the board!</a></h2>
<div class="level2">
@@ -680,7 +690,7 @@ The way to access these modes differs among the <acronym title="Graphical User I
</p>
</div>
-<!-- SECTION "I cant't move the components on the other side of the board!" [21857-27529] -->
+<!-- SECTION "I cant't move the components on the other side of the board!" [22188-27860] -->
<h2><a name="i_got_stuck_how_do_i_go_back" id="i_got_stuck_how_do_i_go_back">I got stuck! How do I go back?</a></h2>
<div class="level2">
@@ -689,7 +699,7 @@ The universal undo key [<strong><code>U</code></strong>] works even while in the
</p>
</div>
-<!-- SECTION "I got stuck! How do I go back?" [27530-27802] -->
+<!-- SECTION "I got stuck! How do I go back?" [27861-28133] -->
<h2><a name="how_do_i_move_one_set_of_layer_tracks_to_a_different_layer" id="how_do_i_move_one_set_of_layer_tracks_to_a_different_layer">How do I move one set of layer tracks to a different layer?</a></h2>
<div class="level2">
<ol>
@@ -702,7 +712,7 @@ The universal undo key [<strong><code>U</code></strong>] works even while in the
</ol>
</div>
-<!-- SECTION "How do I move one set of layer tracks to a different layer?" [27803-28243] -->
+<!-- SECTION "How do I move one set of layer tracks to a different layer?" [28134-28574] -->
<h2><a name="how_do_i_achieve_open_vias_clear_of_soldermask" id="how_do_i_achieve_open_vias_clear_of_soldermask">How do I achieve open vias clear of soldermask</a></h2>
<div class="level2">
@@ -744,7 +754,7 @@ where <code><delta></code> is a size given in 1/100 of a mil. Thus the num
</p>
</div>
-<!-- SECTION "How do I achieve open vias clear of soldermask" [28244-30019] -->
+<!-- SECTION "How do I achieve open vias clear of soldermask" [28575-30350] -->
<h2><a name="how_do_i_change_the_soldermask_clearance_around_a_hole_pad" id="how_do_i_change_the_soldermask_clearance_around_a_hole_pad">How do I change the soldermask clearance around a hole/pad?</a></h2>
<div class="level2">
@@ -753,7 +763,7 @@ By default holes and pads will be cleared by an amount given in the correspondin
</p>
</div>
-<!-- SECTION "How do I change the soldermask clearance around a hole/pad?" [30020-30546] -->
+<!-- SECTION "How do I change the soldermask clearance around a hole/pad?" [30351-30877] -->
<h2><a name="how_do_i_change_the_size_of_my_tracks" id="how_do_i_change_the_size_of_my_tracks">How do I change the size of my tracks?</a></h2>
<div class="level2">
@@ -770,7 +780,7 @@ There are a number of ways to change the size of already laid down tracks:
</ol>
</div>
-<!-- SECTION "How do I change the size of my tracks?" [30547-31484] -->
+<!-- SECTION "How do I change the size of my tracks?" [30878-31815] -->
<h2><a name="how_do_i_drive_a_via_to_connect_a_track_to_a_ground_plane_on_a_different_layer" id="how_do_i_drive_a_via_to_connect_a_track_to_a_ground_plane_on_a_different_layer">How do I drive a via to connect a track to a ground plane on a different layer?</a></h2>
<div class="level2">
<ol>
@@ -793,7 +803,7 @@ There are a number of ways to change the size of already laid down tracks:
</ol>
</div>
-<!-- SECTION "How do I drive a via to connect a track to a ground plane on a different layer?" [31485-31970] -->
+<!-- SECTION "How do I drive a via to connect a track to a ground plane on a different layer?" [31816-32301] -->
<h2><a name="what_is_the_easiest_way_to_create_a_thermal_via" id="what_is_the_easiest_way_to_create_a_thermal_via">What is the easiest way to create a "thermal via"?</a></h2>
<div class="level2">
@@ -812,7 +822,7 @@ Here are some suggestions:
</ul>
</div>
-<!-- SECTION "What is the easiest way to create a thermal via?" [31971-32748] -->
+<!-- SECTION "What is the easiest way to create a thermal via?" [32302-33079] -->
<h2><a name="i_want_to_draw_a_track_between_two_segments_on_the_same_net_but_pcb_won_t_let_me_why" id="i_want_to_draw_a_track_between_two_segments_on_the_same_net_but_pcb_won_t_let_me_why">I want to draw a track between two segments on the same net, but PCB won't let me! Why?</a></h2>
<div class="level2">
@@ -831,7 +841,7 @@ You are likely drawing tracks with auto-DRC on. To connect the two segments, her
</ul>
</div>
-<!-- SECTION "I want to draw a track between two segments on the same net, but PCB won't let me! Why?" [32749-34067] -->
+<!-- SECTION "I want to draw a track between two segments on the same net, but PCB won't let me! Why?" [33080-34398] -->
<h2><a name="pcb_seems_to_munge_my_components_names_and_complains_that_it_can_t_find_proper_nets_for_the_pins_how_come" id="pcb_seems_to_munge_my_components_names_and_complains_that_it_can_t_find_proper_nets_for_the_pins_how_come">PCB seems to munge my components names and complains that it can't find proper nets for the pins! How come?</a></h2>
<div class="level2">
@@ -841,7 +851,7 @@ Most likely you named them such that pcb believes they are one part. Lower case
</p>
</div>
-<!-- SECTION "PCB seems to munge my components names and complains that it can't find proper nets for the pins! How come?" [34068-34706] -->
+<!-- SECTION "PCB seems to munge my components names and complains that it can't find proper nets for the pins! How come?" [34399-35037] -->
<h2><a name="how_can_i_set_color_and_thickness_of_the_rats_nests" id="how_can_i_set_color_and_thickness_of_the_rats_nests">How can I set color and thickness of the rats nests?</a></h2>
<div class="level2">
@@ -858,7 +868,7 @@ Values 0..19 are fixed width in screen pixels. Anything larger means PCB units (
</p>
</div>
-<!-- SECTION "How can I set color and thickness of the rats nests?" [34707-35211] -->
+<!-- SECTION "How can I set color and thickness of the rats nests?" [35038-35542] -->
<h2><a name="where_is_that_last_remaining_rat" id="where_is_that_last_remaining_rat">Where is that last remaining rat?</a></h2>
<div class="level2">
@@ -867,12 +877,12 @@ Sometimes remaining rats are hard to see, because they have zero length. This wi
</p>
</div>
-<!-- SECTION "Where is that last remaining rat?" [35212-35539] -->
+<!-- SECTION "Where is that last remaining rat?" [35543-35870] -->
<h1><a name="beyond_tracks_and_footprints" id="beyond_tracks_and_footprints">Beyond tracks and footprints</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Beyond tracks and footprints" [35540-35582] -->
+<!-- SECTION "Beyond tracks and footprints" [35871-35913] -->
<h2><a name="how_do_i_trace_a_drawing_a_print_or_another_pcb" id="how_do_i_trace_a_drawing_a_print_or_another_pcb">How do I trace a drawing, a print, or another PCB?</a></h2>
<div class="level2">
@@ -889,7 +899,7 @@ If you donâ??t like to use PCB confined to the area of the board, i.e. if you wa
</p>
</div>
-<!-- SECTION "How do I trace a drawing, a print, or another PCB?" [35583-36423] -->
+<!-- SECTION "How do I trace a drawing, a print, or another PCB?" [35914-36754] -->
<h2><a name="i_can_t_copy_component_pads_in_a_layout._what_gives" id="i_can_t_copy_component_pads_in_a_layout._what_gives">I can't copy component pads in a layout. What gives?</a></h2>
<div class="level2">
@@ -914,7 +924,7 @@ Then I go to paste the copied area… and all that moves are a couple of tr
</p>
</div>
-<!-- SECTION "I can't copy component pads in a layout. What gives?" [36424-37078] -->
+<!-- SECTION "I can't copy component pads in a layout. What gives?" [36755-37409] -->
<h2><a name="how_do_i_fill_areas_with_copper" id="how_do_i_fill_areas_with_copper">How do I fill areas with copper?</a></h2>
<div class="level2">
@@ -923,7 +933,7 @@ Use rectangles and polygon planes. These items will always avoid vias, pads and
</p>
</div>
-<!-- SECTION "How do I fill areas with copper?" [37079-37442] -->
+<!-- SECTION "How do I fill areas with copper?" [37410-37773] -->
<h2><a name="how_can_i_assign_my_polygon_to_a_net" id="how_can_i_assign_my_polygon_to_a_net">How can I assign my polygon to a net?</a></h2>
<div class="level2">
@@ -932,7 +942,7 @@ Polygons are not â??assignedâ?? to nets, theyâ??re connected to them. Pads are t
</p>
</div>
-<!-- SECTION "How can I assign my polygon to a net?" [37443-37745] -->
+<!-- SECTION "How can I assign my polygon to a net?" [37774-38076] -->
<h2><a name="how_can_i_connect_tracks_pads_or_vias_to_my_polygon" id="how_can_i_connect_tracks_pads_or_vias_to_my_polygon">How can I connect tracks, pads, or vias to my polygon?</a></h2>
<div class="level2">
@@ -951,7 +961,7 @@ There are different ways to adequately connect different types of objects to a p
</ul>
</div>
-<!-- SECTION "How can I connect tracks, pads, or vias to my polygon?" [37746-38632] -->
+<!-- SECTION "How can I connect tracks, pads, or vias to my polygon?" [38077-38963] -->
<h2><a name="the_polygons_are_shorting_my_tracks_what_can_i_do_about_it" id="the_polygons_are_shorting_my_tracks_what_can_i_do_about_it">The polygons are shorting my tracks! What can I do about it?</a></h2>
<div class="level2">
@@ -960,7 +970,7 @@ You didnâ??t have â??Enable_new_lines_clear_polygonsâ?? checked in the settings
</p>
</div>
-<!-- SECTION "The polygons are shorting my tracks! What can I do about it?" [38633-39282] -->
+<!-- SECTION "The polygons are shorting my tracks! What can I do about it?" [38964-39613] -->
<h2><a name="how_do_i_change_polygon_clearance" id="how_do_i_change_polygon_clearance">How do I change polygon clearance?</a></h2>
<div class="level2">
@@ -973,16 +983,16 @@ The amount of the increment can be configured in the dialog File/Preference/Incr
</p>
</div>
-<!-- SECTION "How do I change polygon clearance?" [39283-39783] -->
+<!-- SECTION "How do I change polygon clearance?" [39614-40115] -->
<h2><a name="how_do_i_hide_the_polygons_while_i_edit_the_layout" id="how_do_i_hide_the_polygons_while_i_edit_the_layout">How do I hide the polygons while I edit the layout?</a></h2>
<div class="level2">
<p>
-Put the polygons (and rectangles) on a separate layer. Use the preference to make sure, this layer is not in the same group as the tracks. Disable the layer by a click on the corresponding layer button in the main window. After you are finished with the changes, use the preference dialog to let the polygon layer join the layer of the tracks. You will have to save and reload the layout to trigger recalculation of polygons so they are adapted to your edits. Alternatively a restart will recaalculate the polygons too.
+Put the polygons (and rectangles) on a separate layer. Use the preference to make sure, this layer is not in the same group as the tracks. Disable the layer by a click on the corresponding layer button in the main window. After you are finished with the changes, use the preference dialog to let the polygon layer join the layer of the tracks. You will have to save and reload the layout to trigger recalculation of polygons so they are adapted to your edits. Alternatively a restart will recalculate the polygons too.
</p>
</div>
-<!-- SECTION "How do I hide the polygons while I edit the layout?" [39784-40369] -->
+<!-- SECTION "How do I hide the polygons while I edit the layout?" [40116-40700] -->
<h2><a name="polygons_are_making_the_gui_sluggish._what_i_can_do_about_it" id="polygons_are_making_the_gui_sluggish._what_i_can_do_about_it">Polygons are making the GUI sluggish. What I can do about it?</a></h2>
<div class="level2">
@@ -999,7 +1009,7 @@ Parts of the polygon that are not connected to some net are automatically elimin
</ul>
</div>
-<!-- SECTION "Polygons are making the GUI sluggish. What I can do about it?" [40370-41413] -->
+<!-- SECTION "Polygons are making the GUI sluggish. What I can do about it?" [40701-41744] -->
<h2><a name="after_i_defined_those_ground_planes_pcb_takes_ages_to_load._how_come" id="after_i_defined_those_ground_planes_pcb_takes_ages_to_load._how_come">After I defined those ground planes, pcb takes ages to load. How come?</a></h2>
<div class="level2">
@@ -1008,7 +1018,7 @@ Polygon calculation is potentially an expensive operation in terms of processor
</p>
</div>
-<!-- SECTION "After I defined those ground planes, pcb takes ages to load. How come?" [41414-41834] -->
+<!-- SECTION "After I defined those ground planes, pcb takes ages to load. How come?" [41745-42165] -->
<h2><a name="how_do_i_edit_polygons" id="how_do_i_edit_polygons">How do I edit polygons?</a></h2>
<div class="level2">
@@ -1021,7 +1031,7 @@ There are four basic ways to edit polygon outlines. You can move and delete vert
</p>
</div>
-<!-- SECTION "How do I edit polygons?" [41835-43020] -->
+<!-- SECTION "How do I edit polygons?" [42166-43351] -->
<h2><a name="how_do_i_place_vias_that_connect_to_a_polygon_for_full_thermal_dissipation_or_full_shielding_integrity" id="how_do_i_place_vias_that_connect_to_a_polygon_for_full_thermal_dissipation_or_full_shielding_integrity">How do I place vias that connect to a polygon for full thermal dissipation or full shielding integrity?</a></h2>
<div class="level2">
@@ -1050,7 +1060,7 @@ You can also add another polygon on-top of the polygon to which you want to conn
</p>
</div>
-<!-- SECTION "How do I place vias that connect to a polygon for full thermal dissipation or full shielding integrity?" [43021-44942] -->
+<!-- SECTION "How do I place vias that connect to a polygon for full thermal dissipation or full shielding integrity?" [43352-45273] -->
<h2><a name="can_polygons_be_un-masked_can_a_polygon_be_made_bare-copper_with_no_solder_mask" id="can_polygons_be_un-masked_can_a_polygon_be_made_bare-copper_with_no_solder_mask">Can polygons be un-masked? (Can a polygon be made bare-copper with no solder mask?)</a></h2>
<div class="level2">
@@ -1077,7 +1087,7 @@ While the pad witdth is limited to 250 mil, clearance can be arbitrary.
</p>
</div>
-<!-- SECTION "Can polygons be un-masked? (Can a polygon be made bare-copper with no solder mask?)" [44943-45692] -->
+<!-- SECTION "Can polygons be un-masked? (Can a polygon be made bare-copper with no solder mask?)" [45274-46023] -->
<h2><a name="how_do_i_place_mounting_holes" id="how_do_i_place_mounting_holes">How do I place mounting holes?</a></h2>
<div class="level2">
@@ -1098,7 +1108,7 @@ For footprint examples see <a href="http://www.luciani.org/geda/pcb/pcb-footprin
</p>
</div>
-<!-- SECTION "How do I place mounting holes?" [45693-46357] -->
+<!-- SECTION "How do I place mounting holes?" [46024-46688] -->
<h2><a name="why_is_it_possible_to_make_a_thermal_for_pin_but_not_for_a_pad" id="why_is_it_possible_to_make_a_thermal_for_pin_but_not_for_a_pad">Why is it possible to make a thermal for pin, but not for a pad?</a></h2>
<div class="level2">
@@ -1107,7 +1117,7 @@ The reason is that pins usually have sufficient spacing that the plane surroundi
</p>
</div>
-<!-- SECTION "Why is it possible to make a thermal for pin, but not for a pad?" [46358-46989] -->
+<!-- SECTION "Why is it possible to make a thermal for pin, but not for a pad?" [46689-47320] -->
<h2><a name="can_pcb_be_used_to_make_single_layer_boards" id="can_pcb_be_used_to_make_single_layer_boards">Can PCB be used to make single layer boards?</a></h2>
<div class="level2">
@@ -1128,7 +1138,7 @@ When you dump your gerbers, delete the component side one and rename the plated-
</p>
</div>
-<!-- SECTION "Can PCB be used to make single layer boards?" [46990-48215] -->
+<!-- SECTION "Can PCB be used to make single layer boards?" [47321-48546] -->
<h2><a name="what_resources_exist_to_process_pcb_files_using_scripts" id="what_resources_exist_to_process_pcb_files_using_scripts">What resources exist to process PCB files using scripts?</a></h2>
<div class="level2">
@@ -1147,7 +1157,7 @@ One of PCBâ??s great features is that it uses an easily understood <acronym titl
</ol>
</div>
-<!-- SECTION "What resources exist to process PCB files using scripts?" [48216-49501] -->
+<!-- SECTION "What resources exist to process PCB files using scripts?" [48547-49832] -->
<h2><a name="how_do_i_import_external_vector_graphics" id="how_do_i_import_external_vector_graphics">How do I import external vector graphics?</a></h2>
<div class="level2">
@@ -1160,7 +1170,7 @@ Import of external vector graphics is usefull if an irregular shape of the pcb i
</p>
</div>
-<!-- SECTION "How do I import external vector graphics?" [49502-50581] -->
+<!-- SECTION "How do I import external vector graphics?" [49833-50912] -->
<h2><a name="is_there_a_way_to_import_a_dxf_drawing_from_mechanical_cad_applications" id="is_there_a_way_to_import_a_dxf_drawing_from_mechanical_cad_applications">Is there a way to import a DXF drawing from mechanical CAD applications?</a></h2>
<div class="level2">
@@ -1169,7 +1179,7 @@ There is no import filter to directly load a DXF file to pcb. However, the open
</p>
</div>
-<!-- SECTION "Is there a way to import a DXF drawing from mechanical CAD applications?" [50582-50936] -->
+<!-- SECTION "Is there a way to import a DXF drawing from mechanical CAD applications?" [50913-51267] -->
<h2><a name="what_is_the_best_way_to_do_weird_footprints" id="what_is_the_best_way_to_do_weird_footprints">What is the best way to do weird footprints?</a></h2>
<div class="level2">
@@ -1220,7 +1230,7 @@ Sometimes footprints call for shapes that are difficult to achieve with the rest
</ul>
</div>
-<!-- SECTION "What is the best way to do weird footprints?" [50937-51798] -->
+<!-- SECTION "What is the best way to do weird footprints?" [51268-52129] -->
<h2><a name="how_do_i_attach_a_name_to_my_layout" id="how_do_i_attach_a_name_to_my_layout">How Do I attach a name to my layout?</a></h2>
<div class="level2">
@@ -1229,7 +1239,7 @@ You can set the name of the current pcb with <code>Menu Edit - Edit name of - la
</p>
</div>
-<!-- SECTION "How Do I attach a name to my layout?" [51799-52071] -->
+<!-- SECTION "How Do I attach a name to my layout?" [52130-52402] -->
<h2><a name="is_there_a_way_to_do_multiple_instances_of_a_subcircuits" id="is_there_a_way_to_do_multiple_instances_of_a_subcircuits">Is there a way to do multiple instances of a subcircuits?</a></h2>
<div class="level2">
@@ -1246,12 +1256,12 @@ The pair of scripts was written a few years ago and is not used regularily. They
</p>
</div>
-<!-- SECTION "Is there a way to do multiple instances of a subcircuits?" [52072-53179] -->
+<!-- SECTION "Is there a way to do multiple instances of a subcircuits?" [52403-53510] -->
<h1><a name="auto_router" id="auto_router">Auto Router</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Auto Router" [53180-53209] -->
+<!-- SECTION "Auto Router" [53511-53540] -->
<h2><a name="how_do_i_make_the_most_of_the_auto_router" id="how_do_i_make_the_most_of_the_auto_router">How do I make the most of the auto router?</a></h2>
<div class="level2">
<ol>
@@ -1288,7 +1298,7 @@ If you really want to muck with the router because you have a special design, e.
</p>
</div>
-<!-- SECTION "How do I make the most of the auto router?" [53210-54977] -->
+<!-- SECTION "How do I make the most of the auto router?" [53541-55308] -->
<h2><a name="how_do_i_force_the_autorouter_to_only_put_traces_on_a_particular_layer" id="how_do_i_force_the_autorouter_to_only_put_traces_on_a_particular_layer">How do I force the autorouter to only put traces on a particular layer?</a></h2>
<div class="level2">
@@ -1297,7 +1307,7 @@ Just unselect the layers you donâ??t want (usually green and blue) by clicking o
</p>
</div>
-<!-- SECTION "How do I force the autorouter to only put traces on a particular layer?" [54978-55189] -->
+<!-- SECTION "How do I force the autorouter to only put traces on a particular layer?" [55309-55520] -->
<h2><a name="how_do_i_make_autorouter_leave_particular_nets_alone" id="how_do_i_make_autorouter_leave_particular_nets_alone">How do I make autorouter leave particular nets alone?</a></h2>
<div class="level2">
@@ -1306,7 +1316,7 @@ Open up the netlist window. It has options for including or excluding nets from
</p>
</div>
-<!-- SECTION "How do I make autorouter leave particular nets alone?" [55190-55514] -->
+<!-- SECTION "How do I make autorouter leave particular nets alone?" [55521-55845] -->
<h2><a name="how_do_i_force_the_autorouter_to_route_only_within_my_pcb_outline" id="how_do_i_force_the_autorouter_to_route_only_within_my_pcb_outline">How do I force the autorouter to route only within my pcb outline?</a></h2>
<div class="level2">
@@ -1315,7 +1325,7 @@ You can have the autorouter work only within a given area by drawing a copper po
</p>
</div>
-<!-- SECTION "How do I force the autorouter to route only within my pcb outline?" [55515-55946] -->
+<!-- SECTION "How do I force the autorouter to route only within my pcb outline?" [55846-56277] -->
<h2><a name="how_do_i_route_power_and_ground_planes_with_the_autorouter" id="how_do_i_route_power_and_ground_planes_with_the_autorouter">How do I route power and ground planes with the autorouter?</a></h2>
<div class="level2">
@@ -1324,7 +1334,7 @@ Connect the polygon that will become your power planes to a net and the autorout
</p>
</div>
-<!-- SECTION "How do I route power and ground planes with the autorouter?" [55947-56228] -->
+<!-- SECTION "How do I route power and ground planes with the autorouter?" [56278-56559] -->
<h2><a name="the_layout_produced_by_the_autorouter_is_inefficient" id="the_layout_produced_by_the_autorouter_is_inefficient">The layout produced by the autorouter is inefficient!</a></h2>
<div class="level2">
@@ -1333,7 +1343,7 @@ This is a technological limitation of the current auto router. It is gridless an
</p>
</div>
-<!-- SECTION "The layout produced by the autorouter is inefficient!" [56229-56409] -->
+<!-- SECTION "The layout produced by the autorouter is inefficient!" [56560-56740] -->
<h2><a name="the_layout_produced_by_the_autorouter_is_ugly" id="the_layout_produced_by_the_autorouter_is_ugly">The layout produced by the autorouter is ugly!</a></h2>
<div class="level2">
@@ -1342,12 +1352,12 @@ Have you tried the various clean-up tools under connects–>optimize rout
</p>
</div>
-<!-- SECTION "The layout produced by the autorouter is ugly!" [56410-56553] -->
+<!-- SECTION "The layout produced by the autorouter is ugly!" [56741-56884] -->
<h1><a name="gerber_files_prints_and_other_i_o_issues" id="gerber_files_prints_and_other_i_o_issues">Gerber files, prints and other I/O issues</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Gerber files, prints and other I/O issues" [56554-56610] -->
+<!-- SECTION "Gerber files, prints and other I/O issues" [56885-56941] -->
<h2><a name="is_is_possible_to_produce_output_without_gui_intervention" id="is_is_possible_to_produce_output_without_gui_intervention">Is is possible to produce output without GUI intervention?</a></h2>
<div class="level2">
@@ -1381,7 +1391,7 @@ Different output procedures allow for different options. See the output of <code
</p>
</div>
-<!-- SECTION "Is is possible to produce output without GUI intervention?" [56611-57212] -->
+<!-- SECTION "Is is possible to produce output without GUI intervention?" [56942-57543] -->
<h2><a name="how_do_i_make_a_board_outline_to_go_with_my_gerbers_to_the_board_maker" id="how_do_i_make_a_board_outline_to_go_with_my_gerbers_to_the_board_maker">How do I make a board outline to go with my gerbers to the board maker?</a></h2>
<div class="level2">
@@ -1406,7 +1416,7 @@ Itâ??s also possible to edit the native .pcb file format of your layout. I usual
)</pre>
</div>
-<!-- SECTION "How do I make a board outline to go with my gerbers to the board maker?" [57213-58061] -->
+<!-- SECTION "How do I make a board outline to go with my gerbers to the board maker?" [57544-58392] -->
<h2><a name="yes_i_tried_that_but_the_gerber_exporter_didn_t_give_me_an_outline_file._why" id="yes_i_tried_that_but_the_gerber_exporter_didn_t_give_me_an_outline_file._why">Yes, I tried that, but the gerber exporter didn't give me an outline file. Why?</a></h2>
<div class="level2">
@@ -1415,7 +1425,7 @@ By default, gsch2pcb creates layer groups in a way which prevents your outline l
</p>
</div>
-<!-- SECTION "Yes, I tried that, but the gerber exporter didn't give me an outline file. Why?" [58062-58514] -->
+<!-- SECTION "Yes, I tried that, but the gerber exporter didn't give me an outline file. Why?" [58393-58845] -->
<h2><a name="how_do_i_make_sure_that_the_design_contains_only_certain_hole_sizes" id="how_do_i_make_sure_that_the_design_contains_only_certain_hole_sizes">How do I make sure, that the design contains only certain hole sizes?</a></h2>
<div class="level2">
@@ -1432,7 +1442,7 @@ On load, pcb will substitute drill sizes so that the layout conforms to the list
</p>
</div>
-<!-- SECTION "How do I make sure, that the design contains only certain hole sizes?" [58515-59486] -->
+<!-- SECTION "How do I make sure, that the design contains only certain hole sizes?" [58846-59817] -->
<h2><a name="i_m_done_with_my_layout._how_should_i_check_my_design" id="i_m_done_with_my_layout._how_should_i_check_my_design">I'm done with my layout. How should I check my design?</a></h2>
<div class="level2">
<ul>
@@ -1465,12 +1475,12 @@ Besides running the DRC checker, it is essential to check your Gerber files. The
</ul>
</div>
-<!-- SECTION "I'm done with my layout. How should I check my design?" [59487-61706] -->
+<!-- SECTION "I'm done with my layout. How should I check my design?" [59818-62037] -->
<h1><a name="exporting_other_formatsraster_and_ps_files" id="exporting_other_formatsraster_and_ps_files">Exporting Other Formats: Raster and PS Files</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Exporting Other Formats: Raster and PS Files" [61707-61766] -->
+<!-- SECTION "Exporting Other Formats: Raster and PS Files" [62038-62097] -->
<h2><a name="what_is_xy-max_in_the_png_export_dialog_box" id="what_is_xy-max_in_the_png_export_dialog_box">What is xy-max in the PNG export dialog box?</a></h2>
<div class="level2">
@@ -1479,12 +1489,12 @@ It limits the size of the image to NxN pixels, but maintains the aspect ratio.
</p>
</div>
-<!-- SECTION "What is xy-max in the PNG export dialog box?" [61767-62037] -->
+<!-- SECTION "What is xy-max in the PNG export dialog box?" [62098-62368] -->
<h1><a name="customization" id="customization">Customization</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Customization" [62038-62066] -->
+<!-- SECTION "Customization" [62369-62397] -->
<h2><a name="i_don_t_like_that_old-style_black_background._how_can_i_get_a_light_canvas" id="i_don_t_like_that_old-style_black_background._how_can_i_get_a_light_canvas">I don't like that old-style black background. How can I get a light canvas?</a></h2>
<div class="level2">
@@ -1493,7 +1503,7 @@ In <a href="geda-glossary.html" class="wikilink1" title="geda-glossary.html">GTK
</p>
</div>
-<!-- SECTION "I don't like that old-style black background. How can I get a light canvas?" [62067-62521] -->
+<!-- SECTION "I don't like that old-style black background. How can I get a light canvas?" [62398-62852] -->
<h2><a name="how_do_i_set_the_default_values_of_the_postscript_dialog" id="how_do_i_set_the_default_values_of_the_postscript_dialog">How do I set the default values of the postscript dialog?</a></h2>
<div class="level2">
@@ -1505,7 +1515,7 @@ align-marks = 0
multi-file = 1</pre>
</div>
-<!-- SECTION "How do I set the default values of the postscript dialog?" [62522-62960] -->
+<!-- SECTION "How do I set the default values of the postscript dialog?" [62853-63291] -->
<h1><a name="you_didn_t_answer_my_question._what_other_resources_exist_for_pcb_information" id="you_didn_t_answer_my_question._what_other_resources_exist_for_pcb_information">You didn't answer my question. What other resources exist for PCB information?</a></h1>
<div class="level1">
@@ -1520,5 +1530,5 @@ You can get fast responses from the geda-user email list. If you havenâ??t found
</p>
</div>
-<!-- SECTION "You didn't answer my question. What other resources exist for PCB information?" [62961-] --></body>
+<!-- SECTION "You didn't answer my question. What other resources exist for PCB information?" [63292-] --></body>
</html>
diff --git a/docs/wiki/geda-release_engineering.html b/docs/wiki/geda-release_engineering.html
index 011a9a4..bde39e2 100644
--- a/docs/wiki/geda-release_engineering.html
+++ b/docs/wiki/geda-release_engineering.html
@@ -18,7 +18,7 @@
<div class="level1">
</div>
-<!-- SECTION "gEDA's Release Engineering" [1-44] -->
+<!-- SECTION "gEDA's Release Engineering" [1-47] -->
<h2><a name="geda_gaf_release_creation_checklist" id="geda_gaf_release_creation_checklist">gEDA/gaf Release Creation Checklist</a></h2>
<div class="level2">
@@ -39,7 +39,9 @@
</li>
<li class="level1"><div class="li"> In the toplevel configure.ac file update the package version in the AC_INIT macro, the date in the AX_GIT_VERSION macro, and update libgedaâ??s shared library version (libgedaâ??s so version should follow what is described in <a href="http://sourceware.org/autobook/autobook/autobook_91.html"; class="urlextern" title="http://sourceware.org/autobook/autobook/autobook_91.html"; rel="nofollow"> Autobook's library versioning</a> chapter).</div>
</li>
-<li class="level1"><div class="li"> Update all the versions and dates in the man pages (gschem.1, gnetlist.1, gsymcheck.1)</div>
+<li class="level1"><div class="li"> Update all the versions and dates in the man pages (gschem.1, gnetlist.1, gsymcheck.1, grenum.1)</div>
+</li>
+<li class="level1"><div class="li"> Go into the wiki pages and update the â??gEDA/gaf File Format Documentâ?? and add the release date to the version field.</div>
</li>
<li class="level1"><div class="li"> Update the wiki documentation (this is far far far too manual)</div>
</li>
@@ -80,7 +82,7 @@
</pre>
<p>
-and make sure it completes without any errors. After this is complete you will find the distribution tarball in the toplevel directory (named gEDA-gaf-VERSION.tar.gz).
+and make sure it completes without any errors. After this is complete you will find the distribution tarball in the toplevel directory (named geda-gaf-VERSION.tar.gz).
</p>
<ul>
<li class="level1"><div class="li"> Copy the distribution tarball some place else along with the toplevel README (which should be renamed to gEDA-gaf-VERSION-README.txt).</div>
@@ -89,7 +91,7 @@ and make sure it completes without any errors. After this is complete you will
</li>
</ul>
<pre class="code">
- md5sum -b gEDA-gaf-1.5.3.tar.gz > gEDA-gaf-1.5.3.md5sum
+ md5sum -b geda-gaf-1.5.3.tar.gz > geda-gaf-1.5.3.md5sum
</pre>
<ul>
<li class="level1"><div class="li"> Untar the tarballs and compare what is inside to what is in the repository. You should only find additional dist files inside the tarballs and no missing required files.</div>
@@ -121,7 +123,7 @@ and make sure it completes without any errors. After this is complete you will
</li>
<li class="level1"><div class="li"> Write release announcement and send to mailing lists</div>
</li>
-<li class="level1"><div class="li"> Write up release notes and send pointer to mailing lists (named: gEDA-gaf-VERSION-releasenotes.html)</div>
+<li class="level1"><div class="li"> Write up release notes and send pointer to mailing lists (named: geda-gaf-VERSION-releasenotes.html)</div>
</li>
<li class="level1"><div class="li"> Update news update the sources download pages on the website with links to the new version</div>
</li>
@@ -132,5 +134,5 @@ and make sure it completes without any errors. After this is complete you will
</ul>
</div>
-<!-- SECTION "gEDA/gaf Release Creation Checklist" [45-] --></body>
+<!-- SECTION "gEDA/gaf Release Creation Checklist" [48-] --></body>
</html>
diff --git a/docs/wiki/geda-scg.html b/docs/wiki/geda-scg.html
index 83d058e..3da3c56 100644
--- a/docs/wiki/geda-scg.html
+++ b/docs/wiki/geda-scg.html
@@ -11,42 +11,6 @@
</head>
<body>
-<div class="toc">
-<div class="tocheader toctoggle" id="toc__header">Table of Contents</div>
-<div id="toc__inside">
-
-<ul class="toc">
-<li class="level1"><div class="li"><span class="li"><a href="#geda_gaf_symbol_creation_document" class="toc">gEDA/gaf Symbol Creation Document</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#overview" class="toc">Overview</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#component_symbol_creation" class="toc">Component symbol creation</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#requirements" class="toc">Requirements</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#style" class="toc">Style</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#text" class="toc">Text</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#attributes" class="toc">Attributes</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#graphics" class="toc">Graphics</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#pins" class="toc">Pins</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#electrical" class="toc">Electrical</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#footprint_naming_conventions" class="toc">Footprint naming conventions</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#notes" class="toc">Notes</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#integrated_circuit_packages" class="toc">Integrated circuit packages</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#integrated_circuit_smt_packages" class="toc">Integrated circuit SMT packages</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#basic_semiconductors" class="toc">Basic semiconductors</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#basic_smt_semiconductors" class="toc">Basic SMT semiconductors</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#passive_components" class="toc">Passive components</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#passive_smt_components" class="toc">Passive SMT components</a></span></div></li>
-</ul>
-</li>
-<li class="level2"><div class="li"><span class="li"><a href="#hints_and_tips" class="toc">Hints and Tips</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#example" class="toc">Example</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#document_revision_history" class="toc">Document Revision History</a></span></div></li></ul>
-</li></ul>
-</div>
-</div>
@@ -54,557 +18,13 @@
<div class="level1">
<p>
-by: Ales V. Hvezda / July 6th, 2004
-</p>
-
-<p>
-The latest version of this document may be found at: <a href="http://geda.seul.org/wiki/geda:scg"; class="urlextern" title="http://geda.seul.org/wiki/geda:scg"; rel="nofollow">http://geda.seul.org/wiki/geda:scg</a>
-</p>
-
-<p>
-This document is released under the <a href="geda-gfdl.html" class="wikilink1" title="geda-gfdl.html">GNU Free Documentation License (GFDL)</a>.
-</p>
-
-</div>
-<!-- SECTION "gEDA/gaf Symbol Creation Document" [1-264] -->
-<h2><a name="overview" id="overview">Overview</a></h2>
-<div class="level2">
-
-<p>
-This document describes the creation of component symbols, including style conventions, and hints/tips and things to look out for when drawing symbols for the gEDA/gaf system.
-</p>
-
-</div>
-<!-- SECTION "Overview" [265-462] -->
-<h2><a name="component_symbol_creation" id="component_symbol_creation">Component symbol creation</a></h2>
-<div class="level2">
-
-<p>
-Component symbols (from here on known as â??symbolsâ??) are drawn using gschem just like drawing a schematic sheet. Here are the steps in a symbol in the gEDA/gaf system:<br/>
- 1. Run gschem and find a blank page or run: gschem filename-1.sym<br/>
- 2. Draw the symbol (see the style guide below for some conventions).<br/>
- 3. Translate the symbol to the origin using Edit/Symbol Translate…<br/>
-
-</p>
-<ul>
-<li class="level1"><div class="li"> Zoom in at least one step.</div>
-</li>
-<li class="level1"><div class="li"> Make sure the snap is ON (this is critical).</div>
-</li>
-<li class="level1"><div class="li"> Make sure grid snap size is set to 100 (this is critical).</div>
-</li>
-<li class="level1"><div class="li"> Select â??Symbol Translate…â?? or the press equivalent hotkey.</div>
-</li>
-<li class="level1"><div class="li"> Enter 0 into the entry field and press OK.<br/>
-</div>
-</li>
-</ul>
-
-<p>
-Translating the symbol to the origin is a required step. To translate a symbol elsewhere, enter a offset (in mils) which is a even multiple of 100. Make sure all pins are snapped to a 100 mil grid point.
-</p>
-
-<p>
-4. Save the symbol using Save or SaveAs… Here are some symbol naming conventions:<br/>
-
-</p>
-<ul>
-<li class="level1"><div class="li"> Symbols are named: symbolname-#.sym</div>
-</li>
-<li class="level1"><div class="li"> Symbols end with a .sym extension.</div>
-</li>
-<li class="level1"><div class="li"> Symbols have a -# where # is a number. Typically # is 1 but if there are multiple symbols for a device then this number simply increments.</div>
-</li>
-<li class="level1"><div class="li"> Symbol names are typically lowercase but letters which are part of a part number are uppercase.</div>
-</li>
-<li class="level1"><div class="li"> The above case rule can be broken if the filename looks incorrect or wrong.</div>
-</li>
-</ul>
-
-<p>
- 5. Place the symbol in one of the directories specified by the componentlibrary keyword in the system-gafrc file. Once this is done, the symbol should be visible immediately and can be selected and placed with the â??Add/Select Component…â?? menu item.
-</p>
-
-</div>
-<!-- SECTION "Component symbol creation" [463-2082] -->
-<h2><a name="requirements" id="requirements">Requirements</a></h2>
-<div class="level2">
-
-<p>
-This section describes the various requirements which must be met in order to create a valid symbol which will display and netlist in the gEDA/gaf system. Most of the requirements center around having certain attributes attached or inside the symbol.<br/>
- Running gsymcheck will check that all of these requirements are met. gsymcheck will output fatal errors which are quite serious and must be corrected. gsymcheck will also output warnings on things which should be fixed but are not fatal.<br/>
- For more information on the attributes presented here, please see the Master Attribute Document.
-</p>
-<ul>
-<li class="level1"><div class="li"> device=DEVICENAME should be placed somewhere in the symbol and made invisible. device= is the device name and is required. Typically the devicename is in all caps (capital letters). This attribute should not be used as a label. Use a separate text object for the label. If the object is a graphic then device= should be set to none (device=none). It is no longer required to attach this attribute anything; just having it exist as device=DEVICENAME is good enough.</div>
-</li>
-<li class="level1"><div class="li"> graphical=1 should exist somewhere in a symbol which is purely graphical (such as a title block or decon symbol). Symbols which have this attribute have no electrical or circuit significance. Donâ??t forget to set device=none.</div>
-</li>
-<li class="level1"><div class="li"> description=text should exist somewhere in the symbol. This attribute provides an one line description of the symbol.</div>
-</li>
-<li class="level1"><div class="li"> All pins should have a pair of attributes attached to them: pinseq=# and pinnumber=#. The first attribute, pinseq=# is just a sequence number and increments sequentially starting at 1. The second attribute pinnumber=# is the number of the pin. When a symbol is netlisted, the pin numbers are output in order of pin sequence. The pin number can be alphanumeric (i.e. like E or C).</div>
-</li>
-<li class="level1"><div class="li"> All pins should also have pinlabel=value attached to them. This attribute is the name or label of the pin (vs the pin number). This attribute is also used when a symbol is used in a hierarchical schematic. Please make this attribute green (instead of the default attribute yellow).</div>
-</li>
-<li class="level1"><div class="li"> All pins should also have pintype=value attached to them. This attribute describes the kind of a pin. Possible values are: in, out, io, oc, oe, pas, tp, tri, clk, pwr. Please see the Master Attribute Document for more info.</div>
-</li>
-<li class="level1"><div class="li"> If a component has multiple slots in a package (such as a 7400 (NAND) which has 4 NANDs per package) then you need a numslots=# attribute. The # is the number of slots the device has. numslots= should be exist somewhere in the symbol and made invisible. Additional slot related required attributes are described below.</div>
-</li>
-<li class="level1"><div class="li"> If a component has multiple slots in a physical package then you also need to include a slotdef=#:#,#,#… for every slot. The first # corresponds to the slot number. If a device has 4 slots then there should be slotdef=1:…, slotdef=2:…, slotdef=3:…, and slotdef=4:…, attributes existing somewhere in the symbol and made invisible. The subsequent # have a one-to-one correspondence to pinseq=# attributes and specify what corresponding pinnumber=# should be when that slot is set. See The attached 7400-1.sym as an example of how this should all work.</div>
-</li>
-<li class="level1"><div class="li"> It is recommended that all symbols which have slots have a slot=1 attribute inside the symbol.</div>
-</li>
-<li class="level1"><div class="li"> footprint=PACKAGENAME should exist somewhere in the symbol which might be used with the PCB netlister. PACKAGENAME is the PCB footprint or package type like DIP14 or DIP40. Please see the Footprint naming conventions chapter for further detail. See also the PCB documentation and gnetlist/docs/README.pcb for more info on this attribute.</div>
-</li>
-<li class="level1"><div class="li"> You should put a refdes=U? attribute inside the symbol. Make only the value visible and it will be promoted (attached to the outside of the symbol (so it can be edited) when the symbol is placed in a schematic.</div>
-</li>
-<li class="level1"><div class="li"> The label= attribute should not be attached anywhere in the symbol. It is obsolete.</div>
-</li>
-<li class="level1"><div class="li"> The name= attribute should not be attached anywhere in the symbol.</div>
-</li>
-<li class="level1"><div class="li"> The netname= attribute should not be attached anywhere in the symbol. It is only used in schematics.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Requirements" [2083-6223] -->
-<h2><a name="style" id="style">Style</a></h2>
-<div class="level2">
-
-<p>
-This section describes the style in which is used in the standard gEDA/gaf symbol library.
-</p>
-
-</div>
-<!-- SECTION "Style" [6224-6334] -->
-<h3><a name="text" id="text">Text</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> All Text labels should all be 10 pt in size.</div>
-</li>
-<li class="level1"><div class="li"> Text (labels not attributes) should be color number 9 (text | green).</div>
-</li>
-<li class="level1"><div class="li"> Use the special overbar encoding (e.g. â??pinlabel=\_Reset\_â??) to express inverse logic levels</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Text" [6335-6570] -->
-<h3><a name="attributes" id="attributes">Attributes</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Pin numbers (which are attributes) should all be 8 pt in size.</div>
-</li>
-<li class="level1"><div class="li"> Attached attributes should be yellow. The color is set automatically to yellow if the text item is attached.</div>
-</li>
-<li class="level1"><div class="li"> The only exception to this is pinlabel= attributes, those should be color number 9 (text | green). If every text item within a symbol is yellow, the symbol looks too yellow.</div>
-</li>
-<li class="level1"><div class="li"> Attributes can be attached to some part of the symbol. Toplevel attributes (like the device= or net= attributes) used to be required to be attached to something to be attributes, but now they just have to exist in the symbol file as name=value.</div>
-</li>
-<li class="level1"><div class="li"> Expanding a bit on the last sentence, as long as the text item has the format name=value, it is considered an attribute. Attributes inside a symbol do not have to be attached to anything. In order to see hidden attributes in gschem select Edit/Show/Hide Inv Text.</div>
-</li>
-<li class="level1"><div class="li"> There is a symbol content versioning system in libgeda which is based on the symversion= attribute. Please see the Master Attribute Document for more information on using this versioning scheme.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Attributes" [6571-7667] -->
-<h3><a name="graphics" id="graphics">Graphics</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Lines, boxes, arcs, and any other graphics should be color number 3 (graphic | green).</div>
-</li>
-<li class="level1"><div class="li"> Polarity bubbles should be color number 6 (logic bubble | cyan)</div>
-</li>
-<li class="level1"><div class="li"> If you are unsure on how to make a new symbol look or how big to make a new symbol, look at the existing symbols to get a feel for the appropriate appearance and size.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Graphics" [7668-8018] -->
-<h3><a name="pins" id="pins">Pins</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Pins should all be 300 mils (3 grid spaces) long.</div>
-</li>
-<li class="level1"><div class="li"> For pins which are next to a logic bubble, make the pins 200 mils (2 grid spaces) long and then make the logic bubble 100 mils in diameter. In order to draw a 100 mil diameter circle, you will need to change the snap spacing to 50.</div>
-</li>
-<li class="level1"><div class="li"> A pin has two ends: one end has a red endpoint and one end that does not. The red endpoint is where nets can be connected. You can either rotate the pin so that this active end is in the right place or manually edit the symbol file changing the â??whichendâ?? parameter on the pin object. See the File Format document for more info.</div>
-</li>
-<li class="level1"><div class="li"> Be that all endpoints of pins which are meant to be connected to are on the 100 mil grid. The endpoint which is not active can be off the grid if necessary.</div>
-</li>
-<li class="level1"><div class="li"> Pins should be color number 1 (pins | white).</div>
-</li>
-<li class="level1"><div class="li"> Leave 400 mils (4 grid spaces) between (vertically) pins, unless you are drawing a special symbol, then just try to make it look good.</div>
-</li>
-<li class="level1"><div class="li"> Pin number attributes should be 50 mils above (or below; which ever makes the most sense) the pin which they are attached to.</div>
-</li>
-<li class="level1"><div class="li"> Input pins belong on the left and output pins belong on the right of the symbol.</div>
-</li>
-<li class="level1"><div class="li"> Please do not mix inputs and outputs on the same side of the symbol, unless absolutely necessary.</div>
-</li>
-<li class="level1"><div class="li"> You can have pins on the top or bottom of a symbol.</div>
-</li>
-<li class="level1"><div class="li"> The order for rows of pins (buses) should be LSB (least significant bit) to MSB (most significant bit). When drawing pins which are part of a bus, make sure the LSB of the bus is at the top (or for pins on top/bottom of a symbol, left of the rest of the other pins). Look at 74/74181-1.sym for a correct example of this order (A0 on top through A3 and B0 on top through B3). Violating this rule will make connecting buses much more diffcult.</div>
-</li>
-<li class="level1"><div class="li"> When placing pins on logic gates, be sure to place the smallest pin numbers toward the top (or left) and then increment going down (or across).</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Pins" [8019-9974] -->
-<h3><a name="electrical" id="electrical">Electrical</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Do not draw power and ground pins. That information will be conveyed using attributes (see the netattrib document).</div>
-</li>
-<li class="level1"><div class="li"> The above rule can be broken if necessary, but keep in mind most of the standard library does not have power pins showing.</div>
-</li>
-<li class="level1"><div class="li"> Keep in mind, symbols are supposed to be symbolic, they do not represent the physical package that the device comes in.</div>
-</li>
-<li class="level1"><div class="li"> There is some disagreement on above, so this is okay too: Arrange the pins on a symbol logically so that they promote an uncluttered schematic. Note that this is frequently not the same pin arrangement as the physical device.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Electrical" [9975-10597] -->
-<h2><a name="footprint_naming_conventions" id="footprint_naming_conventions">Footprint naming conventions</a></h2>
-<div class="level2">
-
-<p>
-This section describes the conventions for naming of footprints used in gEDA/gaf.<br/>
- The purpose of the naming convention is to establish a standard to maintain the same naming convention through the different phases of the CAD chain. This helps in ensuring that the collaborative effort of gEDA/gaf is not lost.
-</p>
-
-</div>
-<!-- SECTION "Footprint naming conventions" [10598-10951] -->
-<h3><a name="notes" id="notes">Notes</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Unless otherwise noted, numerical pin names will be used, starting from 1.</div>
-</li>
-<li class="level1"><div class="li"> n is for the pin count.</div>
-</li>
-<li class="level1"><div class="li"> m is for the pin spacing in mils.</div>
-</li>
-<li class="level1"><div class="li"> x is for the x dimension of the package (excluding pins). In particular this is used for the QFP package family.</div>
-</li>
-<li class="level1"><div class="li"> SMT means surface mount, other components are through-hole.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Notes" [10952-11294] -->
-<h3><a name="integrated_circuit_packages" id="integrated_circuit_packages">Integrated circuit packages</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Dual in line packages with up to 22 100 mil spaced pins and 300 mil row spacing are called DIPn.</div>
-</li>
-<li class="level1"><div class="li"> Dual in line packages with 24 or more 100 mil spaced pins and 300 mil row spacing are called DIPnN.</div>
-</li>
-<li class="level1"><div class="li"> Dual in line packages with 100 mil spaced pins and 400 mil row spacing are called DIPnH.</div>
-</li>
-<li class="level1"><div class="li"> Dual in line packages with 24 or more 100 mil spaced pins and 600 mil row spacing are called DIPn.</div>
-</li>
-<li class="level1"><div class="li"> Shrink dual in line packages with up to 24 70 mil spaced pins and 300 mil row spacing are called SDIPn.</div>
-</li>
-<li class="level1"><div class="li"> Shrink dual in line packages with more than 24 70 mil spaced pins and 400 mil row spacing are called SDIPn.</div>
-</li>
-<li class="level1"><div class="li"> Single in line packages with 100 mil spaced pins are called SIPnN. See also JUMPER, below.</div>
-</li>
-<li class="level1"><div class="li"> Zig-zag in-line package are called ZIPn.</div>
-</li>
-<li class="level1"><div class="li"> Plastic leadless chip carrier with pin socket are called PLCCnX.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Integrated circuit packages" [11295-12163] -->
-<h3><a name="integrated_circuit_smt_packages" id="integrated_circuit_smt_packages">Integrated circuit SMT packages</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Small outline SMT packages with up to 16 50 mil spaced pins and 150 mil total width are called SOn.</div>
-</li>
-<li class="level1"><div class="li"> Small outline SMT packages with more than 16 50 mil spaced pins and 150 mil total width are called SOnN.</div>
-</li>
-<li class="level1"><div class="li"> Small outline SMT packages with 50 mil spaced pins and 200 mil total width are called SOnM.</div>
-</li>
-<li class="level1"><div class="li"> Small outline SMT packages with up to 20 50 mil spaced pins and 300 mil total width are called SOnW.</div>
-</li>
-<li class="level1"><div class="li"> Small outline SMT packages with more than 20 50 mil spaced pins and 300 mil total width are called SOn.</div>
-</li>
-<li class="level1"><div class="li"> Small outline SMT packages with 44 or more 50 mil spaced pins and 525 mil total width are called SOn.</div>
-</li>
-<li class="level1"><div class="li"> Metric shrink small outline SMT packages with 0.65 mm spaced pins and 323 mil total width are called MSSOPn. NOTE: To be confirmed.</div>
-</li>
-<li class="level1"><div class="li"> Metric shrink small outline SMT packages with up to 44 0.65 mm spaced pins and 420 mil total width are called MSSOPnW.</div>
-</li>
-<li class="level1"><div class="li"> Metric shrink small outline SMT packages with over 44 0.65 mm spaced pins and 545 mil total width are called MSSOPnW.</div>
-</li>
-<li class="level1"><div class="li"> Shrink small outline SMT packages with 25 mil spaced pins and 420 mil total width are called SSOPnW.</div>
-</li>
-<li class="level1"><div class="li"> Quarter size small outline SMT packages with 25 mil spaced pins and 244 mil total width are called SSOPn.</div>
-</li>
-<li class="level1"><div class="li"> Thin small outline SMT packages with 21.65 mil spaced pins and 535 mil total width are called TSOPn.</div>
-</li>
-<li class="level1"><div class="li"> Thin small outline SMT packages with 20 mil spaced pins and 795 mil total width are called TSOPnA.</div>
-</li>
-<li class="level1"><div class="li"> Thin small outline SMT packages with 20 mil spaced pins and 559 mil total width are called TSOPnB.</div>
-</li>
-<li class="level1"><div class="li"> Thin shrink small outline SMT packages with up to 28 26 mil spaced pins and 260 mil total width are called TSSOPn.</div>
-</li>
-<li class="level1"><div class="li"> Thin shrink small outline SMT packages with over 28 20 mil spaced pins and 319 mil total width are called TSSOPn.</div>
-</li>
-<li class="level1"><div class="li"> Ultra Super Mini SMT packages with up to 16 0.5 mm spaced pins are called USn.</div>
-</li>
-<li class="level1"><div class="li"> Plastic leadless chip carrier SMT are called PLCCn.</div>
-</li>
-<li class="level1"><div class="li"> Square quad-side at pack SMT are called QFPn x.</div>
-</li>
-<li class="level1"><div class="li"> Rectangular quad-side at pack SMT are called QFPn R.</div>
-</li>
-<li class="level1"><div class="li"> Square low profile quad-side at pack SMT are called LQFPn x.</div>
-</li>
-<li class="level1"><div class="li"> Square thin quad-side at pack SMT are called TQFPn x.</div>
-</li>
-<li class="level1"><div class="li"> Square Quad-side at no-lead SMT without exposed paddle (back side contact) are called QFNn x. Pin count is n and package size is x mm.</div>
-</li>
-<li class="level1"><div class="li"> Square Quad-side at no-lead SMT with exposed paddle (back side contact) are called QFNn x EP. Pin count is n and package size is x mm.</div>
-</li>
-<li class="level1"><div class="li"> Thin profile square Quad-side at no-lead SMT without exposed paddle (back side contact) are called TQFNn x. Pin count is n and package size is x mm.</div>
-</li>
-<li class="level1"><div class="li"> Thin profile square Quad-side at no-lead SMT with exposed paddle (back side contact) are called TQFNn x EP. Pin count is n and package size is x mm.</div>
-</li>
-<li class="level1"><div class="li"> Dual in line style crystal oscillators are OSC8 and OSC14.</div>
-</li>
-<li class="level1"><div class="li"> 5 pin SOT SMT packages are SOT25 and SOT325.</div>
-</li>
-<li class="level1"><div class="li"> 6 pin SOT SMT packages are SOT26 and SOT326.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Integrated circuit SMT packages" [12164-15094] -->
-<h3><a name="basic_semiconductors" id="basic_semiconductors">Basic semiconductors</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Axial diodes are called ALFm. Pin 1 is the cathode.</div>
-</li>
-<li class="level1"><div class="li"> Conventional through hole LED is LED3 and LED5 for 3 and 5 mm respectively. Pin 1 is plus. NOTE: Should probably be changed to be in line with diode convention.</div>
-</li>
-<li class="level1"><div class="li"> TO transistors are TO5, TO92, TO126, TO220 etc. Suxes may apply, e.g. TO126W is for wide, TO126S is for standing, TO126SW is for standing, wide.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Basic semiconductors" [15095-15497] -->
-<h3><a name="basic_smt_semiconductors" id="basic_smt_semiconductors">Basic SMT semiconductors</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> SOD diode SMT packages use their standard package name, e.g. SOD80, SOD87, SOD106A, SOD110. There are also SOD123, SOD323 with narrow pads.</div>
-</li>
-<li class="level1"><div class="li"> SOT transistor SMT packages use their standard package name, e.g. SOT23, SOT323. There is also an SC90.</div>
-</li>
-<li class="level1"><div class="li"> SOT transistor SMT packages with numbering as for diodes (pin 1 is cathode, pin 2 anode) are SOT23D, SOT323D.</div>
-</li>
-<li class="level1"><div class="li"> 4 pin SOT SMT packages are SOT89, SOT143, SOT223.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Basic SMT semiconductors" [15498-15953] -->
-<h3><a name="passive_components" id="passive_components">Passive components</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Axial non-polar components (typically resistor, capacitor) are called ACYm.</div>
-</li>
-<li class="level1"><div class="li"> Bottom lead (radial) non-polar circular component (typically capacitor) is RCYm.</div>
-</li>
-<li class="level1"><div class="li"> Bottom lead non-polar rectangular component (typically capacitor) is BREm.</div>
-</li>
-<li class="level1"><div class="li"> A standard crystal is HC49, or other HC designations as required.</div>
-</li>
-<li class="level1"><div class="li"> Single row 100 mil pin spacing jumpers are JUMPERn. The main difference compared to single in line package is the hole size.</div>
-</li>
-<li class="level1"><div class="li"> Dual row 100 mil spacing headers with DIP pin numbering are HEADERn 1. Note that n is an even number.</div>
-</li>
-<li class="level1"><div class="li"> Dual row 100 mil spacing headers with ribbon cable numbering are HEADERn 2. Note that n is an even number.</div>
-</li>
-<li class="level1"><div class="li"> Angled full header connectors with latches are DIN41651 n.</div>
-</li>
-<li class="level1"><div class="li"> Standing full header connectors with latches are DIN41651 nS.</div>
-</li>
-<li class="level1"><div class="li"> DSUB connectors female are DBnF.</div>
-</li>
-<li class="level1"><div class="li"> DSUB connectors male are DBnM.</div>
-</li>
-<li class="level1"><div class="li"> Female DIN card-to-card connectors are DIN41612CnF. Add S suffix for standing.</div>
-</li>
-<li class="level1"><div class="li"> Male DIN card-to-card connectors are DIN41612CnM. Add S suffix for standing.</div>
-</li>
-<li class="level1"><div class="li"> AMP modular RJ connectors with screen are RJ11, RJ12 and RJ45.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Passive components" [15954-17075] -->
-<h3><a name="passive_smt_components" id="passive_smt_components">Passive SMT components</a></h3>
-<div class="level3">
-<ul>
-<li class="level1"><div class="li"> Standard SMT resistors, inductors, capacitors etc are 0201, 0402, 0603, 0805, 1206, 1210, 1806, 1812, 1825, 2020, 2706.</div>
-</li>
-<li class="level1"><div class="li"> Tantalum SMT capacitors are EIA3216, EIA3528, EIA6032, and EIA7343. Pin 1 is plus.</div>
-</li>
-<li class="level1"><div class="li"> SMT electrolytics are designated by can diameter in 1/10 mm: SME33, SME43, SME53, SME66, SME84, SME104.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Passive SMT components" [17076-17428] -->
-<h2><a name="hints_and_tips" id="hints_and_tips">Hints and Tips</a></h2>
-<div class="level2">
-
-<p>
-This section describes some hints and tips which will make your symbol creation experience easier.<br/>
-
-</p>
-<ul>
-<li class="level1"><div class="li"> Avoid drawing things off of the grid. If you do, you cannot move the object(s) using the move command (if the grid is on) since the object will be snapped to the grid. [This was an old bug, which I think has been fixed, but avoid doing this anyway]. Use the symbol translate command instead (or move the object with grid snap off)</div>
-</li>
-<li class="level1"><div class="li"> If you need a finer grid then use Options/Snap Grid Spacing… to set a finer grid snap spacing. Just remember to set this back to 100 once you are ready to translate the symbol to the origin.</div>
-</li>
-<li class="level1"><div class="li"> If you want to translate a symbol from the origin to elsewhere, then use the â??Symbol translateâ?? command and enter a non zero number. Make sure this number is a multiple of 100 (ie 1000, or 1100).</div>
-</li>
-<li class="level1"><div class="li"> Pins MUST be snapped on the 100 spaced grid (at least the end which will have nets connected to it).</div>
-</li>
-<li class="level1"><div class="li"> Pins MUST be snapped on the 100 spaced grid (at least the end which will have nets connected to it). Yes this is line a duplicate. I canâ??t stress this point enough.</div>
-</li>
-<li class="level1"><div class="li"> Remember that pins are special objects; if you want to add a pin, make sure it is a pin and not a line or net. Use the Add/Pin command to place a pin.</div>
-</li>
-<li class="level1"><div class="li"> Donâ??t include nets or buses inside symbols. That is not supported and doesnâ??t make much sense anyway.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "Hints and Tips" [17429-18824] -->
-<h2><a name="example" id="example">Example</a></h2>
-<div class="level2">
-
-<p>
-This section provides a simple example which tries to follow all of the above rules. This symbol is of a 7400 (NAND gate).<br/>
-
-</p>
-
-<p>
-<pre STYLE="background : LightGreen;
-margin-left : 2em"><font size="+0">v 20031231 1
-L 300 200 300 800 3 0 0 0 -1 -1
-T 300 0 9 8 1 0 0 0 1
-7400
-L 300 800 700 800 3 0 0 0 -1 -1
-T 500 900 5 10 0 0 0 0 1
-device=7400
-T 500 1100 5 10 0 0 0 0 1
-slot=1
-T 500 1300 5 10 0 0 0 0 1
-numslots=4
-T 500 1500 5 10 0 0 0 0 1
-slotdef=1:1,2,3
-T 500 1700 5 10 0 0 0 0 1
-slotdef=2:4,5,6
-T 500 1900 5 10 0 0 0 0 1
-slotdef=3:9,10,8
-T 500 2100 5 10 0 0 0 0 1
-slotdef=4:12,13,11
-L 300 200 700 200 3 0 0 0 -1 -1
-A 700 500 300 270 180 3 0 0 0 -1 -1
-V 1050 500 50 6 0 0 0 -1 -1 0 -1 -1 -1 -1 -1
-P 1100 500 1300 500 1 0 1
-{
-T 1100 550 5 8 1 1 0 0 1
-pinnumber=3
-T 1100 450 5 8 0 1 0 2 1
-pinseq=3
-T 950 500 9 8 0 1 0 6 1
-pinlabel=Y
-T 950 500 5 8 0 1 0 8 1
-pintype=out
-}
-P 300 300 0 300 1 0 1
-{
-T 200 350 5 8 1 1 0 6 1
-pinnumber=2
-T 200 250 5 8 0 1 0 8 1
-pinseq=2
-T 350 300 9 8 0 1 0 0 1
-pinlabel=B
-T 350 300 5 8 0 1 0 2 1
-pintype=in
-}
-P 300 700 0 700 1 0 1
-{
-T 200 750 5 8 1 1 0 6 1
-pinnumber=1
-T 200 650 5 8 0 1 0 8 1
-pinseq=1
-T 350 700 9 8 0 1 0 0 1
-pinlabel=A
-T 350 700 5 8 0 1 0 2 1
-pintype=in
-}
-T 300 900 8 10 1 1 0 0 1
-refdes=U?
-T 500 2250 5 10 0 0 0 0 1
-footprint=DIP14
-T 500 2450 5 10 0 0 0 0 1
-description=4 NAND gates with 2 inputs
-T 500 2850 5 10 0 0 0 0 1
-net=Vcc:14
-T 500 3050 5 10 0 0 0 0 1
-net=GND:7
-T 500 2650 5 10 0 0 0 0 1
-documentation=http://www-s.ti.com/sc/ds/sn74hc00.pdf
-</font></pre>
-</p>
-
-<p>
-This example produces the following (using gschem):
-</p>
-
-<p>
-<a href="media/geda/symbol_7400-1_hidden.png" class="media" target="_blank" title="geda:symbol_7400-1_hidden.png"><img src="media/geda/symbol_7400-1_hidden.png" class="media" title=":geda:symbol_7400-1_hidden.png" alt=":geda:symbol_7400-1_hidden.png" /></a>
-</p>
-
-<p>
-This is the same symbol with all the hidden text visible (via Edit/Show/Hide Inv Text):
+ This page has MOVED to:
</p>
<p>
-<a href="media/geda/symbol_7400-1.png" class="media" target="_blank" title="geda:symbol_7400-1.png"><img src="media/geda/symbol_7400-1.png" class="media" title=":geda:symbol_7400-1.png" alt=":geda:symbol_7400-1.png" /></a>
+<a href="http://geda.seul.org/wiki/geda:gschem_symbol_creation"; class="urlextern" title="http://geda.seul.org/wiki/geda:gschem_symbol_creation"; rel="nofollow">http://geda.seul.org/wiki/geda:gschem_symbol_creation</a>
</p>
</div>
-<!-- SECTION "Example" [18825-20541] -->
-<h2><a name="document_revision_history" id="document_revision_history">Document Revision History</a></h2>
-<div class="level2">
-<table class="inline">
- <tr>
- <td> September 14th, 2002</td><td>Created symbol.tex from symbols.html </td>
- </tr>
- <tr>
- <td> October 31st, 2002</td><td>Fixed bad example symbol </td>
- </tr>
- <tr>
- <td> February 11th, 2003</td><td>Footprint naming conventions added </td>
- </tr>
- <tr>
- <td> September 27th, 2003</td><td>Applied Dan McMahillâ??s QFP and QFN patch </td>
- </tr>
- <tr>
- <td> July 6th, 2004</td><td>Added a bunch more details/hints to the pin section </td>
- </tr>
-</table>
-
-</div>
-<!-- SECTION "Document Revision History" [20542-] --></body>
+<!-- SECTION "gEDA/gaf Symbol Creation Document" [2-] --></body>
</html>
diff --git a/docs/wiki/geda-todos.html b/docs/wiki/geda-todos.html
index a21fb9e..ae00cd4 100644
--- a/docs/wiki/geda-todos.html
+++ b/docs/wiki/geda-todos.html
@@ -20,9 +20,9 @@
<ul class="toc">
<li class="level2"><div class="li"><span class="li"><a href="#release_roadmap" class="toc">Release roadmap</a></span></div>
<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#unstable" class="toc">1.5.3/1.5.4 (unstable)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#stable" class="toc">1.6 (stable)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#stable1" class="toc">1.8 (stable)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#stable" class="toc">1.6.1 (stable)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#stable1" class="toc">1.6.2 (stable)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#stable2" class="toc">1.8 (stable)</a></span></div></li>
</ul>
</li>
<li class="level2"><div class="li"><span class="li"><a href="#longer_term_upgrades_desired_for_specific_tools" class="toc">Longer term upgrades desired for specific tools</a></span></div></li>
@@ -59,86 +59,36 @@ Todos for past releases can be seen on the <a href="geda-todos_historical.html"
</p>
</div>
-<!-- SECTION "Release roadmap" [305-717] -->
-<h3><a name="unstable" id="unstable">1.5.3/1.5.4 (unstable)</a></h3>
+<!-- SECTION "Release roadmap" [305-709] -->
+<h3><a name="stable" id="stable">1.6.1 (stable)</a></h3>
<div class="level3">
<p>
- Target release date: <strong>August 2009</strong> <br/>
- Actual release date: <strong>August 29th 2009 and August 30th 2009</strong> <br/>
- 1.5.3 was withdrawn from distribution after some release critical bugs were discovered. <br/>
-
-</p>
-<table class="inline">
- <tr>
- <th class="leftalign"> Description </th><th class="leftalign"> SF bug </th><th class="leftalign"> Developer(s) </th><th class="leftalign"> Status </th>
- </tr>
- <tr>
- <td class="leftalign"> Renderer improvements (pango text on screen) </td><td class="rightalign"> </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=f8a0f1c1b5fd42c78a7165dcfa4b5135790a24a5"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=f8a0f1c1b5fd42c78a7165dcfa4b5135790a24a5"; rel="nofollow"> Done </a> </td>
- </tr>
- <tr>
- <td> Embeded symbol contents different depending on how embedded </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2460301&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2460301&group_id=161080&atid=818426"; rel="nofollow"> 2460301 </a> </td><td class="leftalign"> Peter B </td><td> Fixed (<a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=ea46d8defce4390b9650e8d2a5035de4794673df"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=ea46d8defce4390b9650e8d2a5035de4794673df"; rel="nofollow"> 1</a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=a419f4f196ef6574940d082d88f46b95bbeb0ea9"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=a419f4f196ef6574940d082d88f46b95bbeb0ea9"; rel="nofollow"> 2</a>) </td>
- </tr>
- <tr>
- <td> <del>gattrib: Fix file→load to do something useful</del> </td><td class="centeralign"> <del>n/a</del> </td><td> </td><td> Cancelled </td>
- </tr>
- <tr>
- <td> gschem: Preselect current setting when editing fill and line styles </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2344964&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2344964&group_id=161080&atid=818426"; rel="nofollow"> 2344964 </a> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2344956&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2344956&group_id=161080&atid=818426"; rel="nofollow"> 2344956 </a> </td><td class="leftalign"> Werner </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=e84330457016f1bfb3db1cd6c8a6980a72a6e90c"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=e84330457016f1bfb3db1cd6c8a6980a72a6e90c"; rel="nofollow">Fixed</a> </td>
- </tr>
- <tr>
- <td> Dangerous button focus in â??Save changesâ?? dialog at quit </td><td> <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=2058707&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker/index.php?func=detail&aid=2058707&group_id=161080&atid=818426"; rel="nofollow"> 2058707</a> </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=c006ec0603fd570ec6c10386f3a3d19f9cbd525d"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=c006ec0603fd570ec6c10386f3a3d19f9cbd525d"; rel="nofollow"> Fixed gschem </a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=7253fb551e683b3c7c15c0f8595178f88129e7c5"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=7253fb551e683b3c7c15c0f8595178f88129e7c5"; rel="nofollow"> Fixed gattrib </a> </td>
- </tr>
- <tr>
- <td> Fix zooming with (warp-cursor â??disabledâ??) </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2001299&group_id=161080&atid=818429"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2001299&group_id=161080&atid=818429"; rel="nofollow"> 2001299 </a> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2212748&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2212748&group_id=161080&atid=818426"; rel="nofollow"> 2212748 </a> </td><td> Werner </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=d48b0b36c5348abd52413de14afb6ab0958b260d"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=d48b0b36c5348abd52413de14afb6ab0958b260d"; rel="nofollow"> Fixed </a></td>
- </tr>
- <tr>
- <td> Fix drawing artifact sometimes left after cancelling net mode </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2449060&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2449060&group_id=161080&atid=818426"; rel="nofollow"> 2449060 </a> </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commitdiff;h=0fe820aa442bba02d164832ce771932f2189d231#patch14"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commitdiff;h=0fe820aa442bba02d164832ce771932f2189d231#patch14"; rel="nofollow"> Fixed </a> (in invalidate/expose code) </td>
- </tr>
- <tr>
- <td> Deselecting component doesnâ??t deselect hidden attrib </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2430369&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2430369&group_id=161080&atid=818426"; rel="nofollow"> 2430369 </a> </td><td class="leftalign"> Peter C </td><td class="leftalign"> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=d3bd67e8ccb5ed47f17603392f480f220380daa5"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=d3bd67e8ccb5ed47f17603392f480f220380daa5"; rel="nofollow"> Fixed </a> </td>
- </tr>
- <tr>
- <td> Fix gnetlist ordering / test-suite against recent GLib </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2455061&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2455061&group_id=161080&atid=818426"; rel="nofollow"> 2455061 </a> </td><td> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=2d888258d954c993aa03e4a1beb7b03e62df4d95"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=2d888258d954c993aa03e4a1beb7b03e62df4d95"; rel="nofollow"> Fixed </a> </td>
- </tr>
- <tr>
- <td class="leftalign"> Unified build system </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=1758673&group_id=161080&atid=818429"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=1758673&group_id=161080&atid=818429"; rel="nofollow"> 1758673 </a> </td><td class="leftalign"> Peter B </td><td class="leftalign"> Done </td>
- </tr>
- <tr>
- <td> Get rid of all obsolete auto* macros </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter B </td><td class="leftalign"> Done </td>
- </tr>
-</table>
-
-<p>
- Wishlist
+ Target release date: <strong>February 2010</strong> <br/>
+ Actual release date: <strong>TBD</strong>
</p>
<table class="inline">
<tr>
<th class="leftalign"> Description </th><th class="leftalign"> SF bug </th><th class="leftalign"> Developer(s) </th><th class="leftalign"> Status </th>
</tr>
<tr>
- <td> Printing improvements (Arbitrary UTF8 postscript) - print with cairo </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter B, Peter C </td><td> 50% </td>
- </tr>
- <tr>
- <td> gschem: interface for creating paths and inserting / deleting nodes </td><td class="centeralign"> n/a </td><td class="rightalign"> </td><td> </td>
- </tr>
- <tr>
- <td> Bitmap export options: allow specifying DPI rather than / as well as absolute page size </td><td> <a href="https://sourceforge.net/tracker/?func=detail&atid=818429&aid=2226522&group_id=161080"; class="urlextern" title="https://sourceforge.net/tracker/?func=detail&atid=818429&aid=2226522&group_id=161080"; rel="nofollow"> 2226522 </a> </td><td> </td><td> </td>
+ <td> Screenshots of release version for a publicity revamp of gEDA website. </td><td class="centeralign"> n/a </td><td> Peter C </td><td> </td>
</tr>
<tr>
- <td> Set print border size </td><td> <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=2243238&group_id=161080&atid=818429"; class="urlextern" title="https://sourceforge.net/tracker/index.php?func=detail&aid=2243238&group_id=161080&atid=818429"; rel="nofollow"> 2243238 </a> </td><td> Werner </td><td> </td>
+ <td> Merge translations from Launchpad upstream. </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter C </td><td> Ongoing sync </td>
</tr>
<tr>
- <td> Allow setting gschem on-screen border </td><td> <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=2243238&group_id=161080&atid=818429"; class="urlextern" title="https://sourceforge.net/tracker/index.php?func=detail&aid=2243238&group_id=161080&atid=818429"; rel="nofollow"> 2243238 </a> </td><td> </td><td> </td>
+ <td class="leftalign"> Check copyright headers are up-to-date </td><td class="centeralign"> n/a </td><td> Ales H </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=bd34cfde2450790b357e574281f9562adce64303"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=bd34cfde2450790b357e574281f9562adce64303"; rel="nofollow"> Done </a> </td>
</tr>
</table>
</div>
-<!-- SECTION "1.5.3/1.5.4 (unstable)" [718-4896] -->
-<h3><a name="stable" id="stable">1.6 (stable)</a></h3>
+<!-- SECTION "1.6.1 (stable)" [710-1264] -->
+<h3><a name="stable1" id="stable1">1.6.2 (stable)</a></h3>
<div class="level3">
<p>
- Target release date: <strong>September 2009 (soon after 1.5.4 is complete) </strong> <br/>
+ Target release date: <strong>Unknown</strong> <br/>
Actual release date: <strong>TBD</strong>
</p>
<table class="inline">
@@ -146,52 +96,28 @@ Todos for past releases can be seen on the <a href="geda-todos_historical.html"
<th class="leftalign"> Description </th><th class="leftalign"> SF bug </th><th class="leftalign"> Developer(s) </th><th class="leftalign"> Status </th>
</tr>
<tr>
- <td class="leftalign"> Fix gattrib build with recent GTK+ </td><td class="leftalign"> <a href="http://sourceforge.net/tracker/index.php?func=detail&aid=2832985&group_id=161080&atid=818426"; class="urlextern" title="http://sourceforge.net/tracker/index.php?func=detail&aid=2832985&group_id=161080&atid=818426"; rel="nofollow"> 2832985 </a> </td><td class="leftalign"> Peter C </td><td class="leftalign"> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=78da20ca286eb2f6e518c64dca94b888fc8c19af"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=78da20ca286eb2f6e518c64dca94b888fc8c19af"; rel="nofollow"> Fixed </a> </td>
+ <td> Screenshots of release version for a publicity revamp of gEDA website. </td><td class="centeralign"> n/a </td><td> Peter C </td><td> </td>
</tr>
<tr>
- <td class="leftalign"> Update documentation from wiki </td><td class="rightalign"> </td><td class="leftalign"> Ales </td><td class="rightalign"> </td>
+ <td> Merge translations from Launchpad upstream. </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter C </td><td> </td>
</tr>
<tr>
<td class="leftalign"> Check copyright headers are up-to-date </td><td class="centeralign"> n/a </td><td class="rightalign"> </td><td class="rightalign"> </td>
</tr>
<tr>
- <td> <del>UTF-8 / system / filesystem encoding bugs</del> </td><td> <del><a href="https://sourceforge.net/tracker/?func=detail&group_id=161080&atid=818426&aid=1868072"; class="urlextern" title="https://sourceforge.net/tracker/?func=detail&group_id=161080&atid=818426&aid=1868072"; rel="nofollow"> 1868072</a></del> </td><td> </td><td> Cancelled (minor impact) </td>
- </tr>
- <tr>
- <td class="leftalign"> Portability patches for mingw32 landed in some form or other. </td><td> </td><td> Cesar S, Peter C </td><td> Awaiting testing and feedback </td>
- </tr>
- <tr>
- <td> Screenshots of release version for a publicity revamp of gEDA website. </td><td class="centeralign"> n/a </td><td> Peter C </td><td> </td>
+ <td> UTF-8 / system / filesystem encoding bugs </td><td> <a href="https://sourceforge.net/tracker/?func=detail&group_id=161080&atid=818426&aid=1868072"; class="urlextern" title="https://sourceforge.net/tracker/?func=detail&group_id=161080&atid=818426&aid=1868072"; rel="nofollow"> 1868072</a> </td><td> </td><td> </td>
</tr>
<tr>
- <td> Merge translations from Launchpad upstream. </td><td> </td><td> Peter C (?) </td><td> </td>
- </tr>
- <tr>
- <td> Cure all: â??warning: format not a string literal and no format argumentsâ?? compiling with recent GCC versions </td><td> </td><td> </td><td> Fixed </td>
+ <td> Prettify symbols (e.g. gates) using paths </td><td class="centeralign"> n/a </td><td class="rightalign"> </td><td class="rightalign"> </td>
</tr>
<tr>
<td> Cure all: â??warning : ignoring return value of â??…â??, declared with attribute warn_unused_resultâ?? compiling with recent GCC versions </td><td> </td><td> </td><td> </td>
</tr>
- <tr>
- <td> gattrib: Remove all deliberately-non-functioning menu options / buttons </td><td class="centeralign"> n/a </td><td> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=0deb0abc3d82a8127c9566d886858811c1dcc717"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=0deb0abc3d82a8127c9566d886858811c1dcc717"; rel="nofollow"> Fixed menu items </a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=22d5b2abcd1aa5c098566ee5b292c6d7215b9b8e"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=22d5b2abcd1aa5c098566ee5b292c6d7215b9b8e"; rel="nofollow"> Fixed Nets sheet </a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=721114eccc913dbbbd5e1d0700b87662aac316fc"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=721114eccc913dbbbd5e1d0700b87662aac316fc"; rel="nofollow"> Fixed Pins sheet </a> </td>
- </tr>
- <tr>
- <td class="leftalign"> <del>Prettify symbols (e.g. gates) using paths</del> </td><td class="centeralign"> <del>n/a</del> </td><td class="rightalign"> </td><td> Cancelled (cosmetic) </td>
- </tr>
- <tr>
- <td> Fix symbols using explicit lines for overbars </td><td class="centeralign"> n/a </td><td> Bert T, Werner </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=9e3e45193643d5bca628df5074fd1aedd7ff619c"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=9e3e45193643d5bca628df5074fd1aedd7ff619c"; rel="nofollow">Done</a></td>
- </tr>
- <tr>
- <td> utils: Teach gsch2pcb to detect and avoid the common â??footprint saved as PCB fileâ?? mistake </td><td class="centeralign"> n/a </td><td> Peter B </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=821845073b187409488bbf78ed947fd084439546"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=821845073b187409488bbf78ed947fd084439546"; rel="nofollow"> Done </a> </td>
- </tr>
- <tr>
- <td> gschem: Fix broken net consolidation for certain scenarios </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=399560caafde7046fe0e361712389e559969a424"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=399560caafde7046fe0e361712389e559969a424"; rel="nofollow"> Fixed </a> (hack) </td>
- </tr>
</table>
</div>
-<!-- SECTION "1.6 (stable)" [4897-7452] -->
-<h3><a name="stable1" id="stable1">1.8 (stable)</a></h3>
+<!-- SECTION "1.6.2 (stable)" [1265-2066] -->
+<h3><a name="stable2" id="stable2">1.8 (stable)</a></h3>
<div class="level3">
<p>
@@ -252,8 +178,32 @@ Todos for past releases can be seen on the <a href="geda-todos_historical.html"
</tr>
</table>
+<p>
+ Wishlist
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Description </th><th class="leftalign"> SF bug </th><th class="leftalign"> Developer(s) </th><th class="leftalign"> Status </th>
+ </tr>
+ <tr>
+ <td> Printing improvements (Arbitrary UTF8 postscript) - print with cairo </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter B, Peter C </td><td> 50% </td>
+ </tr>
+ <tr>
+ <td> gschem: interface for creating paths and inserting / deleting nodes </td><td class="centeralign"> n/a </td><td class="rightalign"> </td><td> </td>
+ </tr>
+ <tr>
+ <td> Bitmap export options: allow specifying DPI rather than / as well as absolute page size </td><td> <a href="https://sourceforge.net/tracker/?func=detail&atid=818429&aid=2226522&group_id=161080"; class="urlextern" title="https://sourceforge.net/tracker/?func=detail&atid=818429&aid=2226522&group_id=161080"; rel="nofollow"> 2226522 </a> </td><td> </td><td> </td>
+ </tr>
+ <tr>
+ <td> Set print border size </td><td> <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=2243238&group_id=161080&atid=818429"; class="urlextern" title="https://sourceforge.net/tracker/index.php?func=detail&aid=2243238&group_id=161080&atid=818429"; rel="nofollow"> 2243238 </a> </td><td> Werner </td><td> </td>
+ </tr>
+ <tr>
+ <td> Allow setting gschem on-screen border </td><td> <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=2243238&group_id=161080&atid=818429"; class="urlextern" title="https://sourceforge.net/tracker/index.php?func=detail&aid=2243238&group_id=161080&atid=818429"; rel="nofollow"> 2243238 </a> </td><td> </td><td> </td>
+ </tr>
+</table>
+
</div>
-<!-- SECTION "1.8 (stable)" [7453-9505] -->
+<!-- SECTION "1.8 (stable)" [2067-4963] -->
<h2><a name="longer_term_upgrades_desired_for_specific_tools" id="longer_term_upgrades_desired_for_specific_tools">Longer term upgrades desired for specific tools</a></h2>
<div class="level2">
<ul>
@@ -364,7 +314,7 @@ Todos for past releases can be seen on the <a href="geda-todos_historical.html"
</ul>
</div>
-<!-- SECTION "Longer term upgrades desired for specific tools" [9506-13235] -->
+<!-- SECTION "Longer term upgrades desired for specific tools" [4964-8693] -->
<h2><a name="ideas_for_new_tools_or_geda_suite-wide_enhancements" id="ideas_for_new_tools_or_geda_suite-wide_enhancements">Ideas for new tools or gEDA Suite-wide enhancements</a></h2>
<div class="level2">
<ul>
@@ -379,7 +329,7 @@ Todos for past releases can be seen on the <a href="geda-todos_historical.html"
</ul>
</div>
-<!-- SECTION "Ideas for new tools or gEDA Suite-wide enhancements" [13236-13802] -->
+<!-- SECTION "Ideas for new tools or gEDA Suite-wide enhancements" [8694-9260] -->
<h2><a name="code_cleanup_and_refactoring" id="code_cleanup_and_refactoring">Code cleanup and refactoring</a></h2>
<div class="level2">
<ul>
@@ -398,5 +348,5 @@ Todos for past releases can be seen on the <a href="geda-todos_historical.html"
</ul>
</div>
-<!-- SECTION "Code cleanup and refactoring" [13803-] --></body>
+<!-- SECTION "Code cleanup and refactoring" [9261-] --></body>
</html>
diff --git a/docs/wiki/geda-todos_historical.html b/docs/wiki/geda-todos_historical.html
index d759dab..967cb5b 100644
--- a/docs/wiki/geda-todos_historical.html
+++ b/docs/wiki/geda-todos_historical.html
@@ -24,7 +24,9 @@
<li class="level3"><div class="li"><span class="li"><a href="#stable" class="toc">1.4.2 (stable)</a></span></div></li>
<li class="level3"><div class="li"><span class="li"><a href="#stable1" class="toc">1.4.3 (stable)</a></span></div></li>
<li class="level3"><div class="li"><span class="li"><a href="#unstable" class="toc">1.5.1 (unstable)</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#unstable1" class="toc">1.5.2 (unstable)</a></span></div></li></ul>
+<li class="level3"><div class="li"><span class="li"><a href="#unstable1" class="toc">1.5.2 (unstable)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#unstable2" class="toc">1.5.3/1.5.4 (unstable)</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#stable2" class="toc">1.6.0 (stable)</a></span></div></li></ul>
</li></ul>
</li></ul>
</div>
@@ -234,5 +236,94 @@
</table>
</div>
-<!-- SECTION "1.5.2 (unstable)" [10171-] --></body>
+<!-- SECTION "1.5.2 (unstable)" [10171-14178] -->
+<h3><a name="unstable2" id="unstable2">1.5.3/1.5.4 (unstable)</a></h3>
+<div class="level3">
+
+<p>
+ Target release date: <strong>August 2009</strong> <br/>
+ Actual release date: <strong>August 29th 2009 and August 30th 2009</strong> <br/>
+ 1.5.3 was withdrawn from distribution after some release critical bugs were discovered. <br/>
+
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Description </th><th class="leftalign"> SF bug </th><th class="leftalign"> Developer(s) </th><th class="leftalign"> Status </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> Renderer improvements (pango text on screen) </td><td class="rightalign"> </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=f8a0f1c1b5fd42c78a7165dcfa4b5135790a24a5"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=f8a0f1c1b5fd42c78a7165dcfa4b5135790a24a5"; rel="nofollow"> Done </a> </td>
+ </tr>
+ <tr>
+ <td> Embeded symbol contents different depending on how embedded </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2460301&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2460301&group_id=161080&atid=818426"; rel="nofollow"> 2460301 </a> </td><td class="leftalign"> Peter B </td><td> Fixed (<a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=ea46d8defce4390b9650e8d2a5035de4794673df"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=ea46d8defce4390b9650e8d2a5035de4794673df"; rel="nofollow"> 1</a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=a419f4f196ef6574940d082d88f46b95bbeb0ea9"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=a419f4f196ef6574940d082d88f46b95bbeb0ea9"; rel="nofollow"> 2</a>) </td>
+ </tr>
+ <tr>
+ <td> <del>gattrib: Fix file→load to do something useful</del> </td><td class="centeralign"> <del>n/a</del> </td><td> </td><td> Cancelled </td>
+ </tr>
+ <tr>
+ <td> gschem: Preselect current setting when editing fill and line styles </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2344964&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2344964&group_id=161080&atid=818426"; rel="nofollow"> 2344964 </a> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2344956&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2344956&group_id=161080&atid=818426"; rel="nofollow"> 2344956 </a> </td><td class="leftalign"> Werner </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=e84330457016f1bfb3db1cd6c8a6980a72a6e90c"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=e84330457016f1bfb3db1cd6c8a6980a72a6e90c"; rel="nofollow">Fixed</a> </td>
+ </tr>
+ <tr>
+ <td> Dangerous button focus in â??Save changesâ?? dialog at quit </td><td> <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=2058707&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker/index.php?func=detail&aid=2058707&group_id=161080&atid=818426"; rel="nofollow"> 2058707</a> </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=c006ec0603fd570ec6c10386f3a3d19f9cbd525d"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=c006ec0603fd570ec6c10386f3a3d19f9cbd525d"; rel="nofollow"> Fixed gschem </a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=7253fb551e683b3c7c15c0f8595178f88129e7c5"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=7253fb551e683b3c7c15c0f8595178f88129e7c5"; rel="nofollow"> Fixed gattrib </a> </td>
+ </tr>
+ <tr>
+ <td> Fix zooming with (warp-cursor â??disabledâ??) </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2001299&group_id=161080&atid=818429"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2001299&group_id=161080&atid=818429"; rel="nofollow"> 2001299 </a> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2212748&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2212748&group_id=161080&atid=818426"; rel="nofollow"> 2212748 </a> </td><td> Werner </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=d48b0b36c5348abd52413de14afb6ab0958b260d"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=d48b0b36c5348abd52413de14afb6ab0958b260d"; rel="nofollow"> Fixed </a></td>
+ </tr>
+ <tr>
+ <td> Fix drawing artifact sometimes left after cancelling net mode </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2449060&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2449060&group_id=161080&atid=818426"; rel="nofollow"> 2449060 </a> </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commitdiff;h=0fe820aa442bba02d164832ce771932f2189d231#patch14"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commitdiff;h=0fe820aa442bba02d164832ce771932f2189d231#patch14"; rel="nofollow"> Fixed </a> (in invalidate/expose code) </td>
+ </tr>
+ <tr>
+ <td> Deselecting component doesnâ??t deselect hidden attrib </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2430369&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2430369&group_id=161080&atid=818426"; rel="nofollow"> 2430369 </a> </td><td class="leftalign"> Peter C </td><td class="leftalign"> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=d3bd67e8ccb5ed47f17603392f480f220380daa5"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=d3bd67e8ccb5ed47f17603392f480f220380daa5"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td> Fix gnetlist ordering / test-suite against recent GLib </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=2455061&group_id=161080&atid=818426"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=2455061&group_id=161080&atid=818426"; rel="nofollow"> 2455061 </a> </td><td> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=2d888258d954c993aa03e4a1beb7b03e62df4d95"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=2d888258d954c993aa03e4a1beb7b03e62df4d95"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Unified build system </td><td> <a href="https://sourceforge.net/tracker2/?func=detail&aid=1758673&group_id=161080&atid=818429"; class="urlextern" title="https://sourceforge.net/tracker2/?func=detail&aid=1758673&group_id=161080&atid=818429"; rel="nofollow"> 1758673 </a> </td><td class="leftalign"> Peter B </td><td class="leftalign"> Done </td>
+ </tr>
+ <tr>
+ <td> Get rid of all obsolete auto* macros </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter B </td><td class="leftalign"> Done </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "1.5.3/1.5.4 (unstable)" [14179-17508] -->
+<h3><a name="stable2" id="stable2">1.6.0 (stable)</a></h3>
+<div class="level3">
+
+<p>
+ Target release date: <strong>September 2009 (soon after 1.5.4 is complete) </strong> <br/>
+ Actual release date: <strong>October 4th, 2009</strong>
+</p>
+<table class="inline">
+ <tr>
+ <th class="leftalign"> Description </th><th class="leftalign"> SF bug </th><th class="leftalign"> Developer(s) </th><th class="leftalign"> Status </th>
+ </tr>
+ <tr>
+ <td class="leftalign"> Fix gattrib build with recent GTK+ </td><td class="leftalign"> <a href="http://sourceforge.net/tracker/index.php?func=detail&aid=2832985&group_id=161080&atid=818426"; class="urlextern" title="http://sourceforge.net/tracker/index.php?func=detail&aid=2832985&group_id=161080&atid=818426"; rel="nofollow"> 2832985 </a> </td><td class="leftalign"> Peter C </td><td class="leftalign"> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=78da20ca286eb2f6e518c64dca94b888fc8c19af"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=78da20ca286eb2f6e518c64dca94b888fc8c19af"; rel="nofollow"> Fixed </a> </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Update documentation from wiki </td><td class="rightalign"> </td><td class="leftalign"> Ales </td><td class="leftalign"> Done </td>
+ </tr>
+ <tr>
+ <td class="leftalign"> Portability patches for mingw32 landed in some form or other. </td><td> </td><td> Cesar S, Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=5ca5b9768cf70f3d0f905d784d0896c6b442c34f"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=5ca5b9768cf70f3d0f905d784d0896c6b442c34f"; rel="nofollow"> Done </a> </td>
+ </tr>
+ <tr>
+ <td> Cure all: â??warning: format not a string literal and no format argumentsâ?? compiling with recent GCC versions </td><td> </td><td> </td><td> Fixed </td>
+ </tr>
+ <tr>
+ <td> gattrib: Remove all deliberately-non-functioning menu options / buttons </td><td class="centeralign"> n/a </td><td> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=0deb0abc3d82a8127c9566d886858811c1dcc717"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=0deb0abc3d82a8127c9566d886858811c1dcc717"; rel="nofollow"> Fixed menu items </a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=22d5b2abcd1aa5c098566ee5b292c6d7215b9b8e"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=22d5b2abcd1aa5c098566ee5b292c6d7215b9b8e"; rel="nofollow"> Fixed Nets sheet </a> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=721114eccc913dbbbd5e1d0700b87662aac316fc"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=721114eccc913dbbbd5e1d0700b87662aac316fc"; rel="nofollow"> Fixed Pins sheet </a> </td>
+ </tr>
+ <tr>
+ <td> Fix symbols using explicit lines for overbars </td><td class="centeralign"> n/a </td><td> Bert T, Werner </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=9e3e45193643d5bca628df5074fd1aedd7ff619c"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=9e3e45193643d5bca628df5074fd1aedd7ff619c"; rel="nofollow">Done</a></td>
+ </tr>
+ <tr>
+ <td> utils: Teach gsch2pcb to detect and avoid the common â??footprint saved as PCB fileâ?? mistake </td><td class="centeralign"> n/a </td><td> Peter B </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=821845073b187409488bbf78ed947fd084439546"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=821845073b187409488bbf78ed947fd084439546"; rel="nofollow"> Done </a> </td>
+ </tr>
+ <tr>
+ <td> gschem: Fix broken net consolidation for certain scenarios </td><td class="centeralign"> n/a </td><td class="leftalign"> Peter C </td><td> <a href="http://git.gpleda.org/?p=gaf.git;a=commit;h=399560caafde7046fe0e361712389e559969a424"; class="urlextern" title="http://git.gpleda.org/?p=gaf.git;a=commit;h=399560caafde7046fe0e361712389e559969a424"; rel="nofollow"> Fixed </a> (hack) </td>
+ </tr>
+</table>
+
+</div>
+<!-- SECTION "1.6.0 (stable)" [17509-] --></body>
</html>
diff --git a/docs/wiki/images/Makefile.am b/docs/wiki/images/Makefile.am
index b8db727..c971ff5 100644
--- a/docs/wiki/images/Makefile.am
+++ b/docs/wiki/images/Makefile.am
@@ -3,9 +3,9 @@
docname=wiki
docsdir = $(docdir)/$(docname)/images
-SUBDIRS = smileys interwiki
+SUBDIRS = interwiki smileys
-docs_DATA = link_icon.gif open.gif interwiki.png closed.gif button-cc.gif button-donate.gif mail_icon.gif tocdot2.gif button-rss.png button-php.gif button-xhtml.png bullet.gif button-css.png button-dw.png windows.gif
+docs_DATA = interwiki.png link_icon.gif button-dw.png open.gif button-php.gif windows.gif button-rss.png bullet.gif button-donate.gif mail_icon.gif button-cc.gif tocdot2.gif closed.gif button-css.png button-xhtml.png
EXTRA_DIST = $(docs_DATA)
diff --git a/docs/wiki/images/interwiki/Makefile.am b/docs/wiki/images/interwiki/Makefile.am
index a294f2c..0723035 100644
--- a/docs/wiki/images/interwiki/Makefile.am
+++ b/docs/wiki/images/interwiki/Makefile.am
@@ -3,7 +3,7 @@
docname=wiki
docsdir = $(docdir)/$(docname)/images/interwiki
-docs_DATA = bug.gif coral.gif amazon.de.gif google.gif amazon.gif wpmeta.gif sb.gif doku.gif wiki.gif amazon.uk.gif wp.gif wpde.gif meatball.gif phpfn.gif
+docs_DATA = wiki.gif wpde.gif google.gif phpfn.gif amazon.de.gif meatball.gif wpmeta.gif amazon.uk.gif sb.gif wp.gif amazon.gif coral.gif bug.gif doku.gif
EXTRA_DIST = $(docs_DATA)
diff --git a/docs/wiki/images/smileys/Makefile.am b/docs/wiki/images/smileys/Makefile.am
index 2e01243..77e5024 100644
--- a/docs/wiki/images/smileys/Makefile.am
+++ b/docs/wiki/images/smileys/Makefile.am
@@ -3,7 +3,7 @@
docname=wiki
docsdir = $(docdir)/$(docname)/images/smileys
-docs_DATA = icon_twisted.gif icon_neutral.gif icon_wink.gif fixme.gif icon_evil.gif icon_idea.gif icon_doubt2.gif icon_razz.gif icon_eek.gif delete.gif icon_doubt.gif icon_redface.gif icon_mrgreen.gif icon_smile.gif icon_frown.gif icon_silenced.gif icon_cool.gif icon_rolleyes.gif icon_biggrin.gif icon_question.gif icon_exclaim.gif icon_surprised.gif icon_arrow.gif icon_lol.gif icon_kaddi.gif icon_sad.gif icon_smile2.gif icon_cry.gif icon_confused.gif icon_fun.gif
+docs_DATA = icon_arrow.gif icon_biggrin.gif fixme.gif delete.gif icon_idea.gif icon_cry.gif icon_lol.gif icon_evil.gif icon_question.gif icon_mrgreen.gif icon_confused.gif icon_smile2.gif icon_silenced.gif icon_smile.gif icon_twisted.gif icon_redface.gif icon_sad.gif icon_wink.gif icon_fun.gif icon_kaddi.gif icon_exclaim.gif icon_surprised.gif icon_doubt.gif icon_doubt2.gif icon_razz.gif icon_frown.gif icon_cool.gif icon_eek.gif icon_neutral.gif icon_rolleyes.gif
EXTRA_DIST = $(docs_DATA)
diff --git a/docs/wiki/index.html b/docs/wiki/index.html
index d876a26..19d0714 100644
--- a/docs/wiki/index.html
+++ b/docs/wiki/index.html
@@ -20,7 +20,7 @@
<ul class="toc">
<li class="level2"><div class="li"><span class="li"><a href="#what_is_geda" class="toc">What is gEDA?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#official_project_documentation" class="toc">Official Project documentation</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#faqs_and_informal_project_documentation" class="toc">FAQs and Informal Project Documentation</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#faqs_quick_reference" class="toc">FAQs & Quick Reference</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#developer_documentation" class="toc">Developer Documentation</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#talks" class="toc">Talks</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#google_summer_of_code" class="toc">Google Summer of Code</a></span></div></li>
@@ -54,7 +54,7 @@ All of the software in the gEDA suite can be found on the <a href="http://www.gp
</p>
</div>
-<!-- SECTION "What is gEDA?" [36-1175] -->
+<!-- SECTION "What is gEDA?" [36-1176] -->
<h2><a name="official_project_documentation" id="official_project_documentation">Official Project documentation</a></h2>
<div class="level2">
@@ -62,17 +62,17 @@ All of the software in the gEDA suite can be found on the <a href="http://www.gp
These are the official project docs. They have been converted from LaTeX and <acronym title="HyperText Markup Language">HTML</acronym> documents into Wiki pages so that the gEDA community may more easily maintain them.
</p>
<ul>
-<li class="level1"><div class="li"> <a href="geda-documentation.html" class="wikilink1" title="geda-documentation.html">Documentation</a> : The latest versions of the gEDA Tool Suite documentation.</div>
+<li class="level1"><div class="li"> <a href="geda-documentation.html" class="wikilink1" title="geda-documentation.html">Documentation</a> : Contains links to tutorials, manuals, HOWTOs and format specifications of the gEDA suite. </div>
</li>
</ul>
</div>
-<!-- SECTION "Official Project documentation" [1176-1478] -->
-<h2><a name="faqs_and_informal_project_documentation" id="faqs_and_informal_project_documentation">FAQs and Informal Project Documentation</a></h2>
+<!-- SECTION "Official Project documentation" [1177-1516] -->
+<h2><a name="faqs_quick_reference" id="faqs_quick_reference">FAQs & Quick Reference</a></h2>
<div class="level2">
<p>
-These are FAQs, HOWTOs, and tips/tricks to help you with the practical details of using the gEDA Suite. If you are having a problem, browse these pages first.
+These are informal FAQs, HOWTOs, and tips/tricks to help you with the practical details of using the gEDA Suite. If you are having a problem, browse these pages first.
</p>
<ul>
<li class="level1"><div class="li"> <a href="geda-faq.html" class="wikilink1" title="geda-faq.html">FAQ</a> : Frequently Asked Questions about the gEDA project itself.</div>
@@ -101,14 +101,14 @@ These are FAQs, HOWTOs, and tips/tricks to help you with the practical details o
</li>
<li class="level1"><div class="li"> <a href="geda-pcb_footprints.html" class="wikilink1" title="geda-pcb_footprints.html">PCB footprints</a> : How to create, use and share footprints.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda-scg.html" class="wikilink1" title="geda-scg.html">scg</a> : gschem symbol creation guide.</div>
+<li class="level1"><div class="li"> <a href="geda-gschem_symbol_creation.html" class="wikilink1" title="geda-gschem_symbol_creation.html">gschem Symbol Creation</a> : gschem symbol creation guide.</div>
</li>
<li class="level1"><div class="li"> <a href="geda-guile_scripting.html" class="wikilink1" title="geda-guile_scripting.html">Guile scripting</a> : Guile functions & variables provided by the gEDA tools.</div>
</li>
</ul>
</div>
-<!-- SECTION "FAQs and Informal Project Documentation" [1479-2986] -->
+<!-- SECTION "FAQs & Quick Reference" [1517-3035] -->
<h2><a name="developer_documentation" id="developer_documentation">Developer Documentation</a></h2>
<div class="level2">
@@ -146,10 +146,12 @@ The following pages are related to the day-to-day development of the gEDA suite:
</li>
<li class="level1"><div class="li"> <a href="geda-format_translation.html" class="wikilink1" title="geda-format_translation.html">format translation</a> : Some notes on file format translation.</div>
</li>
+<li class="level1"><div class="li"> <a href="geda-gparts_dd.html" class="wikilink1" title="geda-gparts_dd.html">Parts Manager</a> : A working document for a gEDA parts manager</div>
+</li>
</ul>
</div>
-<!-- SECTION "Developer Documentation" [2987-4465] -->
+<!-- SECTION "Developer Documentation" [3036-4598] -->
<h2><a name="talks" id="talks">Talks</a></h2>
<div class="level2">
@@ -162,7 +164,7 @@ These are slides of presentations done about gEDA. They provide a good top-leve
</ul>
</div>
-<!-- SECTION "Talks" [4466-4706] -->
+<!-- SECTION "Talks" [4599-4839] -->
<h2><a name="google_summer_of_code" id="google_summer_of_code">Google Summer of Code</a></h2>
<div class="level2">
@@ -189,7 +191,7 @@ Here is this yearâ??s Google Summer of Code page:
</ul>
</div>
-<!-- SECTION "Google Summer of Code" [4707-5086] -->
+<!-- SECTION "Google Summer of Code" [4840-5219] -->
<h2><a name="translations" id="translations">Translations</a></h2>
<div class="level2">
<ul>
@@ -200,7 +202,7 @@ Here is this yearâ??s Google Summer of Code page:
</ul>
</div>
-<!-- SECTION "Translations" [5087-5203] -->
+<!-- SECTION "Translations" [5220-5336] -->
<h2><a name="geda_users" id="geda_users">gEDA Users</a></h2>
<div class="level2">
@@ -217,7 +219,7 @@ The so-called â??Free Dogâ?? organization ( <a href="http://freeedaug.org/"; clas
</p>
</div>
-<!-- SECTION "gEDA Users" [5204-5736] -->
+<!-- SECTION "gEDA Users" [5337-5869] -->
<h2><a name="about_this_wiki" id="about_this_wiki">About this Wiki</a></h2>
<div class="level2">
@@ -230,5 +232,5 @@ Anyone is welcome to contribute. Unlike Wikipedia there is no button to create a
</p>
</div>
-<!-- SECTION "About this Wiki" [5737-] --></body>
+<!-- SECTION "About this Wiki" [5870-] --></body>
</html>
diff --git a/docs/wiki/media/Makefile.am b/docs/wiki/media/Makefile.am
index 8ce7d79..943c93a 100644
--- a/docs/wiki/media/Makefile.am
+++ b/docs/wiki/media/Makefile.am
@@ -3,6 +3,11 @@
docname=wiki
docsdir = $(docdir)/$(docname)/media
-SUBDIRS = geda wiki tragesym devel_tips
+SUBDIRS = devel_tips wiki tragesym geda
+docs_DATA =
+
+EXTRA_DIST = $(docs_DATA)
+
+MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
diff --git a/docs/wiki/media/geda/Makefile.am b/docs/wiki/media/geda/Makefile.am
index ab3fb70..64ae657 100644
--- a/docs/wiki/media/geda/Makefile.am
+++ b/docs/wiki/media/geda/Makefile.am
@@ -3,7 +3,7 @@
docname=wiki
docsdir = $(docdir)/$(docname)/media/geda
-docs_DATA = board-5.png symbol_7400-1_hidden.png dialogvdc1.png pcb-el-2.png warmup_add_component.png ambiguous1.png schematicfinished2.png net.jpg board-3.png one-sch-1.png switcap_figure4.jpg gschem-sym-1.png dialogdirective.png faq_attrib.jpg two-sch-1.png board-4.png symbol_7400-1.png dialogmodel.png gschem-sym-2.png geda_flow.png dialoginclude.png status_screenshot.jpg ambiguous1_fixed.png board-1.png gschem_workflow_01.jpg schematicfinished.png nets.jpg gschem_screenshot_001.jpg pcb-el-1.png path_example_and_gate-smaller.png path_example_and_gate.png warmup_gschem03.png switcap_figure1.jpg dialogvac.png design_flow.jpg simple1.png board-6.png board-2.png switcap_figure2.jpg coordinatespace.jpg one-sch-2.png terminal_screenshot_001.jpg suse_electronics_menu.png switcap_figure3.jpg warmup_gschem01.png dialogtrans.png fileformat_textgraphic.jpg warmup_gschem02.png gschem-sym-3.png rf_cascade_figure1.jpg paper1.gif one-sch-3.png rf_cascade_figure2.jpg two-sch-2.png
+docs_DATA = dialogvac.png gparts-ss-parts-2.png warmup_gschem01.png symbol_7400-1_hidden.png two-sch-2.png gparts-ss-devices.png gschem-sym-3.png gparts-ss-packages.png pcb-el-2.png one-sch-1.png switcap_figure1.jpg gschem-sym-1.png board-4.png status_screenshot.jpg coordinatespace.jpg gparts-ss-footprints.png board-1.png dialoginclude.png dialogtrans.png board-3.png symbol_7400-1.png geda_flow.png nets.jpg warmup_add_component.png ambiguous1_fixed.png net.jpg rf_cascade_figure1.jpg gparts-flow-2.png rf_cascade_figure2.jpg gparts-ss-symbols-2.png gparts-ss-symbols.png schematicfinished2.png board-2.png dialogmodel.png switcap_figure3.jpg gparts-ss-companies.png paper1.gif pcb-el-1.png one-sch-3.png ambiguous1.png faq_attrib.jpg dialogvdc1.png two-sch-1.png board-5.png gparts_erd_main.png gparts-ss-parts.png board-6.png switcap_figure2.jpg terminal_screenshot_001.jpg path_example_and_gate-smaller.png warmup_gschem03.png gschem_screenshot_001.jpg path_example_and_gate.png simple1.png gparts_flow.png design_flow.jpg dialogdirective.png gparts-ss-documentation.png fileformat_textgraphic.jpg one-sch-2.png gschem-sym-2.png warmup_gschem02.png schematicfinished.png gschem_workflow_01.jpg switcap_figure4.jpg suse_electronics_menu.png
EXTRA_DIST = $(docs_DATA)
diff --git a/docs/wiki/media/geda/gparts-flow-2.png b/docs/wiki/media/geda/gparts-flow-2.png
new file mode 100644
index 0000000..734a40e
Binary files /dev/null and b/docs/wiki/media/geda/gparts-flow-2.png differ
diff --git a/docs/wiki/media/geda/gparts-ss-companies.png b/docs/wiki/media/geda/gparts-ss-companies.png
new file mode 100644
index 0000000..8e5bff5
Binary files /dev/null and b/docs/wiki/media/geda/gparts-ss-companies.png differ
diff --git a/docs/wiki/media/geda/gparts-ss-devices.png b/docs/wiki/media/geda/gparts-ss-devices.png
new file mode 100644
index 0000000..e2265db
Binary files /dev/null and b/docs/wiki/media/geda/gparts-ss-devices.png differ
diff --git a/docs/wiki/media/geda/gparts-ss-documentation.png b/docs/wiki/media/geda/gparts-ss-documentation.png
new file mode 100644
index 0000000..463a717
Binary files /dev/null and b/docs/wiki/media/geda/gparts-ss-documentation.png differ
diff --git a/docs/wiki/media/geda/gparts-ss-footprints.png b/docs/wiki/media/geda/gparts-ss-footprints.png
new file mode 100644
index 0000000..59238b1
Binary files /dev/null and b/docs/wiki/media/geda/gparts-ss-footprints.png differ
diff --git a/docs/wiki/media/geda/gparts-ss-packages.png b/docs/wiki/media/geda/gparts-ss-packages.png
new file mode 100644
index 0000000..961ce68
Binary files /dev/null and b/docs/wiki/media/geda/gparts-ss-packages.png differ
diff --git a/docs/wiki/media/geda/gparts-ss-parts-2.png b/docs/wiki/media/geda/gparts-ss-parts-2.png
new file mode 100644
index 0000000..95a8530
Binary files /dev/null and b/docs/wiki/media/geda/gparts-ss-parts-2.png differ
diff --git a/docs/wiki/media/geda/gparts-ss-parts.png b/docs/wiki/media/geda/gparts-ss-parts.png
new file mode 100644
index 0000000..b878536
Binary files /dev/null and b/docs/wiki/media/geda/gparts-ss-parts.png differ
diff --git a/docs/wiki/media/geda/gparts-ss-symbols-2.png b/docs/wiki/media/geda/gparts-ss-symbols-2.png
new file mode 100644
index 0000000..d51ffa4
Binary files /dev/null and b/docs/wiki/media/geda/gparts-ss-symbols-2.png differ
diff --git a/docs/wiki/media/geda/gparts-ss-symbols.png b/docs/wiki/media/geda/gparts-ss-symbols.png
new file mode 100644
index 0000000..389dfd7
Binary files /dev/null and b/docs/wiki/media/geda/gparts-ss-symbols.png differ
diff --git a/docs/wiki/media/geda/gparts_erd_main.png b/docs/wiki/media/geda/gparts_erd_main.png
new file mode 100644
index 0000000..2f45297
Binary files /dev/null and b/docs/wiki/media/geda/gparts_erd_main.png differ
diff --git a/docs/wiki/media/geda/gparts_flow.png b/docs/wiki/media/geda/gparts_flow.png
new file mode 100644
index 0000000..384fd60
Binary files /dev/null and b/docs/wiki/media/geda/gparts_flow.png differ
diff --git a/docs/wiki/media/tragesym/Makefile.am b/docs/wiki/media/tragesym/Makefile.am
index 857988c..fd88f56 100644
--- a/docs/wiki/media/tragesym/Makefile.am
+++ b/docs/wiki/media/tragesym/Makefile.am
@@ -5,7 +5,7 @@ docsdir = $(docdir)/$(docname)/media/tragesym
SUBDIRS = tragesym
-docs_DATA = gschem_finished.png ooo_rearanged.png kpdf_pindescription.png acroread_selectiontable.png xemacs_rawselection.png gschem_showhidden.png template.txt kpdf_pinconfiguration.png template2.ods template.ods ooo_attributes.png ooo_selection.png xemacs_modifiedselection.png ooo_changedpins.png template2.txt.src
+docs_DATA = kpdf_pinconfiguration.png ooo_changedpins.png xemacs_modifiedselection.png gschem_showhidden.png ooo_attributes.png template.ods ooo_rearanged.png xemacs_rawselection.png kpdf_pindescription.png acroread_selectiontable.png template.txt template2.ods template2.txt.src gschem_finished.png ooo_selection.png
EXTRA_DIST = $(docs_DATA)
diff --git a/docs/wiki/playground-playground.html b/docs/wiki/playground-playground.html
deleted file mode 100644
index 4f6c787..0000000
--- a/docs/wiki/playground-playground.html
+++ /dev/null
@@ -1,99 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
-<html>
-<head>
- <title></title>
- <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
- <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
- <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
-
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-</head>
-<body>
-
-
-<p>
-Playground. <img src="images/smileys/icon_fun.gif" align="middle" alt="^_^" /><br/>
- <em class="u"><em><strong>It is a simple text.</strong></em></em> <pre STYLE="background : LightGreen;
-margin-left : 2em"><font size="+0">
-<linux:/home/zabbix$ <strong>ls -l | grep</strong>
-drwxr-xr-x 2 zabbix zabbix 4096 Mar 23 2004 autom4te.cache
-drwxr-xr-x 2 zabbix zabbix 4096 Oct 4 2004 bin
-drwxr-xr-x 5 zabbix zabbix 4096 Mar 23 2004 create
-drwxr-xr-x 2 zabbix zabbix 4096 Mar 23 2004 doc
-</font></pre>
-</p>
-
-<p>
-A schematic symbol for gschem, that I made is for the 36-pin Centronics connector.<br/>
- See the picture!<br/>
- But I donâ??t know, how to upload a picture?
-</p>
-<div class="box round orange" style="width: 80%; ">
- <b class='xtop'><b class='xb1'></b><b class='xb2'></b><b class='xb3'></b><b class='xb4'></b></b>
- <div class='xbox'>
-<p class='box_title'>a title</p>
-<div class='box_content'> the box contents</div>
- </div>
- <b class='xbottom'><b class='xb4'></b><b class='xb3'></b><b class='xb2'></b><b class='xb1'></b></b>
-</div>
-<div class="box left blue" style="width: 50%; ">
- <b class='xtop'><b class='xb1'></b><b class='xb2'></b><b class='xb3'></b><b class='xb4'></b></b>
- <div class='xbox'>
-<div class='box_content'>the box contents</div>
-<p class='box_caption'>a caption</p>
- </div>
- <b class='xbottom'><b class='xb4'></b><b class='xb3'></b><b class='xb2'></b><b class='xb1'></b></b>
-</div>
-<div class="box round" style="width: 60%; background-color: rgb(255,204,204); border-color: rgb(255,102,0);">
- <b class='xtop'><b class='xb1' style="background-color: rgb(255,204,204); border-color: rgb(255,102,0);"></b><b class='xb2' style="background-color: rgb(255,204,204); border-color: rgb(255,102,0);"></b><b class='xb3' style="background-color: rgb(255,204,204); border-color: rgb(255,102,0);"></b><b class='xb4' style="background-color: rgb(255,204,204); border-color: rgb(255,102,0);"></b></b>
- <div class='xbox' style="background-color: rgb(255,204,204); border-color: rgb(255,102,0);">
-<p class='box_title'style="background-color: rgb(255,204,153);">title</p>
-<div class='box_content'style="background-color: rgb(255,153,153); border-color: rgb(255,102,0)">the box contents></div>
-<p class='box_caption'style="background-color: rgb(255,204,153);">caption</p>
- </div>
- <b class='xbottom'><b class='xb4' style="background-color: rgb(255,204,204); border-color: rgb(255,102,0);"></b><b class='xb3' style="background-color: rgb(255,204,204); border-color: rgb(255,102,0);"></b><b class='xb2' style="background-color: rgb(255,204,204); border-color: rgb(255,102,0);"></b><b class='xb1' style="background-color: rgb(255,204,204); border-color: rgb(255,102,0);"></b></b>
-</div>
-<div class="box green">
- <b class='xtop'><b class='xb1'></b><b class='xb2'></b><b class='xb3'></b><b class='xb4'></b></b>
- <div class='xbox'>
-<div class='box_content'> this is also boxed </div>
-<p class='box_caption'>boxed & captioned</p>
- </div>
- <b class='xbottom'><b class='xb4'></b><b class='xb3'></b><b class='xb2'></b><b class='xb1'></b></b>
-</div>
-<div class="box">
- <b class='xtop'><b class='xb1'></b><b class='xb2'></b><b class='xb3'></b><b class='xb4'></b></b>
- <div class='xbox'>
-<div class='box_content'> the box contents 1 2 3 4 5 </div>
- </div>
- <b class='xbottom'><b class='xb4'></b><b class='xb3'></b><b class='xb2'></b><b class='xb1'></b></b>
-</div>
-<div class="box">
- <b class='xtop'><b class='xb1'></b><b class='xb2'></b><b class='xb3'></b><b class='xb4'></b></b>
- <div class='xbox'>
-<p class='box_title'>Example box</p>
-<div class='box_content'> to test what is possible: <strong>NICE PLUGIN:</strong> You can <ul>
-<li class="level1"><div class="li"> make Lists</div>
-</li>
-<li class="level1"><div class="li"> other markup</div>
-</li>
-<li class="level1"><div class="li"> set the color of the box</div>
-</li>
-<li class="level1"><div class="li"> …</div>
-</li>
-</ul>
-
-<p>
- looks good?
-</p>
-</div>
- </div>
- <b class='xbottom'><b class='xb4'></b><b class='xb3'></b><b class='xb2'></b><b class='xb1'></b></b>
-</div>
-
-<p>
-Just testing if I can log in and edit.
-</p>
-</body>
-</html>
diff --git a/docs/wiki/playground-transistor_guide.html b/docs/wiki/playground-transistor_guide.html
deleted file mode 100644
index f13fe82..0000000
--- a/docs/wiki/playground-transistor_guide.html
+++ /dev/null
@@ -1,129 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
-<html>
-<head>
- <title></title>
- <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
- <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
- <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
-
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-</head>
-<body>
-
-<div class="toc">
-<div class="tocheader toctoggle" id="toc__header">Table of Contents</div>
-<div id="toc__inside">
-
-<ul class="toc">
-<li class="level1"><div class="li"><span class="li"><a href="#gschem_symbol_and_pcb_element_transistor_guide" class="toc">gschem Symbol and PCB Element Transistor Guide</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#gschem_symbols" class="toc">gschem symbols</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#pcb_elements" class="toc">PCB Elements</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#general_procedure" class="toc">General Procedure</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#special_cases" class="toc">Special Cases</a></span></div></li></ul>
-</li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="gschem_symbol_and_pcb_element_transistor_guide" id="gschem_symbol_and_pcb_element_transistor_guide">gschem Symbol and PCB Element Transistor Guide</a></h1>
-<div class="level1">
-
-<p>
- The issue is how to manage a library of <em><strong>gschem</strong></em> transistor symbols and a library of PCB transistor elements such that we can be confident of correct pin number correspondence between the libraries. We need to understand how to handle the many permutations of emitter, base, and collector (e,b,c) pinouts and the variations of package number of pins and pin numbering. This doc shows the approach Iâ??ve taken in my custom <em><strong>gschem</strong></em> symbols and PCB elements.
-</p>
-
-</div>
-<!-- SECTION "gschem Symbol and PCB Element Transistor Guide" [1-531] -->
-<h2><a name="gschem_symbols" id="gschem_symbols">gschem symbols</a></h2>
-<div class="level2">
-
-<p>
- There are a couple of ways to consider:
-</p>
-<ol>
-<li class="level1"><div class="li"> Have a base set of <em><strong>gschem</strong></em> transistor symbols such as npn.sym, pnp.sym, fet.sym, etc. which have a fixed and arbitrarily assigned pin number for the emitter, base, and, collector. To accommodate the different permutations of (e,b,c) to pin numbers that exist for transistor packages, you would have to have a set of PCB elements for each transistor package like <a href="http://en.wikipedia.org/wiki/TO92"; class="urlextern" title="http://en.wikipedia.org/wiki/TO92"; rel="nofollow">TO-92</a>-123, TO-92-132, TO-92-213, TO-92-231, TO-92-312, TO-92-321, and similarly for <a href="http://en.wikipedia.org/wiki/TO220"; class="urlextern" title="http://en.wikipedia.org/wiki/TO220"; rel="nofollow">TO-220</a>, TO-5, etc. The problem with this is that manufacturers do specify pin numbers for their packages and we would be making many elements with pin numbers not corresponding to real packages. Remember, a PCB element on a PCB layout is supposed to correspond to a physical electronic component.</div>
-</li>
-<li class="level1"><div class="li"> Have a base set of <em><strong>gschem</strong></em> transistor symbols which spans the possible (e,b,c) permutations which can exist for any given transistor package. The set of <em><strong>gschem</strong></em> symbols for npn transistors would be npn-ebc.sym, npn-ecb.sym, npn-bec.sym, npn-bce.sym, npn-ceb.sym, and npn-cbe.sym. There would be similar sets for pnp transistors and FETs (fet-sdg.sym, fet-sgd.sym, …). Then there would be PCB elements only for actual physical transistor packages.</div>
-</li>
-</ol>
-
-<p>
- It makes sense to me to say the second approach is obviously better. Setting up the <em><strong>gschem</strong></em> symbols is simple enough, just create the six symbols for each transistor type with the pin numbers of the emitter, base, and collector corresponding to the sequence indicated in the name. For example, the symbol npn-ebc.sym would have an emitter <strong>pinnumber</strong> attribute of <strong>1</strong>, a base <strong>pinnumber</strong> attribute of <strong>2</strong> and a collector <strong>pinnumber</strong> attribute of <strong>3</strong>. Now you only need to make PCB elements with correctly numbered pins for transistor packages as you need them and you need to have a systematic approach for naming these elements.
-</p>
-
-</div>
-<!-- SECTION "gschem symbols" [532-2550] -->
-<h2><a name="pcb_elements" id="pcb_elements">PCB Elements</a></h2>
-<div class="level2">
-
-<p>
- A point to keep in mind when looking at transistor package pin configurations and numbers is that a TO (Transistor Outline) designation is really only just that - a designation of a particular shaped and sized outline. It actually is not a specification of the pins coming out of that package. Manufacturers may have have a TO package designation qualified by their internal â??case styleâ?? or â??package numberâ?? code. This qualification determines the definition of the number of pins, the arrangement of the pins, and the pin numbering.
-</p>
-
-<p>
-However, most TO packages do conform to a standard pin numbering convention and have a predominant number of pins and pin placement configuration. So it makes sense to have PCB elements with a particular TO name which can be used for a majority of cases. Then when a non conforming case is encountered, we can make a new TO element for it.
-</p>
-
-<p>
-Hereâ??s a description of what seems to be the most common transistor outline configurations:
-</p>
-<ul>
-<li class="level1"><div class="li"> <em>Power Transistors - Plastic</em>: Look at the package front (where the lettering is) with the pins pointing down. The pins are numbered left to right (1,2,3). This is very common, so it makes sense to create initial sets of three pin PCB elements with this number order using base names such as TO-126, TO-220, TO-264, etc. For variations such as a five pin TO-220 package for a LM383, you could make a PCB element with its name qualified such as TO-220-5, or maybe TO-220-T05B if you wanted to qualify it with the National Semiconductor T05B package designation for their 5 pin TO-220 package.</div>
-</li>
-<li class="level1"><div class="li"> <em>Power Transistors - Metal</em>: This would be the TO-3 package which can have from 2 to many pins. There is no index tab on the package so you need to look at a diagram of the pin out to see the pin numbering. The common 2 pin package could be named TO-3, and N pin packages with N > 2 could be named TO-3-N.</div>
-</li>
-<li class="level1"><div class="li"> <em>Small Signal Transistors - Metal</em>: Look at the transistor bottom with the pins pointing at you. The pins are numbered clockwise from the index tab (1,2,3,…) Metal can packages such as TO-18, TO-39, or TO-72 will frequently have 3 or 4 pins, while the TO-5 may have 3, 4, 5, 6, 8, or 10 pins. Because of the variable pin numbers, you could, for example, name the PCB elements TO-18-3 and TO-18-4, or you could use TO-18 and TO-18-4 assuming that a three pin can is more common and thus earns the base TO-18 element name.</div>
-</li>
-<li class="level1"><div class="li"> <em>Small Signal Transistors - Plastic</em>: Look at the transistor package flat side (where the lettering is) with the pins pointing down. Almost all packages where the three pins are in a straight line will have the left to right pin number ordering of (1,2,3) and these can be the base TO-92 PCB element. There are a very small number of cases where the pins will be in a straight line and numbered left to right (3,2,1). You could have a distinct PCB element for these, but you could also decide to ignore the manufacturerâ??s pin numbering and pretend itâ??s the more common (1,2,3). However, if the package has the middle pin offset so the pins are in a triangular arrangement, the pin number ordering will frequently be (3,2,1) and this will possibly require a custom PCB element. But see my comments about my <a href="playground-transistor_guide.html#special_cases" class="wikilink1" title="playground-transistor_guide.html">TO-92o</a> element below.</div>
-</li>
-<li class="level1"><div class="li"> <em>Surface Mount Transistors</em>: The SOT (Small Outline Transistor) packages are much more standard than the TO packages and the pins are consistently numbered counterclockwise from the top left as are IC packages. But for a transistor that has a TO and a SOT version, you canâ??t simply change the <strong>footprint</strong> attribute on the schematic because the package pin numbers donâ??t map the same to the emitter, base, and collector. You need a separate <em><strong>gschem</strong></em> symbol for them. For example: <strong>2N3904.sym</strong> for the TO and <strong>MMBT3904.sym</strong> for the SOT.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "PCB Elements" [2551-6419] -->
-<h2><a name="general_procedure" id="general_procedure">General Procedure</a></h2>
-<div class="level2">
-
-<p>
- The process of using a transistor for the first time in a <em><strong>gschem</strong></em> to PCB design takes these steps (2N3904 used as an example):
-</p>
-<ol>
-<li class="level1"><div class="li"> Most transistor <acronym title="specification">spec</acronym> sheets can be found in pdf format on the web, so get one and determine the case style and pin name and number ordering. For the 2N3904 the case style is TO-92, the pin number order left to right is (1,2,3), and the pin name order left to right is (e,b,c).</div>
-</li>
-<li class="level1"><div class="li"> If we have a PCB element in our library for that case style with the correct pin number order, use it. If not, make a new PCB element. For the 2N3904, I have a TO-92 element in my custom library that has the pin number order of (1,2,3), so I can use it.</div>
-</li>
-<li class="level1"><div class="li"> Copy the <em><strong>gschem</strong></em> transistor symbol corresponding to the pin name order to a new transistor symbol name. For the 2N3904 example, the pin name order is (e,b,c) so copy the base symbol npn-ebc.sym into 2N3904.sym.</div>
-</li>
-<li class="level1"><div class="li"> Edit the new symbol and change the <strong>value</strong> attribute to the transistor name and the <strong>footprint</strong> attribute to the right PCB element. For our example, this would be <strong>2N3904</strong> and <strong>TO-92</strong>.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "General Procedure" [6420-7545] -->
-<h3><a name="special_cases" id="special_cases">Special Cases</a></h3>
-<div class="level3">
-<ol>
-<li class="level1"><div class="li"> I have in my library a TO-92o PCB element which has the middle pin offset so the pins are in a triangular arrangement. This element has the left to right pin number order of (1,2,3) and can be used in place of the TO-92 for layout considerations. You only have to slightly bend the middle pin of the transistor when installing it.</div>
-</li>
-<li class="level1"><div class="li"> The BC546 transistor <acronym title="specification">spec</acronym> sheet shows its pin number order to be (1,2,3) in a straight line and the pin name order to be (c,b,e). But Iâ??ve seen this transistor shipped from the factory with the middle pin prebent into the offset configuration. For this transistor, you would create the <em><strong>gschem</strong></em> symbol from npn-cbe.sym as expected but use the PCB element TO-92o.</div>
-</li>
-<li class="level1"><div class="li"> The BF240 transistor <acronym title="specification">spec</acronym> sheet shows its pin number order to be left to right (3,2,1) in a straight line and the pin name order would be left to right (c,e,b). If you made a new PCB element with pins numbered (3,2,1), then you would have to create the <em><strong>gschem</strong></em> BF240.sym from npn-bec.sym because pin 1 on the PCB element has to correspond to pin 1 on the <em><strong>gschem</strong></em> symbol. But it would be easier to just ignore this uncommon pin numbering and assume the transistor pins are actually numbered the standard left to right (1,2,3). Then you could use the existing TO-92 PCB element and create the <em><strong>gschem</strong></em> symbol using npn-ceb.sym. Some transistor <acronym title="specification">spec</acronym> sheets give the pin name order and do not give a pin number order, and for these you just make the same assumption that the pins are numbered left to right (1,2,3).</div>
-</li>
-<li class="level1"><div class="li"> In the second case above, the transistor had an offset pin 2 when the <acronym title="specification">spec</acronym> sheet showed the pins in a straight line, and the pin numbers on the <acronym title="specification">spec</acronym> sheet were ordered left to right (1,2,3). But many transistors have the offset pin 2 indicated on the the <acronym title="specification">spec</acronym> sheet and the pin numbers are ordered left to right (3,2,1). You could use an element such as my TO-92o by ignoring the <acronym title="specification">spec</acronym> sheet ordering as I suggested in case 3. But this configuration is much more common than the BF240 example so you might want to have a distinct PCB element for it with pins numbered to match the <acronym title="specification">spec</acronym> sheet.</div>
-</li>
-</ol>
-<hr />
-
-<p>
-tutorial by Bill Wilson (bill–at–gkrellm.net)
-</p>
-
-</div>
-<!-- SECTION "Special Cases" [7546-] --></body>
-</html>
diff --git a/docs/wiki/start.html b/docs/wiki/start.html
index d876a26..19d0714 100644
--- a/docs/wiki/start.html
+++ b/docs/wiki/start.html
@@ -20,7 +20,7 @@
<ul class="toc">
<li class="level2"><div class="li"><span class="li"><a href="#what_is_geda" class="toc">What is gEDA?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#official_project_documentation" class="toc">Official Project documentation</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#faqs_and_informal_project_documentation" class="toc">FAQs and Informal Project Documentation</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#faqs_quick_reference" class="toc">FAQs & Quick Reference</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#developer_documentation" class="toc">Developer Documentation</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#talks" class="toc">Talks</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#google_summer_of_code" class="toc">Google Summer of Code</a></span></div></li>
@@ -54,7 +54,7 @@ All of the software in the gEDA suite can be found on the <a href="http://www.gp
</p>
</div>
-<!-- SECTION "What is gEDA?" [36-1175] -->
+<!-- SECTION "What is gEDA?" [36-1176] -->
<h2><a name="official_project_documentation" id="official_project_documentation">Official Project documentation</a></h2>
<div class="level2">
@@ -62,17 +62,17 @@ All of the software in the gEDA suite can be found on the <a href="http://www.gp
These are the official project docs. They have been converted from LaTeX and <acronym title="HyperText Markup Language">HTML</acronym> documents into Wiki pages so that the gEDA community may more easily maintain them.
</p>
<ul>
-<li class="level1"><div class="li"> <a href="geda-documentation.html" class="wikilink1" title="geda-documentation.html">Documentation</a> : The latest versions of the gEDA Tool Suite documentation.</div>
+<li class="level1"><div class="li"> <a href="geda-documentation.html" class="wikilink1" title="geda-documentation.html">Documentation</a> : Contains links to tutorials, manuals, HOWTOs and format specifications of the gEDA suite. </div>
</li>
</ul>
</div>
-<!-- SECTION "Official Project documentation" [1176-1478] -->
-<h2><a name="faqs_and_informal_project_documentation" id="faqs_and_informal_project_documentation">FAQs and Informal Project Documentation</a></h2>
+<!-- SECTION "Official Project documentation" [1177-1516] -->
+<h2><a name="faqs_quick_reference" id="faqs_quick_reference">FAQs & Quick Reference</a></h2>
<div class="level2">
<p>
-These are FAQs, HOWTOs, and tips/tricks to help you with the practical details of using the gEDA Suite. If you are having a problem, browse these pages first.
+These are informal FAQs, HOWTOs, and tips/tricks to help you with the practical details of using the gEDA Suite. If you are having a problem, browse these pages first.
</p>
<ul>
<li class="level1"><div class="li"> <a href="geda-faq.html" class="wikilink1" title="geda-faq.html">FAQ</a> : Frequently Asked Questions about the gEDA project itself.</div>
@@ -101,14 +101,14 @@ These are FAQs, HOWTOs, and tips/tricks to help you with the practical details o
</li>
<li class="level1"><div class="li"> <a href="geda-pcb_footprints.html" class="wikilink1" title="geda-pcb_footprints.html">PCB footprints</a> : How to create, use and share footprints.</div>
</li>
-<li class="level1"><div class="li"> <a href="geda-scg.html" class="wikilink1" title="geda-scg.html">scg</a> : gschem symbol creation guide.</div>
+<li class="level1"><div class="li"> <a href="geda-gschem_symbol_creation.html" class="wikilink1" title="geda-gschem_symbol_creation.html">gschem Symbol Creation</a> : gschem symbol creation guide.</div>
</li>
<li class="level1"><div class="li"> <a href="geda-guile_scripting.html" class="wikilink1" title="geda-guile_scripting.html">Guile scripting</a> : Guile functions & variables provided by the gEDA tools.</div>
</li>
</ul>
</div>
-<!-- SECTION "FAQs and Informal Project Documentation" [1479-2986] -->
+<!-- SECTION "FAQs & Quick Reference" [1517-3035] -->
<h2><a name="developer_documentation" id="developer_documentation">Developer Documentation</a></h2>
<div class="level2">
@@ -146,10 +146,12 @@ The following pages are related to the day-to-day development of the gEDA suite:
</li>
<li class="level1"><div class="li"> <a href="geda-format_translation.html" class="wikilink1" title="geda-format_translation.html">format translation</a> : Some notes on file format translation.</div>
</li>
+<li class="level1"><div class="li"> <a href="geda-gparts_dd.html" class="wikilink1" title="geda-gparts_dd.html">Parts Manager</a> : A working document for a gEDA parts manager</div>
+</li>
</ul>
</div>
-<!-- SECTION "Developer Documentation" [2987-4465] -->
+<!-- SECTION "Developer Documentation" [3036-4598] -->
<h2><a name="talks" id="talks">Talks</a></h2>
<div class="level2">
@@ -162,7 +164,7 @@ These are slides of presentations done about gEDA. They provide a good top-leve
</ul>
</div>
-<!-- SECTION "Talks" [4466-4706] -->
+<!-- SECTION "Talks" [4599-4839] -->
<h2><a name="google_summer_of_code" id="google_summer_of_code">Google Summer of Code</a></h2>
<div class="level2">
@@ -189,7 +191,7 @@ Here is this yearâ??s Google Summer of Code page:
</ul>
</div>
-<!-- SECTION "Google Summer of Code" [4707-5086] -->
+<!-- SECTION "Google Summer of Code" [4840-5219] -->
<h2><a name="translations" id="translations">Translations</a></h2>
<div class="level2">
<ul>
@@ -200,7 +202,7 @@ Here is this yearâ??s Google Summer of Code page:
</ul>
</div>
-<!-- SECTION "Translations" [5087-5203] -->
+<!-- SECTION "Translations" [5220-5336] -->
<h2><a name="geda_users" id="geda_users">gEDA Users</a></h2>
<div class="level2">
@@ -217,7 +219,7 @@ The so-called â??Free Dogâ?? organization ( <a href="http://freeedaug.org/"; clas
</p>
</div>
-<!-- SECTION "gEDA Users" [5204-5736] -->
+<!-- SECTION "gEDA Users" [5337-5869] -->
<h2><a name="about_this_wiki" id="about_this_wiki">About this Wiki</a></h2>
<div class="level2">
@@ -230,5 +232,5 @@ Anyone is welcome to contribute. Unlike Wikipedia there is no button to create a
</p>
</div>
-<!-- SECTION "About this Wiki" [5737-] --></body>
+<!-- SECTION "About this Wiki" [5870-] --></body>
</html>
diff --git a/docs/wiki/start_es.html b/docs/wiki/start_es.html
index 540ce33..4408be8 100644
--- a/docs/wiki/start_es.html
+++ b/docs/wiki/start_es.html
@@ -53,7 +53,7 @@
</p>
</div>
-<!-- SECTION "Tutoriales" [175-358] -->
+<!-- SECTION "Tutoriales" [175-359] -->
<h2><a name="otros" id="otros">Otros</a></h2>
<div class="level2">
@@ -66,9 +66,13 @@
</p>
<p>
-<a href="http://marcelo.memebot.com/linux/Geda01.html"; class="urlextern" title="http://marcelo.memebot.com/linux/Geda01.html"; rel="nofollow"> Como de GEDA + Spice + easy_spice Debian Sarge.</a>
+<a href="http://marcelo.memebot.com/linux/Geda01.html"; class="urlextern" title="http://marcelo.memebot.com/linux/Geda01.html"; rel="nofollow"> Como de GEDA + Spice + easy_spice Debian Sarge.</a>
+</p>
+
+<p>
+<a href="http://migueldemalaga.blogspot.es/img/Geda-gschem-.pdf"; class="urlextern" title="http://migueldemalaga.blogspot.es/img/Geda-gschem-.pdf"; rel="nofollow"> gEDA - gschem</a>
</p>
</div>
-<!-- SECTION "Otros" [359-] --></body>
+<!-- SECTION "Otros" [360-] --></body>
</html>
diff --git a/docs/wiki/wiki-syntax.html b/docs/wiki/wiki-syntax.html
index 17b47f2..156e0c2 100644
--- a/docs/wiki/wiki-syntax.html
+++ b/docs/wiki/wiki-syntax.html
@@ -656,7 +656,7 @@ echo '<img src="' . $_SERVER['PHP_SELF'] . '?=&
<p>
DokuWikiâ??s syntax can be extended by <a href="http://wiki.splitbrain.org/wiki%3Aplugins"; class="interwiki iw_doku" title="http://wiki.splitbrain.org/wiki%3Aplugins";>Plugins</a>. How the installed plugins are used is described on their appropriate description pages. The following syntax plugins are available in this particular DokuWiki installation:
</p>
-<ul><li><div class="li"><a href="http://wiki.splitbrain.org/plugin:info"; class="urlextern" title="http://wiki.splitbrain.org/plugin:info"; rel="nofollow">Info Plugin</a> <em>2006-12-09</em> by <a href="mailto:andi@splitbrain.org"; class="mail JSnocheck" title="andi@splitbrain.org">Andreas Gohr</a><br />Displays information about various DokuWiki internals</div></li><li><div class="li"><a href="http://wiki.splitbrain.org/plugin:definitions"; class="urlextern" title="http://wiki.splitbrain.org/plugin:definitions"; rel="nofollow">Definition list plugin</a> <em>2005-09-17</em> by <a href="mailto:chris@jalakai.co.uk"; class="mail JSnocheck" title="chris@jalakai.co.uk">Christopher Smith</a><br />Add HTML style definition list ; term : definition</div></li><li><div class="li"><a href="http://wiki.splitbrain.org/plugin:hilited"; class="urlextern" title="http://wiki.splitbrain.org/plugin:hilited"; rel="nofollow">Hilited Plugin</a> <em>2005-06-27</em> by <a href="mailto:esther@kaffeehaus.ch"; class="mail JSnocheck" title="esther@kaffeehaus.ch">Esther Brunner</a><br />Enables highlighted text</div></li><li><div class="li"><a href="http://wiki.splitbrain.org/plugin:note"; class="urlextern" title="http://wiki.splitbrain.org/plugin:note"; rel="nofollow">Note Plugin</a> <em>2006-03-29</em> by <a href="mailto:olive@deep-ocean.net"; class="mail JSnocheck" title="olive@deep-ocean.net">Olivier Cortès / Eric Hameleers / Christopher Smith</a><br />Add Note/Important/Tip/Warning Capability (DIV+CSS box)</div></li><li><div class="li"><a href="http://wiki.splitbrain.org/plugin:xterm"; class="urlextern" title="http://wiki.splitbrain.org/plugin:xterm"; rel="nofollow">xterm Plugin</a> <em>2005-10-12</em> by <a href="mailto:tom_trenker@yahoo.com"; class="mail JSnocheck" title="tom_trenker@yahoo.com">Tom Trenker</a><br />for displaying xterm with formatting.<br /> <xterm> text **bold text** </xterm></div></li><li><div class="li"><a href="http://wiki.splitbrain.org/plugin:boxes"; class="urlextern" title="http://wiki.splitbrain.org/plugin:boxes"; rel="nofollow">Box Plugin</a> <em>2008-03-03</em> by <a href="mailto:chris@jalakai.co.uk"; class="mail JSnocheck" title="chris@jalakai.co.uk">Christopher Smith</a><br />Boxes with titles, colour and rounded corners. <br /> Syntax: <box width class colours|title> ... </box|caption><br /> width, class, colours title & caption are optional.<br /> The title can include some wiki markup, the box<br /> contents can include almost any wiki markup.</div></li></ul>
+<ul><li><div class="li"><a href="http://wiki.splitbrain.org/plugin:boxes"; class="urlextern" title="http://wiki.splitbrain.org/plugin:boxes"; rel="nofollow">Box Plugin</a> <em>2008-03-03</em> by <a href="mailto:chris@jalakai.co.uk"; class="mail JSnocheck" title="chris@jalakai.co.uk">Christopher Smith</a><br />Boxes with titles, colour and rounded corners. <br /> Syntax: <box width class colours|title> ... </box|caption><br /> width, class, colours title & caption are optional.<br /> The title can include some wiki markup, the box<br /> contents can include almost any wiki markup.</div></li><li><div class="li"><a href="http://wiki.splitbrain.org/plugin:definitions"; class="urlextern" title="http://wiki.splitbrain.org/plugin:definitions"; rel="nofollow">Definition list plugin</a> <em>2005-09-17</em> by <a href="mailto:chris@jalakai.co.uk"; class="mail JSnocheck" title="chris@jalakai.co.uk">Christopher Smith</a><br />Add HTML style definition list ; term : definition</div></li><li><div class="li"><a href="http://wiki.splitbrain.org/plugin:hilited"; class="urlextern" title="http://wiki.splitbrain.org/plugin:hilited"; rel="nofollow">Hilited Plugin</a> <em>2005-06-27</em> by <a href="mailto:esther@kaffeehaus.ch"; class="mail JSnocheck" title="esther@kaffeehaus.ch">Esther Brunner</a><br />Enables highlighted text</div></li><li><div class="li"><a href="http://wiki.splitbrain.org/plugin:info"; class="urlextern" title="http://wiki.splitbrain.org/plugin:info"; rel="nofollow">Info Plugin</a> <em>2006-12-09</em> by <a href="mailto:andi@splitbrain.org"; class="mail JSnocheck" title="andi@splitbrain.org">Andreas Gohr</a><br />Displays information about various DokuWiki internals</div></li><li><div class="li"><a href="http://wiki.splitbrain.org/plugin:note"; class="urlextern" title="http://wiki.splitbrain.org/plugin:note"; rel="nofollow">Note Plugin</a> <em>2006-03-29</em> by <a href="mailto:olive@deep-ocean.net"; class="mail JSnocheck" title="olive@deep-ocean.net">Olivier Cortès / Eric Hameleers / Christopher Smith</a><br />Add Note/Important/Tip/Warning Capability (DIV+CSS box)</div></li><li><div class="li"><a href="http://wiki.splitbrain.org/plugin:xterm"; class="urlextern" title="http://wiki.splitbrain.org/plugin:xterm"; rel="nofollow">xterm Plugin</a> <em>2005-10-12</em> by <a href="mailto:tom_trenker@yahoo.com"; class="mail JSnocheck" title="tom_trenker@yahoo.com">Tom Trenker</a><br />for displaying xterm with formatting.<br /> <xterm> text **bold text** </xterm></div></li></ul>
</div>
<!-- SECTION "Syntax Plugins" [14285-] --><div class="footnotes">
<div class="fn"><a href="#fnt__1" id="fn__1" name="fn__1" class="fn_bot">1)</a>
commit 19e4de650dad95977bc07bae4f897ab6b9d7b110
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Commit: Ales Hvezda <ahvezda@xxxxxxxx>
Tweaked scripts with updated paths
Eventually these scripts should be fixed or rewritten so that they
do not have any hardcoded paths.
diff --git a/docs/scripts/copygitignores.sh b/docs/scripts/copygitignores.sh
index e7da5a1..d43aa67 100755
--- a/docs/scripts/copygitignores.sh
+++ b/docs/scripts/copygitignores.sh
@@ -1,18 +1,18 @@
#!/bin/sh
-if [ ! -d "wiki" -a ! -d "wip" ]
+if [ ! -d "wiki" -a ! -d "wikiold" ]
then
echo "You must start this program in the toplevel docs directory"
- echo "wherever wiki and wip live."
+ echo "wherever wiki and wikiold live."
exit 1
fi
-files=`find wiki -name .gitignore -print`
+files=`find wikiold -name .gitignore -print`
for i in $files
do
src=$i
- dest=`echo $i | sed "s/^wiki/wip/"`
+ dest=`echo $i | sed "s/^wikiold/wiki/"`
echo Copying $src to $dest
cp -f $src $dest
done
diff --git a/docs/scripts/populatemkfiles.sh b/docs/scripts/populatemkfiles.sh
index 8553471..3f8ed9a 100755
--- a/docs/scripts/populatemkfiles.sh
+++ b/docs/scripts/populatemkfiles.sh
@@ -76,8 +76,8 @@ do_work()
}
pwd=`pwd`
-thisprogram=/home/ahvezda/gaf/docs/scripts/populatemkfiles.sh
-basedir=/home/ahvezda/gaf/docs/wip
+thisprogram=/home/ahvezda/gaf.git/docs/scripts/populatemkfiles.sh
+basedir=/home/ahvezda/gaf/docs/wiki
subdir=`echo $pwd | awk -F$basedir '{print $2}'`
_______________________________________________
geda-cvs mailing list
geda-cvs@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-cvs