[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
gEDA-cvs: branch: master updated (1.1.2.20070818-226-gd237ea6)
The branch, master has been updated
via d237ea60a5221ea8dad20765e07d62c8c5596515 (commit)
from ba474af87840a0d49e04a00de96b7df2944c09bd (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/wiki/001geda_documentation.html | 10 +-
docs/wiki/Makefile.am | 2 +-
docs/wiki/geda_cygwin.html | 16 +-
docs/wiki/geda_documentation.html | 22 +-
docs/wiki/geda_faq-gsch2pcb.html | 37 ++-
docs/wiki/geda_faq-gschem.html | 136 ++++--
docs/wiki/geda_faq-pcb.html | 4 +-
docs/wiki/geda_faq.html | 2 +-
docs/wiki/geda_fedora_rpm_installation.html | 10 +-
docs/wiki/geda_file_format_spec.html | 40 +-
docs/wiki/geda_glossary.html | 22 +-
docs/wiki/geda_gsch2pcb_tutorial.html | 4 +-
docs/wiki/geda_guile_scripting.html | 236 ++++++++++
docs/wiki/geda_pcb_tips.html | 268 ++++++++---
docs/wiki/geda_scm.html | 79 +++--
docs/wiki/geda_suse_rpm_installation.html | 54 ++-
docs/wiki/geda_tasks.html | 8 +-
docs/wiki/geda_todos.html | 78 +++-
docs/wiki/geda_transistor_guide.html | 2 +-
docs/wiki/geda_usage.html | 14 +-
docs/wiki/gsoc2007.html | 198 ++++++++
docs/wiki/gsoc2007_projects.html | 650 +++++++++++++++++++++++++++
docs/wiki/index.html | 32 +-
docs/wiki/lib/exe/001css | 2 +-
docs/wiki/lib/exe/002css | 2 +-
docs/wiki/lib/exe/css | 2 +-
docs/wiki/lib/images/fileicons/Makefile.am | 2 +-
docs/wiki/lib/images/fileicons/conf.png | Bin 1226 -> 0 bytes
docs/wiki/lib/images/fileicons/htm.png | Bin 796 -> 0 bytes
docs/wiki/lib/images/fileicons/html.png | Bin 796 -> 0 bytes
docs/wiki/lib/images/fileicons/src.png | Bin 0 -> 542 bytes
docs/wiki/lib/images/fileicons/txt.png | Bin 277 -> 0 bytes
docs/wiki/lib/images/fileicons/xml.png | Bin 1059 -> 0 bytes
docs/wiki/libgeda3.html | 12 +-
docs/wiki/start_es.html | 10 +-
35 files changed, 1690 insertions(+), 264 deletions(-)
create mode 100644 docs/wiki/geda_guile_scripting.html
create mode 100644 docs/wiki/gsoc2007.html
create mode 100644 docs/wiki/gsoc2007_projects.html
delete mode 100644 docs/wiki/lib/images/fileicons/conf.png
delete mode 100644 docs/wiki/lib/images/fileicons/htm.png
delete mode 100644 docs/wiki/lib/images/fileicons/html.png
create mode 100644 docs/wiki/lib/images/fileicons/src.png
delete mode 100644 docs/wiki/lib/images/fileicons/txt.png
delete mode 100644 docs/wiki/lib/images/fileicons/xml.png
=================
Commit Messages
=================
commit d237ea60a5221ea8dad20765e07d62c8c5596515
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Date: Sat Dec 29 11:32:06 2007 -0500
Updated documentation (wiki) snapshot from master wiki on the geda website
:100644 100644 1a4f591... ef342a6... M docs/wiki/001geda_documentation.html
:100644 100644 8d3dc1e... 40cc8e9... M docs/wiki/Makefile.am
:100644 100644 c82c2b5... 861c898... M docs/wiki/geda_cygwin.html
:100644 100644 05128c2... 08f4ba1... M docs/wiki/geda_documentation.html
:100644 100644 6acc3f6... 9d0b7ae... M docs/wiki/geda_faq-gsch2pcb.html
:100644 100644 14e00a1... 66a7587... M docs/wiki/geda_faq-gschem.html
:100644 100644 23a0f43... 0aac218... M docs/wiki/geda_faq-pcb.html
:100644 100644 00b4d35... 0c4d12c... M docs/wiki/geda_faq.html
:100644 100644 bf30cfc... e3785e0... M docs/wiki/geda_fedora_rpm_installation.html
:100644 100644 ab0404e... d73c7e7... M docs/wiki/geda_file_format_spec.html
:100644 100644 6eb4317... b533c97... M docs/wiki/geda_glossary.html
:100644 100644 49135e3... 2c36f64... M docs/wiki/geda_gsch2pcb_tutorial.html
:000000 100644 0000000... df3e372... A docs/wiki/geda_guile_scripting.html
:100644 100644 6efd72e... d66e49b... M docs/wiki/geda_pcb_tips.html
:100644 100644 3c2ad43... 097b0b1... M docs/wiki/geda_scm.html
:100644 100644 4196c74... 877fef6... M docs/wiki/geda_suse_rpm_installation.html
:100644 100644 dfde142... c541e79... M docs/wiki/geda_tasks.html
:100644 100644 a5f6a07... 6b90f45... M docs/wiki/geda_todos.html
:100644 100644 6dd4223... e2dccd7... M docs/wiki/geda_transistor_guide.html
:100644 100644 a8b310d... ad12f5c... M docs/wiki/geda_usage.html
:000000 100644 0000000... 21474d5... A docs/wiki/gsoc2007.html
:000000 100644 0000000... 61e0f65... A docs/wiki/gsoc2007_projects.html
:100644 100644 6297660... f75649e... M docs/wiki/index.html
:100644 100644 7b22b2d... 7622e88... M docs/wiki/lib/exe/001css
:100644 100644 b105ade... 632fd89... M docs/wiki/lib/exe/002css
:100644 100644 98cf713... 6501c40... M docs/wiki/lib/exe/css
:100644 100644 648a3b3... d826916... M docs/wiki/lib/images/fileicons/Makefile.am
:100644 000000 7d9225e... 0000000... D docs/wiki/lib/images/fileicons/conf.png
:100644 000000 0e3ee49... 0000000... D docs/wiki/lib/images/fileicons/htm.png
:100644 000000 8a7163d... 0000000... D docs/wiki/lib/images/fileicons/html.png
:000000 100644 0000000... da20009... A docs/wiki/lib/images/fileicons/src.png
:100644 000000 1bc7f1c... 0000000... D docs/wiki/lib/images/fileicons/txt.png
:100644 000000 1286a5b... 0000000... D docs/wiki/lib/images/fileicons/xml.png
:100644 100644 e28c67f... eea723f... M docs/wiki/libgeda3.html
:100644 100644 a0e08c5... 22ace54... M docs/wiki/start_es.html
=========
Changes
=========
commit d237ea60a5221ea8dad20765e07d62c8c5596515
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Date: Sat Dec 29 11:32:06 2007 -0500
Updated documentation (wiki) snapshot from master wiki on the geda website
diff --git a/docs/wiki/001geda_documentation.html b/docs/wiki/001geda_documentation.html
index 1a4f591..ef342a6 100644
--- a/docs/wiki/001geda_documentation.html
+++ b/docs/wiki/001geda_documentation.html
@@ -83,11 +83,11 @@ New features are available for document authors:
</li>
<li class="level1"><div class="li"> <a href="001geda_gschem_mp.html" class="wikilink2" title="geda:gschem_mp.fr">page de manuel gschem</a></div>
</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:scg.fr"; class="wikilink1" title="geda:scg.fr">Guide de la Création de Symbole</a> (à traduire)</div>
+<li class="level1"><div class="li"> <a href="001geda_scg.html" class="wikilink1" title="geda:scg.fr">Guide de la Création de Symbole</a> (à traduire)</div>
</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:hse_howto.fr"; class="wikilink2" title="geda:hse_howto.fr">Hooks/Scheme Extension HOWTO</a></div>
+<li class="level1"><div class="li"> <a href="001geda_hse_howto.html" class="wikilink2" title="geda:hse_howto.fr">Hooks/Scheme Extension HOWTO</a></div>
</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:kig_howto.fr"; class="wikilink2" title="geda:kig_howto.fr">HOWTO du Keymapping dans gschem</a></div>
+<li class="level1"><div class="li"> <a href="001geda_kig_howto.html" class="wikilink2" title="geda:kig_howto.fr">HOWTO du Keymapping dans gschem</a></div>
</li>
</ul>
@@ -144,11 +144,11 @@ New features are available for document authors:
<ul>
<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gsch2pcb_readme"; class="wikilink1" title="geda:gsch2pcb_readme">gsch2pcb (gschem to PCB) README</a></div>
</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:bill_wilson_s"; class="wikilink2" title="geda:bill_wilson_s">gschem and pcb tutorial</a></div>
+<li class="level1"><div class="li"> <a href="geda_bill_wilson_s.html" class="wikilink2" title="geda:bill_wilson_s">gschem and pcb tutorial</a></div>
</li>
<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:tragesym_readme"; class="wikilink1" title="geda:tragesym_readme">tragesym (symbol generator) README</a></div>
</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:tragesym_tutorial.fr"; class="wikilink1" title="geda:tragesym_tutorial.fr">Tutoriel tragesym.fr</a></div>
+<li class="level1"><div class="li"> <a href="001geda_tragesym_tutorial.html" class="wikilink1" title="geda:tragesym_tutorial.fr">Tutoriel tragesym.fr</a></div>
</li>
<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:olib_readme"; class="wikilink1" title="geda:olib_readme">olib (OrCAD (TM) converter) README</a></div>
</li>
diff --git a/docs/wiki/Makefile.am b/docs/wiki/Makefile.am
index 8d3dc1e..40cc8e9 100644
--- a/docs/wiki/Makefile.am
+++ b/docs/wiki/Makefile.am
@@ -5,7 +5,7 @@ docsdir = @GEDADOCDIR@/$(docname)/
SUBDIRS = _media _detail lib
-docs_DATA = geda_gtkwave_lxt2vcd_mp.html geda_faq-simulation.html geda_sn_readme.html geda_data_plotting_improvements.html geda_gtkwave_mp.html geda_fc4.html geda_covered_rv.html geda_gsymcheck_mp.html geda_gtkwave_tex2vcd_mp.html docs_20060124_gschem_ug_components_symbols_objects_attributes.html .gitignore geda_gschem_mp.html geda_wcalc_mp.html geda_installation.html geda_icarus_vvp_runtime.html geda_kig_howto.html geda_eagle_pcb_netlister_readme.html 001geda_tasks.html geda_grenum_mp.html geda_pcb_footprints.html geda_gsch2pcb_tutorial.html geda_grcsan.html geda_ngsconvert_mp.html geda_icarus_readme.html 001geda_kig_howto.html geda_olib_readme.html geda_faq-gschem.html 001geda_suse_10.html geda_scg.html geda_fc3.html geda_version_control_migration.html geda_tragesym_tutorial.html 001geda_gschem_ug.html geda_transistor_guide.html geda_gschem_ug.html geda_icarus_xilinx_hints.html 001geda_faq-simulation.html geda_gattrib_readme.html geda_fbabgapp.html geda_icarus_quick_start.html geda_icarus_anc.html 001geda_usage.html index.html 001geda_faq-gsch2pcb.html geda_example_usbjtag.html geda_pcb_mp.html geda_bill_wilson_s.html 001geda_faq-gschem.html geda_mcalc_readme.html 001geda_pcb-quick_reference.html geda_suse_rpm_installation.html geda_icarus_xnf.html geda_gtkwave_tla2vcd_mp.html geda_gtkwave_lxt2miner_mp.html geda_gschem_warmup.html start_es.html geda_vams_netlister_readme.html geda_tasks.html geda_pcb-quick_reference.html docs_20060124_gschem_ug_installing_gschem.html 001geda_faq-gnetlist.html geda_devel-tips.html geda_style_guide.html geda_gsch2pcb_tutorial_releasenotes.html geda_systemc_netlister_readme.html geda_data_structure_design_discussion.html geda_syntax_features.html geda_gtkwave_vcd2vzt_mp.html 001geda_installation.html geda_gtkwave_vcd2lxt_mp.html start_fr.html geda_gtkwave_mvl2lxt_mp.html geda_csygas.html geda_wcalc_readme.html docs_20060124_gschem_ug_the_status_window.html geda_icarus_ieee1364.html geda_suse_10.html geda_footprint_creation.html geda_fc2.html geda_debian.html geda_gtkwave_mvl2vcd_mp.html geda_installed_plugins.html geda_example_hsm.html geda_gtkwave_vzt2vcd_mp.html 001geda_hse_howto.html geda_gtkwave_vcd2lxt2_mp.html geda_verilog_netlister_readme.html 001geda_debian.html geda_icarus_glossary.html docs_20060124_gschem_ug_app_a.html geda_glossaire.html geda_vhdl_netlister_readme.html docs_20060124_gschem_ug_resources.html geda_faq-gsch2pcb.html geda_glossary.html geda_gsch2pcb_readme.html geda_fedora_rpm_installation.html geda_covered_mp.html geda_master_attributes_list.html geda_icarus_vvp_simulation.html 001geda_todos.html geda_todos.html docs_20060124_gschem_ug_the_main_window.html geda_ssan.html wikinode.html geda_gtkwave_vztminer_mp.html 001geda_faq-attribs.html geda_ngspice_mp.html geda_icarus_vpi_within_vvp.html geda_pcb.html geda_gfdl.html libgeda3.html geda_pcb_tips.html geda_sdb_howto.html geda_gnetlist_ug.html geda_tragesym_readme.html docs_20060124_gschem_ug_app_b.html 001geda_scg.html geda_design_flow_and_hierarchy_roadmap.html docs_20060124_gschem_ug_electrical_connectivity.html geda_cygwin.html geda_icarus_mp.html 001geda_gschem_mp.html geda_gerbv_pnp_readme.html geda_icarus_vpi_mp.html geda_na_howto.html geda_igarus_fpga_lcg.html geda_faq-pcb.html 001geda_pcb_tips.html geda_wcalc_stdio_mp.html 001geda_faq.html geda_usage.html geda_gedasuite_installation.html geda_faq-attribs.html 001geda_tragesym_tutorial.html geda_icarus_extensions.html geda_icarus_opcodes.html docs_20060124_gschem_ug_app_c.html geda_gschem2pcb_readme.html geda_suse_9.html geda_gerbv_mp.html geda_bom_readme.html 001geda_documentation.html geda_ubuntu.html geda_scm.html geda_ngnutmeg_mp.html geda_hse_howto.html docs_20060124_gschem_ug_how_to_ask_questions.html geda_documentation.html geda_fc1.html geda_file_format_spec.html geda_circuit_simulation_improvements.html geda_faq-gnetlist.html geda_gnetlist_mp.html geda_faq.html geda_pcb_ug.html
+docs_DATA = geda_gtkwave_lxt2vcd_mp.html geda_faq-simulation.html geda_sn_readme.html geda_data_plotting_improvements.html geda_gtkwave_mp.html geda_fc4.html geda_covered_rv.html geda_gsymcheck_mp.html geda_gtkwave_tex2vcd_mp.html docs_20060124_gschem_ug_components_symbols_objects_attributes.html .gitignore geda_gschem_mp.html geda_wcalc_mp.html geda_installation.html geda_icarus_vvp_runtime.html geda_kig_howto.html geda_eagle_pcb_netlister_readme.html 001geda_tasks.html geda_guile_scripting.html geda_grenum_mp.html geda_pcb_footprints.html geda_gsch2pcb_tutorial.html geda_grcsan.html geda_ngsconvert_mp.html geda_icarus_readme.html 001geda_kig_howto.html geda_olib_readme.html geda_faq-gschem.html 001geda_suse_10.html geda_scg.html geda_fc3.html geda_version_control_migration.html geda_tragesym_tutorial.html 001geda_gschem_ug.html geda_transistor_guide.html geda_gschem_ug.html geda_icarus_xilinx_hints.html 001geda_faq-simulation.html geda_gattrib_readme.html geda_fbabgapp.html geda_icarus_quick_start.html geda_icarus_anc.html 001geda_usage.html index.html 001geda_faq-gsch2pcb.html geda_example_usbjtag.html geda_pcb_mp.html geda_bill_wilson_s.html 001geda_faq-gschem.html geda_mcalc_readme.html 001geda_pcb-quick_reference.html geda_suse_rpm_installation.html geda_icarus_xnf.html geda_gtkwave_tla2vcd_mp.html geda_gtkwave_lxt2miner_mp.html geda_gschem_warmup.html start_es.html geda_vams_netlister_readme.html geda_tasks.html geda_pcb-quick_reference.html docs_20060124_gschem_ug_installing_gschem.html 001geda_faq-gnetlist.html gsoc2007.html geda_devel-tips.html geda_style_guide.html geda_gsch2pcb_tutorial_releasenotes.html geda_systemc_netlister_readme.html geda_data_structure_design_discussion.html geda_syntax_features.html geda_gtkwave_vcd2vzt_mp.html 001geda_installation.html geda_gtkwave_vcd2lxt_mp.html start_fr.html gsoc2007_projects.html geda_gtkwave_mvl2lxt_mp.html geda_csygas.html geda_wcalc_readme.html docs_20060124_gschem_ug_the_status_window.html geda_icarus_ieee1364.html geda_suse_10.html geda_footprint_creation.html geda_fc2.html geda_debian.html geda_gtkwave_mvl2vcd_mp.html geda_installed_plugins.html geda_example_hsm.html geda_gtkwave_vzt2vcd_mp.html 001geda_hse_howto.html geda_gtkwave_vcd2lxt2_mp.html geda_verilog_netlister_readme.html 001geda_debian.html geda_icarus_glossary.html docs_20060124_gschem_ug_app_a.html geda_glossaire.html geda_vhdl_netlister_readme.html docs_20060124_gschem_ug_resources.html geda_faq-gsch2pcb.html geda_glossary.html geda_gsch2pcb_readme.html geda_fedora_rpm_installation.html geda_covered_mp.html geda_master_attributes_list.html geda_icarus_vvp_simulation.html 001geda_todos.html geda_todos.html docs_20060124_gschem_ug_the_main_window.html geda_ssan.html wikinode.html geda_gtkwave_vztminer_mp.html 001geda_faq-attribs.html geda_ngspice_mp.html geda_icarus_vpi_within_vvp.html geda_pcb.html geda_gfdl.html libgeda3.html geda_pcb_tips.html geda_sdb_howto.html geda_gnetlist_ug.html geda_tragesym_readme.html docs_20060124_gschem_ug_app_b.html 001geda_scg.html geda_design_flow_and_hierarchy_roadmap.html docs_20060124_gschem_ug_electrical_connectivity.html geda_cygwin.html geda_icarus_mp.html 001geda_gschem_mp.html geda_gerbv_pnp_readme.html geda_icarus_vpi_mp.html geda_na_howto.html geda_igarus_fpga_lcg.html geda_faq-pcb.html 001geda_pcb_tips.html geda_wcalc_stdio_mp.html 001geda_faq.html geda_usage.html geda_gedasuite_installation.html geda_faq-attribs.html 001geda_tragesym_tutorial.html geda_icarus_extensions.html geda_icarus_opcodes.html docs_20060124_gschem_ug_app_c.html geda_gschem2pcb_readme.html geda_suse_9.html geda_gerbv_mp.html geda_bom_readme.html 001geda_documentation.html geda_ubuntu.html geda_scm.html geda_ngnutmeg_mp.html geda_hse_howto.html docs_20060124_gschem_ug_how_to_ask_questions.html geda_documentation.html geda_fc1.html geda_file_format_spec.html geda_circuit_simulation_improvements.html geda_faq-gnetlist.html geda_gnetlist_mp.html geda_faq.html geda_pcb_ug.html
EXTRA_DIST = $(docs_DATA)
diff --git a/docs/wiki/geda_cygwin.html b/docs/wiki/geda_cygwin.html
index c82c2b5..861c898 100644
--- a/docs/wiki/geda_cygwin.html
+++ b/docs/wiki/geda_cygwin.html
@@ -7,7 +7,7 @@
<title>geda:cygwin</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:25-0400" />
+<meta name="date" content="2007-10-08T13:25:47-0400" />
<meta name="keywords" content="geda,cygwin" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -49,10 +49,13 @@ In the package selection dialog, select the following packages:
(Hint: press the â??viewâ?? button once to arrange the list in alphabetical order)
</p>
<pre class="code">atk-devel
+crypt
file
gcc
gtk2-x11-devel
guile-devel
+libgmp-devel
+libtool1.5
make
pango-devel
patchutils
@@ -64,11 +67,7 @@ xorg-x11-fscl
xterm</pre>
<p>
- Take care that you select guile and guile-devel version 1.6.7. Version 1.8.1 doesnâ??t work. (Werner)
-</p>
-
-<p>
-<strong>2. Append these lines to your .bash_profile:</strong>
+ <strong>2. Append these lines to your .bash_profile:</strong>
</p>
<pre class="code">export LD_LIBRARY_PATH=$HOME/geda/lib:$LD_LIBRARY_PATH
export PATH=$HOME/geda/bin:$PATH
@@ -84,11 +83,12 @@ export PKG_CONFIG_PATH=$HOME/geda/lib/pkgconfig:$PKG_CONFIG_PATH</pre>
</p>
<p>
-From the gEDA/gaf group, download <strong>only</strong> the packages which have a date as its version. The necessary dependencies where already installed in step 1.
+From the gEDA/gaf group, download <strong>only</strong> the packages which have a date as its version. The necessary dependencies were already installed in step 1. However, if you havenâ??t installed or built the libstroke package, be sure to uncomment the opts= line in the gaf Makefile and change it to
</p>
+<pre class="code">opts=--disable-stroke</pre>
<p>
-<strong>4. Go to the download directory and type:</strong>
+ <strong>4. Go to the download directory and type:</strong>
</p>
<pre class="code">$ make open
$ make install
diff --git a/docs/wiki/geda_documentation.html b/docs/wiki/geda_documentation.html
index 05128c2..08f4ba1 100644
--- a/docs/wiki/geda_documentation.html
+++ b/docs/wiki/geda_documentation.html
@@ -7,7 +7,7 @@
<title>geda:documentation</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-25T10:51:43-0400" />
+<meta name="date" content="2007-11-19T06:48:09-0500" />
<meta name="keywords" content="geda,documentation" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -243,7 +243,7 @@
</ul>
</div>
-<!-- SECTION "gSpiceUI" [3767-3875] -->
+<!-- SECTION "gSpiceUI" [3767-3874] -->
<h1><a name="pcb" id="pcb">PCB</a></h1>
<div class="level1">
<ul>
@@ -251,14 +251,14 @@
</li>
<li class="level1"><div class="li"> The official <a href="http://pcb.sourceforge.net/manual.html"; class="urlextern" title="http://pcb.sourceforge.net/manual.html"; rel="nofollow">manual of pcb</a></div>
</li>
-<li class="level1"><div class="li"> A very detailed <a href="http://www.brorson.com/gEDA/land_patterns_20050129.pdf"; class="urlextern" title="http://www.brorson.com/gEDA/land_patterns_20050129.pdf"; rel="nofollow">manual on footprint creation</a> by Stephen Meier and Stuart Brorson. It also covers most of the syntax of the *.pcb format. The document refers to the 2005 version of pcb.</div>
+<li class="level1"><div class="li"> A very detailed <a href="http://www.brorson.com/gEDA/land_patterns_20070818.pdf"; class="urlextern" title="http://www.brorson.com/gEDA/land_patterns_20070818.pdf"; rel="nofollow">manual on footprint creation</a> by Stephen Meier and Stuart Brorson. It also covers most of the syntax of the *.pcb format. The document refers to the 2007 version of pcb.</div>
</li>
<li class="level1"><div class="li"> The <a href="geda_pcb_mp.html" class="wikilink1" title="geda:pcb_mp">man-page of pcb</a></div>
</li>
</ul>
</div>
-<!-- SECTION "PCB" [3876-4285] -->
+<!-- SECTION "PCB" [3875-4284] -->
<h1><a name="gerbv" id="gerbv">gerbv</a></h1>
<div class="level1">
<ul>
@@ -269,7 +269,7 @@
</ul>
</div>
-<!-- SECTION "gerbv" [4286-4431] -->
+<!-- SECTION "gerbv" [4285-4430] -->
<h1><a name="icarus_verilog" id="icarus_verilog">Icarus Verilog</a></h1>
<div class="level1">
<ul>
@@ -308,7 +308,7 @@
</ul>
</div>
-<!-- SECTION "Icarus Verilog" [4432-5426] -->
+<!-- SECTION "Icarus Verilog" [4431-5425] -->
<h1><a name="gtkwave" id="gtkwave">GTKWave</a></h1>
<div class="level1">
<ul>
@@ -342,7 +342,7 @@
</ul>
</div>
-<!-- SECTION "GTKWave" [5427-6458] -->
+<!-- SECTION "GTKWave" [5426-6457] -->
<h1><a name="wcalc" id="wcalc">Wcalc</a></h1>
<div class="level1">
<ul>
@@ -355,7 +355,7 @@
</ul>
</div>
-<!-- SECTION "Wcalc" [6459-6605] -->
+<!-- SECTION "Wcalc" [6458-6604] -->
<h1><a name="mcalc" id="mcalc">mcalc</a></h1>
<div class="level1">
<ul>
@@ -366,7 +366,7 @@
</ul>
</div>
-<!-- SECTION "mcalc" [6606-6785] -->
+<!-- SECTION "mcalc" [6605-6784] -->
<h1><a name="covered" id="covered">covered</a></h1>
<div class="level1">
<ul>
@@ -379,7 +379,7 @@
</ul>
</div>
-<!-- SECTION "covered" [6786-7083] -->
+<!-- SECTION "covered" [6785-7082] -->
<h1><a name="for_document_authors" id="for_document_authors">For document authors</a></h1>
<div class="level1">
@@ -396,6 +396,6 @@ New features are available for document authors:
</ul>
</div>
-<!-- SECTION "For document authors" [7084-] --></div>
+<!-- SECTION "For document authors" [7083-] --></div>
</body>
</html>
diff --git a/docs/wiki/geda_faq-gsch2pcb.html b/docs/wiki/geda_faq-gsch2pcb.html
index 6acc3f6..9d0b7ae 100644
--- a/docs/wiki/geda_faq-gsch2pcb.html
+++ b/docs/wiki/geda_faq-gsch2pcb.html
@@ -7,7 +7,7 @@
<title>geda:faq-gsch2pcb</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-06-27T07:29:37-0400" />
+<meta name="date" content="2007-10-17T12:54:25-0400" />
<meta name="keywords" content="geda,faq-gsch2pcb" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -31,7 +31,8 @@
<ul class="toc">
<li class="level2"><div class="li"><span class="li"><a href="#where_is_the_gsch2pcb_tutorial" class="toc">Where is the gsch2pcb tutorial?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#where_can_i_download_gsch2pcb" class="toc">Where can I download gsch2pcb?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#gsch2pcb_can_t_find_some_of_my_footprints_or_errors_out._what_can_i_do_to_diagnose_my_problem" class="toc">gsch2pcb can't find some of my footprints, or errors out. What can I do to diagnose my problem?</a></span></div></li></ul>
+<li class="level2"><div class="li"><span class="li"><a href="#gsch2pcb_can_t_find_some_of_my_footprints_or_errors_out._what_can_i_do_to_diagnose_my_problem" class="toc">gsch2pcb can't find some of my footprints, or errors out. What can I do to diagnose my problem?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#i_don_t_like_the_default_layer_stack_of_gschem2pcb._how_can_i_change_this" class="toc">I don't like the default layer stack of gschem2pcb. How can I change this?</a></span></div></li></ul>
</li></ul>
</div>
</div>
@@ -51,7 +52,7 @@ Currently, the best information about how to get started with gsch2pcb is contai
</p>
<p>
-There is a wrapper script for gsch2pcb called sch2pcb. Read about it in the <a href="geda_pcb_tips.html" class="wikilink1" title="geda:pcb_tips">pcb_tips</a> section of this wiki.
+There is a wrapper script for gsch2pcb called sch2pcb. Read about it in the <a href="http://geda.seul.org/wiki/geda:pcb_tips"; class="wikilink1" title="geda:pcb_tips">pcb_tips</a> section of this wiki.
</p>
</div>
@@ -81,10 +82,36 @@ gsch2pcb is part of gEDA/gaf, in the utils. It is normally installed by default
<div class="level2">
<p>
-Try running gsch2pcb in double verbose mode: â??gsch2pcb -v -vâ??. This will produce lots of spew telling you where gsch2pcb is looking while it tries to find footprints. It will also tell you where it does find the footprints it uses.
+Try running gsch2pcb in double verbose mode: â??gsch2pcb -v -vâ??. This will produce lots of spew telling you where gsch2pcb is looking while it tries to find footprints. It will also tell you where it does find the footprints it uses.
</p>
</div>
-<!-- SECTION "gsch2pcb can't find some of my footprints, or errors out. What can I do to diagnose my problem?" [792-] --></div>
+<!-- SECTION "gsch2pcb can't find some of my footprints, or errors out. What can I do to diagnose my problem?" [792-1136] -->
+<h2><a name="i_don_t_like_the_default_layer_stack_of_gschem2pcb._how_can_i_change_this" id="i_don_t_like_the_default_layer_stack_of_gschem2pcb._how_can_i_change_this">I don't like the default layer stack of gschem2pcb. How can I change this?</a></h2>
+<div class="level2">
+
+<p>
+Edit $INSTALLDIR/share/gEDA/schemegnet-gsch2pcb.scm to reflect your preferred layer stack. In particular you may have to modify the line that defines the layer groups:
+</p>
+<pre class="code"> (display "Groups(\"1,2,3,s:4,5,6,c:7:8\")\n" port) </pre>
+
+<p>
+ and the layer stack itself:
+</p>
+<pre class="code">(lambda (port)
+ (display "Layer(1 \"bottom\")\n(\n)\n" port)
+ (display "Layer(2 \"bott.-poly.\")\n(\n)\n" port)
+ ...
+ (display "Layer(8 \"lineout\")\n(\n)" port)
+ (display "Layer(9 \"ignored\")\n(\n)\n" port)
+ (display "Layer(10 \"ignored\")\n(\n)" port)
+ (newline port)))</pre>
+
+<p>
+ Note, the last two layers will map to silk on both sides of the board. So you will have to define two more layers than you want for your copper layout.
+</p>
+
+</div>
+<!-- SECTION "I don't like the default layer stack of gschem2pcb. How can I change this?" [1137-] --></div>
</body>
</html>
diff --git a/docs/wiki/geda_faq-gschem.html b/docs/wiki/geda_faq-gschem.html
index 14e00a1..66a7587 100644
--- a/docs/wiki/geda_faq-gschem.html
+++ b/docs/wiki/geda_faq-gschem.html
@@ -6,8 +6,8 @@
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>geda:faq-gschem</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,nofollow" />
-<meta name="date" content="2007-08-14T07:05:51-0400" />
+<meta name="robots" content="index,follow" />
+<meta name="date" content="2007-10-23T05:33:47-0400" />
<meta name="keywords" content="geda,faq-gschem" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -53,14 +53,17 @@
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_promote_an_invisible_symbol_attribute_into_the_schematic" class="toc">How do I promote an invisible symbol attribute into the schematic?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#what_should_i_do_about_power_pins_on_my_symbolsmake_them_visible_explicit_or_invisible_implicit" class="toc">What should I do about power pins on my symbols: Make them visible (explicit) or invisible (implicit)?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#is_there_a_specification_or_manual_for_creating_gschem_symbols_where_is_it" class="toc">Is there a specification or manual for creating gschem symbols? Where is it?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#can_my_local_library_cover_frequently_needed_sub_circuits" class="toc">Can my local library cover frequently needed sub circuits?</a></span></div></li>
</ul>
</li>
<li class="level1"><div class="li"><span class="li"><a href="#gschem_configuration_customization" class="toc">Gschem configuration/customization</a></span></div>
<ul class="toc">
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_configure_my_local_gafrc_to_find_my_local_symbol_directory" class="toc">How do I configure my local gafrc to find my local symbol directory?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#the_library_window_is_cluttered_with_default_symbols._can_i_restrict_to_my_local_lib" class="toc">The library window is cluttered with default symbols. Can I restrict to my local lib?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_change_the_default_size_of_floating_text" class="toc">How can I change the default size of floating text?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_have_a_different_background_color_other_than_black" class="toc">How can I have a different background color other than black?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#each_time_i_start_gschem_the_log_message_window_is_shown._can_i_disable_it" class="toc">Each time I start gschem, the log message window is shown. Can I disable it?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#can_i_get_a_customized_title_block_with_new_schematics" class="toc">Can I get a customized title block with new schematics?</a></span></div></li>
</ul>
</li>
<li class="level1"><div class="li"><span class="li"><a href="#printing_output" class="toc">Printing/Output</a></span></div>
@@ -127,7 +130,7 @@
</p>
<p>
-For folks with older versions of gschem, here are three ways to easily move components with gschem:
+For folks with older versions of gschem, here are three ways to move components within gschem:
</p>
<p>
@@ -169,7 +172,7 @@ One:
</ol>
</div>
-<!-- SECTION "How do I move a component?" [975-2414] -->
+<!-- SECTION "How do I move a component?" [975-2409] -->
<h2><a name="how_do_i_move_components_without_dragging_a_tail_of_connectet_nets" id="how_do_i_move_components_without_dragging_a_tail_of_connectet_nets">How do I move components without dragging a tail of connectet nets?</a></h2>
<div class="level2">
@@ -178,7 +181,7 @@ Type [or] to toggle this behaviour. That is, the â??oâ?? key followed by the â??
</p>
</div>
-<!-- SECTION "How do I move components without dragging a tail of connectet nets?" [2415-2699] -->
+<!-- SECTION "How do I move components without dragging a tail of connectet nets?" [2410-2694] -->
<h2><a name="how_do_i_change_the_size_of_the_text_on_a_symbol" id="how_do_i_change_the_size_of_the_text_on_a_symbol">How do I change the size of the text on a symbol?</a></h2>
<div class="level2">
<ol>
@@ -207,7 +210,7 @@ Type [or] to toggle this behaviour. That is, the â??oâ?? key followed by the â??
</p>
</div>
-<!-- SECTION "How do I change the size of the text on a symbol?" [2700-3490] -->
+<!-- SECTION "How do I change the size of the text on a symbol?" [2695-3485] -->
<h2><a name="how_do_i_unlock_a_locked_component" id="how_do_i_unlock_a_locked_component">How do I unlock a locked component</a></h2>
<div class="level2">
@@ -216,7 +219,7 @@ When a component is locked it cannot be selected with the middle mouse button; h
</p>
</div>
-<!-- SECTION "How do I unlock a locked component" [3491-3904] -->
+<!-- SECTION "How do I unlock a locked component" [3486-3899] -->
<h2><a name="how_can_i_get_refdes_automatically_numbered_when_i_draw_a_schematic" id="how_can_i_get_refdes_automatically_numbered_when_i_draw_a_schematic">How can I get refdes automatically numbered when I draw a schematic?</a></h2>
<div class="level2">
@@ -234,7 +237,7 @@ Please substitute $YOUR_INSTALL_PATH by the path where geda is installed.
</p>
</div>
-<!-- SECTION "How can I get refdes automatically numbered when I draw a schematic?" [3905-4516] -->
+<!-- SECTION "How can I get refdes automatically numbered when I draw a schematic?" [3900-4511] -->
<h2><a name="what_is_a_bus_and_how_do_i_use_it" id="what_is_a_bus_and_how_do_i_use_it">What is a Bus and how do I use it?</a></h2>
<div class="level2">
@@ -247,7 +250,7 @@ Some users have found it helpful to organize their nets by incorporating a bus n
</p>
</div>
-<!-- SECTION "What is a Bus and how do I use it?" [4517-5072] -->
+<!-- SECTION "What is a Bus and how do I use it?" [4512-5067] -->
<h2><a name="how_can_i_change_key_bindings_in_gschem" id="how_can_i_change_key_bindings_in_gschem">How can I change Key Bindings in gschem?</a></h2>
<div class="level2">
@@ -256,7 +259,7 @@ Key accels are determined by configuration files read on start-up. The default k
</p>
</div>
-<!-- SECTION "How can I change Key Bindings in gschem?" [5073-5499] -->
+<!-- SECTION "How can I change Key Bindings in gschem?" [5068-5494] -->
<h2><a name="what_are_the_mouse_bindings_in_gschem" id="what_are_the_mouse_bindings_in_gschem">What are the mouse bindings in gschem?</a></h2>
<div class="level2">
@@ -302,7 +305,7 @@ For more information on these options, please see the <code>${install_prefix}/sh
</p>
</div>
-<!-- SECTION "What are the mouse bindings in gschem?" [5500-6582] -->
+<!-- SECTION "What are the mouse bindings in gschem?" [5495-6577] -->
<h2><a name="can_gschem_do_hierarchical_designs_with_sub_sheets" id="can_gschem_do_hierarchical_designs_with_sub_sheets">Can gschem do hierarchical designs with sub sheets?</a></h2>
<div class="level2">
@@ -319,12 +322,12 @@ To convert a hierarchy to a netlist just call gsch2pcb on the top level schemati
</p>
</div>
-<!-- SECTION "Can gschem do hierarchical designs with sub sheets?" [6583-8320] -->
+<!-- SECTION "Can gschem do hierarchical designs with sub sheets?" [6578-8315] -->
<h1><a name="gschem_symbols" id="gschem_symbols">gschem symbols</a></h1>
<div class="level1">
</div>
-<!-- SECTION "gschem symbols" [8321-8350] -->
+<!-- SECTION "gschem symbols" [8316-8345] -->
<h2><a name="what_s_this_business_about_heavy_vs._light_symbols" id="what_s_this_business_about_heavy_vs._light_symbols">What's this business about heavy vs. light symbols?</a></h2>
<div class="level2">
@@ -349,7 +352,7 @@ GEDA/gaf, as default configured, uses light symbols, although it can be configur
</p>
</div>
-<!-- SECTION "What's this business about heavy vs. light symbols?" [8351-10479] -->
+<!-- SECTION "What's this business about heavy vs. light symbols?" [8346-10474] -->
<h2><a name="i_am_using_a_symbol_out_of_the_library._how_come_it_s_not_aligned_to_the_grid" id="i_am_using_a_symbol_out_of_the_library._how_come_it_s_not_aligned_to_the_grid">I am using a symbol out of the library. How come it's not aligned to the grid?</a></h2>
<div class="level2">
@@ -362,7 +365,7 @@ Yes, the gEDA docs suggest that you use a 100mil grid spacing. But everybody li
</p>
</div>
-<!-- SECTION "I am using a symbol out of the library. How come it's not aligned to the grid?" [10480-11253] -->
+<!-- SECTION "I am using a symbol out of the library. How come it's not aligned to the grid?" [10475-11248] -->
<h2><a name="is_there_an_explicit_no_connect_symbol_that_i_can_should_place_in_the_schematic_to_prevent_gnetlist_from_thinking_i_ve_forgotten_a_connection" id="is_there_an_explicit_no_connect_symbol_that_i_can_should_place_in_the_schematic_to_prevent_gnetlist_from_thinking_i_ve_forgotten_a_connection">Is there an explicit "no connect" symbol that I can/should place in the schematic to prevent gnetlist from thinking I've forgotten a connection?</a></h2>
<div class="level2">
@@ -379,7 +382,7 @@ If you want an entire symbol to be graphical (no elec. connections) , add a â??g
</p>
</div>
-<!-- SECTION "Is there an explicit no connect symbol that I can/should place in the schematic to prevent gnetlist from thinking I've forgotten a connection?" [11254-11823] -->
+<!-- SECTION "Is there an explicit no connect symbol that I can/should place in the schematic to prevent gnetlist from thinking I've forgotten a connection?" [11249-11818] -->
<h2><a name="how_do_i_promote_an_invisible_symbol_attribute_into_the_schematic" id="how_do_i_promote_an_invisible_symbol_attribute_into_the_schematic">How do I promote an invisible symbol attribute into the schematic?</a></h2>
<div class="level2">
@@ -400,7 +403,7 @@ and you will get all the attributes promoted. The â??keep-invisibleâ?? keyword w
</p>
</div>
-<!-- SECTION "How do I promote an invisible symbol attribute into the schematic?" [11824-12443] -->
+<!-- SECTION "How do I promote an invisible symbol attribute into the schematic?" [11819-12438] -->
<h2><a name="what_should_i_do_about_power_pins_on_my_symbolsmake_them_visible_explicit_or_invisible_implicit" id="what_should_i_do_about_power_pins_on_my_symbolsmake_them_visible_explicit_or_invisible_implicit">What should I do about power pins on my symbols: Make them visible (explicit) or invisible (implicit)?</a></h2>
<div class="level2">
@@ -429,7 +432,7 @@ That said, it may still be useful to detach the power pins from the functional p
</p>
</div>
-<!-- SECTION "What should I do about power pins on my symbols: Make them visible (explicit) or invisible (implicit)?" [12444-14700] -->
+<!-- SECTION "What should I do about power pins on my symbols: Make them visible (explicit) or invisible (implicit)?" [12439-14695] -->
<h2><a name="is_there_a_specification_or_manual_for_creating_gschem_symbols_where_is_it" id="is_there_a_specification_or_manual_for_creating_gschem_symbols_where_is_it">Is there a specification or manual for creating gschem symbols? Where is it?</a></h2>
<div class="level2">
@@ -438,7 +441,28 @@ Yes. It is the <a href="geda_scg.html" class="wikilink1" title="geda:scg">Symbol
</p>
</div>
-<!-- SECTION "Is there a specification or manual for creating gschem symbols? Where is it?" [14701-14841] -->
+<!-- SECTION "Is there a specification or manual for creating gschem symbols? Where is it?" [14696-14836] -->
+<h2><a name="can_my_local_library_cover_frequently_needed_sub_circuits" id="can_my_local_library_cover_frequently_needed_sub_circuits">Can my local library cover frequently needed sub circuits?</a></h2>
+<div class="level2">
+
+<p>
+Yes. Symbols can contain symbols and nets.
+</p>
+<ol>
+<li class="level1"><div class="li"> Copy the subcircuit to a fresh sheet. (unlock and remove the default title block as you wonâ??t need it)</div>
+</li>
+<li class="level1"><div class="li"> The values of refdes attributes should end with "?", to allow to auto number them later. </div>
+</li>
+<li class="level1"><div class="li"> Move the sub circuit to the lower left of the available space. (You can use symbol-translate from the edit menu)</div>
+</li>
+<li class="level1"><div class="li"> Save the sub circuit as a *.sym file in your local library. </div>
+</li>
+<li class="level1"><div class="li"> Choose â??Include component as individual objectsâ?? when selecting this complex symbol for your actual schematic. The whole sub circuit will be pasted to your sheet. Be sure to switch back to the default mode for inclusion of ordinary symbols. </div>
+</li>
+</ol>
+
+</div>
+<!-- SECTION "Can my local library cover frequently needed sub circuits?" [14837-15582] -->
<h1><a name="gschem_configuration_customization" id="gschem_configuration_customization">Gschem configuration/customization</a></h1>
<div class="level1">
@@ -447,7 +471,7 @@ Gschem is configurable in more ways than can be describe here. Look at â??system
</p>
</div>
-<!-- SECTION "Gschem configuration/customization" [14842-15019] -->
+<!-- SECTION "Gschem configuration/customization" [15583-15760] -->
<h2><a name="how_do_i_configure_my_local_gafrc_to_find_my_local_symbol_directory" id="how_do_i_configure_my_local_gafrc_to_find_my_local_symbol_directory">How do I configure my local gafrc to find my local symbol directory?</a></h2>
<div class="level2">
<ol>
@@ -483,7 +507,26 @@ gschem myschematic.sch</pre>
</ul>
</div>
-<!-- SECTION "How do I configure my local gafrc to find my local symbol directory?" [15020-16273] -->
+<!-- SECTION "How do I configure my local gafrc to find my local symbol directory?" [15761-17014] -->
+<h2><a name="the_library_window_is_cluttered_with_default_symbols._can_i_restrict_to_my_local_lib" id="the_library_window_is_cluttered_with_default_symbols._can_i_restrict_to_my_local_lib">The library window is cluttered with default symbols. Can I restrict to my local lib?</a></h2>
+<div class="level2">
+
+<p>
+Put a localized version of the following lines in a gafrc.
+</p>
+<pre class="code">
+; empty the library path and populate it with local paths
+(reset-component-library)
+(component-library "/foo/localgedalib1")
+(component-library "/bar/foo/localgedalib2")
+</pre>
+
+<p>
+ You have to add each and every dir of your local library. Subdirs are not automatically reckognized by gschem and gsch2pcb. Its a good idea to place this gafrc in your projects dir. That way, if you start gschem from some other place, you still get the system symbols shown. This also allows to configure special symbol libs for specific projects.
+</p>
+
+</div>
+<!-- SECTION "The library window is cluttered with default symbols. Can I restrict to my local lib?" [17015-17706] -->
<h2><a name="how_can_i_change_the_default_size_of_floating_text" id="how_can_i_change_the_default_size_of_floating_text">How can I change the default size of floating text?</a></h2>
<div class="level2">
@@ -497,7 +540,7 @@ Put
</p>
</div>
-<!-- SECTION "How can I change the default size of floating text?" [16274-16432] -->
+<!-- SECTION "How can I change the default size of floating text?" [17707-17865] -->
<h2><a name="how_can_i_have_a_different_background_color_other_than_black" id="how_can_i_have_a_different_background_color_other_than_black">How can I have a different background color other than black?</a></h2>
<div class="level2">
@@ -515,11 +558,16 @@ Edit the system-gschemrc file and near the top you will find lines like:
;(load (string-append gedadatarc "/gschem-lightbg")) ; light background</pre>
<p>
-Comment out the <strong><code>darkbg</code></strong> line (with a ;) and comment in the <strong><code>lightbg</code></strong> line. This will give you a light background instead of a black background. It also adjust all the other colors to be compatible with a light background.
+Comment out the <strong><code>darkbg</code></strong> line (with a ;) and comment in the <strong><code>lightbg</code></strong> line. This will give you a light background instead of a black background. It also adjust all the other colors to be compatible with a light background.
+</p>
+
+<p>
+Note, starting with version 1.2 of gschem the syntax of this line changed to
</p>
+<pre class="code">(load (build-path geda-rc-path "gschem-lightbg")) ; light background</pre>
<p>
-If you want more control over the colors, please edit <strong><code>${prefix}/share/gEDA/gschem-darkbg</code></strong> or <strong><code>${prefix}/share/gEDA/gschem-lightbg</code></strong> or create your own file and load it in the <strong><code>system-gschemrc</code></strong> file.
+ If you want more control over the colors, please edit <strong><code>${prefix}/share/gEDA/gschem-darkbg</code></strong> or <strong><code>${prefix}/share/gEDA/gschem-lightbg</code></strong> or create your own file and load it in the <strong><code>system-gschemrc</code></strong> file.
</p>
<p>
@@ -527,7 +575,7 @@ A dark background is preferred by many users.
</p>
</div>
-<!-- SECTION "How can I have a different background color other than black?" [16433-17468] -->
+<!-- SECTION "How can I have a different background color other than black?" [17866-19064] -->
<h2><a name="each_time_i_start_gschem_the_log_message_window_is_shown._can_i_disable_it" id="each_time_i_start_gschem_the_log_message_window_is_shown._can_i_disable_it">Each time I start gschem, the log message window is shown. Can I disable it?</a></h2>
<div class="level2">
@@ -552,12 +600,26 @@ Comment out the <strong><code>startup</code></strong> line (with a ;) and commen
<pre class="code">(log-window "later")</pre>
</div>
-<!-- SECTION "Each time I start gschem, the log message window is shown. Can I disable it?" [17469-18131] -->
+<!-- SECTION "Each time I start gschem, the log message window is shown. Can I disable it?" [19065-19727] -->
+<h2><a name="can_i_get_a_customized_title_block_with_new_schematics" id="can_i_get_a_customized_title_block_with_new_schematics">Can I get a customized title block with new schematics?</a></h2>
+<div class="level2">
+
+<p>
+Put the following line into your gschemrc file:
+</p>
+<pre class="code">(define default-titleblock "title-A3.sym")</pre>
+
+<p>
+ Replace â??title-A3.symâ?? with the file name of your favorite title block symbol.
+</p>
+
+</div>
+<!-- SECTION "Can I get a customized title block with new schematics?" [19728-19980] -->
<h1><a name="printing_output" id="printing_output">Printing/Output</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Printing/Output" [18132-18161] -->
+<!-- SECTION "Printing/Output" [19981-20010] -->
<h2><a name="how_do_i_print_schematics_from_the_command_line" id="how_do_i_print_schematics_from_the_command_line">How do I print schematics from the command line?</a></h2>
<div class="level2">
@@ -588,7 +650,7 @@ do
done</pre>
</div>
-<!-- SECTION "How do I print schematics from the command line?" [18162-19159] -->
+<!-- SECTION "How do I print schematics from the command line?" [20011-21008] -->
<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">
@@ -617,7 +679,7 @@ The 255 255 255 are the RGB components for the background color of the <acronym
</p>
</div>
-<!-- SECTION "How can I get color postscript/PNG output?" [19160-20291] -->
+<!-- SECTION "How can I get color postscript/PNG output?" [21009-22140] -->
<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">
@@ -632,7 +694,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?" [20292-20657] -->
+<!-- SECTION "How can I get black and white postscript/PNG output?" [22141-22506] -->
<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>
@@ -656,7 +718,7 @@ For black and white <acronym title="Portable Network Graphics">PNG</acronym> ima
\end{document}</pre>
</div>
-<!-- SECTION "How can I insert schematics into my LaTex document?" [20658-21226] -->
+<!-- SECTION "How can I insert schematics into my LaTex document?" [22507-23075] -->
<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">
@@ -665,12 +727,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?" [21227-21570] -->
+<!-- SECTION "How can I split Postscript output over multiple pages?" [23076-23419] -->
<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" [21571-21623] -->
+<!-- SECTION "Gschem installation/run-time problems" [23420-23472] -->
<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">
@@ -693,7 +755,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?" [21624-22278] -->
+<!-- SECTION "Gschem segfaults when I delete components on FC5 (and other Linux distributions)! Is there a work-around?" [23473-24127] -->
<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">
@@ -731,7 +793,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?" [22279-24202] -->
+<!-- SECTION "After installation gschem does not work!? What could be wrong?" [24128-26051] -->
<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">
@@ -763,7 +825,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?" [24203-25006] -->
+<!-- SECTION "Add Components offers no symbols! What can I do about it?" [26052-26855] -->
<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">
@@ -782,6 +844,6 @@ 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.'" [25007-] --></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.'" [26856-] --></div>
</body>
</html>
diff --git a/docs/wiki/geda_faq-pcb.html b/docs/wiki/geda_faq-pcb.html
index 23a0f43..0aac218 100644
--- a/docs/wiki/geda_faq-pcb.html
+++ b/docs/wiki/geda_faq-pcb.html
@@ -93,7 +93,7 @@ No.
<div class="level3">
<p>
-No. Lines on a layer with layer name <code>outline</code> will be interpreted as physical edges of the board. Also see <a href="geda_pcb_tips.html" class="wikilink1" title="geda:pcb_tips">this note</a> in the more comprehensive <a href="geda_pcb_tips.html" class="wikilink1" title="geda:pcb_tips">pcb_tips</a>
+No. Lines on a layer with layer name <code>outline</code> will be interpreted as physical edges of the board. Also see <a href="http://geda.seul.org/wiki/geda:pcb_tips#how_do_i_make_a_board_outline_to_go_with_my_gerbers_to_the_board_maker"; class="wikilink1" title="geda:pcb_tips">this note</a> in the more comprehensive <a href="http://geda.seul.org/wiki/geda:pcb_tips"; class="wikilink1" title="geda:pcb_tips">pcb_tips</a>
</p>
</div>
@@ -121,7 +121,7 @@ Generally, you start with a schematic, run gsch2pcb to generate the netlist. See
</p>
<p>
-Then you … Hey, did you know about the pcb manual, the <a href="geda_pcb_tips.html" class="wikilink1" title="geda:pcb_tips">pcb_tips</a>, and the <a href="geda_pcb-quick_reference.html" class="wikilink1" title="geda:pcb-quick_reference">pcb-quick_reference</a>?
+Then you … Hey, did you know about the pcb manual, the <a href="http://geda.seul.org/wiki/geda:pcb_tips"; class="wikilink1" title="geda:pcb_tips">pcb_tips</a>, and the <a href="http://geda.seul.org/wiki/geda:pcb-quick_reference"; class="wikilink1" title="geda:pcb-quick_reference">pcb-quick_reference</a>?
</p>
</div>
diff --git a/docs/wiki/geda_faq.html b/docs/wiki/geda_faq.html
index 00b4d35..0c4d12c 100644
--- a/docs/wiki/geda_faq.html
+++ b/docs/wiki/geda_faq.html
@@ -231,7 +231,7 @@ This is ultimately a matter of religion. Iâ??ll summarize some of the pros and c
</li>
<li class="level1"><div class="li"> Different programs have different UI conventions (i.e. menu organization is different, keyboard or mouse bindings are different). This can be uncomfortable to those who arenâ??t familiar with the programs.</div>
</li>
-<li class="level1"><div class="li"> Since no assumptions are made about the design flow, schematic symbols are necessarily <a href="http://geda.seul.org/wiki/geda:faq-gschem#what_s_this_business_about_heavy_vs._light_symbols"; class="wikilink1" title="geda:faq-gschem">light</a>. This forces the user to spend more time attaching e.g. footprint attributes to his design. Moreover, the user must spend more time actually researching which footprints to use. However, a good suite (like the gEDA suite) will offer multiple methods to perform this task (e.g. gattrib, <acronym title="Practical Extraction and Report Language">Perl</acronym> scripts to populate footprints, etc.).</div>
+<li class="level1"><div class="li"> Since no assumptions are made about the design flow, schematic symbols are necessarily <a href="geda_faq-gschem.html" class="wikilink1" title="geda:faq-gschem">light</a>. This forces the user to spend more time attaching e.g. footprint attributes to his design. Moreover, the user must spend more time actually researching which footprints to use. However, a good suite (like the gEDA suite) will offer multiple methods to perform this task (e.g. gattrib, <acronym title="Practical Extraction and Report Language">Perl</acronym> scripts to populate footprints, etc.).</div>
</li>
<li class="level1"><div class="li"> Some developers are more energetic than others, or have more free time. Therefore, some programs in a suite will be more developed (and less buggy) than others. Unfortunately, a single buggy program in a suite can unfairly taint a new userâ??s perception of the entire suite.</div>
</li>
diff --git a/docs/wiki/geda_fedora_rpm_installation.html b/docs/wiki/geda_fedora_rpm_installation.html
index bf30cfc..e3785e0 100644
--- a/docs/wiki/geda_fedora_rpm_installation.html
+++ b/docs/wiki/geda_fedora_rpm_installation.html
@@ -7,7 +7,7 @@
<title>geda:fedora_rpm_installation</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-07-14T16:52:08-0400" />
+<meta name="date" content="2007-08-24T19:50:12-0400" />
<meta name="keywords" content="geda,fedora_rpm_installation" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -111,7 +111,7 @@ under the following architectures:
</p>
<p>
-<code><strong>yum install geda-gschem geda-docs geda-examples geda-gattrib geda-gsymcheck geda-gnetlist geda-utils pcb gerbv</strong></code>
+<code><strong>yum install geda\* pcb gerbv</strong></code>
</p>
<p>
@@ -141,7 +141,7 @@ One can follow up
</p>
</div>
-<!-- SECTION "The easiest way" [871-1933] -->
+<!-- SECTION "The easiest way" [871-1851] -->
<h3><a name="compile_it_yourself" id="compile_it_yourself">Compile it yourself</a></h3>
<div class="level3">
@@ -190,7 +190,7 @@ The recommended procedure is to compile and install (one by one):
</p>
</div>
-<!-- SECTION "Compile it yourself" [1934-2588] -->
+<!-- SECTION "Compile it yourself" [1852-2506] -->
<h3><a name="rebuild_your_own_rpms" id="rebuild_your_own_rpms">Rebuild your own rpms</a></h3>
<div class="level3">
@@ -312,6 +312,6 @@ The successfully build RPMS will be found in the folders of ~/rpmbuild/RPMS/.
</p>
</div>
-<!-- SECTION "Rebuild your own rpms" [2589-] --></div>
+<!-- SECTION "Rebuild your own rpms" [2507-] --></div>
</body>
</html>
diff --git a/docs/wiki/geda_file_format_spec.html b/docs/wiki/geda_file_format_spec.html
index ab0404e..d73c7e7 100644
--- a/docs/wiki/geda_file_format_spec.html
+++ b/docs/wiki/geda_file_format_spec.html
@@ -7,7 +7,7 @@
<title>geda:file_format_spec</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-07-08T20:51:33-0400" />
+<meta name="date" content="2007-09-02T17:22:32-0400" />
<meta name="keywords" content="geda,file_format_spec" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -154,7 +154,7 @@ A schematic/symbol file for gEDA/gaf consists of:
</p>
</div>
-<!-- SECTION "Object types" [2241-3508] -->
+<!-- SECTION "Object types" [2241-3509] -->
<h3><a name="version" id="version">version</a></h3>
<div class="level3">
@@ -195,9 +195,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</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</div>
</li>
-<li class="level1"><div class="li"> Stable versions include: 20070526, 20070626</div>
+<li class="level1"><div class="li"> Stable versions include: 20070526, 20070626, 20070902</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>
@@ -212,7 +212,7 @@ Valid in: Schematic and Symbol files<br/>
<pre class="code">v 20040111 1</pre>
</div>
-<!-- SECTION "version" [3509-5357] -->
+<!-- SECTION "version" [3510-5378] -->
<h3><a name="line" id="line">line</a></h3>
<div class="level3">
@@ -300,7 +300,7 @@ A line segment from (23000, 69000) to (28000, 69000) with color index 3, 40 mils
</p>
</div>
-<!-- SECTION "line" [5358-6592] -->
+<!-- SECTION "line" [5379-6613] -->
<h3><a name="picture" id="picture">picture</a></h3>
<div class="level3">
@@ -410,7 +410,7 @@ A picture object with the lower left corner at (16900, 35800). The width of the
</p>
</div>
-<!-- SECTION "picture" [6593-9386] -->
+<!-- SECTION "picture" [6614-9407] -->
<h3><a name="box" id="box">box</a></h3>
<div class="level3">
@@ -539,7 +539,7 @@ A box with the lower left hand corner at (33000, 67300) and a width and height o
</p>
</div>
-<!-- SECTION "box" [9387-11593] -->
+<!-- SECTION "box" [9408-11614] -->
<h3><a name="circle" id="circle">circle</a></h3>
<div class="level3">
@@ -655,7 +655,7 @@ A circle with the center at (38000, 67000) and a radius of 900 mils, color index
</p>
</div>
-<!-- SECTION "circle" [11594-13719] -->
+<!-- SECTION "circle" [11615-13740] -->
<h3><a name="arc" id="arc">arc</a></h3>
<div class="level3">
@@ -751,7 +751,7 @@ dashlength dashspace</code></strong>
</p>
</div>
-<!-- SECTION "arc" [13720-15235] -->
+<!-- SECTION "arc" [13741-15256] -->
<h3><a name="text" id="text">text</a></h3>
<div class="level3">
@@ -885,7 +885,7 @@ This is a similar text object as the above example, however here there are five
</p>
</div>
-<!-- SECTION "text" [15236-17889] -->
+<!-- SECTION "text" [15257-17910] -->
<h3><a name="net" id="net">net</a></h3>
<div class="level3">
@@ -934,7 +934,7 @@ A net segment from (12700, 29400) to (32900, 29400) with color index 4.
</p>
</div>
-<!-- SECTION "net" [17890-18415] -->
+<!-- SECTION "net" [17911-18436] -->
<h3><a name="bus" id="bus">bus</a></h3>
<div class="level3">
@@ -990,7 +990,7 @@ A bus segment from (27300, 37400) to (27300, 35300) with color index 3 and no ne
</p>
</div>
-<!-- SECTION "bus" [18416-19347] -->
+<!-- SECTION "bus" [18437-19368] -->
<h3><a name="pin" id="pin">pin</a></h3>
<div class="level3">
@@ -1057,7 +1057,7 @@ A pin from (0, 200) to (200, 200) with color index 1, a regular pin, and the fir
</p>
</div>
-<!-- SECTION "pin" [19348-20344] -->
+<!-- SECTION "pin" [19369-20365] -->
<h3><a name="component" id="component">component</a></h3>
<div class="level3">
@@ -1119,7 +1119,7 @@ A component whoâ??s origin is at (18600,19900), is selectable, not rotated, not
</p>
</div>
-<!-- SECTION "component" [20345-21348] -->
+<!-- SECTION "component" [20366-21369] -->
<h3><a name="font" id="font">font</a></h3>
<div class="level3">
@@ -1162,7 +1162,7 @@ The above font definition is for the space character.
</p>
</div>
-<!-- SECTION "font" [21349-21869] -->
+<!-- SECTION "font" [21370-21890] -->
<h2><a name="colors" id="colors">Colors</a></h2>
<div class="level2">
@@ -1231,7 +1231,7 @@ In the gEDA/gaf schematic and symbol file format colors are specified via an int
</p>
</div>
-<!-- SECTION "Colors" [21870-22741] -->
+<!-- SECTION "Colors" [21891-22762] -->
<h2><a name="attributes" id="attributes">Attributes</a></h2>
<div class="level2">
@@ -1253,7 +1253,7 @@ The object is a pin which has an attribute pinnumber=3 and pinseq=3 (name=value)
</p>
</div>
-<!-- SECTION "Attributes" [22742-23729] -->
+<!-- SECTION "Attributes" [22763-23750] -->
<h2><a name="embedded_components" id="embedded_components">Embedded Components</a></h2>
<div class="level2">
@@ -1272,7 +1272,7 @@ In the example above, <strong>555-1.sym</strong> is the component. The EMBEDDED
</p>
</div>
-<!-- SECTION "Embedded Components" [23730-24489] -->
+<!-- SECTION "Embedded Components" [23751-24510] -->
<h2><a name="document_revision_history" id="document_revision_history">Document Revision History</a></h2>
<div class="level2">
<table class="inline">
@@ -1291,6 +1291,6 @@ In the example above, <strong>555-1.sym</strong> is the component. The EMBEDDED
</table>
</div>
-<!-- SECTION "Document Revision History" [24490-] --></div>
+<!-- SECTION "Document Revision History" [24511-] --></div>
</body>
</html>
diff --git a/docs/wiki/geda_glossary.html b/docs/wiki/geda_glossary.html
index 6eb4317..b533c97 100644
--- a/docs/wiki/geda_glossary.html
+++ b/docs/wiki/geda_glossary.html
@@ -7,7 +7,7 @@
<title>geda:glossary</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:26-0400" />
+<meta name="date" content="2007-10-29T17:37:15-0400" />
<meta name="keywords" content="geda,glossary" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -29,7 +29,7 @@
<div class="level1">
<p>
- The design of electronics involves a host of specific terms. Some words have a meaning that only vaguely resembles the use in everyday life. This glossary aims to be a dictionary of terms specific to the gEDA suite, as well as to the larger world of CAD for electronics. Unfortunately there is no universal naming scheme for concepts in the area of electronic design. The glossary will give hints on how things are called in other design suites.
+ The design of electronics involves a host of specific terms. Some words have a meaning that only vaguely resembles the use in everyday life. This glossary aims to be a dictionary of terms specific to the gEDA suite, as well as to the larger world of CAD for electronics. Unfortunately, there is no universal naming scheme for concepts in the area of electronic design. The glossary will give hints on how things are called in other design suites.
</p>
<p>
@@ -38,11 +38,17 @@
<ul>
<li class="level1"><div class="li"> <strong>annular ring</strong>: The annular ring, sometimes also called <strong>annulus</strong>, is a diameter of copper that needs to be placed arround metalized holes like pads and vias. The minimum size of the annular ring is specified by the pcb-fab. A common requirements is 16 mil larger than the hole.</div>
</li>
+<li class="level1"><div class="li"> <strong>dead copper</strong>: A part of the copper layer which is not connected to any net defined in the netlist. By definition, this may be any object pcb defines. However, the term commonly refers to unconnected snippets of a polygon which is devided by a track. </div>
+</li>
<li class="level1"><div class="li"> <strong>design flow</strong>: The order or stages through which you take your design as you progress from initial concept, through schematic capture, attribute attachment, netlisting, and layout. One typically uses different tools to accomplish different tasks during the design process. The gEDA Suite uses entirely separate programs for different stages of the flow; each tool in the suite reads the output file produced by the previous tool, and writes a file to be read by the next tool in the flow. The gEDA design flow for designing a PCB is illustrated <a href="http://geda.seul.org/dokuwiki/doku.php?id=geda:usage#what_does_the_design_flow_in_geda_look_like"; class="urlextern" title="http://geda.seul.org/dokuwiki/doku.php?id=geda:usage#what_does_the_design_flow_in_geda_look_like"; rel="nofollow">here</a>. Note that the design flow for different tasks might look different. For example, if your goal is to simulate your circuit, you will use a different flow than that shown in the link above. Finally, other â?? usually simpler â?? PCB design tools use a monolithic approach in which one single program (albeit with different edit modes) is used for the entire design. Which approach is better usually is a matter of personal religion.</div>
</li>
<li class="level1"><div class="li"> <strong>footprint</strong>: The pattern of metal and silkscreen which defines where you place a component on a PCB. Footprints are the placed by the user onto the PC board during the â??placementâ?? phase of PCB layout (using e.g. the open-source tool PCB). A footprint is also sometimes called called a â??decalâ?? (PADS), or a â??land-patternâ??.</div>
</li>
-<li class="level1"><div class="li"> <strong>net</strong>: A net is the representation of a wire, or electrical connection in your schematic diagram. It is basically a line connecting two symbol pins. The term â??netâ?? is also sometimes used loosely to talk about an electical connection (via a wire or PCB trace) in a real circuit. Some schematic capture tools call a net a â??wireâ??.</div>
+<li class="level1"><div class="li"> <strong>GTK-HID</strong>: The GTK version of the pcb user interface. â??HIDâ?? is an acronym for â??human interface deviceâ??. As the name sugests, GTK-HID uses the GTK+ widgetset and tries to comply with GTK usability standards.This is the default <acronym title="Graphical User Interface">GUI</acronym> of pcb. Menu and keyboard configuration is read from gpcb-menu.res. (See Lesstif-HID for an alternative)</div>
+</li>
+<li class="level1"><div class="li"> <strong>Lesstif-HID</strong>: The Lesstif version of the pcb user interface. It uses the Lesstif widgetset, which is the open source version of Motif. Menu and keyboard configuration read from <code>pcb-menu.res</code> try to comply with Lesstif usability standards. If you want to give this interface a try, you have to give the option <code>–with-gui=lesstif</code> at compile time.</div>
+</li>
+<li class="level1"><div class="li"> <strong>net</strong>: A net is the representation of a wire, or electrical connection in your schematic diagram. It is basically a line connecting two symbol pins. The term â??netâ?? is also sometimes used loosely to talk about an electrical connection (via a wire or PCB trace) in a real circuit. Some schematic capture tools call a net a â??wireâ??.</div>
</li>
<li class="level1"><div class="li"> <strong>netlist</strong>: A netlist is an text file representation of your circuit which emphasizes the connections between the different circuit elements, perhaps independently of the physical packages constituting the actual components in the circuit.</div>
</li>
@@ -54,7 +60,7 @@
<ol>
<li class="level2"><div class="li"> An abbreviation of â??printed circuit boardâ??. This is the actual hardware that is used to connect electronic components. It is also sometimes called a â??printed wiring boardâ?? (PWB), although this usage may be dying out.</div>
</li>
-<li class="level2"><div class="li"> A powerfull, open-source tool used to design the layout of a printed circuit board. The output of the gaf tools can be used as an input to pcb.(<a href="http://pcb.sourceforge.net/index.html"; class="urlextern" title="http://pcb.sourceforge.net/index.html"; rel="nofollow">homepage of pcb</a>)</div>
+<li class="level2"><div class="li"> A powerful, open-source tool used to design the layout of a printed circuit board. The output of the gaf tools can be used as an input to pcb.(<a href="http://pcb.sourceforge.net/index.html"; class="urlextern" title="http://pcb.sourceforge.net/index.html"; rel="nofollow">homepage of pcb</a>)</div>
</li>
</ol>
</li>
@@ -62,10 +68,18 @@
</li>
<li class="level1"><div class="li"> <strong>refdes</strong>: Short for â??reference designatorâ??. The unique designator (or name) of a component. The gEDA tools rely on the refdefs to organize the components internally. Therefore, for successful creation of a printed circuit board every component has to be linked with a refdes. Usually, the refdes consists of a few upper case letters and a digit. Examples: R1, R2, U115, CONN3. (Protel: â??Designatorâ??)</div>
</li>
+<li class="level1"><div class="li"> <strong>silkscreen</strong>: This is the layer that defines the text and graphics printed on the pcb board. It usually contains the name of the board, outlines of the components and possibly their values or refdes. The origin of the name is the silk traditionally used during the print process. </div>
+</li>
<li class="level1"><div class="li"> <strong>slot</strong>: Some components contain multiple, identical devices inside a signal package. The IOs for each component are mapped to different pin sets on the package. A classic example is the TTL 7400 quad nand gate. Gschem (like other schematic capture packages) handles this type of component by allowing you to draw four separate nand gate symbols, and then selecting which <strong>slot</strong> each symbol should have by attaching a slot attribute to the symbol. In the example of the 7400 quad nand, you would select <strong><code>slot=1</code></strong> for the first appearance of the symbol, slot=2 for the second appearance, and so on. Note that in gschem you need to attach power nets to a slotted component only <strong>once</strong>. (Other schematic capture programs like Orcad require you to attach common nets â?? like power nets â?? on each instantiation of the slotted symbol.)</div>
</li>
+<li class="level1"><div class="li"> <strong>solder layer</strong>: This is the side of the board where traditional, thru hole components are soldered. (Protel: â??Bottom Layerâ??)</div>
+</li>
<li class="level1"><div class="li"> <strong>symbol</strong>: A symbol is the representation of a particular component in your schematic diagram. The classic examples are squiggley lines for resistors (in US usage anyway), or a triangle for an op-amp. Using a schematic capture program (e.g. gschem) you place symbols on your board, and then wire them up to create a representation of your circuit.</div>
</li>
+<li class="level1"><div class="li"> <strong>component layer</strong>: This is the side of the board where traditional, thru hole components sit, Usually the top side of the board. (Protel: â??Top Layerâ??)</div>
+</li>
+<li class="level1"><div class="li"> <strong>thermal</strong>: A thermal is a way to connect a via with a copper plane through narrow bridges. The aim is to connect electrically, but provide enough thermal resistance to allow for convenient soldering. There is a special mode in pcb to convert the annular ring of vias into thermals. </div>
+</li>
<li class="level1"><div class="li"> <strong>via</strong>: A via is a metalized hole that is meant to electrically connect different layers of the pcb. Usually, vias are as small as possible to save valuable real estate on the pcb.</div>
</li>
</ul>
diff --git a/docs/wiki/geda_gsch2pcb_tutorial.html b/docs/wiki/geda_gsch2pcb_tutorial.html
index 49135e3..2c36f64 100644
--- a/docs/wiki/geda_gsch2pcb_tutorial.html
+++ b/docs/wiki/geda_gsch2pcb_tutorial.html
@@ -179,7 +179,7 @@ output-name board
<div class="level3">
<p>
- If you are using gschem for the first time, try stepping through this simple <a href="http://geda.seul.org/wiki/geda:gschem_warmup"; class="wikilink1" title="geda:gschem_warmup">gschem warmup</a>.
+ If you are using gschem for the first time, try stepping through this simple <a href="geda_gschem_warmup.html" class="wikilink1" title="geda:gschem_warmup">gschem warmup</a>.
</p>
<p>
@@ -633,7 +633,7 @@ Pin(0 0 70 20 70 42 "" "1" 0x00000101)
</pre>
<p>
- Possibly youâ??ve noticed, but there are some things not right about the <strong>myproject1</strong> example. For one thing, silk layer lines are overlapping solder pads on some of the elements, and for another, the transistor is backwards on the layout! You otherwise shouldnâ??t have a problem like this when working with gschem and PCB, but transistor pin numbering can be confusing. If you will be using transistors in your designs, hereâ??s a description of my approach to making sure my gschem transistor symbol pin numbering is coordinated with PCB element pin numbers: <a href="http://geda.seul.org/wiki/geda:transistor_guide"; class="wikilink1" title="geda:transistor_guide">transistor guide.</a>
+ Possibly youâ??ve noticed, but there are some things not right about the <strong>myproject1</strong> example. For one thing, silk layer lines are overlapping solder pads on some of the elements, and for another, the transistor is backwards on the layout! You otherwise shouldnâ??t have a problem like this when working with gschem and PCB, but transistor pin numbering can be confusing. If you will be using transistors in your designs, hereâ??s a description of my approach to making sure my gschem transistor symbol pin numbering is coordinated with PCB element pin numbers: <a href="geda_transistor_guide.html" class="wikilink1" title="geda:transistor_guide">transistor guide.</a>
</p>
<p>
diff --git a/docs/wiki/geda_guile_scripting.html b/docs/wiki/geda_guile_scripting.html
new file mode 100644
index 0000000..df3e372
--- /dev/null
+++ b/docs/wiki/geda_guile_scripting.html
@@ -0,0 +1,236 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en"
+ lang="en" dir="ltr">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+ <title>geda:guile_scripting</title>
+<meta name="generator" content="DokuWiki Release rc2007-05-24" />
+<meta name="robots" content="index,follow" />
+<meta name="date" content="2007-12-20T12:38:57-0500" />
+<meta name="keywords" content="geda,guile_scripting" />
+<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
+<link rel="start" href="http://geda.seul.org/wiki/"; />
+<link rel="contents" href="http://geda.seul.org/wiki/geda:guile_scripting?do=index"; title="Index" />
+<link rel="alternate" type="application/rss+xml" title="Recent Changes" href="http://geda.seul.org/wiki/feed.php"; />
+<link rel="alternate" type="application/rss+xml" title="Current Namespace" href="http://geda.seul.org/wiki/feed.php?mode=list&ns=geda"; />
+<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:guile_scripting"; />
+<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:guile_scripting"; />
+<link rel="stylesheet" media="all" type="text/css" href="lib/exe/css" />
+<link rel="stylesheet" media="screen" type="text/css" href="lib/exe/001css" />
+<link rel="stylesheet" media="print" type="text/css" href="lib/exe/002css" />
+</head>
+<body>
+<div class="dokuwiki export">
+<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="#guile_scripting_reference" class="toc">Guile scripting reference</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="#libgeda_geda.scm" class="toc">libgeda geda.scm</a></span></div></li></ul>
+</li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h2><a name="guile_scripting_reference" id="guile_scripting_reference">Guile scripting reference</a></h2>
+<div class="level2">
+
+</div>
+<!-- SECTION "Guile scripting reference" [1-39] -->
+<h3><a name="libgeda_c_library" id="libgeda_c_library">libgeda C library</a></h3>
+<div class="level3">
+
+<p>
+ libgeda defines a number of low-level functions in C for configuring its behaviour and manipulating features such as the component and subcircuit libraries.
+</p>
+
+</div>
+
+<h4><a name="types" id="types">Types</a></h4>
+<div class="level4">
+<ul>
+<li class="level1"><div class="li"> attribute</div>
+</li>
+<li class="level1"><div class="li"> object</div>
+</li>
+<li class="level1"><div class="li"> page</div>
+</li>
+</ul>
+
+</div>
+
+<h4><a name="variables" id="variables">Variables</a></h4>
+<div class="level4">
+
+<p>
+ Basic configuration (defined by libgeda, read-only)
+</p>
+<ul>
+<li class="level1"><div class="li"> path-sep</div>
+</li>
+<li class="level1"><div class="li"> geda-rc-path</div>
+</li>
+<li class="level1"><div class="li"> geda-data-path</div>
+</li>
+</ul>
+
+<p>
+ Object type identifiers (defined by libgeda, read-only)
+</p>
+<ul>
+<li class="level1"><div class="li"> OBJ_LINE</div>
+</li>
+<li class="level1"><div class="li"> OBJ_BOX</div>
+</li>
+<li class="level1"><div class="li"> OBJ_PICTURE</div>
+</li>
+<li class="level1"><div class="li"> OBJ_CIRCLE</div>
+</li>
+<li class="level1"><div class="li"> OBJ_NET</div>
+</li>
+<li class="level1"><div class="li"> OBJ_BUS</div>
+</li>
+<li class="level1"><div class="li"> OBJ_COMPLEX</div>
+</li>
+<li class="level1"><div class="li"> OBJ_TEXT</div>
+</li>
+<li class="level1"><div class="li"> OBJ_<acronym title="Personal Identification Number">PIN</acronym></div>
+</li>
+<li class="level1"><div class="li"> OBJ_ARC</div>
+</li>
+<li class="level1"><div class="li"> OBJ_ROUTE</div>
+</li>
+<li class="level1"><div class="li"> OBJ_THRU_HOLE</div>
+</li>
+<li class="level1"><div class="li"> OBJ_PLACEHOLDER</div>
+</li>
+</ul>
+
+</div>
+
+<h4><a name="functions" id="functions">Functions</a></h4>
+<div class="level4">
+
+<p>
+ Component library:
+</p>
+<ul>
+<li class="level1"><div class="li"> component-library</div>
+</li>
+<li class="level1"><div class="li"> component-library-command</div>
+</li>
+<li class="level1"><div class="li"> component-library-funcs</div>
+</li>
+<li class="level1"><div class="li"> component-library-search</div>
+</li>
+<li class="level1"><div class="li"> reset-component-library</div>
+</li>
+</ul>
+
+<p>
+ Subcircuit library:
+</p>
+<ul>
+<li class="level1"><div class="li"> source-library</div>
+</li>
+<li class="level1"><div class="li"> source-library-search</div>
+</li>
+<li class="level1"><div class="li"> reset-source-library</div>
+</li>
+</ul>
+
+<p>
+ Libgeda behaviour configuration (write-only):
+</p>
+<ul>
+<li class="level1"><div class="li"> always-promote-attributes</div>
+</li>
+<li class="level1"><div class="li"> attribute-promotion</div>
+</li>
+<li class="level1"><div class="li"> bitmap-directory</div>
+</li>
+<li class="level1"><div class="li"> bus-ripper-symname</div>
+</li>
+<li class="level1"><div class="li"> default-series-name</div>
+</li>
+<li class="level1"><div class="li"> font-directory</div>
+</li>
+<li class="level1"><div class="li"> keep-invisible</div>
+</li>
+<li class="level1"><div class="li"> map-font-character-to-file</div>
+</li>
+<li class="level1"><div class="li"> postscript-prolog</div>
+</li>
+<li class="level1"><div class="li"> promote-invisible</div>
+</li>
+<li class="level1"><div class="li"> scheme-directory</div>
+</li>
+<li class="level1"><div class="li"> untitled-name</div>
+</li>
+<li class="level1"><div class="li"> world-size</div>
+</li>
+</ul>
+
+<p>
+ Smob type manipulators:
+</p>
+<ul>
+<li class="level1"><div class="li"> get-attribute-name-value</div>
+</li>
+<li class="level1"><div class="li"> get-attribute-bounds</div>
+</li>
+<li class="level1"><div class="li"> get-attribute-angle</div>
+</li>
+<li class="level1"><div class="li"> calcule-new-attrib-bounds</div>
+</li>
+<li class="level1"><div class="li"> get-object-attributes</div>
+</li>
+<li class="level1"><div class="li"> get-attrib-value-by-attrib-name</div>
+</li>
+<li class="level1"><div class="li"> get-object-type</div>
+</li>
+<li class="level1"><div class="li"> get-line-width</div>
+</li>
+<li class="level1"><div class="li"> get-page-filename</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "libgeda C library" [40-1504] -->
+<h3><a name="libgeda_geda.scm" id="libgeda_geda.scm">libgeda geda.scm</a></h3>
+<div class="level3">
+
+<p>
+ geda.scm, installed with libgeda, provides several useful functions for doing simple manipulation of paths and files, as well as loading rc files from gafrc.d directories.
+</p>
+
+</div>
+
+<h4><a name="functions1" id="functions1">Functions</a></h4>
+<div class="level4">
+<ul>
+<li class="level1"><div class="li"> build-path</div>
+</li>
+<li class="level1"><div class="li"> regular-file?</div>
+</li>
+<li class="level1"><div class="li"> directory?</div>
+</li>
+<li class="level1"><div class="li"> has-suffix?</div>
+</li>
+<li class="level1"><div class="li"> load-scheme-dir</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "libgeda geda.scm" [1505-] --></div>
+</body>
+</html>
diff --git a/docs/wiki/geda_pcb_tips.html b/docs/wiki/geda_pcb_tips.html
index 6efd72e..d66e49b 100644
--- a/docs/wiki/geda_pcb_tips.html
+++ b/docs/wiki/geda_pcb_tips.html
@@ -7,7 +7,7 @@
<title>geda:pcb_tips</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-07-24T17:36:35-0400" />
+<meta name="date" content="2007-11-16T08:02:54-0500" />
<meta name="keywords" content="geda,pcb_tips" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -38,6 +38,7 @@
<ul class="toc">
<li class="level2"><div class="li"><span class="li"><a href="#auto-pan_bugs_me._what_can_i_do_about_it" class="toc">Auto-pan bugs me. What can I do about it?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#the_delete_key_sometimes_refuses_to_delete" class="toc">The delete key sometimes refuses to delete</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#i_try_to_move_an_object_but_pcb_won_t_let_me_what_can_i_do_about_it" class="toc">I try to move an object, but pcb won't let me! What can I do about it?</a></span></div></li>
</ul>
</li>
<li class="level1"><div class="li"><span class="li"><a href="#footprint_issues" class="toc">Footprint issues</a></span></div>
@@ -83,6 +84,7 @@
<li class="level2"><div class="li"><span class="li"><a href="#i_want_to_draw_a_track_between_two_segments_on_the_same_net_but_pcb_won_t_let_me_why" class="toc">I want to draw a track between two segments on the same net, but PCB won't let me! Why?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#pcb_seems_to_munge_my_components_names_and_complains_that_it_can_t_find_proper_nets_for_the_pins_how_come" class="toc">PCB seems to munge my components names and complains that it can't find proper nets for the pins! How come?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#how_can_i_set_color_and_thickness_of_the_rats_nests" class="toc">How can I set color and thickness of the rats nests?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#where_is_that_last_remaining_rat" class="toc">Where is that last remaining rat?</a></span></div></li>
</ul>
</li>
<li class="level1"><div class="li"><span class="li"><a href="#beyond_tracks_and_footprints" class="toc">Beyond tracks and footprints</a></span></div>
@@ -93,6 +95,8 @@
<li class="level2"><div class="li"><span class="li"><a href="#the_polygons_are_shorting_my_tracks_what_can_i_do_about_it" class="toc">The polygons are shorting my tracks! What can I do about it?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_change_polygon_clearance" class="toc">How do I change polygon clearance?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_hide_the_polygons_while_i_edit_the_layout" class="toc">How do I hide the polygons while I edit the layout?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#polygons_are_making_the_gui_sluggish._what_i_can_do_about_it" class="toc">Polygons are making the GUI sluggish. What I can do about it?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#after_i_defined_those_ground_planes_pcb_takes_ages_to_load._how_come" class="toc">After I defined those ground planes, pcb takes ages to load. How come?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_edit_polygons" class="toc">How do I edit polygons?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_place_vias_that_connect_to_a_polygon_for_full_thermal_dissipation_or_full_shielding_integrity" class="toc">How do I place vias that connect to a polygon for full thermal dissipation or full shielding integrity?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#can_polygons_be_un-masked_can_a_polygon_be_made_bare-copper_with_no_solder_mask" class="toc">Can polygons be un-masked? (Can a polygon be made bare-copper with no solder mask?)</a></span></div></li>
@@ -107,6 +111,7 @@
<li class="level1"><div class="li"><span class="li"><a href="#auto_router" class="toc">Auto Router</a></span></div>
<ul class="toc">
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_force_the_autorouter_to_only_put_traces_on_a_particular_layer" class="toc">How do I force the autorouter to only put traces on a particular layer?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_make_autorouter_leave_particular_nets_alone" class="toc">How do I make autorouter leave particular nets alone?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_force_the_autorouter_to_route_only_within_my_pcb_outline" class="toc">How do I force the autorouter to route only within my pcb outline?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_route_power_and_ground_planes_with_the_autorouter" class="toc">How do I route power and ground planes with the autorouter?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#the_layout_produced_by_the_autorouter_is_inefficient" class="toc">The layout produced by the autorouter is inefficient!</a></span></div></li>
@@ -116,6 +121,7 @@
<li class="level1"><div class="li"><span class="li"><a href="#gerber_generation_and_file_i_o_issues" class="toc">Gerber generation and file I/O issues</a></span></div>
<ul class="toc">
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_make_a_board_outline_to_go_with_my_gerbers_to_the_board_maker" class="toc">How do I make a board outline to go with my gerbers to the board maker?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#yes_i_tried_that_but_the_gerber_exporter_didn_t_give_me_an_outline_file._why" class="toc">Yes, I tried that, but the gerber exporter didn't give me an outline file. Why?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#i_m_done_with_my_layout._how_should_i_check_my_design" class="toc">I'm done with my layout. How should I check my design?</a></span></div></li>
</ul>
</li>
@@ -124,6 +130,12 @@
<li class="level2"><div class="li"><span class="li"><a href="#what_is_xy-max_in_the_png_export_dialog_box" class="toc">What is xy-max in the PNG export dialog box?</a></span></div></li>
</ul>
</li>
+<li class="level1"><div class="li"><span class="li"><a href="#customization" class="toc">Customization</a></span></div>
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#i_don_t_like_that_old-style_black_backgropund._how_can_i_get_a_light_canvas" class="toc">I don't like that old-style black backgropund. How can I get a light canvas?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_set_the_default_values_of_the_postscript_dialog" class="toc">How do I set the default values of the postscript dialog?</a></span></div></li>
+</ul>
+</li>
<li class="level1"><div class="li"><span class="li"><a href="#you_didn_t_answer_my_question._what_other_resources_exist_for_pcb_information" class="toc">You didn't answer my question. What other resources exist for PCB information?</a></span></div></li></ul>
</div>
</div>
@@ -199,13 +211,30 @@ Probably you try to delete a selected object. In pcb the delete button does not
However, the Select menu contains an action that lets you delete the current selection. Currently, there is no accel key attached to this action.
</p>
+<p>
+Note, for versions younger than summer 2007 this issue is resolved. The delete key acts on selected objects too.
+</p>
+
</div>
-<!-- SECTION "The delete key sometimes refuses to delete" [1999-2563] -->
+<!-- SECTION "The delete key sometimes refuses to delete" [1999-2677] -->
+<h2><a name="i_try_to_move_an_object_but_pcb_won_t_let_me_what_can_i_do_about_it" id="i_try_to_move_an_object_but_pcb_won_t_let_me_what_can_i_do_about_it">I try to move an object, but pcb won't let me! What can I do about it?</a></h2>
+<div class="level2">
+
+<p>
+Most probably the object is locked. To see, wether it indeeed is, select-all-connected-objects from the select menu. Locked objects wonâ??t highlight. Use the lock tool to unlock the object in question. Note, that the lock tool always toggles the lock state of the object you click at. Afterwards an n object report pops up that contains the lock state in the last line.
+</p>
+
+<p>
+If you want to remove all locks, you may consider to remove all occurences of the string <em>lock</em> in the *.pcb file with your favorite ascii editor.
+</p>
+
+</div>
+<!-- SECTION "I try to move an object, but pcb won't let me! What can I do about it?" [2678-3283] -->
<h1><a name="footprint_issues" id="footprint_issues">Footprint issues</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Footprint issues" [2564-2595] -->
+<!-- SECTION "Footprint issues" [3284-3315] -->
<h2><a name="how_do_pcb_s_footprints_work" id="how_do_pcb_s_footprints_work">How do PCB's footprints work?</a></h2>
<div class="level2">
@@ -224,7 +253,7 @@ PCB supports two entirely separate footprint library mechanisms:
</p>
</div>
-<!-- SECTION "How do PCB's footprints work?" [2596-4300] -->
+<!-- SECTION "How do PCB's footprints work?" [3316-5020] -->
<h2><a name="where_can_i_get_pre-drawn_footprints_for_pcb" id="where_can_i_get_pre-drawn_footprints_for_pcb">Where can I get pre-drawn footprints for PCB?</a></h2>
<div class="level2">
@@ -233,7 +262,7 @@ Currently, the best place to get footprints (besides in the PCB distribution) is
</p>
</div>
-<!-- SECTION "Where can I get pre-drawn footprints for PCB?" [4301-5039] -->
+<!-- SECTION "Where can I get pre-drawn footprints for PCB?" [5021-5759] -->
<h2><a name="i_want_to_use_pcb_to_do_layout._how_do_i_know_what_value_to_use_for_the_footprint_attribute" id="i_want_to_use_pcb_to_do_layout._how_do_i_know_what_value_to_use_for_the_footprint_attribute">I want to use PCB to do layout. How do I know what value to use for the footprint attribute?</a></h2>
<div class="level2">
@@ -242,7 +271,7 @@ This question is a common one amongst new gEDA users. Indeed, helping newbies de
</p>
</div>
-<!-- SECTION "I want to use PCB to do layout. How do I know what value to use for the footprint attribute?" [5040-5663] -->
+<!-- SECTION "I want to use PCB to do layout. How do I know what value to use for the footprint attribute?" [5760-6383] -->
<h3><a name="newlib" id="newlib">Newlib</a></h3>
<div class="level3">
@@ -267,7 +296,7 @@ There are several ways to determine the newlib footprint names to use:
</ul>
</div>
-<!-- SECTION "Newlib" [5664-7818] -->
+<!-- SECTION "Newlib" [6384-8538] -->
<h3><a name="m4_library" id="m4_library">M4 library</a></h3>
<div class="level3">
@@ -306,7 +335,7 @@ Also, once you generate Gerber files, make sure you <span class="curid"><a href=
</p>
</div>
-<!-- SECTION "M4 library" [7819-9728] -->
+<!-- SECTION "M4 library" [8539-10448] -->
<h2><a name="what_is_the_recommended_way_to_deal_with_different_footprints_for_the_same_sort_of_device" id="what_is_the_recommended_way_to_deal_with_different_footprints_for_the_same_sort_of_device">What is the recommended way to deal with different footprints for the same sort of device?</a></h2>
<div class="level2">
@@ -323,7 +352,7 @@ As far as managing the footprint choices (and indeed the large number of compone
</p>
</div>
-<!-- SECTION "What is the recommended way to deal with different footprints for the same sort of device?" [9729-10806] -->
+<!-- SECTION "What is the recommended way to deal with different footprints for the same sort of device?" [10449-11526] -->
<h2><a name="how_do_i_draw_a_new_footprint" id="how_do_i_draw_a_new_footprint">How do I draw a new footprint?</a></h2>
<div class="level2">
@@ -340,7 +369,7 @@ Everybody does this a little differently. Some people draw the footprint entirel
</ul>
</div>
-<!-- SECTION "How do I draw a new footprint?" [10807-11634] -->
+<!-- SECTION "How do I draw a new footprint?" [11527-12354] -->
<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">
@@ -381,28 +410,28 @@ 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?" [11635-12602] -->
+<!-- SECTION "How do I edit/change an existing footprint?" [12355-13322] -->
<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">
<p>
Adding footprint libraries can be done from the <acronym title="Graphical User Interface">GUI</acronym>:<br/>
<strong><em>File</em></strong> â??> <strong><em>Preferences</em></strong> â??> <strong><em>Library</em></strong> â??> <strong>FOOTPRINTDIRECTORY</strong><br/>
- Alternatively you can edit the file <code>$HOME/.pcb/preferences</code>. Look for the line that starts with â??library-newlibâ??. Donâ??t forget to include the new directory into your gsch2pcb resource file (if you are using gsch2pcb, that is).
+ Alternatively you can edit the file <code>$HOME/.pcb/preferences</code>. Make sure, no instance of pcb is currently running. Look for the line that starts with â??library-newlibâ??. Donâ??t forget to include the new directory into either your gsch2pcbrc, or your local gafrc file (if you are using gsch2pcb, that is).
</p>
</div>
-<!-- SECTION "How do I add a footprint library to PCB?" [12603-13035] -->
+<!-- SECTION "How do I add a footprint library to PCB?" [13323-13828] -->
<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">
<p>
There is no way to automatically replace all instances of a footprint with the new version, yet. But there is a special mode of the buffer-paste tool, that will reduce the amount of clicks for manual replacement.<br/>
- Use the Info→Library dialog box to manually choose the new footprint. The tool becomes the buffer-paste tool, with the new footprint preloaded. Rotate it if needed with Buffer→Rotate Buffer. Position the new footprint over the old one, and shift-left-mouse-click to replace the old footprint with the new one. Watch out for being 180 degrees off, use â??oâ?? to check the rats nest after each placement, and undo if it appears you placed it backwards.
+ Use the Window→Library dialog box to manually choose the new footprint. The tool becomes the buffer-paste tool, with the new footprint preloaded. Rotate it if needed with Buffer→Rotate Buffer. Position the new footprint over the old one, and shift-left-mouse-click to replace the old footprint with the new one. Watch out for being 180 degrees off, use â??oâ?? to check the rats nest after each placement, and undo if it appears you placed it backwards.
</p>
</div>
-<!-- SECTION "How do I update a footprint in my layout?" [13036-13756] -->
+<!-- SECTION "How do I update a footprint in my layout?" [13829-14551] -->
<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">
@@ -411,12 +440,12 @@ The footprint path that PCB uses is defined using the <strong><code>Pcb.elementP
</p>
</div>
-<!-- SECTION "PCB is not finding my footprints. Why?" [13757-14104] -->
+<!-- SECTION "PCB is not finding my footprints. Why?" [14552-14899] -->
<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">
<p>
-I prefer to place all â??production-readyâ?? footprints in a single directory that is not in the gEDA/PCB install tree. When a new version of gEDA/PCB comes out I do not make any changes to project files or libraries. If there are newlib footprints in the PCB library that I want to use I copy them to the �������������production-readyâ?? footprint directory.
+I prefer to place all â??production-readyâ?? footprints in a single directory that is not in the gEDA/PCB install tree. When a new version of gEDA/PCB comes out I do not make any changes to project files or libraries. If there are newlib footprints in the PCB library that I want to use I copy them to the â??production-readyâ?? footprint directory.
</p>
<p>
@@ -441,12 +470,12 @@ gsch2pcb --elements-dir /home/user/pcb/footprints/user --use-files $@
</pre>
</div>
-<!-- SECTION "Now that I have all of these footprints where do I put them?" [14105-15161] -->
+<!-- SECTION "Now that I have all of these footprints where do I put them?" [14900-15916] -->
<h1><a name="component_placement" id="component_placement">Component placement</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Component placement" [15162-15196] -->
+<!-- SECTION "Component placement" [15917-15951] -->
<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>
@@ -461,7 +490,7 @@ gsch2pcb --elements-dir /home/user/pcb/footprints/user --use-files $@
</ol>
</div>
-<!-- SECTION "How do I rotate a selection (i.e. of more than one item)?" [15197-15456] -->
+<!-- SECTION "How do I rotate a selection (i.e. of more than one item)?" [15952-16211] -->
<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>
@@ -476,7 +505,7 @@ gsch2pcb --elements-dir /home/user/pcb/footprints/user --use-files $@
</p>
</div>
-<!-- SECTION "How do I change the size of a graphical object (such as text, silkscreen lines, etc)?" [15457-15906] -->
+<!-- SECTION "How do I change the size of a graphical object (such as text, silkscreen lines, etc)?" [16212-16661] -->
<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">
@@ -491,7 +520,7 @@ There are two ways to do it:
</ul>
</div>
-<!-- SECTION "How do I put components on both faces in PCB?" [15907-16375] -->
+<!-- SECTION "How do I put components on both faces in PCB?" [16662-17130] -->
<h2><a name="how_do_i_set_the_origin_in_pcb" id="how_do_i_set_the_origin_in_pcb">How do I set the origin in pcb?</a></h2>
<div class="level2">
@@ -500,7 +529,7 @@ The absolute origin is always in the upper left corner of the accessible area. T
</p>
</div>
-<!-- SECTION "How do I set the origin in pcb?" [16376-16990] -->
+<!-- SECTION "How do I set the origin in pcb?" [17131-17745] -->
<h2><a name="how_do_i_measure_distances_and_dimensions_of_components" id="how_do_i_measure_distances_and_dimensions_of_components">How do I measure distances and dimensions of components?</a></h2>
<div class="level2">
@@ -509,7 +538,7 @@ Use [<strong><code>ctrl-m</code></strong>] to set the origin and read the distan
</p>
</div>
-<!-- SECTION "How do I measure distances and dimensions of components?" [16991-17370] -->
+<!-- SECTION "How do I measure distances and dimensions of components?" [17746-18125] -->
<h2><a name="how_do_i_hide_rats_of_specific_nets" id="how_do_i_hide_rats_of_specific_nets">How do I hide rats of specific nets?</a></h2>
<div class="level2">
@@ -518,12 +547,12 @@ In the netlist window, doubleclick on the specific rat name, then press â??oâ??
</p>
</div>
-<!-- SECTION "How do I hide rats of specific nets?" [17371-17659] -->
+<!-- SECTION "How do I hide rats of specific nets?" [18126-18414] -->
<h1><a name="routing" id="routing">Routing</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Routing" [17660-17681] -->
+<!-- SECTION "Routing" [18415-18436] -->
<h2><a name="how_do_i_route_a_connection_from_solder_to_component_side_and_back" id="how_do_i_route_a_connection_from_solder_to_component_side_and_back">How do I route a connection from solder to component side and back?</a></h2>
<div class="level2">
@@ -532,7 +561,7 @@ While using the line tool, use the number keys on top of the keyboard to switch
</p>
</div>
-<!-- SECTION "How do I route a connection from solder to component side and back?" [17682-17931] -->
+<!-- SECTION "How do I route a connection from solder to component side and back?" [18437-18686] -->
<h2><a name="how_do_i_change_the_routing_style" id="how_do_i_change_the_routing_style">How do I change the routing style?</a></h2>
<div class="level2">
@@ -555,7 +584,7 @@ The way to access these modes differs among the <acronym title="Graphical User I
</p>
</div>
-<!-- SECTION "How do I change the routing style?" [17932-18891] -->
+<!-- SECTION "How do I change the routing style?" [18687-19646] -->
<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">
@@ -564,7 +593,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?" [18892-19164] -->
+<!-- SECTION "I got stuck! How do I go back?" [19647-19919] -->
<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>
@@ -577,7 +606,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?" [19165-19605] -->
+<!-- SECTION "How do I move one set of layer tracks to a different layer?" [19920-20360] -->
<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">
@@ -619,7 +648,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" [19606-21381] -->
+<!-- SECTION "How do I achieve open vias clear of soldermask" [20361-22136] -->
<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">
@@ -628,7 +657,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?" [21382-21908] -->
+<!-- SECTION "How do I change the soldermask clearance around a hole/pad?" [22137-22663] -->
<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">
@@ -645,7 +674,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?" [21909-22846] -->
+<!-- SECTION "How do I change the size of my tracks?" [22664-23601] -->
<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>
@@ -668,7 +697,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?" [22847-23332] -->
+<!-- SECTION "How do I drive a via to connect a track to a ground plane on a different layer?" [23602-24087] -->
<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">
@@ -687,7 +716,7 @@ Here are some suggestions:
</ul>
</div>
-<!-- SECTION "What is the easiest way to create a thermal via?" [23333-24110] -->
+<!-- SECTION "What is the easiest way to create a thermal via?" [24088-24865] -->
<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">
@@ -706,7 +735,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?" [24111-25429] -->
+<!-- SECTION "I want to draw a track between two segments on the same net, but PCB won't let me! Why?" [24866-26184] -->
<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">
@@ -716,7 +745,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?" [25430-26067] -->
+<!-- SECTION "PCB seems to munge my components names and complains that it can't find proper nets for the pins! How come?" [26185-26822] -->
<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">
@@ -729,12 +758,21 @@ There is currently no <acronym title="Graphical User Interface">GUI</acronym> wa
</p>
</div>
-<!-- SECTION "How can I set color and thickness of the rats nests?" [26068-26419] -->
+<!-- SECTION "How can I set color and thickness of the rats nests?" [26823-27174] -->
+<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">
+
+<p>
+Sometimes remaining rats are hard to see, because they have zero length. This will be the case if a via is missing for some reason. You can make them pop into your eye by setting the rat thickness to some big value e.g. 3000 mil. Rat thickness is set in <code>$HOME/.pcb/preference</code>.
+</p>
+
+</div>
+<!-- SECTION "Where is that last remaining rat?" [27175-27502] -->
<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" [26420-26462] -->
+<!-- SECTION "Beyond tracks and footprints" [27503-27545] -->
<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">
@@ -751,7 +789,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?" [26463-27303] -->
+<!-- SECTION "How do I trace a drawing, a print, or another PCB?" [27546-28386] -->
<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">
@@ -776,7 +814,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?" [27304-27958] -->
+<!-- SECTION "I can't copy component pads in a layout. What gives?" [28387-29041] -->
<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">
@@ -785,7 +823,7 @@ Use rectangles and polygon planes. These items will always avoid vias, pads and
</p>
</div>
-<!-- SECTION "How do I fill areas with copper?" [27959-28320] -->
+<!-- SECTION "How do I fill areas with copper?" [29042-29403] -->
<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">
@@ -794,7 +832,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?" [28321-28970] -->
+<!-- SECTION "The polygons are shorting my tracks! What can I do about it?" [29404-30053] -->
<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">
@@ -807,16 +845,42 @@ The amount of the increment can be configured in the dialog File/Preference/Incr
</p>
</div>
-<!-- SECTION "How do I change polygon clearance?" [28971-29471] -->
+<!-- SECTION "How do I change polygon clearance?" [30054-30554] -->
<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.
+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.
+</p>
+
+</div>
+<!-- SECTION "How do I hide the polygons while I edit the layout?" [30555-31140] -->
+<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">
+
+<p>
+Parts of the polygon that are not connected to some net are automatically eliminated. This effectively removes <a href="http://geda.seul.org/wiki/geda:glossary"; class="wikilink1" title="geda:glossary">dead copper</a>. While this is desirable for the actual board, it requires calculation of quite extensive algorithms. So it is not necessarily a bug, but a price to be paid for a powerful feature. Still, there is a couple of things you can do to improve the situation:
+</p>
+<ul>
+<li class="level1"><div class="li"> Temporarily hide the polygons. (see above)</div>
+</li>
+<li class="level1"><div class="li"> Choose â??thin draw polyâ?? from the settings menu to display only the outlines of the polygons and disable dead copper removal. In recent versions of gschem, i.e. later than september 2007, you can select through the polygons. </div>
+</li>
+<li class="level1"><div class="li"> Make sure, you donâ??t have redundant polygons defined, which multiply overlay the same area. These polygons wonâ??t display becaus they shade each other. But they demand calculation resources. The best way to check for redundant polygons is to edit the source of your layout with an ascii editor. </div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Polygons are making the GUI sluggish. What I can do about it?" [31141-32184] -->
+<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">
+
+<p>
+Polygon calculation is potentially an expensive operation in terms of processor cyles. Unless your layout is pretty complex, you most likely have redundant polygons defined. Look into the source of your layout to find and delete unnecessary polygons. If this does not apply, see above for possible measures to ameliorate the situation.
</p>
</div>
-<!-- SECTION "How do I hide the polygons while I edit the layout?" [29472-29880] -->
+<!-- SECTION "After I defined those ground planes, pcb takes ages to load. How come?" [32185-32605] -->
<h2><a name="how_do_i_edit_polygons" id="how_do_i_edit_polygons">How do I edit polygons?</a></h2>
<div class="level2">
@@ -829,7 +893,7 @@ There are four basic ways to edit polygon outlines. You can move and delete vert
</p>
</div>
-<!-- SECTION "How do I edit polygons?" [29881-31066] -->
+<!-- SECTION "How do I edit polygons?" [32606-33791] -->
<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">
@@ -838,7 +902,7 @@ Often itâ??s useful to have vias connect completely to a polygon (a field of cop
</p>
<p>
-One way, youâ??ll make an object thatâ??s almost just like a thermal in that it goes between your via and the polygonâ??the difference is that youâ??ll actually create an annulus to completely fill the space between the hole and polygon (which because itâ??s clearance is turned on, is not connected to the pin). This annulus is four arc segments. You can copy these four items to the buffer to create a �����zero-clearance thermal toolâ??. The drawback of this trick is that when you change via size, youâ??ll also have to modify the size of these filler parts.
+One way, youâ??ll make an object thatâ??s almost just like a thermal in that it goes between your via and the polygonâ??the difference is that youâ??ll actually create an annulus to completely fill the space between the hole and polygon (which because itâ??s clearance is turned on, is not connected to the pin). This annulus is four arc segments. You can copy these four items to the buffer to create a â??zero-clearance thermal toolâ??. The drawback of this trick is that when you change via size, youâ??ll also have to modify the size of these filler parts.
</p>
<p>
@@ -854,20 +918,38 @@ Power-users may want to keep a small custom library of these parts by saving the
</p>
<p>
-You can also add another polygon on-top of the polygon to which you want to connect you vias. Youâ??ll un-set the ���clear pins/viasâ?? flag and the vias will be connected to the larger polygon underneath.
+You can also add another polygon on-top of the polygon to which you want to connect you vias. Youâ??ll un-set the â??clear pins/viasâ?? flag and the vias will be connected to the larger polygon underneath.
</p>
</div>
-<!-- SECTION "How do I place vias that connect to a polygon for full thermal dissipation or full shielding integrity?" [31067-33014] -->
+<!-- SECTION "How do I place vias that connect to a polygon for full thermal dissipation or full shielding integrity?" [33792-35713] -->
<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">
<p>
-Currently this is not possible in PCB. The usual workaround (for example if you want to leave a bare area to attach a heatsink or shielding) is to make an element that is a single pad. This pad should be as small as possible (0 x 0) but with a large clearance. Itâ??s the soldermask clearance from this part you will use to un-mask the polygon. PCB internally limits the size of the pad to 250 mils. For larger exposed areas you will need to use multiple pads.
+Currently, there is no way to directly make polgons clear solder mask. The usual workaround is to work with pads.
+</p>
+<ol>
+<li class="level1"><div class="li"> Draw a track in the middle of the desired no solder mask area. Every track will become a pad.</div>
+</li>
+<li class="level1"><div class="li"> Select the tracks</div>
+</li>
+<li class="level1"><div class="li"> Do convert-selection-to-element from the select menu</div>
+</li>
+<li class="level1"><div class="li"> Activate the solder mask layer. The solder mask should keep clear of the tracks</div>
+</li>
+<li class="level1"><div class="li"> Increase the clearance of the pads to match the desired bare copper area. To do this, press [k] while the mouse cursor hovers above the pads.</div>
+</li>
+<li class="level1"><div class="li"> Optionally press q to set the square flag of the pads.</div>
+</li>
+</ol>
+
+<p>
+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?)" [33015-33572] -->
+<!-- SECTION "Can polygons be un-masked? (Can a polygon be made bare-copper with no solder mask?)" [35714-36463] -->
<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">
@@ -888,7 +970,7 @@ For footprint examples see <a href="http://www.luciani.org/geda/pcb/pcb-footprin
</p>
</div>
-<!-- SECTION "How do I place mounting holes?" [33573-34237] -->
+<!-- SECTION "How do I place mounting holes?" [36464-37128] -->
<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">
@@ -897,7 +979,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?" [34238-34868] -->
+<!-- SECTION "Why is it possible to make a thermal for pin, but not for a pad?" [37129-37759] -->
<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">
@@ -916,7 +998,7 @@ Yes. Just plot your gerbers and toss any layers that are not needed. You can jus
</p>
</div>
-<!-- SECTION "Can PCB be used to make single layer boards?" [34869-35666] -->
+<!-- SECTION "Can PCB be used to make single layer boards?" [37760-38557] -->
<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">
@@ -935,7 +1017,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?" [35667-36951] -->
+<!-- SECTION "What resources exist to process PCB files using scripts?" [38558-39842] -->
<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">
@@ -948,7 +1030,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?" [36952-38030] -->
+<!-- SECTION "How do I import external vector graphics?" [39843-40921] -->
<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">
@@ -957,12 +1039,12 @@ 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?" [38031-38301] -->
+<!-- SECTION "How Do I attach a name to my layout?" [40922-41192] -->
<h1><a name="auto_router" id="auto_router">Auto Router</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Auto Router" [38302-38327] -->
+<!-- SECTION "Auto Router" [41193-41219] -->
<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">
@@ -971,7 +1053,16 @@ 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?" [38328-38539] -->
+<!-- SECTION "How do I force the autorouter to only put traces on a particular layer?" [41220-41431] -->
+<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">
+
+<p>
+Open up the netlist window. It has options for including or excluding nets from the ratlist. If you use the GTK-HID double-click a route to disable it. Make sure, only the nets you want are enabled. Optimize the rats with key [o]. Do â??autoroute all ratsâ??.
+</p>
+
+</div>
+<!-- SECTION "How do I make autorouter leave particular nets alone?" [41432-41756] -->
<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">
@@ -980,7 +1071,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?" [38540-38971] -->
+<!-- SECTION "How do I force the autorouter to route only within my pcb outline?" [41757-42188] -->
<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">
@@ -989,7 +1080,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?" [38972-39253] -->
+<!-- SECTION "How do I route power and ground planes with the autorouter?" [42189-42470] -->
<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">
@@ -998,7 +1089,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!" [39254-39434] -->
+<!-- SECTION "The layout produced by the autorouter is inefficient!" [42471-42651] -->
<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">
@@ -1007,12 +1098,12 @@ Have you tried the various clean-up tools under connects–>optimize rout
</p>
</div>
-<!-- SECTION "The layout produced by the autorouter is ugly!" [39435-39577] -->
+<!-- SECTION "The layout produced by the autorouter is ugly!" [42652-42794] -->
<h1><a name="gerber_generation_and_file_i_o_issues" id="gerber_generation_and_file_i_o_issues">Gerber generation and file I/O issues</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Gerber generation and file I/O issues" [39578-39630] -->
+<!-- SECTION "Gerber generation and file I/O issues" [42795-42847] -->
<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">
@@ -1037,7 +1128,16 @@ 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?" [39631-40477] -->
+<!-- SECTION "How do I make a board outline to go with my gerbers to the board maker?" [42848-43694] -->
+<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">
+
+<p>
+ By default, gsch2pcb creates layer groups in a way which prevents your outline layer from being treated properly. So you should remove all the unnecessary layers (i.e, all but your copper layers and silkscreen), then add an outline layer (named <code>outline</code>), on which you define your outline. The gerber exporter should then give you the outline gerber file.
+</p>
+
+</div>
+<!-- SECTION "Yes, I tried that, but the gerber exporter didn't give me an outline file. Why?" [43695-44147] -->
<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>
@@ -1070,21 +1170,47 @@ 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?" [40478-42697] -->
+<!-- SECTION "I'm done with my layout. How should I check my design?" [44148-46367] -->
<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" [42698-42756] -->
+<!-- SECTION "Exporting Other Formats: Raster and PS Files" [46368-46427] -->
<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">
<p>
-It limits the size of the image to NxN pixels, but maintains the aspect ratio. For example, if you set it to 400, a 6000×8000 mil board would yeild a 300×400 image, but a 6000×4500 board yeilds a 400×300 image.
+It limits the size of the image to NxN pixels, but maintains the aspect ratio. For example, if you set it to 400, a 6000×8000 mil board would yield a 300×400 image, but a 6000×4500 board yeilds a 400×300 image.
+</p>
+
+</div>
+<!-- SECTION "What is xy-max in the PNG export dialog box?" [46428-46698] -->
+<h1><a name="customization" id="customization">Customization</a></h1>
+<div class="level1">
+
+</div>
+<!-- SECTION "Customization" [46699-46726] -->
+<h2><a name="i_don_t_like_that_old-style_black_backgropund._how_can_i_get_a_light_canvas" id="i_don_t_like_that_old-style_black_backgropund._how_can_i_get_a_light_canvas">I don't like that old-style black backgropund. How can I get a light canvas?</a></h2>
+<div class="level2">
+
+<p>
+In <a href="http://geda.seul.org/wiki/geda:glossary"; class="wikilink1" title="geda:glossary">GTK-HID</a> there is a preference dialog in the file menu. The Colors tab presents a convinient way to set all the colros pcb uses via the standard GTK color chooser. The colors are saved to $HOME/.pcb/preferences on shut down of the application. With <a href="http://geda.seul.org/wiki/geda:glossary"; class="wikilink1" title="geda:glossary">Lesstif-HID</a> there is no preference dialog. Colors can be set in <code>$HOME/.pcb/settings</code>
+</p>
+
+</div>
+<!-- SECTION "I don't like that old-style black backgropund. How can I get a light canvas?" [46727-47182] -->
+<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">
+
+<p>
+You can set the default options of the postscript printing dialog as command line parameters when invoking pcb. Type <code>pcb –help</code> for a list of available options. These options can also be set in a file <code>$HOME/.pcb/settings</code>. A settings file for a4 paper, no alignment marks, multi page output would contain:
</p>
+<pre class="code">media = A4
+align-marks = 0
+multi-file = 1</pre>
</div>
-<!-- SECTION "What is xy-max in the PNG export dialog box?" [42757-43027] -->
+<!-- SECTION "How do I set the default values of the postscript dialog?" [47183-47621] -->
<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">
@@ -1099,6 +1225,6 @@ 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?" [43028-] --></div>
+<!-- SECTION "You didn't answer my question. What other resources exist for PCB information?" [47622-] --></div>
</body>
</html>
diff --git a/docs/wiki/geda_scm.html b/docs/wiki/geda_scm.html
index 3c2ad43..097b0b1 100644
--- a/docs/wiki/geda_scm.html
+++ b/docs/wiki/geda_scm.html
@@ -7,7 +7,7 @@
<title>geda:scm</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-07-14T20:01:43-0400" />
+<meta name="date" content="2007-12-01T01:20:56-0500" />
<meta name="keywords" content="geda,scm" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -51,7 +51,8 @@
<li class="level3"><div class="li"><span class="li"><a href="#keep_my_local_copy_current" class="toc">... keep my local copy current?</a></span></div></li>
<li class="level3"><div class="li"><span class="li"><a href="#commit_my_changes_to_the_local_git_repository" class="toc">... commit my changes to the local git repository?</a></span></div></li>
<li class="level3"><div class="li"><span class="li"><a href="#undo_any_uncommitted_local_changes" class="toc">... undo any uncommitted local changes?</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#fix_change_my_last_commit" class="toc">... fix/change my last commit?</a></span></div></li></ul>
+<li class="level3"><div class="li"><span class="li"><a href="#fix_change_my_last_commit" class="toc">... fix/change my last commit?</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#recover_from_a_really_messed_up_local_repository" class="toc">... recover from a really messed up local repository?</a></span></div></li></ul>
</li></ul>
</li></ul>
</div>
@@ -79,7 +80,7 @@
</p>
</div>
-<!-- SECTION "gEDA/gaf's Source Control Management" [1-493] -->
+<!-- SECTION "gEDA/gaf's Source Control Management" [1-494] -->
<h2><a name="installing_git_related_tools" id="installing_git_related_tools">Installing git & related tools</a></h2>
<div class="level2">
@@ -87,9 +88,7 @@
The core git tools are of course required for using the repository, and the documentation is always useful. However, other tools are often helpful for working with git:
</p>
<ul>
-<li class="level1"><div class="li"> gitk, a visual history repository browser</div>
-</li>
-<li class="level1"><div class="li"> <a href="http://git.or.cz/cogito/"; class="urlextern" title="http://git.or.cz/cogito/"; rel="nofollow">Cogito</a>, a more user-friendly front-end to git</div>
+<li class="level1"><div class="li"> <a href="http://www.kernel.org/pub/software/scm/git/docs/gitk.html"; class="urlextern" title="http://www.kernel.org/pub/software/scm/git/docs/gitk.html"; rel="nofollow">gitk</a>, a visual history repository browser</div>
</li>
<li class="level1"><div class="li"> <a href="http://www.procode.org/stgit/"; class="urlextern" title="http://www.procode.org/stgit/"; rel="nofollow">Stacked Git</a>, for working with patchsets</div>
</li>
@@ -100,10 +99,10 @@
</p>
</div>
-<!-- SECTION "Installing git & related tools" [494-1042] -->
+<!-- SECTION "Installing git & related tools" [495-1027] -->
<h3><a name="debian-based" id="debian-based">Debian-based</a></h3>
<div class="level3">
-<pre class="code">apt-get install git-core git-doc gitk cogito stgit</pre>
+<pre class="code">apt-get install git-core git-doc gitk stgit</pre>
<p>
you may also want:
@@ -115,13 +114,13 @@
</p>
</div>
-<!-- SECTION "Debian-based" [1043-1317] -->
+<!-- SECTION "Debian-based" [1028-1295] -->
<h3><a name="fedora_linux" id="fedora_linux">Fedora Linux</a></h3>
<div class="level3">
-<pre class="code">yum install git cogito stgit</pre>
+<pre class="code">yum install git stgit </pre>
</div>
-<!-- SECTION "Fedora Linux" [1318-1375] -->
+<!-- SECTION "Fedora Linux" [1296-1346] -->
<h2><a name="learning_to_use_git" id="learning_to_use_git">Learning to use git</a></h2>
<div class="level2">
@@ -155,9 +154,7 @@ Other nice tutorials/webpages:
<p>
<a href="http://wiki.sourcemage.org/Git_Guide"; class="urlextern" title="http://wiki.sourcemage.org/Git_Guide"; rel="nofollow">Git Guide</a><br/>
- <a href="http://wiki.sourcemage.org/Cogito_Guide"; class="urlextern" title="http://wiki.sourcemage.org/Cogito_Guide"; rel="nofollow">Cogito Guide</a><br/>
<a href="http://git.or.cz/course/index.html"; class="urlextern" title="http://git.or.cz/course/index.html"; rel="nofollow">git Crash Courses</a><br/>
- <a href="http://git.or.cz/course/cvs.html"; class="urlextern" title="http://git.or.cz/course/cvs.html"; rel="nofollow">Cogito for CVS Users</a><br/>
<a href="http://www.kernel.org/pub/software/scm/git/docs/tutorial.html"; class="urlextern" title="http://www.kernel.org/pub/software/scm/git/docs/tutorial.html"; rel="nofollow">Git for Everyone</a><br/>
</p>
@@ -167,7 +164,7 @@ Keep in mind that some of these tutorials are a little dated and may not cover c
</p>
</div>
-<!-- SECTION "Learning to use git" [1376-2245] -->
+<!-- SECTION "Learning to use git" [1347-2097] -->
<h2><a name="accessing_the_repository" id="accessing_the_repository">Accessing the repository</a></h2>
<div class="level2">
@@ -203,12 +200,12 @@ Port 5022</pre>
</p>
</div>
-<!-- SECTION "Accessing the repository" [2246-3230] -->
+<!-- SECTION "Accessing the repository" [2098-3082] -->
<h2><a name="making_and_committing_changes" id="making_and_committing_changes">Making and committing changes</a></h2>
<div class="level2">
</div>
-<!-- SECTION "Making and committing changes" [3231-3275] -->
+<!-- SECTION "Making and committing changes" [3083-3127] -->
<h3><a name="setting_up_user_information" id="setting_up_user_information">Setting up user information</a></h3>
<div class="level3">
@@ -219,7 +216,7 @@ Port 5022</pre>
$ git config --global user.email you@xxxxxxxxxxxxxxxxxxxxxx</pre>
</div>
-<!-- SECTION "Setting up user information" [3276-3533] -->
+<!-- SECTION "Setting up user information" [3128-3385] -->
<h3><a name="committing_patches_from_other_contributors" id="committing_patches_from_other_contributors">Committing patches from other contributors</a></h3>
<div class="level3">
@@ -249,6 +246,11 @@ Apply the patch as usual (as an example):
<pre class="code">$ patch -p1 < example_changes.patch</pre>
<p>
+ You can also use the git apply command:
+</p>
+<pre class="code">$ git apply example_changes.patch</pre>
+
+<p>
If the patch needs any minor editing before it is committed (eg. white-space changes), please inform the author this was done. They may have other work based on their patch and will want to know if there were changes to the applied version.
</p>
@@ -289,7 +291,7 @@ Commit the patch, making sure that the Authorâ??s name and e-mail address are sp
</p>
</div>
-<!-- SECTION "Committing patches from other contributors" [3534-5385] -->
+<!-- SECTION "Committing patches from other contributors" [3386-5315] -->
<h3><a name="writing_good_commit_messages" id="writing_good_commit_messages">Writing good commit messages</a></h3>
<div class="level3">
@@ -318,7 +320,7 @@ currenly implemented as a macro.
</pre>
</div>
-<!-- SECTION "Writing good commit messages" [5386-6367] -->
+<!-- SECTION "Writing good commit messages" [5316-6297] -->
<h3><a name="push_is_destructive" id="push_is_destructive">Push is Destructive</a></h3>
<div class="level3">
@@ -327,11 +329,11 @@ currenly implemented as a macro.
</p>
<p>
-Unlike <acronym title="Concurrent Versions System">CVS</acronym>, it is not the committing of changes which changes the master repository, but pushing changes using cg-push or git-push. You should always double- (or triple-) check that the commits you are about to push are actually meant for the main repository.
+Unlike <acronym title="Concurrent Versions System">CVS</acronym>, it is not the committing of changes which changes the master repository, but pushing changes using git-push. You should always double- (or triple-) check that the commits you are about to push are actually meant for the main repository.
</p>
</div>
-<!-- SECTION "Push is Destructive" [6368-6732] -->
+<!-- SECTION "Push is Destructive" [6298-6651] -->
<h2><a name="how_do_i" id="how_do_i">How Do I ... ?</a></h2>
<div class="level2">
@@ -340,7 +342,7 @@ Unlike <acronym title="Concurrent Versions System">CVS</acronym>, it is not the
</p>
</div>
-<!-- SECTION "How Do I ... ?" [6733-6856] -->
+<!-- SECTION "How Do I ... ?" [6652-6775] -->
<h3><a name="get_a_copy_of_geda_gaf_git_repository" id="get_a_copy_of_geda_gaf_git_repository">... get a copy of gEDA/gaf git repository?</a></h3>
<div class="level3">
@@ -355,7 +357,7 @@ Unlike <acronym title="Concurrent Versions System">CVS</acronym>, it is not the
<pre class="code">$ git clone git://git.gpleda.org/home/git/gaf.git</pre>
</div>
-<!-- SECTION "... get a copy of gEDA/gaf git repository?" [6857-7076] -->
+<!-- SECTION "... get a copy of gEDA/gaf git repository?" [6776-6995] -->
<h3><a name="keep_my_local_copy_current" id="keep_my_local_copy_current">... keep my local copy current?</a></h3>
<div class="level3">
@@ -371,7 +373,7 @@ Unlike <acronym title="Concurrent Versions System">CVS</acronym>, it is not the
$ git rebase origin</pre>
</div>
-<!-- SECTION "... keep my local copy current?" [7077-7491] -->
+<!-- SECTION "... keep my local copy current?" [6996-7410] -->
<h3><a name="commit_my_changes_to_the_local_git_repository" id="commit_my_changes_to_the_local_git_repository">... commit my changes to the local git repository?</a></h3>
<div class="level3">
<pre class="code">$ git commit -a </pre>
@@ -386,7 +388,7 @@ If you want to commit files in the current directory or want to explicitly commi
<pre class="code">$ git commit filename1 filename2</pre>
</div>
-<!-- SECTION "... commit my changes to the local git repository?" [7492-8045] -->
+<!-- SECTION "... commit my changes to the local git repository?" [7411-7964] -->
<h3><a name="undo_any_uncommitted_local_changes" id="undo_any_uncommitted_local_changes">... undo any uncommitted local changes?</a></h3>
<div class="level3">
<pre class="code">$ git checkout -f </pre>
@@ -396,7 +398,7 @@ If you want to commit files in the current directory or want to explicitly commi
</p>
</div>
-<!-- SECTION "... undo any uncommitted local changes?" [8046-8199] -->
+<!-- SECTION "... undo any uncommitted local changes?" [7965-8118] -->
<h3><a name="fix_change_my_last_commit" id="fix_change_my_last_commit">... fix/change my last commit?</a></h3>
<div class="level3">
<pre class="code">$ Edit whatever files
@@ -407,6 +409,29 @@ $ git commit --amend filename1..filenameN </pre>
</p>
</div>
-<!-- SECTION "... fix/change my last commit?" [8200-] --></div>
+<!-- SECTION "... fix/change my last commit?" [8119-8329] -->
+<h3><a name="recover_from_a_really_messed_up_local_repository" id="recover_from_a_really_messed_up_local_repository">... recover from a really messed up local repository?</a></h3>
+<div class="level3">
+
+<p>
+ First off, do not push any repository that you think is somehow messed up. Ask one of the experienced git people first.
+</p>
+
+<p>
+Second, the command that will really save your bacon is git-reflog. Using it works something like this:
+</p>
+<pre class="code"> $ git reflog
+ 086908e... HEAD@{0}: cherry-pick: Last minute updates to the READMEs for all pro
+ 2a79a23... HEAD@{1}: checkout: moving to master
+ 2a79a23... HEAD@{2}: checkout: moving to master
+ ...
+ $ git reset --hard HEAD@{1}</pre>
+
+<p>
+ The last command (git reset –hard …) will rollback all your changes to the â??checkout: moving to masterâ??. Remember: donâ??t panic! Most things are fixable when using git.
+</p>
+
+</div>
+<!-- SECTION "... recover from a really messed up local repository?" [8330-] --></div>
</body>
</html>
diff --git a/docs/wiki/geda_suse_rpm_installation.html b/docs/wiki/geda_suse_rpm_installation.html
index 4196c74..877fef6 100644
--- a/docs/wiki/geda_suse_rpm_installation.html
+++ b/docs/wiki/geda_suse_rpm_installation.html
@@ -7,7 +7,7 @@
<title>geda:suse_rpm_installation</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-07-28T14:58:18-0400" />
+<meta name="date" content="2007-09-23T14:29:07-0400" />
<meta name="keywords" content="geda,suse_rpm_installation" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -35,7 +35,8 @@
<ul class="toc">
<li class="level3"><div class="li"><span class="li"><a href="#suse_10.0" class="toc">SuSE 10.0</a></span></div></li>
<li class="level3"><div class="li"><span class="li"><a href="#suse_10.1" class="toc">SuSE 10.1</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#suse_10.2" class="toc">SuSE 10.2</a></span></div></li></ul>
+<li class="level3"><div class="li"><span class="li"><a href="#suse_10.2" class="toc">SuSE 10.2</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#suse_10.3" class="toc">SuSE 10.3</a></span></div></li></ul>
</li></ul>
</li></ul>
</div>
@@ -47,41 +48,41 @@
<div class="level1">
</div>
-<!-- SECTION "Installing gEDA rpm packages on SuSE" [1-55] -->
+<!-- SECTION "Installing gEDA rpm packages on SuSE" [1-56] -->
<h2><a name="available_rpm_packages" id="available_rpm_packages">Available rpm packages</a></h2>
<div class="level2">
<ul>
-<li class="level1"><div class="li"> libgeda (1.0.1 alias 20070626)</div>
+<li class="level1"><div class="li"> libgeda (1.2.0)</div>
</li>
-<li class="level1"><div class="li"> geda-docs (1.0.1 alias 20070626)</div>
+<li class="level1"><div class="li"> geda-docs (1.2.0)</div>
</li>
-<li class="level1"><div class="li"> geda-examples (1.0.1 alias 20070626)</div>
+<li class="level1"><div class="li"> geda-examples (1.2.0)</div>
</li>
-<li class="level1"><div class="li"> geda-gattrib (1.0.1 alias 20070626)</div>
+<li class="level1"><div class="li"> geda-gattrib (1.2.0)</div>
</li>
-<li class="level1"><div class="li"> geda-gnetlist (1.0.1 alias 20070626)</div>
+<li class="level1"><div class="li"> geda-gnetlist (1.2.0)</div>
</li>
-<li class="level1"><div class="li"> geda-gschem (1.0.1 alias 20070626)</div>
+<li class="level1"><div class="li"> geda-gschem (1.2.0)</div>
</li>
-<li class="level1"><div class="li"> geda-gsymcheck (1.0.1 alias 20070626)</div>
+<li class="level1"><div class="li"> geda-gsymcheck (1.2.0)</div>
</li>
-<li class="level1"><div class="li"> geda-symbols (1.0.1 alias 20070626)</div>
+<li class="level1"><div class="li"> geda-symbols (1.2.0)</div>
</li>
-<li class="level1"><div class="li"> geda-utils (1.0.1 alias 20070626)</div>
+<li class="level1"><div class="li"> geda-utils (1.2.0)</div>
</li>
<li class="level1"><div class="li"> gerbv (1.0.2)</div>
</li>
-<li class="level1"><div class="li"> pcb (20070208p1)</div>
+<li class="level1"><div class="li"> pcb (20070912)</div>
</li>
<li class="level1"><div class="li"> ng-spice-rework (17)</div>
</li>
<li class="level1"><div class="li"> gnucap (0.35)</div>
</li>
-<li class="level1"><div class="li"> gspiceui (0.8.90)</div>
+<li class="level1"><div class="li"> gspiceui (0.9.33)</div>
</li>
<li class="level1"><div class="li"> gwave (20051222)</div>
</li>
-<li class="level1"><div class="li"> gtkwave (3.0.29)</div>
+<li class="level1"><div class="li"> gtkwave (3.1.1)</div>
</li>
<li class="level1"><div class="li"> dinotrace (9.3e)</div>
</li>
@@ -90,7 +91,7 @@
</ul>
</div>
-<!-- SECTION "Available rpm packages" [56-633] -->
+<!-- SECTION "Available rpm packages" [57-496] -->
<h2><a name="installing_packages_from_the_suse_build_service" id="installing_packages_from_the_suse_build_service">Installing Packages from the SuSE Build Service</a></h2>
<div class="level2">
<ol>
@@ -115,11 +116,11 @@
</p>
<p>
-You can also browse through repositories first: <a href="http://software.opensuse.org/download/home:/werner2101/SUSE_Linux_10.0/repodata/"; class="urlextern" title="http://software.opensuse.org/download/home:/werner2101/SUSE_Linux_10.0/repodata/"; rel="nofollow"> SUSE_Linux_10.0 repo</a>, <a href="http://software.opensuse.org/download/home:/werner2101/SUSE_Linux_10.1/repodata/"; class="urlextern" title="http://software.opensuse.org/download/home:/werner2101/SUSE_Linux_10.1/repodata/"; rel="nofollow"> SUSE_Linux_10.1 repo</a>, <a href="http://software.opensuse.org/download/home:/werner2101/openSUSE_10.2/repodata/"; class="urlextern" title="http://software.opensuse.org/download/home:/werner2101/openSUSE_10.2/repodata/"; rel="nofollow"> openSUSE_10.2 repo</a>
+You can also browse through repositories first: <a href="http://software.opensuse.org/download/home:/werner2101/SUSE_Linux_10.0/repodata/"; class="urlextern" title="http://software.opensuse.org/download/home:/werner2101/SUSE_Linux_10.0/repodata/"; rel="nofollow"> SUSE_Linux_10.0 repo</a>, <a href="http://software.opensuse.org/download/home:/werner2101/SUSE_Linux_10.1/repodata/"; class="urlextern" title="http://software.opensuse.org/download/home:/werner2101/SUSE_Linux_10.1/repodata/"; rel="nofollow"> SUSE_Linux_10.1 repo</a>, <a href="http://software.opensuse.org/download/home:/werner2101/openSUSE_10.2/repodata/"; class="urlextern" title="http://software.opensuse.org/download/home:/werner2101/openSUSE_10.2/repodata/"; rel="nofollow"> openSUSE_10.2 repo</a>, <a href="http://software.opensuse.org/download/home:/werner2101/openSUSE_10.3/repodata/"; class="urlextern" title="http://software.opensuse.org/download/home:/werner2101/openSUSE_10.3/repodata/"; rel="nofollow"> openSUSE_10.3 repo</a>
</p>
</div>
-<!-- SECTION "Installing Packages from the SuSE Build Service" [634-1677] -->
+<!-- SECTION "Installing Packages from the SuSE Build Service" [497-1645] -->
<h2><a name="distribution_specific_notes" id="distribution_specific_notes">Distribution specific notes</a></h2>
<div class="level2">
@@ -128,7 +129,7 @@ You can also browse through repositories first: <a href="http://software.opensu
</p>
</div>
-<!-- SECTION "Distribution specific notes" [1678-1795] -->
+<!-- SECTION "Distribution specific notes" [1646-1763] -->
<h3><a name="suse_10.0" id="suse_10.0">SuSE 10.0</a></h3>
<div class="level3">
<ul>
@@ -137,7 +138,7 @@ You can also browse through repositories first: <a href="http://software.opensu
</ul>
</div>
-<!-- SECTION "SuSE 10.0" [1796-1820] -->
+<!-- SECTION "SuSE 10.0" [1764-1788] -->
<h3><a name="suse_10.1" id="suse_10.1">SuSE 10.1</a></h3>
<div class="level3">
<ul>
@@ -146,7 +147,7 @@ You can also browse through repositories first: <a href="http://software.opensu
</ul>
</div>
-<!-- SECTION "SuSE 10.1" [1821-1845] -->
+<!-- SECTION "SuSE 10.1" [1789-1813] -->
<h3><a name="suse_10.2" id="suse_10.2">SuSE 10.2</a></h3>
<div class="level3">
<ul>
@@ -155,6 +156,15 @@ You can also browse through repositories first: <a href="http://software.opensu
</ul>
</div>
-<!-- SECTION "SuSE 10.2" [1846-] --></div>
+<!-- SECTION "SuSE 10.2" [1814-1976] -->
+<h3><a name="suse_10.3" id="suse_10.3">SuSE 10.3</a></h3>
+<div class="level3">
+<ul>
+<li class="level1"><div class="li"> <strong>gwave cannot be build</strong>, it requires guile-gtk which requires libglade and gtk12. libglade is no longer part of the SuSE distribution.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "SuSE 10.3" [1977-] --></div>
</body>
</html>
diff --git a/docs/wiki/geda_tasks.html b/docs/wiki/geda_tasks.html
index dfde142..c541e79 100644
--- a/docs/wiki/geda_tasks.html
+++ b/docs/wiki/geda_tasks.html
@@ -7,7 +7,7 @@
<title>geda:tasks</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-30T16:31:46-0400" />
+<meta name="date" content="2007-09-25T06:10:05-0400" />
<meta name="keywords" content="geda,tasks" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -67,7 +67,7 @@ gEDA is run by volunteers, so these are volunteer (read: unpaid) tasks. Please c
</ul>
</div>
-<!-- SECTION "important tasks for normal volunteers" [138-2110] -->
+<!-- SECTION "important tasks for normal volunteers" [138-2111] -->
<h2><a name="tasks_for_programmers" id="tasks_for_programmers">tasks for programmers</a></h2>
<div class="level2">
@@ -87,12 +87,14 @@ gEDA is run by volunteers, so these are volunteer (read: unpaid) tasks. Please c
<li class="level1"><div class="li"> <strong>Windows Port Hacker/Manager</strong><br/>
Somebody with expertise building and testing gEDA on UNIX systems and familiarity with the <acronym title="Microsoft">MS</acronym> Windows 95/98/NT platform is needed to manage the gEDA Windows port. Testing, bug fixing, packaging, and releasing of gEDA on the Windows platform would be the primary responsibility of this person. This task requires a person who knows C, gtk+, UNIX, and <acronym title="Microsoft">MS</acronym> Windows programming. The Windows port will NOT move forward if this task is not filled.</div>
</li>
+<li class="level1"><div class="li"> <strong>MacOS port manager</strong>: Have the issues mentioned in <a href="http://www.evilmadscientist.com/article.php/pcbtools"; class="urlextern" title="http://www.evilmadscientist.com/article.php/pcbtools"; rel="nofollow"> "Laying out printed circuit boards with open-source tools"</a> been fixed already?</div>
+</li>
<li class="level1"><div class="li"> <strong>Release Hacker</strong><br/>
Somebody who wants to create and manage releases is needed. Releases occur when the code is ready to be released, so thereâ??s no marketing pressure. This task requires gEDA building/testing familiarity as well perhaps some minor code hacking.</div>
</li>
</ul>
</div>
-<!-- SECTION "tasks for programmers" [2111-] --></div>
+<!-- SECTION "tasks for programmers" [2112-] --></div>
</body>
</html>
diff --git a/docs/wiki/geda_todos.html b/docs/wiki/geda_todos.html
index a5f6a07..6b90f45 100644
--- a/docs/wiki/geda_todos.html
+++ b/docs/wiki/geda_todos.html
@@ -7,7 +7,7 @@
<title>geda:todos</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-30T15:55:08-0400" />
+<meta name="date" content="2007-08-23T09:28:32-0400" />
<meta name="keywords" content="geda,todos" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -31,7 +31,8 @@
<ul class="toc">
<li class="level2"><div class="li"><span class="li"><a href="#things_to_be_done_before_the_next_release" class="toc">Things to be done before the next release</a></span></div></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>
-<li class="level2"><div class="li"><span class="li"><a href="#ideas_for_new_tools_or_geda_suite-wide_enhancements" class="toc">Ideas for new tools or gEDA Suite-wide enhancements</a></span></div></li></ul>
+<li class="level2"><div class="li"><span class="li"><a href="#ideas_for_new_tools_or_geda_suite-wide_enhancements" class="toc">Ideas for new tools or gEDA Suite-wide enhancements</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#code_cleanup_and_refactoring" class="toc">Code cleanup and refactoring</a></span></div></li></ul>
</li></ul>
</div>
</div>
@@ -50,22 +51,32 @@ See <a href="http://geda.seul.org/wiki/geda:tasks"; class="wikilink1" title="geda
</p>
</div>
-<!-- SECTION "ToDo" [1-297] -->
+<!-- SECTION "ToDo" [1-298] -->
<h2><a name="things_to_be_done_before_the_next_release" id="things_to_be_done_before_the_next_release">Things to be done before the next release</a></h2>
<div class="level2">
<ul>
-<li class="level1"><div class="li"> guile 1.8.x issues with netlist backends</div>
+<li class="level1"><div class="li"> TBD</div>
</li>
</ul>
</div>
-<!-- SECTION "Things to be done before the next release" [298-397] -->
+<!-- SECTION "Things to be done before the next release" [299-362] -->
<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>
<li class="level1"><div class="li"> <strong>Libgeda</strong>:</div>
<ul>
-<li class="level2"><div class="li"> Enable handling of .sch files with symbols having some (but not all) pins promoted onto the .sch file. This will enable pin-swapping via backannotation from PCB.</div>
+<li class="level2"><div class="li"> Enable handling of .sch files with symbols having some (but not all) pins promoted onto the .sch file. This will enable pin-swapping via backannotation from PCB</div>
+</li>
+<li class="level2"><div class="li"> Merge per-page netlisting from gnetlist (or re-write if necessary).</div>
+</li>
+<li class="level2"><div class="li"> Make postscript output more friendly to the LaTeX package â??pstricksâ??.</div>
+<ul>
+<li class="level3"><div class="li"> Use the â??showâ?? command to display a whole string at once instead of rendering character by character.</div>
+</li>
+<li class="level3"><div class="li"> Might not be possible / simple as the current approach is due to the overbar drawing postscript.</div>
+</li>
+</ul>
</li>
</ul>
</li>
@@ -77,13 +88,39 @@ See <a href="http://geda.seul.org/wiki/geda:tasks"; class="wikilink1" title="geda
</li>
<li class="level2"><div class="li"> Improve symbol library to handle very large symbol collections better</div>
</li>
-<li class="level2"><div class="li"> Whenever the selection changes and we have selection dependant dialog, the dialog should get an information about that. Then it would be possible to change the attribute dialog to be non-modal.</div>
+<li class="level2"><div class="li"> Now the SELECTION is a GedaList and we can get â??changedâ?? signals, make more dialogs non-modal:</div>
+<ul>
+<li class="level3"><div class="li"> Single attribute editor</div>
+</li>
+<li class="level3"><div class="li"> Text properties</div>
+</li>
+<li class="level3"><div class="li"> Line width and type</div>
+</li>
+<li class="level3"><div class="li"> Fill type</div>
+</li>
+<li class="level3"><div class="li"> Edit slot</div>
+</li>
+<li class="level3"><div class="li"> Edit color</div>
+</li>
+<li class="level3"><div class="li"> Text size (Sets size for new text, so doesnâ??t rely on the selection anyway)</div>
+</li>
+</ul>
+</li>
+<li class="level2"><div class="li"> Enable <strong><code>-</code><code>-</code>help</strong> flag. (Currently supports -h only). Consider using GTKâ??s mechanism for this.</div>
+</li>
+<li class="level2"><div class="li"> Support for embedding LaTeX maths to be rendered in text.</div>
+<ul>
+<li class="level3"><div class="li"> This could be output only, or preview bitmaps could be generated and cached by calling LaTeX, dvips and ps2epsi.</div>
+</li>
+<li class="level3"><div class="li"> Would we add a new type of object for this, or allow attaching a â??latex=1â?? attribute to the text object its self?</div>
+</li>
+</ul>
</li>
</ul>
</li>
<li class="level1"><div class="li"> <strong>Gnetlist</strong>:</div>
<ul>
-<li class="level2"><div class="li"> Enable <strong><code>â??help</code></strong> flag. Do other gEDA/gaf programs recognize this flag?</div>
+<li class="level2"><div class="li"> Enable <strong><code>-</code><code>-</code>help</strong> flag. Do other gEDA/gaf programs recognize this flag?</div>
</li>
</ul>
</li>
@@ -95,6 +132,8 @@ See <a href="http://geda.seul.org/wiki/geda:tasks"; class="wikilink1" title="geda
</li>
<li class="level2"><div class="li"> Enable attachment of attributes to nets.</div>
</li>
+<li class="level2"><div class="li"> Consider using GTKâ??s mechanism to display <strong><code>-</code><code>-</code>help</strong> flag text.</div>
+</li>
</ul>
</li>
<li class="level1"><div class="li"> <strong>Garchive</strong>:</div>
@@ -113,14 +152,14 @@ See <a href="http://geda.seul.org/wiki/geda:tasks"; class="wikilink1" title="geda
<ul>
<li class="level2"><div class="li"> Doesnâ??t currently work properly with slotted parts (it gives new refdes numbers to slotted parts). Fix it so it recognizes slotted parts and assigns refdes appropriately.</div>
</li>
-<li class="level2"><div class="li"> Provide <strong><code>â??gentle</code></strong> option, which doesnâ??t clobber (overwrite) any refdeses which are already assigned.</div>
+<li class="level2"><div class="li"> Provide <strong><code>-</code><code>-</code>gentle</strong> option, which doesnâ??t clobber (overwrite) any refdeses which are already assigned.</div>
</li>
</ul>
</li>
</ul>
</div>
-<!-- SECTION "Longer term upgrades desired for specific tools" [398-1918] -->
+<!-- SECTION "Longer term upgrades desired for specific tools" [363-2872] -->
<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>
@@ -133,6 +172,23 @@ See <a href="http://geda.seul.org/wiki/geda:tasks"; class="wikilink1" title="geda
</ul>
</div>
-<!-- SECTION "Ideas for new tools or gEDA Suite-wide enhancements" [1919-] --></div>
+<!-- SECTION "Ideas for new tools or gEDA Suite-wide enhancements" [2873-3309] -->
+<h2><a name="code_cleanup_and_refactoring" id="code_cleanup_and_refactoring">Code cleanup and refactoring</a></h2>
+<div class="level2">
+<ul>
+<li class="level1"><div class="li"> Remove use of non GList linked lists. This is very invasive work, but allows much code cleanup where mixtures of the old and GList methods were available.</div>
+</li>
+<li class="level1"><div class="li"> Remove unused variables and functions from various structures. Unused may also include â??usedâ??, but ineffective.</div>
+</li>
+<li class="level1"><div class="li"> Remove back-exports to libgeda of global function pointers from gschem and other libgeda â??clientsâ??. These arenâ??t portable.</div>
+</li>
+<li class="level1"><div class="li"> Clean up / produce generic <acronym title="Application Programming Interface">API</acronym> interfaces to act on an object of any type, or lists of objects.</div>
+</li>
+<li class="level1"><div class="li"> Convert functions used within one ".câ?? file, and not useful for public <acronym title="Application Programming Interface">API</acronym> into static functions, removing from prototype.h.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Code cleanup and refactoring" [3310-] --></div>
</body>
</html>
diff --git a/docs/wiki/geda_transistor_guide.html b/docs/wiki/geda_transistor_guide.html
index 6dd4223..e2dccd7 100644
--- a/docs/wiki/geda_transistor_guide.html
+++ b/docs/wiki/geda_transistor_guide.html
@@ -6,7 +6,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>geda:transistor_guide</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,nofollow" />
+<meta name="robots" content="index,follow" />
<meta name="date" content="2007-08-18T14:59:56-0400" />
<meta name="keywords" content="geda,transistor_guide" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
diff --git a/docs/wiki/geda_usage.html b/docs/wiki/geda_usage.html
index a8b310d..ad12f5c 100644
--- a/docs/wiki/geda_usage.html
+++ b/docs/wiki/geda_usage.html
@@ -7,7 +7,7 @@
<title>geda:usage</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-06-27T07:19:06-0400" />
+<meta name="date" content="2007-10-06T16:18:14-0400" />
<meta name="keywords" content="geda,usage" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -124,12 +124,12 @@ The most important thing to keep in mind about gEDAâ??s limitations is this: GED
</li>
<li class="level1"><div class="li"> The project manager â??gedaâ?? is out of date, and needs an update.</div>
</li>
-<li class="level1"><div class="li"> Layer count in PCB: Currently, the layer count in PCB is limited to about 8 layers (which is more than adequate for small- and mid-sized projects). The PCB developers are working on increasing the layer count to an aribtrary number, but they are not yet done with this work. Contact them directly if you are interested in this project.</div>
+<li class="level1"><div class="li"> Layer count in PCB: Currently, the layer count in PCB is limited to 16 layers plus two silk layers by default. This is more than adequate for small- and mid-sized projects. If necessary, the number of layers can be increased arbitrarily at compile time. </div>
</li>
</ul>
</div>
-<!-- SECTION "What limitations exist for the gEDA tools?" [2218-4114] -->
+<!-- SECTION "What limitations exist for the gEDA tools?" [2218-4033] -->
<h1><a name="what_local_configuration_files_are_used_for_a_project" id="what_local_configuration_files_are_used_for_a_project">What local configuration files are used for a project?</a></h1>
<div class="level1">
@@ -150,7 +150,7 @@ A typical PCB design requires the following config files in your local directory
</p>
</div>
-<!-- SECTION "What local configuration files are used for a project?" [4115-5069] -->
+<!-- SECTION "What local configuration files are used for a project?" [4034-4988] -->
<h1><a name="what_are_the_names_and_locations_of_the_rc_files_used_with_geda_gaf_applications" id="what_are_the_names_and_locations_of_the_rc_files_used_with_geda_gaf_applications">What are the names and locations of the RC files used with gEDA/gaf applications?</a></h1>
<div class="level1">
@@ -227,7 +227,7 @@ Finally, note that gEDA/gaf applications will look for up to six configuration f
</p>
</div>
-<!-- SECTION "What are the names and locations of the RC files used with gEDA/gaf applications?" [5070-8446] -->
+<!-- SECTION "What are the names and locations of the RC files used with gEDA/gaf applications?" [4989-8365] -->
<h1><a name="what_about_a_project_manager" id="what_about_a_project_manager">What about a project manager?</a></h1>
<div class="level1">
@@ -240,7 +240,7 @@ Unfortunately, development of â??gedaâ?? has not kept up with the rest of gEDA/g
</p>
</div>
-<!-- SECTION "What about a project manager?" [8447-9482] -->
+<!-- SECTION "What about a project manager?" [8366-9401] -->
<h1><a name="can_we_change_geda_to_use_an_xml_file_format" id="can_we_change_geda_to_use_an_xml_file_format">Can we change gEDA to use an XML file format?</a></h1>
<div class="level1">
@@ -269,6 +269,6 @@ Itâ??s unlikely the gEDA Project will ever switch to an <acronym title="Extensib
</ol>
</div>
-<!-- SECTION "Can we change gEDA to use an XML file format?" [9483-] --></div>
+<!-- SECTION "Can we change gEDA to use an XML file format?" [9402-] --></div>
</body>
</html>
diff --git a/docs/wiki/gsoc2007.html b/docs/wiki/gsoc2007.html
new file mode 100644
index 0000000..21474d5
--- /dev/null
+++ b/docs/wiki/gsoc2007.html
@@ -0,0 +1,198 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en"
+ lang="en" dir="ltr">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+ <title>gsoc2007</title>
+<meta name="generator" content="DokuWiki Release rc2007-05-24" />
+<meta name="robots" content="index,follow" />
+<meta name="date" content="2007-10-28T22:49:28-0400" />
+<meta name="keywords" content="gsoc2007" />
+<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
+<link rel="start" href="http://geda.seul.org/wiki/"; />
+<link rel="contents" href="http://geda.seul.org/wiki/gsoc2007?do=index"; title="Index" />
+<link rel="alternate" type="application/rss+xml" title="Recent Changes" href="http://geda.seul.org/wiki/feed.php"; />
+<link rel="alternate" type="application/rss+xml" title="Current Namespace" href="http://geda.seul.org/wiki/feed.php?mode=list&ns="; />
+<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/gsoc2007"; />
+<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/gsoc2007"; />
+<link rel="stylesheet" media="all" type="text/css" href="lib/exe/css" />
+<link rel="stylesheet" media="screen" type="text/css" href="lib/exe/001css" />
+<link rel="stylesheet" media="print" type="text/css" href="lib/exe/002css" />
+</head>
+<body>
+<div class="dokuwiki export">
+<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="clear">
+
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#announcement_of_participation_in_google_s_summer_of_code" class="toc">Announcement of participation in Google's Summer of Code</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#google_application_information" class="toc">Google application information.</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#project_timeline_and_commitment_level" class="toc">Project timeline and commitment level</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#project_integration" class="toc">Project Integration</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#student_information" class="toc">Student Information</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#suggested_projects" class="toc">Suggested Projects</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#mentors" class="toc">Mentors</a></span></div></li></ul>
+</li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h3><a name="announcement_of_participation_in_google_s_summer_of_code" id="announcement_of_participation_in_google_s_summer_of_code">Announcement of participation in Google's Summer of Code</a></h3>
+<div class="level3">
+
+<p>
+ Good news! The gEDA Project has been accepted as a mentoring organization by Googleâ??s Summer of Code program! The alphabetized list of all projects participating in Googleâ??s SoC is presented here:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://code.google.com/soc/"; class="urlextern" title="http://code.google.com/soc/"; rel="nofollow">http://code.google.com/soc/</a> </div>
+</li>
+</ul>
+
+<p>
+ gEDA is listed as â??The gEDA Projectâ??. We are very pleased to be recognized as a participant in the Summer of Code project!
+</p>
+
+<p>
+Now is the time for interested students to get their applications ready. Note that if you want to participate in the SoC, you must apply to Google, not to the gEDA Project. However, prior to making an application to Google, I suggest you contact one of us (Dan, Stuart) who can informally review your project proposal, and suggest a mentor for your project. The mentor will be one of the well-known developers who have worked on the gEDA Project for a while. The list of available mentors is shown at the bottom of this page. Your mentor will be your boss: he will help guide you through the code, refine your project requirements, answer questions, monitor your progress, and rate your performance at the middle and at the end of the project.
+</p>
+
+<p>
+After that, you must apply directly to Google through this web page:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="http://code.google.com/soc/"; class="urlextern" title="http://code.google.com/soc/"; rel="nofollow">http://code.google.com/soc/</a> </div>
+</li>
+</ul>
+
+<p>
+ Good luck with your application, and we look forward to working with you!
+</p>
+
+</div>
+<!-- SECTION "Announcement of participation in Google's Summer of Code" [1-1358] -->
+<h3><a name="google_application_information" id="google_application_information">Google application information.</a></h3>
+<div class="level3">
+
+<p>
+ The gEDA Project invites students to work with us under the auspices of Googleâ??s Summer of Code program! We are a group of professional hardware and software engineers with an interest in developing CAD tools for electronic design under Linux (and other unix flavors). The project is over eight years old, and has matured to the point where our design tools are suitable for use by students, professionals, educators, hobbyists, consultants, and anybody who needs a set of quality EDA tools for Linux. Becoming involved in the gEDA Project is a great way to learn about both software engineering and electronics!
+</p>
+
+<p>
+Details for student applications to Google can be found in the Google SOC Student <acronym title="Frequently Asked Questions">FAQ</acronym>. Students may find the list of gEDA Google SOC project suggestions useful. Note that students apply to Google for project approval, not to the gEDA Project! However, we encourage you to contact us early if you are interested in working on a gEDA Summer of Code project, since we can then hash out the details of your project and help you with your application. To contact us, please post a message on the geda-dev e-mail list. or contact one of the mentors directly.
+</p>
+
+</div>
+<!-- SECTION "Google application information." [1359-2569] -->
+<h3><a name="project_timeline_and_commitment_level" id="project_timeline_and_commitment_level">Project timeline and commitment level</a></h3>
+<div class="level3">
+
+<p>
+ A Google Summer of Code project should be considered a full time job and will require that level of time commitment. In addition, there must be some working code committed in time for the midterm evaluation for a good review. Project Details
+</p>
+
+<p>
+When submitting an application or project proposal, please include the following details about the project:
+</p>
+<ul>
+<li class="level1"><div class="li"> Summary of the project including the end goal. This should be a couple of paragraphs – enough to fully explain what you have in mind. Writing a couple of use-cases will help if you are creating a new program (as opposed to upgrading an existing one).</div>
+</li>
+<li class="level2"><div class="li"> Detail the scope of the project. What do you intend on delivering and what do you not intend on delivering. In best case, this will be a list of features/behaviors your program will possess.</div>
+</li>
+<li class="level2"><div class="li"> Provide a timetable for the project, including milestones (i.e. what features will be working by when).</div>
+</li>
+<li class="level2"><div class="li"> Is this a rewrite/upgrade of existing software or is it a â??from scratchâ?? project.</div>
+</li>
+<li class="level2"><div class="li"> Who is the mentor for your project? Ideally, your mentor will be one of the current gEDA developers, or will be a professor or professional EE familiar with the gEDA project. If you donâ??t know who should mentor your project, then we can help choose somebody for you based upon the project you have chosen.</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Project timeline and commitment level" [2570-3936] -->
+<h3><a name="project_integration" id="project_integration">Project Integration</a></h3>
+<div class="level3">
+
+<p>
+It is important for us to understand how your project will fit into the rest of gEDA. To help us understand this, also include the following information:
+</p>
+<ul>
+<li class="level1"><div class="li"> Which components of gEDA will be affected and require code changes? Examples are â??only PCBâ?? or â??libgeda, gnetlist, gschem, and PCBâ??.</div>
+</li>
+<li class="level2"><div class="li"> Are any new dependencies required over the existing ones? If so, what are they? Are the new dependencies widely ported? (Note that certain gEDA developers frown on new dependencies, so be prepared to thoughtfully defend your choice.)</div>
+</li>
+<li class="level2"><div class="li"> Will these changes force a change in any existing work flows that users may currently be employing?</div>
+</li>
+<li class="level2"><div class="li"> Will your project enable a new work flow or a new feature which has hitherto been lacking in the gEDA Suite?</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Project Integration" [3937-4724] -->
+<h3><a name="student_information" id="student_information">Student Information</a></h3>
+<div class="level3">
+
+<p>
+ Tell us a little about yourself in your application.
+</p>
+<ul>
+<li class="level1"><div class="li"> What programming experience do you have? Please list languages you have used, classwork you have completed, and projects you have completed.</div>
+</li>
+<li class="level2"><div class="li"> What experience do you have with source control systems like <acronym title="Concurrent Versions System">CVS</acronym> and subversion?</div>
+</li>
+<li class="level2"><div class="li"> What experience do you have with software development in a collaborative environment? In particular, if you have worked on open-source projects before, please list some projects to which you have contributed patches.</div>
+</li>
+<li class="level2"><div class="li"> What experience do you have with electronics CAD tools in general, and gEDA in particular?</div>
+</li>
+<li class="level2"><div class="li"> What electronics experience do you have? Please list designs you have completed, courses you have taken, and any electronics-oriented work experience you may have.</div>
+</li>
+<li class="level2"><div class="li"> Are you familiar with the existing codebase for any of the gEDA tools? If so, which one?</div>
+</li>
+<li class="level2"><div class="li"> Do you have a personal web page or a blog which you would like to share with the gEDA developers?</div>
+</li>
+<li class="level2"><div class="li"> Anything else which may be relevant to this project?</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Student Information" [4725-5792] -->
+<h3><a name="suggested_projects" id="suggested_projects">Suggested Projects</a></h3>
+<div class="level3">
+
+<p>
+ The list of suggested projects is available <a href="gsoc2007_projects.html" class="wikilink1" title="gsoc2007_projects">here</a>
+</p>
+
+</div>
+<!-- SECTION "Suggested Projects" [5793-5894] -->
+<h3><a name="mentors" id="mentors">Mentors</a></h3>
+<div class="level3">
+
+<p>
+ Here is a list of mentors for the gEDA Projectâ??s GSoC. Please feel free to contact us with any questions you may have.
+</p>
+<ul>
+<li class="level1"><div class="li"> Dan McMahill (danATmcmahill.net)- Primary GSoC admin, PCB developer, gEDA/gaf developer</div>
+</li>
+<li class="level2"><div class="li"> Stuart Brorson (sdbATcloud9.net) - Backup GSoC admin, gEDA/gaf developer</div>
+</li>
+<li class="level2"><div class="li"> DJ Delorie (djATdelorie.com) - PCB developer</div>
+</li>
+<li class="level2"><div class="li"> Steve Williams (steveATicarus.com) - Icarus Verilog developer</div>
+</li>
+<li class="level2"><div class="li"> Ales Hvezda (ahvezdaATseul.org) - gEDA/gaf developer</div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Mentors" [5895-] --></div>
+</body>
+</html>
diff --git a/docs/wiki/gsoc2007_projects.html b/docs/wiki/gsoc2007_projects.html
new file mode 100644
index 0000000..61e0f65
--- /dev/null
+++ b/docs/wiki/gsoc2007_projects.html
@@ -0,0 +1,650 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en"
+ lang="en" dir="ltr">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+ <title>gsoc2007_projects</title>
+<meta name="generator" content="DokuWiki Release rc2007-05-24" />
+<meta name="robots" content="index,follow" />
+<meta name="date" content="2007-10-28T22:55:15-0400" />
+<meta name="keywords" content="gsoc2007_projects" />
+<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
+<link rel="start" href="http://geda.seul.org/wiki/"; />
+<link rel="contents" href="http://geda.seul.org/wiki/gsoc2007_projects?do=index"; title="Index" />
+<link rel="alternate" type="application/rss+xml" title="Recent Changes" href="http://geda.seul.org/wiki/feed.php"; />
+<link rel="alternate" type="application/rss+xml" title="Current Namespace" href="http://geda.seul.org/wiki/feed.php?mode=list&ns="; />
+<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/gsoc2007_projects"; />
+<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/gsoc2007_projects"; />
+<link rel="stylesheet" media="all" type="text/css" href="lib/exe/css" />
+<link rel="stylesheet" media="screen" type="text/css" href="lib/exe/001css" />
+<link rel="stylesheet" media="print" type="text/css" href="lib/exe/002css" />
+</head>
+<body>
+<div class="dokuwiki export">
+<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="clear">
+
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#geda_gsoc_project_ideas" class="toc">gEDA GSoC Project Ideas</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#project_manager" class="toc">Project manager</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#improve_handling_of_non-copper_layers_in_pcb" class="toc">Improve handling of non-copper layers in pcb</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#gerber_to_pcb_converter" class="toc">Gerber to PCB converter</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#usability_improvements_for_ngspice_gnucap" class="toc">Usability improvements for ngspice/Gnucap</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#parts_manager" class="toc">Parts manager</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#gnetlist_gnetman_support_for_hierarchy" class="toc">Gnetlist/gnetman support for hierarchy</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#libgeda_api_formalization" class="toc">Libgeda API formalization</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#recently_loaded_file_list_for_gschem_and_or_pcb" class="toc">Recently loaded file list for gschem and/or pcb</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#remember_dialog_size_and_positions" class="toc">Remember dialog size and positions</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#show_hidden_attributes_for_selected_components" class="toc">Show hidden attributes for selected components</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#constant_sized_handles_grips" class="toc">Constant sized handles/grips</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#automatically_fill_in_global_attributes_in_gschem" class="toc">Automatically fill in global attributes in gschem</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#visual_feedback_when_pressing_keyboard_accelerators" class="toc">Visual feedback when pressing keyboard accelerators</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#improve_error_messages_in_gschem" class="toc">Improve error messages in gschem</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#global_search_and_replace" class="toc">Global search and replace</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#visual_feedback_for_attached_attributes" class="toc">Visual feedback for attached attributes</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#schematic_and_symbol_modes" class="toc">Schematic and symbol modes</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#movable_symbol_origin" class="toc">Movable symbol origin</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#modify_instantiated_symbols_in_a_schematic" class="toc">Modify instantiated symbols in a schematic</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#finer_grid_when_moving_attributes" class="toc">Finer grid when moving attributes</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#frequently_used_symbols_sidebar" class="toc">Frequently used symbols sidebar</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#add_more_toolbar_buttons" class="toc">Add more toolbar buttons</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#filled_polygon_object" class="toc">Filled polygon object</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#fix_geda_gaf_bugs_and_or_implement_feature_requests" class="toc">Fix gEDA/gaf bugs and/or implement feature requests</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#make_gsch2pcb_use_same_search_paths_as_pcb" class="toc">Make gsch2pcb use same search paths as PCB</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#verilog_vhdl_code_generator_s_for_icarus_verilog" class="toc">Verilog/VHDL code generator[s] for Icarus Verilog</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#create_comprehensive_test_suite_for_entire_geda_suite" class="toc">Create comprehensive test suite for entire gEDA Suite</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#revive_tclspice_add_return_code_to_analysis" class="toc">Revive TCLSpice, add return code to analysis</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#pcb_drc_interface_improvements" class="toc">PCB DRC interface improvements</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#add_enhancements_to_gerbv" class="toc">Add enhancements to gerbv.</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#pcb_autorouter" class="toc">PCB Autorouter</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#improved_and_formalized_mechanism_for_forward_backward_annotation" class="toc">Improved and formalized mechanism for forward/backward annotation</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#ipc_footprint_calculator" class="toc">IPC Footprint Calculator</a></span></div></li></ul>
+</li></ul>
+</li></ul>
+</div>
+</div>
+
+
+
+<h3><a name="geda_gsoc_project_ideas" id="geda_gsoc_project_ideas">gEDA GSoC Project Ideas</a></h3>
+<div class="level3">
+
+<p>
+ This page contains various ideas for projects. You can use these as fodder for creating your application to Google. Also, if you have your own idea, feel free to share it with the gEDA developers – they might like it more than any project on this list!
+</p>
+
+<p>
+Note that some of these projects are too small by themselves to be stand-alone projects. The Summer of Code program is a 3 month program, and youâ??re supposed to treat your project as a full-time job. Applicants should keep that in mind and possibly combine ideas from different projects if one suggested project is too small. To help you, I have graded each project on a scale of 1 to 5, where 1 = too small for a full summer, 3 = roughly enough for a full summer, and 5 = way too large for a full summer. Of course, what takes one programmer one week might take another six months, so any judgement is subjective. However, you can use these ratings to help you figure out which project is the right one for you.
+</p>
+
+<p>
+The vast majority of gEDA Suite programs are written in either C or C++. However, a whole range of scripting languages are used including scheme (guile), perl, python, bourne shell, tcl/tk, and others. <acronym title="Graphical User Interface">GUI</acronym> toolkit use is also fairly broad including GTK+ (this is the primary toolkit of most of the programs), Lesstif, WxWidgets, and others. We are pretty much open to using most languages or <acronym title="Graphical User Interface">GUI</acronym> toolkits for new programs, however some of the projects listed below will require knowledge of a specific language and/or <acronym title="Graphical User Interface">GUI</acronym> toolkit (as they are well established programs).
+</p>
+
+<p>
+Please visit the gEDA Projectâ??s main GSoC page for more info (including contact information).
+</p>
+
+</div>
+<!-- SECTION "gEDA GSoC Project Ideas" [1-1671] -->
+<h3><a name="project_manager" id="project_manager">Project manager</a></h3>
+<div class="level3">
+
+<p>
+gEDA needs a new, top-level project manager. Using this tool, A user would type â??gedaâ?? at the command line (or push a button on his desktop manager), and this program would start a <acronym title="Graphical User Interface">GUI</acronym> which would provide easy, user-friendly access to all design tools. The project manager would implement (at least) the following functionalities:
+</p>
+<ul>
+<li class="level1"><div class="li"> Menu items or buttons to run various gEDA programs like gschem, gattrib, gsch2pcb, PCB, gerbv, ngspice, Gnucap, etc.</div>
+</li>
+<li class="level2"><div class="li"> Manage resource files (i.e. the project manager allows you to edit and write gafrc, gsch2pcb project file, spinit, etc.</div>
+</li>
+<li class="level2"><div class="li"> Enable creation of project archives – i.e. using garchive, but using an intelligent method to gather & archive the symbols & footprints used in the project.</div>
+</li>
+<li class="level2"><div class="li"> Perhaps implement some type of lockfiles, or at least some enforcement of the design flow (good for newbies).</div>
+</li>
+</ul>
+
+<p>
+ Since the project manager is the first program seen by many new users, this program needs a high degree of polish, and should enforce good design practice without getting in the userâ??s way too much.
+</p>
+
+<p>
+Difficulty = 4
+</p>
+
+</div>
+<!-- SECTION "Project manager" [1672-2777] -->
+<h3><a name="improve_handling_of_non-copper_layers_in_pcb" id="improve_handling_of_non-copper_layers_in_pcb">Improve handling of non-copper layers in pcb</a></h3>
+<div class="level3">
+
+<p>
+ PCBâ??s support for non-copper layers needs improvement. In this project, you would add support for more easily-editable non-copper layers. These non-copper layers would be used for things like keepout regions, assembly drawing, and an actual board outline layer that is not just a copper layer. For more thoughts on the issue of layers in PCB, please see database.txt and keepouts.txt
+</p>
+
+<p>
+Difficulty = 2
+</p>
+
+</div>
+<!-- SECTION "Improve handling of non-copper layers in pcb" [2778-3234] -->
+<h3><a name="gerber_to_pcb_converter" id="gerber_to_pcb_converter">Gerber to PCB converter</a></h3>
+<div class="level3">
+
+<p>
+ In this project, the student would create a program which reads a Gerber file, and creates an output file which is a metal layer or footprint editable by PCB. This might be a <acronym title="Practical Extraction and Report Language">Perl</acronym> or Python script. Such a program is very desirable since it gives users the ability to edit legacy designs – i.e. those for which they only have Gerbers.
+</p>
+
+<p>
+Difficulty = 3
+</p>
+
+</div>
+<!-- SECTION "Gerber to PCB converter" [3235-3621] -->
+<h3><a name="usability_improvements_for_ngspice_gnucap" id="usability_improvements_for_ngspice_gnucap">Usability improvements for ngspice/Gnucap</a></h3>
+<div class="level3">
+
+<p>
+ Ngspice and Gnucap are the gEDA Projectâ??s analog circuit simulators. They are both command-line tools, meaning that you type commands into a shell-like program at a prompt. However, some popular commercial simulators support easy simulation and analysis directly from within a schematic capture <acronym title="Graphical User Interface">GUI</acronym>. This method of working is particularly well suited to newbies.
+</p>
+
+<p>
+A new user would like to do the following things inside gschem:
+</p>
+<ul>
+<li class="level1"><div class="li"> Specify what kinds of simulations should be run</div>
+</li>
+<li class="level2"><div class="li"> Specify which voltages and currents should be plotted</div>
+</li>
+<li class="level2"><div class="li"> Start the simulation</div>
+</li>
+</ul>
+
+<p>
+ The simulation runs and the postprocessing may be in an extra program that is triggered by IPC. More thoughts about the project have been entered by Werner Hoch on the gEDA Wiki.
+</p>
+
+<p>
+This project involves tightening the link between gschem and the back-end simulation programs. This might be done using some type of IPC, such as DBUS. Indeed, a preliminary DBUS implementation for gschem ↔ PCB already exists; the student might leverage the DBUS work for this project.
+</p>
+
+<p>
+Difficulty = 3
+</p>
+
+</div>
+<!-- SECTION "Usability improvements for ngspice/Gnucap" [3622-4730] -->
+<h3><a name="parts_manager" id="parts_manager">Parts manager</a></h3>
+<div class="level3">
+
+<p>
+ In this project, you would create a parts manager that takes a graphical symbol and a physical footprint, and marries the two to produce a heavy part. In addition, this tool should be able to support multiple backend flows. By this I mean that the parts manager should be able to also indicate how the symbol should be netlisted for spice, gnucap, or other backends. If possible it would be nice to integrate this into gschem in a way that allowed symbols to be placed and the footprint attribute to come up with a list of choices.
+</p>
+
+<p>
+Another possible direction for improved parts management is to create a program like gattrib (or perhaps just re-use gattrib) which reads a bunch of .sch files, and also interfaces to an <acronym title="Structured Query Language">SQL</acronym> database holding all info about parts (including spice models, footprints, .pdf datasheets, etc) . The program would then allow users to perform database searches for footprints and other attributes stored as columns in the database.
+</p>
+
+<p>
+Difficulty = 4
+</p>
+
+</div>
+<!-- SECTION "Parts manager" [4731-5730] -->
+<h3><a name="gnetlist_gnetman_support_for_hierarchy" id="gnetlist_gnetman_support_for_hierarchy">Gnetlist/gnetman support for hierarchy</a></h3>
+<div class="level3">
+
+<p>
+ The goal of this project is to create a scalable, professional-grade netlister. The project might involve re-writing gnetlist to enable hierarchical designs, or might involve upgrading â??gnetmanâ?? to incorporate scripted back-ends. The upgrade would be done with an eye towards scalability. Ideally, highly capable and efficient internal data structures and methods for accessing the netlist database should be used. Then a scheme/guile <acronym title="Application Programming Interface">API</acronym> provided for an external script engine. (It may be beneficial to use swig to allow easy interfacing to multiple scripting languages.) The idea is to produce a netlister capable of handling large, hierarchical designs while still allowing users to write their own netlisters for their favorite netlist format (as gnetlist does now).
+</p>
+
+<p>
+Gnetman is probably the logical starting point since the database was designed by someone with a lot of experience in EDA, and it uses datadraw which is a proven high power CASE tool. However, the student may take whatever approach he wishes, but should provide a strong argument that his approach makes sense before starting coding. In any event, It will be important to provide a compatibility <acronym title="Application Programming Interface">API</acronym> for the existing backends while providing a more high power and flexible <acronym title="Application Programming Interface">API</acronym> for new backends and improvements of the old ones.
+</p>
+
+<p>
+Difficulty = 3
+</p>
+
+</div>
+<!-- SECTION "Gnetlist/gnetman support for hierarchy" [5731-7097] -->
+<h3><a name="libgeda_api_formalization" id="libgeda_api_formalization">Libgeda API formalization</a></h3>
+<div class="level3">
+
+<p>
+ In this project, you would expand libgeda (if needed) to provide a complete enough guile interface to be able to do more complex database manipulations. One use would be to have a back annotation tool that used libgeda instead of relying on perl. The problem with perl is that youâ??ve involved Yet Another Gschem Parser. This actually may be combined with the previous project about rewriting the gnetlist internals.
+</p>
+
+<p>
+Difficulty = 3
+</p>
+
+</div>
+<!-- SECTION "Libgeda API formalization" [7098-7567] -->
+<h3><a name="recently_loaded_file_list_for_gschem_and_or_pcb" id="recently_loaded_file_list_for_gschem_and_or_pcb">Recently loaded file list for gschem and/or pcb</a></h3>
+<div class="level3">
+
+<p>
+ Presently gschem and pcb do not present a list of recently loaded files in the file menu. It would be nice if gschem and/or pcb kept track of the last few files a user loaded. This is a common feature found in other programs.
+</p>
+
+<p>
+Difficulty = 1
+</p>
+
+</div>
+<!-- SECTION "Recently loaded file list for gschem and/or pcb" [7568-7869] -->
+<h3><a name="remember_dialog_size_and_positions" id="remember_dialog_size_and_positions">Remember dialog size and positions</a></h3>
+<div class="level3">
+
+<p>
+ gschem and pcb dialogs should remember their size and position. Currently they do not remember anything about their position and size and several users have complained since they have to reposition and/or resize the dialog boxes every time they are opened..
+</p>
+
+<p>
+Difficulty = 1
+</p>
+
+</div>
+<!-- SECTION "Remember dialog size and positions" [7870-8190] -->
+<h3><a name="show_hidden_attributes_for_selected_components" id="show_hidden_attributes_for_selected_components">Show hidden attributes for selected components</a></h3>
+<div class="level3">
+
+<p>
+ In gschem, please add a why to show hidden text for just one symbol only. Currently [en] will show all the hidden text for all symbols and that makes a real visual mess. Implement this by just showing the hidden text for the currently selected symbols.
+</p>
+
+<p>
+Difficulty = 1
+</p>
+
+</div>
+<!-- SECTION "Show hidden attributes for selected components" [8191-8518] -->
+<h3><a name="constant_sized_handles_grips" id="constant_sized_handles_grips">Constant sized handles/grips</a></h3>
+<div class="level3">
+
+<p>
+ In gschem, the size of the handles for lines, nets, and objects scale with increasing zoom. Thus for small lines the handles overlap, and if I zoom in closely, it becomes very hard to pick the right object to manipulate. Please let the size of the handles be constant, regardless of the zoom factor. This is virtually how all vector graphics applications work.
+</p>
+
+<p>
+Difficulty = 1
+</p>
+
+</div>
+<!-- SECTION "Constant sized handles/grips" [8519-8936] -->
+<h3><a name="automatically_fill_in_global_attributes_in_gschem" id="automatically_fill_in_global_attributes_in_gschem">Automatically fill in global attributes in gschem</a></h3>
+<div class="level3">
+
+<p>
+ In gschem, implement a mechanism that would (when turned enabled) automatically fill in proper global attributes for the design. These attributes could be the date of the last modification, name of the project, author, number of sheets, etc…
+</p>
+
+<p>
+Difficulty = 1 to 2
+</p>
+
+</div>
+<!-- SECTION "Automatically fill in global attributes in gschem" [8937-9263] -->
+<h3><a name="visual_feedback_when_pressing_keyboard_accelerators" id="visual_feedback_when_pressing_keyboard_accelerators">Visual feedback when pressing keyboard accelerators</a></h3>
+<div class="level3">
+
+<p>
+ In gschem, please give some feedback when a user presses one of the keyboard accelerator keys. Currently gschem allows for multiple key presses to represent a single command. Sometimes it is hard to remember which one you have pressed. Maybe a little area in the status bar can output this information.
+</p>
+
+<p>
+Difficulty = 1
+</p>
+
+</div>
+<!-- SECTION "Visual feedback when pressing keyboard accelerators" [9264-9646] -->
+<h3><a name="improve_error_messages_in_gschem" id="improve_error_messages_in_gschem">Improve error messages in gschem</a></h3>
+<div class="level3">
+
+<p>
+ Improve error messages in gschem when a rc file doesnâ??t load correctly. Currently the error messages are cryptic and not useful at all. There are several other places in gschem where the error messages could be vastly improved.
+</p>
+
+<p>
+Difficulty = 1
+</p>
+
+</div>
+<!-- SECTION "Improve error messages in gschem" [9647-9935] -->
+<h3><a name="global_search_and_replace" id="global_search_and_replace">Global search and replace</a></h3>
+<div class="level3">
+
+<p>
+ Add a dialog box that lets you do a global search and replace. Currently you can do a find for a specific attribute, but several users have asked if gschem could also provide a way of doing a replace operation as well.
+</p>
+
+<p>
+Difficulty = 1 to 2
+</p>
+
+</div>
+<!-- SECTION "Global search and replace" [9936-10213] -->
+<h3><a name="visual_feedback_for_attached_attributes" id="visual_feedback_for_attached_attributes">Visual feedback for attached attributes</a></h3>
+<div class="level3">
+
+<p>
+ In gschem, add some sort of visual feedback to tell the user which attribute is attached to which component. This would be useful since sometimes you move attributes/components around and things get a little bit separated distance wise.
+</p>
+
+<p>
+Difficulty = 1 to 2
+</p>
+
+</div>
+<!-- SECTION "Visual feedback for attached attributes" [10214-10523] -->
+<h3><a name="schematic_and_symbol_modes" id="schematic_and_symbol_modes">Schematic and symbol modes</a></h3>
+<div class="level3">
+
+<p>
+ Add schematic and symbol modes to gschem. Right now users can do invalid things like add a net or bus inside a symbol and gschem allows this quite happily. If there was a symbol mode that disallowed certain actions, then users will not be able to hurt themselves so easily when creating symbols. Like wise a schematic mode wouldnâ??t allow certain operations (such as adding a pin).
+</p>
+
+<p>
+Difficulty = 2 to 3
+</p>
+
+</div>
+<!-- SECTION "Schematic and symbol modes" [10524-10964] -->
+<h3><a name="movable_symbol_origin" id="movable_symbol_origin">Movable symbol origin</a></h3>
+<div class="level3">
+
+<p>
+ Add the ability to move the origin of a symbol in gschem. Right now the origin is always at 0,0 and users have to translate the symbol to the origin. It would be nice if the origin was movable so that you wouldnâ??t have to translate the symbol manually anymore. This would also allow the user to pick the insert point of the symbol when adding components to a schematic.
+</p>
+
+<p>
+Difficulty = 2 to 3
+</p>
+
+</div>
+<!-- SECTION "Movable symbol origin" [10965-11389] -->
+<h3><a name="modify_instantiated_symbols_in_a_schematic" id="modify_instantiated_symbols_in_a_schematic">Modify instantiated symbols in a schematic</a></h3>
+<div class="level3">
+
+<p>
+ Add the ability to move pins/attributes/whatever on instantiated components in a schematic. This one is quite tricky, but it would allow for various things that people have been requesting (this might be a good foundation for a greatly improved back annotation mechanism from PCB).
+</p>
+
+<p>
+Difficulty = 3 to 4
+</p>
+
+</div>
+<!-- SECTION "Modify instantiated symbols in a schematic" [11390-11747] -->
+<h3><a name="finer_grid_when_moving_attributes" id="finer_grid_when_moving_attributes">Finer grid when moving attributes</a></h3>
+<div class="level3">
+
+<p>
+ In gschem, add a finer grid when moving attributes or text around.
+</p>
+
+<p>
+Difficulty = 2
+</p>
+
+</div>
+<!-- SECTION "Finer grid when moving attributes" [11748-11876] -->
+<h3><a name="frequently_used_symbols_sidebar" id="frequently_used_symbols_sidebar">Frequently used symbols sidebar</a></h3>
+<div class="level3">
+
+<p>
+ Add a frequently used symbols sidebar to gschem that is dynamically loaded and/or can be preloaded from an rc file. Several people have asked for this since using the component selection dialog box can be time consuming for recently used/needed components. This is a <acronym title="Graphical User Interface">GUI</acronym> heavy project idea.
+</p>
+
+<p>
+Difficulty = 3
+</p>
+
+</div>
+<!-- SECTION "Frequently used symbols sidebar" [11877-12227] -->
+<h3><a name="add_more_toolbar_buttons" id="add_more_toolbar_buttons">Add more toolbar buttons</a></h3>
+<div class="level3">
+
+<p>
+ Adding some more useful buttons to the gschem toolbar. Typical functionalities that gschem does not have on the toolbar:
+</p>
+<ul>
+<li class="level1"><div class="li"> Up/down schematic/symbol</div>
+</li>
+<li class="level2"><div class="li"> Add various graphical objects (maybe make these only appear in symbol editing mode)</div>
+</li>
+<li class="level2"><div class="li"> Edit component attributes</div>
+</li>
+<li class="level2"><div class="li"> Copy/paste/delete</div>
+</li>
+<li class="level2"><div class="li"> Page forward/back</div>
+</li>
+<li class="level2"><div class="li"> Component mirror/rotate</div>
+</li>
+<li class="level2"><div class="li"> Zoom in/out</div>
+</li>
+</ul>
+
+<p>
+ It would be really nice if the toolbar buttons were configurable either on the fly or through an rc file.
+</p>
+
+<p>
+Difficulty = 2 to 3
+</p>
+
+</div>
+<!-- SECTION "Add more toolbar buttons" [12228-12763] -->
+<h3><a name="filled_polygon_object" id="filled_polygon_object">Filled polygon object</a></h3>
+<div class="level3">
+
+<p>
+ Adding a filled polygon graphical object type to the gschem symbol file format and, of course, gschem would be a nice project. This would be useful for filled arrows (transistors) and a filled triangle for diodes.
+</p>
+
+<p>
+Difficulty = 2 to 3
+</p>
+
+</div>
+<!-- SECTION "Filled polygon object" [12764-13032] -->
+<h3><a name="fix_geda_gaf_bugs_and_or_implement_feature_requests" id="fix_geda_gaf_bugs_and_or_implement_feature_requests">Fix gEDA/gaf bugs and/or implement feature requests</a></h3>
+<div class="level3">
+
+<p>
+ There are several bugs listed at the gEDA/gaf bug tracker and feature request at the gEDA/gaf feature request tracker that could potentially make good student projects. Some of the bugs/feature requests are quite feasible to finish in one summer, while others are way beyond what is possible to finish in one summer. However some of the bugs/feature requests are trivial to implement, so several might need to be combined together to fill up the entire summer.
+</p>
+
+<p>
+There are other bug/feature request trackers for the other gEDA affiliated programs (such as PCB or Icarus Verilog) that contain possible project ideas as well. Selecting bugs or features requests to work on from any of the trackers needs to be approved and agreed upon by the appropriate mentor(s) to make sure it is appropriate, feasible, or even fixable.
+</p>
+
+<p>
+Difficulty = various
+</p>
+
+</div>
+<!-- SECTION "Fix gEDA/gaf bugs and/or implement feature requests" [13033-13938] -->
+<h3><a name="make_gsch2pcb_use_same_search_paths_as_pcb" id="make_gsch2pcb_use_same_search_paths_as_pcb">Make gsch2pcb use same search paths as PCB</a></h3>
+<div class="level3">
+
+<p>
+ Gsch2pcb is a key program in the gEDA Suite. It made it relatively easy to take a schematic drawn using gschem and prepare it for layout using PCB. It has played an important role in popularizing gEDA for PCB design amongst students and hobbyists. However, it has a flaw: It uses footprint search paths which can be different from those in PCB. Users are sometimes perplexed that they can see footprints in PCB, but gsch2pcb claims it canâ??t find them. Or gsch2pcb gives them footprints different from the ones they expect to see based upon a footprint search using PCB. In addition, gsch2pcb needs to be able to parse the PCB .pcb files directly. This means many file format changes trigger a required update to gsch2pcb.
+</p>
+
+<p>
+It would be more preferable for gsch2pcb to be able to query PCB through a well defined and stable <acronym title="Application Programming Interface">API</acronym> to find out the information it needs. In addition, rather than trying to duplicate PCBâ??s mechanism for creating a new board and locating footprints, gsch2pcb should simply instruct PCB to peform these operations. The goal is to provide a stable interface between the tools and impose appropriate abstraction barriers in between.
+</p>
+
+<p>
+Difficulty = 2
+</p>
+
+</div>
+<!-- SECTION "Make gsch2pcb use same search paths as PCB" [13939-15164] -->
+<h3><a name="verilog_vhdl_code_generator_s_for_icarus_verilog" id="verilog_vhdl_code_generator_s_for_icarus_verilog">Verilog/VHDL code generator[s] for Icarus Verilog</a></h3>
+<div class="level3">
+
+<p>
+ A Verilog code generator targets to emit simplified Verilog code. This has use as a Verilog â??reducerâ?? (or obfuscator) to translate verilog to more simplified forms. It can also be used to support other Verilog run time engines.
+</p>
+
+<p>
+A variant of this is to generate VHDL, and thus get a VHDL translation from the Verilog input.
+</p>
+
+<p>
+This task remains pretty clear of the core Icarus Verilog compiler and just works with loadable code generators. SDF Parser/Annotator for Icarus Verilog
+</p>
+
+<p>
+SDF parser to parse SDF files generated by typical SDF sources such as Xilinx ISE. It should be possible to invoke this from an $sdf_annotate system task and match paths with the specify paths actually available (via vpi) in the design.
+</p>
+
+<p>
+The specify paths are now available in the vvp run time, some work is needed to offer up the VPI objects that an SDF annotator needs.
+</p>
+
+<p>
+This task can mostly be done in C and loaded as a VPI module. There is some work needed in the vvp run time engine to make the paths available to VPI modules, though. Macros with Arguments
+</p>
+
+<p>
+The Icarus Verilog preprocessor currently does not support macros with arguments. A good task would be to add support for arguments. This task would work entirely within the ivlpp program that does the preprocessing for the ivl core. It is written in C and bison and would be a good task for someone not an expert in Verilog or EE in general. Upgrading/resurrecting the analog waveform viewer â??gwaveâ??
+</p>
+
+<p>
+In this project, you would work on improving and modernizing the analog waveform viewer â??gwaveâ??. Several improvements are desirable, including (but not limited to):
+</p>
+<ul>
+<li class="level1"><div class="li"> Remove requirement for guile-gtk (which is basically dead I as far as I can tell).</div>
+</li>
+<li class="level2"><div class="li"> Adding support for hdf5 (as a way to help move towards a better than ascii format that is non proprietary).</div>
+</li>
+<li class="level2"><div class="li"> Add a waveform calculator that lets you do things like add waveforms, do fftâ??s, etc.</div>
+</li>
+<li class="level2"><div class="li"> Provide a way for the tool to be easily extensible by the user. Some examples are custom grid lines (smith, nichols, polar, etc), custom cursor functions (smith, nichols, etc), and complex measurement and waveform processing functions.</div>
+</li>
+<li class="level2"><div class="li"> Support for digital as well as analog signals. For example you may have a digital bus present in a mixed signal circuit and would like to plot the value on the bus as simply a digital transition diagram with annotated bus values, or you may wish to plot the bus value as a quantized value. </div>
+</li>
+</ul>
+
+<p>
+ Note that the gEDA Project needs a gwave mentor.
+</p>
+
+<p>
+Difficulty = 3
+</p>
+
+</div>
+<!-- SECTION "Verilog/VHDL code generator[s] for Icarus Verilog" [15165-17735] -->
+<h3><a name="create_comprehensive_test_suite_for_entire_geda_suite" id="create_comprehensive_test_suite_for_entire_geda_suite">Create comprehensive test suite for entire gEDA Suite</a></h3>
+<div class="level3">
+
+<p>
+ This project encompasses the functionality of the entire gEDA PCB design flow. You would develop a test framework for as much of these tools as possible. This likely means creating a large regression test suite. Some examples are sets of layouts (using PCB) that just barely pass and just barely fail each of the different DRC checks, generate BOMâ??s, x-y files, generate gerbers and maybe use gerbv to do a graphical xor against a â??goldenâ?? file. For gnetlist, reference netlists that have been placed into some canonical form should be generated from gschem schematics (.sch files).
+</p>
+
+<p>
+This project should be fun for a hardware hacker, since it would involve creating all kinds of strange circuit designs, and you would learn the detailed ins-and-outs of all tools in the gEDA Suite!
+</p>
+
+<p>
+Difficulty = 3
+</p>
+
+</div>
+<!-- SECTION "Create comprehensive test suite for entire gEDA Suite" [17736-18599] -->
+<h3><a name="revive_tclspice_add_return_code_to_analysis" id="revive_tclspice_add_return_code_to_analysis">Revive TCLSpice, add return code to analysis</a></h3>
+<div class="level3">
+
+<p>
+ TCLSpice is a version of ngspice (the classic analog simulation program) in which the SPICE commands and cards have been exported to TCL. The idea is that you can then write a scripted SPICE analysis using TCL, a feature which is extremely valuable for performing circuit optimizations, repeated circuit simulations for Monte Carlo or corner-case evaluation, and so on.
+</p>
+
+<p>
+A problem with TCLSpice is that the internal data structures do not provide return codes when called, so it is impossible to see if an analysis has run successfully or now. In this project, the student would fix tclspice so that every analysis would provide a return code reporting success or failure.
+</p>
+
+<p>
+Difficulty = 4
+</p>
+
+</div>
+<!-- SECTION "Revive TCLSpice, add return code to analysis" [18600-19345] -->
+<h3><a name="pcb_drc_interface_improvements" id="pcb_drc_interface_improvements">PCB DRC interface improvements</a></h3>
+<div class="level3">
+
+<p>
+ Improve the DRC interface for PCB. Perhaps have a DRC layer that gets generated when you run DRC. Then you could have an interface that lets you step through them and see on that layer, exactly what failed. Maybe this could be combined with making the DRC checks more unit testable.
+</p>
+
+<p>
+Difficulty = 2
+</p>
+
+</div>
+<!-- SECTION "PCB DRC interface improvements" [19346-19687] -->
+<h3><a name="add_enhancements_to_gerbv" id="add_enhancements_to_gerbv">Add enhancements to gerbv.</a></h3>
+<div class="level3">
+
+<p>
+ Gerbv is gEDAâ??s Gerber viewer. It is a good tool for inspecting Gerbers. Adding a different pop-up box displaying the properties of objects you click on (i.e. round pad diameters, track widths, etc.) would be invaluable.
+</p>
+
+<p>
+Difficulty = ?
+</p>
+
+</div>
+<!-- SECTION "Add enhancements to gerbv." [19688-19963] -->
+<h3><a name="pcb_autorouter" id="pcb_autorouter">PCB Autorouter</a></h3>
+<div class="level3">
+
+<p>
+ PCB currently incorporates a simple autorouter. However, a topological autorouter would represent a significant improvement over the existing autorouter. In this ambitious project, the student would create a topological autorouter for PCB.
+</p>
+
+<p>
+Difficulty = 5
+</p>
+
+</div>
+<!-- SECTION "PCB Autorouter" [19964-20246] -->
+<h3><a name="improved_and_formalized_mechanism_for_forward_backward_annotation" id="improved_and_formalized_mechanism_for_forward_backward_annotation">Improved and formalized mechanism for forward/backward annotation</a></h3>
+<div class="level3">
+
+<p>
+ Add hooks into gschem needed to fully support things like backannotation of simulation results and click-to-plot results. Specifically, this would enable you to draw a schematic in gschem, then simulate it in ngspice without leaving gschem. The simulation plots would then appear in a graphical pop-up window.
+</p>
+
+<p>
+Difficulty = 3
+</p>
+
+</div>
+<!-- SECTION "Improved and formalized mechanism for forward/backward annotation" [20247-20650] -->
+<h3><a name="ipc_footprint_calculator" id="ipc_footprint_calculator">IPC Footprint Calculator</a></h3>
+<div class="level3">
+
+<p>
+ Build a footprint calculator that can take the IPC rules and produce a pcb footprint. Preferably write this in a way where the core program is independent of a gui so that you can script it for generating entire large families of footprints or hook it up to a <acronym title="Graphical User Interface">GUI</acronym> of choice (lesstif, gtk, maybe even cgi). Would require the purchase of IPC-7351 (approximately U.S.A. $100)and verifying that one is allowed to produce such a calculator.
+</p>
+
+<p>
+Difficulty = 2
+</p>
+
+</div>
+<!-- SECTION "IPC Footprint Calculator" [20651-] --></div>
+</body>
+</html>
diff --git a/docs/wiki/index.html b/docs/wiki/index.html
index 6297660..f75649e 100644
--- a/docs/wiki/index.html
+++ b/docs/wiki/index.html
@@ -7,7 +7,7 @@
<title>start</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-07-27T08:15:10-0400" />
+<meta name="date" content="2007-12-20T11:26:01-0500" />
<meta name="keywords" content="start" />
<link rel="search" type="application/opensearchdescription+xml" href="lib/exe/opensearch" title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -34,6 +34,7 @@
<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="#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>
<li class="level2"><div class="li"><span class="li"><a href="#translations" class="toc">Translations</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#geda_users" class="toc">gEDA Users</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#about_this_wiki" class="toc">About this Wiki</a></span></div></li></ul>
@@ -77,7 +78,7 @@ These are the official project docs. They have been converted from LaTeX and <a
</ul>
</div>
-<!-- SECTION "Official Project documentation" [1161-1461] -->
+<!-- SECTION "Official Project documentation" [1161-1460] -->
<h2><a name="faqs_and_informal_project_documentation" id="faqs_and_informal_project_documentation">FAQs and Informal Project Documentation</a></h2>
<div class="level2">
@@ -113,10 +114,12 @@ 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_tasks.html" class="wikilink1" title="geda:tasks">Tasks</a> : Top-level list of jobs/tasks that need help.</div>
</li>
+<li class="level1"><div class="li"> <a href="geda_guile_scripting.html" class="wikilink1" title="geda:guile_scripting">Guile scripting</a> : Guile functions & variables provided by the gEDA tools.</div>
+</li>
</ul>
</div>
-<!-- SECTION "FAQs and Informal Project Documentation" [1462-2910] -->
+<!-- SECTION "FAQs and Informal Project Documentation" [1461-2998] -->
<h2><a name="developer_documentation" id="developer_documentation">Developer Documentation</a></h2>
<div class="level2">
@@ -145,7 +148,7 @@ These are pages concerning the development of the gEDA suite.
</ul>
</div>
-<!-- SECTION "Developer Documentation" [2911-4080] -->
+<!-- SECTION "Developer Documentation" [2999-4168] -->
<h2><a name="talks" id="talks">Talks</a></h2>
<div class="level2">
@@ -158,7 +161,20 @@ These are slides of presentations done about gEDA. They provide a good top-leve
</ul>
</div>
-<!-- SECTION "Talks" [4081-4320] -->
+<!-- SECTION "Talks" [4169-4410] -->
+<h2><a name="google_summer_of_code" id="google_summer_of_code">Google Summer of Code</a></h2>
+<div class="level2">
+
+<p>
+ The gEDA project participated in the Google Summer of Code for the following years:
+</p>
+<ul>
+<li class="level1"><div class="li"> <a href="gsoc2007.html" class="wikilink1" title="gsoc2007">2007</a></div>
+</li>
+</ul>
+
+</div>
+<!-- SECTION "Google Summer of Code" [4411-4556] -->
<h2><a name="translations" id="translations">Translations</a></h2>
<div class="level2">
<ul>
@@ -169,7 +185,7 @@ These are slides of presentations done about gEDA. They provide a good top-leve
</ul>
</div>
-<!-- SECTION "Translations" [4321-4436] -->
+<!-- SECTION "Translations" [4557-4672] -->
<h2><a name="geda_users" id="geda_users">gEDA Users</a></h2>
<div class="level2">
@@ -182,7 +198,7 @@ The so-called â??Free Dogâ?? organization ( <a href="http://freeedaug.org/"; clas
</p>
</div>
-<!-- SECTION "gEDA Users" [4437-4806] -->
+<!-- SECTION "gEDA Users" [4673-5042] -->
<h2><a name="about_this_wiki" id="about_this_wiki">About this Wiki</a></h2>
<div class="level2">
@@ -195,6 +211,6 @@ Anyone is welcome to contribute. Unlike wikipedia there is no button to create a
</p>
</div>
-<!-- SECTION "About this Wiki" [4807-] --></div>
+<!-- SECTION "About this Wiki" [5043-] --></div>
</body>
</html>
diff --git a/docs/wiki/lib/exe/001css b/docs/wiki/lib/exe/001css
index 7b22b2d..7622e88 100644
--- a/docs/wiki/lib/exe/001css
+++ b/docs/wiki/lib/exe/001css
@@ -1 +1 @@
-a.interwiki{background:transparent url('../images/interwiki.png') 0px 1px no-repeat;padding-left:16px;}a.iw_wp{background-image:url('../images/interwiki/wp.gif')}a.iw_wpde{background-image:url('../images/interwiki/wpde.gif')}a.iw_wpmeta{background-image:url('../images/interwiki/wpmeta.gif')}a.iw_doku{background-image:url('../images/interwiki/doku.gif')}a.iw_sb{background-image:url('../images/interwiki/sb.gif')}a.iw_amazon{background-image:url('../images/interwiki/amazon.gif')}a.iw_amazon_de{background-image:url('../images/interwiki/amazon.de.gif')}a.iw_amazon_uk{background-image:url('../images/interwiki/amazon.uk.gif')}a.iw_phpfn{background-image:url('../images/interwiki/phpfn.gif')}a.iw_dokubug{background-image:url('../images/interwiki/dokubug.gif')}a.iw_coral{background-image:url('../images/interwiki/coral.gif')}a.iw_google{background-image:url('../images/interwiki/google.gif')}a.iw_meatball{background-image:url('../images/interwiki/meatball.gif')}a.iw_wiki{background-image:url('../images/interwiki/wiki.gif')}a.mediafile{background:transparent url('../images/fileicons/file.png') 0px 1px no-repeat;padding-left:18px;padding-bottom:1px;}a.mf_jpg{background-image:url('../images/fileicons/jpg.png')}a.mf_jpeg{background-image:url('../images/fileicons/jpeg.png')}a.mf_gif{background-image:url('../images/fileicons/gif.png')}a.mf_png{background-image:url('../images/fileicons/png.png')}a.mf_tgz{background-image:url('../images/fileicons/tgz.png')}a.mf_tar{background-image:url('../images/fileicons/tar.png')}a.mf_gz{background-image:url('../images/fileicons/gz.png')}a.mf_zip{background-image:url('../images/fileicons/zip.png')}a.mf_rar{background-image:url('../images/fileicons/rar.png')}a.mf_pdf{background-image:url('../images/fileicons/pdf.png')}a.mf_ps{background-image:url('../images/fileicons/ps.png')}a.mf_doc{background-image:url('../images/fileicons/doc.png')}a.mf_xls{background-image:url('../images/fileicons/xls.png')}a.mf_ppt{background-image:url('../images/fileicons/ppt.png')}a.mf_rtf{background-image:url('../images/fileicons/rtf.png')}a.mf_swf{background-image:url('../images/fileicons/swf.png')}a.mf_rpm{background-image:url('../images/fileicons/rpm.png')}a.mf_deb{background-image:url('../images/fileicons/deb.png')}a.mf_sxw{background-image:url('../images/fileicons/sxw.png')}a.mf_sxc{background-image:url('../images/fileicons/sxc.png')}a.mf_sxi{background-image:url('../images/fileicons/sxi.png')}a.mf_sxd{background-image:url('../images/fileicons/sxd.png')}a.mf_odc{background-image:url('../images/fileicons/odc.png')}a.mf_odf{background-image:url('../images/fileicons/odf.png')}a.mf_odg{background-image:url('../images/fileicons/odg.png')}a.mf_odi{background-image:url('../images/fileicons/odi.png')}a.mf_odp{background-image:url('../images/fileicons/odp.png')}a.mf_ods{background-image:url('../images/fileicons/ods.png')}a.mf_odt{background-image:url('../images/fileicons/odt.png')}div.clearer{clear:both;line-height:0px;height:0;overflow:hidden;}div.no{display:inline;margin:0;padding:0;}.hidden{display:none;}div.error{background:#fcc url('../images/error.png') 0.5em 0px no-repeat;color:#000;border-bottom:1px solid #faa;font-size:90%;margin:0;padding-left:3em;overflow:hidden;}div.info{background:#ccf url('../images/info.png') 0.5em 0px no-repeat;color:#000;border-bottom:1px solid #aaf;font-size:90%;margin:0;padding-left:3em;overflow:hidden;}div.success{background:#cfc url('../images/success.png') 0.5em 0px no-repeat;color:#000;border-bottom:1px solid #afa;font-size:90%;margin:0;padding-left:3em;overflow:hidden;}div.notify{background:#ffc url('../images/notify.png') 0.5em 0px no-repeat;color:#000;border-bottom:1px solid #ffa;font-size:90%;margin:0;padding-left:3em;overflow:hidden;}.medialeft{float:left;}.mediaright{float:right;}.mediacenter{display:block;margin-left:auto;margin-right:auto;}.leftalign{text-align:left;}.centeralign{text-align:center;}.rightalign{text-align:right;}em.u{font-style:normal;text-decoration:underline;}em em.u{font-style:italic;}.code .br0{color:#6c6;}.code .co1{color:#808080;font-style:italic;}.code .co2{color:#808080;font-style:italic;}.code .coMULTI{color:#808080;font-style:italic;}.code .es0{color:#009;font-weight:bold;}.code .kw1{color:#b1b100;}.code .kw2{color:#000;font-weight:bold;}.code .kw3{color:#006;}.code .kw4{color:#933;}.code .kw5{color:#00f;}.code .me0{color:#060;}.code .nu0{color:#c6c;}.code .re0{color:#00f;}.code .re1{color:#00f;}.code .re2{color:#00f;}.code .re4{color:#099;}.code .sc0{color:#0bd;}.code .sc1{color:#db0;}.code .sc2{color:#090;}.code .st0{color:#f00;}div.dokuwiki div#spell__suggest{position:absolute;left:0;top:0;display:none;z-index:2;}div.dokuwiki div#spell__result{display:none;font-family:monospace;overflow:auto;z-index:1;}#acl__manager label{text-align:left;font-weight:normal;display:inline;}#acl__manager table{margin-left:10%;width:80%;}#config__manager div.success,#config__manager div.error,#config__manager div.info{background-position:0.5em;padding:0.5em;text-align:center;}#config__manager fieldset{margin:1em;width:auto;margin-bottom:2em;background-color:#dee7ec;color:#000;padding:0 1em;}#config__manager legend{font-size:1.25em;}#config__manager form{}#config__manager table{margin:1em 0;width:100%;}#config__manager fieldset td{text-align:left;}#config__manager fieldset td.value{width:30em;}#config__manager td input.edit{width:30em;}#config__manager td select.edit{}#config__manager td textarea.edit{width:27.5em;height:4em;}#config__manager tr .input,#config__manager tr input,#config__manager tr textarea,#config__manager tr select{background-color:#fff;color:#000;}#config__manager tr.default .input,#config__manager tr.default input,#config__manager tr.default textarea,#config__manager tr.default select,#config__manager .selectiondefault{background-color:#cdf;color:#000;}#config__manager tr.protected .input,#config__manager tr.protected input,#config__manager tr.protected textarea,#config__manager tr.protected select,#config__manager tr.protected .selection{background-color:#fcc!important;color:#000 !important;}#config__manager td.error{background-color:red;color:#000;}#config__manager .selection{width:14.8em;float:left;margin:0 0.3em 2px 0;}#config__manager .selection label{float:right;width:14em;font-size:90%;}* html #config__manager .selection label{padding-top:2px;}#config__manager .selection input.checkbox{padding-left:0.7em;}#config__manager .other{clear:both;padding-top:0.5em;}#config__manager .other label{padding-left:2px;font-size:90%;}#plugin__manager{}#plugin__manager h2{margin-left:0;}#plugin__manager form{display:block;margin:0;padding:0;}#plugin__manager legend{display:none;}#plugin__manager fieldset{width:auto;}#plugin__manager .button{margin:0;}#plugin__manager p,#plugin__manager label{text-align:left;}#plugin__manager .hidden{display:none;}#plugin__manager .new{background:#dee7ec;}#plugin__manager input[disabled]{color:#ccc;border-color:#ccc;}#plugin__manager .pm_menu,#plugin__manager .pm_info{margin-left:0;text-align:left;}#plugin__manager .pm_menu{float:left;width:48%;}#plugin__manager .pm_info{float:right;width:50%;}#plugin__manager .common{}#plugin__manager .common form{}#plugin__manager .common fieldset{margin:0;padding:0 0 1.0em 0;text-align:left;border:none;}#plugin__manager .common label{padding:0 0 0.5em 0;}#plugin__manager .common input{}#plugin__manager .common input.edit{width:24em;margin:0.5em;}#plugin__manager .common .button{}#plugin__manager form.plugins{}#plugin__manager .plugins fieldset{color:#000;background:#fff;text-align:right;border-top:none;border-right:none;border-left:none;}#plugin__manager .plugins fieldset.protected{background:#fdd;color:#000;}#plugin__manager .plugins fieldset.disabled{background:#e0e0e0;color:#a8a8a8;}#plugin__manager .plugins .legend{color:#000;background:inherit;display:block;margin:0;padding:0;font-size:1em;line-height:1.4em;font-weight:normal;text-align:left;float:left;padding:0;clear:none;}#plugin__manager .plugins .button{font-size:95%;}#plugin__manager .plugins fieldset.buttons{border:none;}#plugin__manager .plugins fieldset.buttons .button{float:left;}#plugin__manager .pm_info h3{margin-left:0;}#plugin__manager .pm_info dl{margin:1em 0;padding:0;}#plugin__manager .pm_info dt{width:6em;float:left;clear:left;margin:0;padding:0;}#plugin__manager .pm_info dd{margin:0 0 0 7em;padding:0;background:none;}#plugin__manager .plugins .enable{float:left;width:auto;margin-right:0.5em;}#user__manager tr.disabled{color:#6f6f6f;background:#e4e4e4;}#user__manager tr.user_info{vertical-align:top;}#user__manager div.edit_user{width:46%;float:left;}#user__manager table{margin-bottom:1em;}#user__manager input.button[disabled]{color:#ccc!important;border-color:#ccc!important;}dl,dt,dd{margin:0;padding:0}dl{font-size:90%;padding-top:1px;}html>body dl{padding-bottom:0.5em;border-bottom:1px dashed #e0e0e0;}dl:after{content:'.';display:block;clear:both;height:0;visibility:hidden;}dt{clear:left;margin-top:0.5em;}dt+dt{margin-top:0;}dd+dt{border-top:1px dashed #e0e0e0;padding-top:0.5em;}dt span.term{float:left;width:10em;}dd{margin-left:10.3em;padding-left:0.8em;background:url('../plugins/definitionlist/images/bullet.gif') no-repeat 0 0.4em;}dd p{margin:0;padding:0;}* html dl{height:1px;}#plugin_manager dd{background-image:none;}.hilited{background-color:#ff0;}.noteclassic,.noteimportant,.notewarning,.notetip{margin:2em;margin-left:auto;margin-right:auto;width:70% !important;min-height:40px;clear:both;text-align:justify;vertical-align:middle;border-collapse:collapse;padding:15px 20px 15px 80px;background-position:20px 50%;background-repeat:no-repeat;-moz-border-radius:20px;-khtml-border-radius:20px;border-radius:20px;}.noteclassic{background-color:#eef;background-image:url('../plugins/note/images/note.png');}.noteimportant{background-color:#ffc;background-image:url('../plugins/note/images/important.png');}.notewarning{background-color:#fdd;background-image:url('../plugins/note/images/warning.png');}.notetip{background-color:#dfd;background-image:url('../plugins/note/images/tip.png');}div.dokuwiki .header{padding:3px 0 0 2px;}div.dokuwiki .pagename{float:left;font-size:200%;font-weight:bolder;color:#dee7ec;text-align:left;vertical-align:middle;}div.dokuwiki .pagename a{color:#436976 !important;text-decoration:none !important;}div.dokuwiki .logo{float:right;font-size:220%;font-weight:bolder;text-align:right;vertical-align:middle;}div.dokuwiki .logo a{color:#dee7ec !important;text-decoration:none !important;font-variant:small-caps;letter-spacing:2pt;}div.dokuwiki .bar{border-top:1px solid #8cacbb;border-bottom:1px solid #8cacbb;background:#dee7ec;padding:0.1em 0.15em;clear:both;}div.dokuwiki .bar-left{float:left;}div.dokuwiki .bar-right{float:right;text-align:right;}div.dokuwiki #bar__bottom{margin-bottom:3px;}div.dokuwiki div.meta{clear:both;margin-top:1em;color:#638c9c;font-size:70%;}div.dokuwiki div.meta div.user{float:left;}div.dokuwiki div.meta div.doc{text-align:right;}*{padding:0;margin:0;}body{font:80% "Lucida Grande",Verdana,Lucida,Helvetica,Arial,sans-serif;background-color:#fff;color:#000;}div.dokuwiki div.page{margin:4px 2em 0 1em;text-align:justify;}div.dokuwiki table{font-size:100%;}div.dokuwiki tr,div.dokuwiki td,div.dokuwiki th{}div.dokuwiki img{border:0;}div.dokuwiki p,div.dokuwiki blockquote,div.dokuwiki table,div.dokuwiki pre{margin:0 0 1.0em 0;}div.dokuwiki hr{border:0px;border-top:1px solid #8cacbb;text-align:center;height:0px;}div.dokuwiki div.nothing{text-align:center;margin:2em;}div.dokuwiki form{border:none;display:inline;}div.dokuwiki label.block{display:block;text-align:right;font-weight:bold;}div.dokuwiki label.simple{display:block;text-align:left;font-weight:normal;}div.dokuwiki label.block input.edit{width:50%;}div.dokuwiki fieldset{width:300px;text-align:center;border:1px solid #8cacbb;padding:0.5em;margin:auto;}div.dokuwiki textarea.edit{font-family:monospace;font-size:14px;color:#000;background-color:#fff;border:1px solid #8cacbb;padding:0.3em 0 0 0.3em;width:100%;}html>body div.dokuwiki textarea.edit{background:#fff url('../tpl/default/images/inputshadow.png') repeat-x top;}div.dokuwiki input.edit,div.dokuwiki select.edit{font-size:100%;border:1px solid #8cacbb;color:#000;background-color:#fff;vertical-align:middle;margin:1px;padding:0.20em 0.3em;display:inline;}html>body div.dokuwiki input.edit,html>body div.dokuwiki select.edit{background:#fff url('../tpl/default/images/inputshadow.png') repeat-x top;}div.dokuwiki select.edit{padding:0.1em 0;}div.dokuwiki input.missing{font-size:100%;border:1px solid #8cacbb;color:#000;background-color:#fcc;vertical-align:middle;margin:1px;padding:0.20em 0.3em;display:inline;}div.dokuwiki textarea.edit[disabled],div.dokuwiki textarea.edit[readonly],div.dokuwiki input.edit[disabled],div.dokuwiki input.edit[readonly],div.dokuwiki select.edit[disabled]{background-color:#f5f5f5!important;color:#666!important;}div.dokuwiki div.toolbar,div.dokuwiki div#wiki__editbar{margin:2px 0;text-align:left;}div.dokuwiki div#size__ctl{float:right;width:60px;height:2.7em;}div.dokuwiki #size__ctl img{cursor:pointer;}div.dokuwiki div#wiki__editbar div.editButtons{float:left;padding:0 1.0em 0.7em 0;}div.dokuwiki div#wiki__editbar div.summary{float:left;}div.dokuwiki .nowrap{white-space:nowrap;}div.dokuwiki div#draft__status{float:right;color:#638c9c;}div.dokuwiki input.button,div.dokuwiki button.button{border:1px solid #8cacbb;color:#000;background-color:#fff;vertical-align:middle;text-decoration:none;font-size:100%;cursor:pointer;margin:1px;padding:0.125em 0.4em;}html>body div.dokuwiki input.button,html>body div.dokuwiki button.button{background:#fff url('../tpl/default/images/buttonshadow.png') repeat-x bottom;}* html div.dokuwiki input.button,* html div.dokuwiki button.button{height:1.8em;}div.dokuwiki div.secedit input.button{border:1px solid #8cacbb;color:#000;background-color:#fff;vertical-align:middle;text-decoration:none;margin:0;padding:0;font-size:10px;cursor:pointer;float:right;display:inline;}div.dokuwiki div.pagenav{margin:1em 0 0 0;}div.dokuwiki div.pagenav-prev{text-align:right;float:left;width:49%}div.dokuwiki div.pagenav-next{text-align:left;float:right;width:49%}div.dokuwiki a:link,div.dokuwiki a:visited{color:#436976;text-decoration:none;}div.dokuwiki a:hover,div.dokuwiki a:active{color:#000;text-decoration:underline;}div.dokuwiki h1 a,div.dokuwiki h2 a,div.dokuwiki h3 a,div.dokuwiki h4 a,div.dokuwiki h5 a,div.dokuwiki a.nolink{color:#000 !important;text-decoration:none !important;}div.dokuwiki a.urlextern{background:transparent url('../tpl/default/images/link_icon.gif') 0px 1px no-repeat;padding:1px 0px 1px 16px;}div.dokuwiki a.windows{background:transparent url('../tpl/default/images/windows.gif') 0px 1px no-repeat;padding:1px 0px 1px 16px;}div.dokuwiki a.interwiki{}div.dokuwiki a.media{}div.dokuwiki a.urlextern:link,div.dokuwiki a.windows:link,div.dokuwiki a.interwiki:link{color:#436976;}div.dokuwiki a.urlextern:visited,div.dokuwiki a.windows:visited,div.dokuwiki a.interwiki:visited{color:purple;}div.dokuwiki a.urlextern:hover,div.dokuwiki a.urlextern:active,div.dokuwiki a.windows:hover,div.dokuwiki a.windows:active,div.dokuwiki a.interwiki:hover,div.dokuwiki a.interwiki:active{color:#000;}div.dokuwiki a.mail{background:transparent url('../tpl/default/images/mail_icon.gif') 0px 1px no-repeat;padding:1px 0px 1px 16px;}div.dokuwiki a.wikilink1{color:#090 !important;}div.dokuwiki a.wikilink2{color:#f30 !important;text-decoration:none !important;border-bottom:dashed 1px #f30 !important;}div.dokuwiki div.preview{background-color:#f5f5f5;margin:0 0 0 2em;padding:4px;border:1px dashed #000;}div.dokuwiki div.breadcrumbs{background-color:#f5f5f5;color:#666;font-size:80%;padding:0 0 0 4px;}div.dokuwiki span.user{color:#ccc;font-size:90%;}div.dokuwiki li.minor{color:#666;font-style:italic;}div.dokuwiki img.media{margin:3px;}div.dokuwiki img.medialeft{border:0;float:left;margin:0 1.5em 0 0;}div.dokuwiki img.mediaright{border:0;float:right;margin:0 0 0 1.5em;}div.dokuwiki img.mediacenter{border:0;display:block;margin:0 auto;}div.dokuwiki img.middle{vertical-align:middle;}div.dokuwiki acronym{cursor:help;border-bottom:1px dotted #000;}div.dokuwiki h1,div.dokuwiki h2,div.dokuwiki h3,div.dokuwiki h4,div.dokuwiki h5{color:#000;background-color:inherit;font-size:100%;font-weight:normal;margin:0 0 1em 0;padding:0.5em 0 0 0;border-bottom:1px solid #8cacbb;clear:left;}div.dokuwiki h1{font-size:160%;margin-left:0px;font-weight:bold;}div.dokuwiki h2{font-size:150%;margin-left:20px;}div.dokuwiki h3{font-size:140%;margin-left:40px;border-bottom:none;font-weight:bold;}div.dokuwiki h4{font-size:120%;margin-left:60px;border-bottom:none;font-weight:bold;}div.dokuwiki h5{font-size:100%;margin-left:80px;border-bottom:none;font-weight:bold;}div.dokuwiki div.level1{margin-left:3px;}div.dokuwiki div.level2{margin-left:23px;}div.dokuwiki div.level3{margin-left:43px;}div.dokuwiki div.level4{margin-left:63px;}div.dokuwiki div.level5{margin-left:83px;}div.dokuwiki ul{line-height:1.5em;list-style-type:square;list-style-image:none;margin:0 0 0.5em 1.5em;color:#638c9c;}div.dokuwiki ol{line-height:1.5em;list-style-image:none;margin:0 0 0.5em 1.5em;color:#638c9c;font-weight:bold;}div.dokuwiki .li{color:#000;font-weight:normal;}div.dokuwiki ol{list-style-type:decimal}div.dokuwiki ol ol{list-style-type:upper-roman}div.dokuwiki ol ol ol{list-style-type:lower-alpha}div.dokuwiki ol ol ol ol{list-style-type:lower-greek}div.dokuwiki li.open{list-style-image:url('../tpl/default/images/open.gif');}div.dokuwiki li.closed{list-style-image:url('../tpl/default/images/closed.gif');}div.dokuwiki blockquote{border-left:2px solid #8cacbb;padding-left:3px;}div.dokuwiki pre{font-size:120%;padding:0.5em;border:1px dashed #8cacbb;color:#000;overflow:auto;}div.dokuwiki pre.pre{background-color:#f7f9fa;}div.dokuwiki pre.code{background-color:#f7f9fa;}div.dokuwiki code{font-size:120%;}div.dokuwiki pre.file{background-color:#dee7ec;}div.dokuwiki table.inline{background-color:#fff;border-spacing:0px;border-collapse:collapse;}div.dokuwiki table.inline th{padding:3px;border:1px solid #8cacbb;background-color:#dee7ec;}div.dokuwiki table.inline td{padding:3px;border:1px solid #8cacbb;}div.dokuwiki div.toc{margin:1.2em 0 0 2em;float:right;width:200px;font-size:80%;clear:both;}div.dokuwiki div.tocheader{border:1px solid #8cacbb;background-color:#dee7ec;text-align:left;font-weight:bold;padding:3px;margin-bottom:2px;}div.dokuwiki span.toc_open,div.dokuwiki span.toc_close{border:0.4em solid #dee7ec;float:right;display:block;margin:0.4em 3px 0 0;}div.dokuwiki span.toc_open span,div.dokuwiki span.toc_close span{display:none;}div.dokuwiki span.toc_open{margin-top:0.4em;border-top:0.4em solid #000;}div.dokuwiki span.toc_close{margin-top:0;border-bottom:0.4em solid #000;}div.dokuwiki #toc__inside{border:1px solid #8cacbb;background-color:#fff;text-align:left;padding:0.5em 0 0.7em 0;}div.dokuwiki ul.toc{list-style-type:none;list-style-image:none;line-height:1.2em;padding-left:1em;margin:0;}div.dokuwiki ul.toc li{background:transparent url('../tpl/default/images/tocdot2.gif') 0 0.6em no-repeat;padding-left:0.4em;}div.dokuwiki ul.toc li.clear{background-image:none;padding-left:0.4em;}div.dokuwiki a.toc:link,div.dokuwiki a.toc:visited{color:#436976;}div.dokuwiki a.toc:hover,div.dokuwiki a.toc:active{color:#000;}div.dokuwiki table.diff{background-color:#fff;width:100%;}div.dokuwiki td.diff-blockheader{font-weight:bold;}div.dokuwiki table.diff th{border-bottom:1px solid #8cacbb;font-size:120%;width:50%;font-weight:normal;text-align:left;}div.dokuwiki table.diff td{font-family:monospace;font-size:100%;}div.dokuwiki td.diff-addedline{background-color:#dfd;}div.dokuwiki td.diff-deletedline{background-color:#ffb;}div.dokuwiki td.diff-context{background-color:#f5f5f5;}div.dokuwiki table.diff td.diff-addedline strong,div.dokuwiki table.diff td.diff-deletedline strong{color:red;}div.dokuwiki div.footnotes{clear:both;border-top:1px solid #8cacbb;padding-left:1em;margin-top:1em;}div.dokuwiki div.fn{font-size:90%;}div.dokuwiki a.fn_top{vertical-align:super;font-size:80%;}div.dokuwiki a.fn_bot{vertical-align:super;font-size:80%;font-weight:bold;}div.insitu-footnote{font-size:80%;line-height:1.2em;border:1px solid #8cacbb;background-color:#f7f9fa;text-align:left;padding:4px;max-width:40%;}* html .insitu-footnote pre.code,* html .insitu-footnote pre.file{padding-bottom:18px;}div.dokuwiki .search_result{margin-bottom:6px;padding:0 10px 0 30px;}div.dokuwiki .search_snippet{color:#ccc;font-size:12px;margin-left:20px;}div.dokuwiki .search_sep{color:#000;}div.dokuwiki .search_hit{color:#000;background-color:#ff9;}div.dokuwiki strong.search_hit{font-weight:normal;}div.dokuwiki div.search_quickresult{margin:0 0 15px 30px;padding:0 10px 10px 0;border-bottom:1px dashed #8cacbb;}div.dokuwiki div.search_quickresult h3{margin:0 0 1.0em 0;font-size:1em;font-weight:bold;}div.dokuwiki ul.search_quickhits{margin:0 0 0.5em 1.0em;}div.dokuwiki ul.search_quickhits li{margin:0 1.0em 0 1.0em;float:left;width:30%;}div.footerinc{text-align:center;}.footerinc a img{opacity:0.5;border:0;}.footerinc a:hover img{opacity:1;}div.dokuwiki div.ajax_qsearch{position:absolute;right:237px;;width:200px;opacity:0.9;display:none;font-size:80%;line-height:1.2em;border:1px solid #8cacbb;background-color:#f7f9fa;text-align:left;padding:4px;}button.toolbutton{background-color:#fff;padding:0px;margin:0 1px 0 0;border:1px solid #8cacbb;cursor:pointer;}html>body button.toolbutton{background:#fff url('../tpl/default/images/buttonshadow.png') repeat-x bottom;}div.picker{width:250px;border:1px solid #8cacbb;background-color:#dee7ec;}button.pickerbutton{padding:0px;margin:0 1px 1px 0;border:0;background-color:transparent;font-size:80%;cursor:pointer;}div.dokuwiki a.spell_error{color:#f00;text-decoration:underline;}div.dokuwiki div#spell__suggest{background-color:#fff;padding:2px;border:1px solid #000;font-size:80%;display:none;}div.dokuwiki div#spell__result{border:1px solid #8cacbb;color:#000;font-size:14px;padding:3px;background-color:#f7f9fa;display:none;}div.dokuwiki span.spell_noerr{color:#093;}div.dokuwiki span.spell_wait{color:#06c;}div.dokuwiki div.img_big{float:left;margin-right:0.5em;}div.dokuwiki dl.img_tags dt{font-weight:bold;background-color:#dee7ec;}div.dokuwiki dl.img_tags dd{background-color:#f5f5f5;}div.dokuwiki div.imagemeta{color:#666;font-size:70%;line-height:95%;}div.dokuwiki div.imagemeta img.thumb{float:left;margin-right:0.1em;}#media__manager{height:100%;overflow:hidden;}#media__left{width:30%;border-right:solid 1px #8cacbb;height:100%;overflow:auto;position:absolute;left:0;}#media__right{width:69.7%;height:100%;overflow:auto;position:absolute;right:0;}#media__manager h1{margin:0;padding:0;margin-bottom:0.5em;}#media__tree img{float:left;padding:0.5em 0.3em 0 0;}#media__tree ul{list-style-type:none;list-style-image:none;}#media__tree li{clear:left;list-style-type:none;list-style-image:none;}* html #media__tree li{border:1px solid #fff;}#media__opts{padding-left:1em;margin-bottom:0.5em;}#media__opts input{float:left;position:absolute;}* html #media__opts input{position:static;}#media__opts label{display:block;float:left;margin-left:30px;}* html #media__opts label{margin-left:10px;}#media__opts br{clear:left;}#media__content img.load{margin:1em auto;}#media__content #scroll__here{border:1px dashed #8cacbb;}#media__content .odd{background-color:#f7f9fa;padding:0.4em;}#media__content .even{padding:0.4em;}#media__content a.mediafile{margin-right:1.5em;font-weight:bold;}#media__content div.detail{padding:0.3em 0 0.3em 2em;}#media__content div.detail div.thumb{float:left;width:130px;text-align:center;margin-right:0.4em;}#media__content img.btn{vertical-align:text-bottom;}#media__content div.example{color:#666;margin-left:1em;}#media__content div.upload{font-size:90%;padding:0 0.5em 0.5em 0.5em;}#media__content form.upload{display:block;border-bottom:solid 1px #8cacbb;padding:0 0.5em 1em 0.5em;}#media__content form.upload fieldset{padding:0;margin:0;border:none;width:auto;}#media__content form.upload p{clear:left;text-align:left;padding:0.25em 0;margin:0;line-height:1.0em;}#media__content form.upload label{float:left;width:30%;}#media__content form.upload label.check{float:none;width:auto;}#media__content form.upload input.check{margin-left:30%;}#media__content form.meta{display:block;padding:0 0 1em 0;}#media__content form.meta label{display:block;width:25%;float:left;font-weight:bold;margin-left:1em;clear:left;}#media__content form.meta .edit{font:100% "Lucida Grande",Verdana,Lucida,Helvetica,Arial,sans-serif;float:left;width:70%;padding-right:0;padding-left:0.2em;margin:2px;}#media__content form.meta textarea.edit{height:8em;}#media__content form.meta div.metafield{clear:left;}#media__content form.meta div.buttons{clear:left;margin-left:20%;padding-left:1em;}
\ No newline at end of file
+a.interwiki{background:transparent url('../images/interwiki.png') 0px 1px no-repeat;padding-left:16px;}a.iw_wp{background-image:url('../images/interwiki/wp.gif')}a.iw_wpde{background-image:url('../images/interwiki/wpde.gif')}a.iw_wpmeta{background-image:url('../images/interwiki/wpmeta.gif')}a.iw_doku{background-image:url('../images/interwiki/doku.gif')}a.iw_sb{background-image:url('../images/interwiki/sb.gif')}a.iw_amazon{background-image:url('../images/interwiki/amazon.gif')}a.iw_amazon_de{background-image:url('../images/interwiki/amazon.de.gif')}a.iw_amazon_uk{background-image:url('../images/interwiki/amazon.uk.gif')}a.iw_phpfn{background-image:url('../images/interwiki/phpfn.gif')}a.iw_dokubug{background-image:url('../images/interwiki/dokubug.gif')}a.iw_coral{background-image:url('../images/interwiki/coral.gif')}a.iw_google{background-image:url('../images/interwiki/google.gif')}a.iw_meatball{background-image:url('../images/interwiki/meatball.gif')}a.iw_wiki{background-image:url('../images/interwiki/wiki.gif')}a.mediafile{background:transparent url('../images/fileicons/file.png') 0px 1px no-repeat;padding-left:18px;padding-bottom:1px;}a.mf_jpg{background-image:url('../images/fileicons/jpg.png')}a.mf_jpeg{background-image:url('../images/fileicons/jpeg.png')}a.mf_gif{background-image:url('../images/fileicons/gif.png')}a.mf_png{background-image:url('../images/fileicons/png.png')}a.mf_tgz{background-image:url('../images/fileicons/tgz.png')}a.mf_tar{background-image:url('../images/fileicons/tar.png')}a.mf_gz{background-image:url('../images/fileicons/gz.png')}a.mf_zip{background-image:url('../images/fileicons/zip.png')}a.mf_rar{background-image:url('../images/fileicons/rar.png')}a.mf_pdf{background-image:url('../images/fileicons/pdf.png')}a.mf_ps{background-image:url('../images/fileicons/ps.png')}a.mf_doc{background-image:url('../images/fileicons/doc.png')}a.mf_xls{background-image:url('../images/fileicons/xls.png')}a.mf_ppt{background-image:url('../images/fileicons/ppt.png')}a.mf_rtf{background-image:url('../images/fileicons/rtf.png')}a.mf_swf{background-image:url('../images/fileicons/swf.png')}a.mf_rpm{background-image:url('../images/fileicons/rpm.png')}a.mf_deb{background-image:url('../images/fileicons/deb.png')}a.mf_sxw{background-image:url('../images/fileicons/sxw.png')}a.mf_sxc{background-image:url('../images/fileicons/sxc.png')}a.mf_sxi{background-image:url('../images/fileicons/sxi.png')}a.mf_sxd{background-image:url('../images/fileicons/sxd.png')}a.mf_odc{background-image:url('../images/fileicons/odc.png')}a.mf_odf{background-image:url('../images/fileicons/odf.png')}a.mf_odg{background-image:url('../images/fileicons/odg.png')}a.mf_odi{background-image:url('../images/fileicons/odi.png')}a.mf_odp{background-image:url('../images/fileicons/odp.png')}a.mf_ods{background-image:url('../images/fileicons/ods.png')}a.mf_odt{background-image:url('../images/fileicons/odt.png')}a.mf_src{background-image:url('../images/fileicons/src.png')}div.clearer{clear:both;line-height:0px;height:0;overflow:hidden;}div.no{display:inline;margin:0;padding:0;}.hidden{display:none;}div.error{background:#fcc url('../images/error.png') 0.5em 0px no-repeat;color:#000;border-bottom:1px solid #faa;font-size:90%;margin:0;padding-left:3em;overflow:hidden;}div.info{background:#ccf url('../images/info.png') 0.5em 0px no-repeat;color:#000;border-bottom:1px solid #aaf;font-size:90%;margin:0;padding-left:3em;overflow:hidden;}div.success{background:#cfc url('../images/success.png') 0.5em 0px no-repeat;color:#000;border-bottom:1px solid #afa;font-size:90%;margin:0;padding-left:3em;overflow:hidden;}div.notify{background:#ffc url('../images/notify.png') 0.5em 0px no-repeat;color:#000;border-bottom:1px solid #ffa;font-size:90%;margin:0;padding-left:3em;overflow:hidden;}.medialeft{float:left;}.mediaright{float:right;}.mediacenter{display:block;margin-left:auto;margin-right:auto;}.leftalign{text-align:left;}.centeralign{text-align:center;}.rightalign{text-align:right;}em.u{font-style:normal;text-decoration:underline;}em em.u{font-style:italic;}.code .br0{color:#6c6;}.code .co1{color:#808080;font-style:italic;}.code .co2{color:#808080;font-style:italic;}.code .coMULTI{color:#808080;font-style:italic;}.code .es0{color:#009;font-weight:bold;}.code .kw1{color:#b1b100;}.code .kw2{color:#000;font-weight:bold;}.code .kw3{color:#006;}.code .kw4{color:#933;}.code .kw5{color:#00f;}.code .me0{color:#060;}.code .nu0{color:#c6c;}.code .re0{color:#00f;}.code .re1{color:#00f;}.code .re2{color:#00f;}.code .re4{color:#099;}.code .sc0{color:#0bd;}.code .sc1{color:#db0;}.code .sc2{color:#090;}.code .st0{color:#f00;}div.dokuwiki div#spell__suggest{position:absolute;left:0;top:0;display:none;z-index:2;}div.dokuwiki div#spell__result{display:none;font-family:monospace;overflow:auto;z-index:1;}#acl__manager label{text-align:left;font-weight:normal;display:inline;}#acl__manager table{margin-left:10%;width:80%;}#config__manager div.success,#config__manager div.error,#config__manager div.info{background-position:0.5em;padding:0.5em;text-align:center;}#config__manager fieldset{margin:1em;width:auto;margin-bottom:2em;background-color:#dee7ec;color:#000;padding:0 1em;}#config__manager legend{font-size:1.25em;}#config__manager form{}#config__manager table{margin:1em 0;width:100%;}#config__manager fieldset td{text-align:left;}#config__manager fieldset td.value{width:30em;}#config__manager td input.edit{width:30em;}#config__manager td select.edit{}#config__manager td textarea.edit{width:27.5em;height:4em;}#config__manager tr .input,#config__manager tr input,#config__manager tr textarea,#config__manager tr select{background-color:#fff;color:#000;}#config__manager tr.default .input,#config__manager tr.default input,#config__manager tr.default textarea,#config__manager tr.default select,#config__manager .selectiondefault{background-color:#cdf;color:#000;}#config__manager tr.protected .input,#config__manager tr.protected input,#config__manager tr.protected textarea,#config__manager tr.protected select,#config__manager tr.protected .selection{background-color:#fcc!important;color:#000 !important;}#config__manager td.error{background-color:red;color:#000;}#config__manager .selection{width:14.8em;float:left;margin:0 0.3em 2px 0;}#config__manager .selection label{float:right;width:14em;font-size:90%;}* html #config__manager .selection label{padding-top:2px;}#config__manager .selection input.checkbox{padding-left:0.7em;}#config__manager .other{clear:both;padding-top:0.5em;}#config__manager .other label{padding-left:2px;font-size:90%;}#plugin__manager{}#plugin__manager h2{margin-left:0;}#plugin__manager form{display:block;margin:0;padding:0;}#plugin__manager legend{display:none;}#plugin__manager fieldset{width:auto;}#plugin__manager .button{margin:0;}#plugin__manager p,#plugin__manager label{text-align:left;}#plugin__manager .hidden{display:none;}#plugin__manager .new{background:#dee7ec;}#plugin__manager input[disabled]{color:#ccc;border-color:#ccc;}#plugin__manager .pm_menu,#plugin__manager .pm_info{margin-left:0;text-align:left;}#plugin__manager .pm_menu{float:left;width:48%;}#plugin__manager .pm_info{float:right;width:50%;}#plugin__manager .common{}#plugin__manager .common form{}#plugin__manager .common fieldset{margin:0;padding:0 0 1.0em 0;text-align:left;border:none;}#plugin__manager .common label{padding:0 0 0.5em 0;}#plugin__manager .common input{}#plugin__manager .common input.edit{width:24em;margin:0.5em;}#plugin__manager .common .button{}#plugin__manager form.plugins{}#plugin__manager .plugins fieldset{color:#000;background:#fff;text-align:right;border-top:none;border-right:none;border-left:none;}#plugin__manager .plugins fieldset.protected{background:#fdd;color:#000;}#plugin__manager .plugins fieldset.disabled{background:#e0e0e0;color:#a8a8a8;}#plugin__manager .plugins .legend{color:#000;background:inherit;display:block;margin:0;padding:0;font-size:1em;line-height:1.4em;font-weight:normal;text-align:left;float:left;padding:0;clear:none;}#plugin__manager .plugins .button{font-size:95%;}#plugin__manager .plugins fieldset.buttons{border:none;}#plugin__manager .plugins fieldset.buttons .button{float:left;}#plugin__manager .pm_info h3{margin-left:0;}#plugin__manager .pm_info dl{margin:1em 0;padding:0;}#plugin__manager .pm_info dt{width:6em;float:left;clear:left;margin:0;padding:0;}#plugin__manager .pm_info dd{margin:0 0 0 7em;padding:0;background:none;}#plugin__manager .plugins .enable{float:left;width:auto;margin-right:0.5em;}#user__manager tr.disabled{color:#6f6f6f;background:#e4e4e4;}#user__manager tr.user_info{vertical-align:top;}#user__manager div.edit_user{width:46%;float:left;}#user__manager table{margin-bottom:1em;}#user__manager input.button[disabled]{color:#ccc!important;border-color:#ccc!important;}dl,dt,dd{margin:0;padding:0}dl{font-size:90%;padding-top:1px;}html>body dl{padding-bottom:0.5em;border-bottom:1px dashed #e0e0e0;}dl:after{content:'.';display:block;clear:both;height:0;visibility:hidden;}dt{clear:left;margin-top:0.5em;}dt+dt{margin-top:0;}dd+dt{border-top:1px dashed #e0e0e0;padding-top:0.5em;}dt span.term{float:left;width:10em;}dd{margin-left:10.3em;padding-left:0.8em;background:url('../plugins/definitionlist/images/bullet.gif') no-repeat 0 0.4em;}dd p{margin:0;padding:0;}* html dl{height:1px;}#plugin_manager dd{background-image:none;}.hilited{background-color:#ff0;}.noteclassic,.noteimportant,.notewarning,.notetip{margin:2em;margin-left:auto;margin-right:auto;width:70% !important;min-height:40px;clear:both;text-align:justify;vertical-align:middle;border-collapse:collapse;padding:15px 20px 15px 80px;background-position:20px 50%;background-repeat:no-repeat;-moz-border-radius:20px;-khtml-border-radius:20px;border-radius:20px;}.noteclassic{background-color:#eef;background-image:url('../plugins/note/images/note.png');}.noteimportant{background-color:#ffc;background-image:url('../plugins/note/images/important.png');}.notewarning{background-color:#fdd;background-image:url('../plugins/note/images/warning.png');}.notetip{background-color:#dfd;background-image:url('../plugins/note/images/tip.png');}div.dokuwiki .header{padding:3px 0 0 2px;}div.dokuwiki .pagename{float:left;font-size:200%;font-weight:bolder;color:#dee7ec;text-align:left;vertical-align:middle;}div.dokuwiki .pagename a{color:#436976 !important;text-decoration:none !important;}div.dokuwiki .logo{float:right;font-size:220%;font-weight:bolder;text-align:right;vertical-align:middle;}div.dokuwiki .logo a{color:#dee7ec !important;text-decoration:none !important;font-variant:small-caps;letter-spacing:2pt;}div.dokuwiki .bar{border-top:1px solid #8cacbb;border-bottom:1px solid #8cacbb;background:#dee7ec;padding:0.1em 0.15em;clear:both;}div.dokuwiki .bar-left{float:left;}div.dokuwiki .bar-right{float:right;text-align:right;}div.dokuwiki #bar__bottom{margin-bottom:3px;}div.dokuwiki div.meta{clear:both;margin-top:1em;color:#638c9c;font-size:70%;}div.dokuwiki div.meta div.user{float:left;}div.dokuwiki div.meta div.doc{text-align:right;}*{padding:0;margin:0;}body{font:80% "Lucida Grande",Verdana,Lucida,Helvetica,Arial,sans-serif;background-color:#fff;color:#000;}div.dokuwiki div.page{margin:4px 2em 0 1em;text-align:justify;}div.dokuwiki table{font-size:100%;}div.dokuwiki tr,div.dokuwiki td,div.dokuwiki th{}div.dokuwiki img{border:0;}div.dokuwiki p,div.dokuwiki blockquote,div.dokuwiki table,div.dokuwiki pre{margin:0 0 1.0em 0;}div.dokuwiki hr{border:0px;border-top:1px solid #8cacbb;text-align:center;height:0px;}div.dokuwiki div.nothing{text-align:center;margin:2em;}div.dokuwiki form{border:none;display:inline;}div.dokuwiki label.block{display:block;text-align:right;font-weight:bold;}div.dokuwiki label.simple{display:block;text-align:left;font-weight:normal;}div.dokuwiki label.block input.edit{width:50%;}div.dokuwiki fieldset{width:300px;text-align:center;border:1px solid #8cacbb;padding:0.5em;margin:auto;}div.dokuwiki textarea.edit{font-family:monospace;font-size:14px;color:#000;background-color:#fff;border:1px solid #8cacbb;padding:0.3em 0 0 0.3em;width:100%;}html>body div.dokuwiki textarea.edit{background:#fff url('../tpl/default/images/inputshadow.png') repeat-x top;}div.dokuwiki input.edit,div.dokuwiki select.edit{font-size:100%;border:1px solid #8cacbb;color:#000;background-color:#fff;vertical-align:middle;margin:1px;padding:0.20em 0.3em;display:inline;}html>body div.dokuwiki input.edit,html>body div.dokuwiki select.edit{background:#fff url('../tpl/default/images/inputshadow.png') repeat-x top;}div.dokuwiki select.edit{padding:0.1em 0;}div.dokuwiki input.missing{font-size:100%;border:1px solid #8cacbb;color:#000;background-color:#fcc;vertical-align:middle;margin:1px;padding:0.20em 0.3em;display:inline;}div.dokuwiki textarea.edit[disabled],div.dokuwiki textarea.edit[readonly],div.dokuwiki input.edit[disabled],div.dokuwiki input.edit[readonly],div.dokuwiki select.edit[disabled]{background-color:#f5f5f5!important;color:#666!important;}div.dokuwiki div.toolbar,div.dokuwiki div#wiki__editbar{margin:2px 0;text-align:left;}div.dokuwiki div#size__ctl{float:right;width:60px;height:2.7em;}div.dokuwiki #size__ctl img{cursor:pointer;}div.dokuwiki div#wiki__editbar div.editButtons{float:left;padding:0 1.0em 0.7em 0;}div.dokuwiki div#wiki__editbar div.summary{float:left;}div.dokuwiki .nowrap{white-space:nowrap;}div.dokuwiki div#draft__status{float:right;color:#638c9c;}div.dokuwiki input.button,div.dokuwiki button.button{border:1px solid #8cacbb;color:#000;background-color:#fff;vertical-align:middle;text-decoration:none;font-size:100%;cursor:pointer;margin:1px;padding:0.125em 0.4em;}html>body div.dokuwiki input.button,html>body div.dokuwiki button.button{background:#fff url('../tpl/default/images/buttonshadow.png') repeat-x bottom;}* html div.dokuwiki input.button,* html div.dokuwiki button.button{height:1.8em;}div.dokuwiki div.secedit input.button{border:1px solid #8cacbb;color:#000;background-color:#fff;vertical-align:middle;text-decoration:none;margin:0;padding:0;font-size:10px;cursor:pointer;float:right;display:inline;}div.dokuwiki div.pagenav{margin:1em 0 0 0;}div.dokuwiki div.pagenav-prev{text-align:right;float:left;width:49%}div.dokuwiki div.pagenav-next{text-align:left;float:right;width:49%}div.dokuwiki a:link,div.dokuwiki a:visited{color:#436976;text-decoration:none;}div.dokuwiki a:hover,div.dokuwiki a:active{color:#000;text-decoration:underline;}div.dokuwiki h1 a,div.dokuwiki h2 a,div.dokuwiki h3 a,div.dokuwiki h4 a,div.dokuwiki h5 a,div.dokuwiki a.nolink{color:#000 !important;text-decoration:none !important;}div.dokuwiki a.urlextern{background:transparent url('../tpl/default/images/link_icon.gif') 0px 1px no-repeat;padding:1px 0px 1px 16px;}div.dokuwiki a.windows{background:transparent url('../tpl/default/images/windows.gif') 0px 1px no-repeat;padding:1px 0px 1px 16px;}div.dokuwiki a.interwiki{}div.dokuwiki a.media{}div.dokuwiki a.urlextern:link,div.dokuwiki a.windows:link,div.dokuwiki a.interwiki:link{color:#436976;}div.dokuwiki a.urlextern:visited,div.dokuwiki a.windows:visited,div.dokuwiki a.interwiki:visited{color:purple;}div.dokuwiki a.urlextern:hover,div.dokuwiki a.urlextern:active,div.dokuwiki a.windows:hover,div.dokuwiki a.windows:active,div.dokuwiki a.interwiki:hover,div.dokuwiki a.interwiki:active{color:#000;}div.dokuwiki a.mail{background:transparent url('../tpl/default/images/mail_icon.gif') 0px 1px no-repeat;padding:1px 0px 1px 16px;}div.dokuwiki a.wikilink1{color:#090 !important;}div.dokuwiki a.wikilink2{color:#f30 !important;text-decoration:none !important;border-bottom:dashed 1px #f30 !important;}div.dokuwiki div.preview{background-color:#f5f5f5;margin:0 0 0 2em;padding:4px;border:1px dashed #000;}div.dokuwiki div.breadcrumbs{background-color:#f5f5f5;color:#666;font-size:80%;padding:0 0 0 4px;}div.dokuwiki span.user{color:#ccc;font-size:90%;}div.dokuwiki li.minor{color:#666;font-style:italic;}div.dokuwiki img.media{margin:3px;}div.dokuwiki img.medialeft{border:0;float:left;margin:0 1.5em 0 0;}div.dokuwiki img.mediaright{border:0;float:right;margin:0 0 0 1.5em;}div.dokuwiki img.mediacenter{border:0;display:block;margin:0 auto;}div.dokuwiki img.middle{vertical-align:middle;}div.dokuwiki acronym{cursor:help;border-bottom:1px dotted #000;}div.dokuwiki h1,div.dokuwiki h2,div.dokuwiki h3,div.dokuwiki h4,div.dokuwiki h5{color:#000;background-color:inherit;font-size:100%;font-weight:normal;margin:0 0 1em 0;padding:0.5em 0 0 0;border-bottom:1px solid #8cacbb;clear:left;}div.dokuwiki h1{font-size:160%;margin-left:0px;font-weight:bold;}div.dokuwiki h2{font-size:150%;margin-left:20px;}div.dokuwiki h3{font-size:140%;margin-left:40px;border-bottom:none;font-weight:bold;}div.dokuwiki h4{font-size:120%;margin-left:60px;border-bottom:none;font-weight:bold;}div.dokuwiki h5{font-size:100%;margin-left:80px;border-bottom:none;font-weight:bold;}div.dokuwiki div.level1{margin-left:3px;}div.dokuwiki div.level2{margin-left:23px;}div.dokuwiki div.level3{margin-left:43px;}div.dokuwiki div.level4{margin-left:63px;}div.dokuwiki div.level5{margin-left:83px;}div.dokuwiki ul{line-height:1.5em;list-style-type:square;list-style-image:none;margin:0 0 0.5em 1.5em;color:#638c9c;}div.dokuwiki ol{line-height:1.5em;list-style-image:none;margin:0 0 0.5em 1.5em;color:#638c9c;font-weight:bold;}div.dokuwiki .li{color:#000;font-weight:normal;}div.dokuwiki ol{list-style-type:decimal}div.dokuwiki ol ol{list-style-type:upper-roman}div.dokuwiki ol ol ol{list-style-type:lower-alpha}div.dokuwiki ol ol ol ol{list-style-type:lower-greek}div.dokuwiki li.open{list-style-image:url('../tpl/default/images/open.gif');}div.dokuwiki li.closed{list-style-image:url('../tpl/default/images/closed.gif');}div.dokuwiki blockquote{border-left:2px solid #8cacbb;padding-left:3px;}div.dokuwiki pre{font-size:120%;padding:0.5em;border:1px dashed #8cacbb;color:#000;overflow:auto;}div.dokuwiki pre.pre{background-color:#f7f9fa;}div.dokuwiki pre.code{background-color:#f7f9fa;}div.dokuwiki code{font-size:120%;}div.dokuwiki pre.file{background-color:#dee7ec;}div.dokuwiki table.inline{background-color:#fff;border-spacing:0px;border-collapse:collapse;}div.dokuwiki table.inline th{padding:3px;border:1px solid #8cacbb;background-color:#dee7ec;}div.dokuwiki table.inline td{padding:3px;border:1px solid #8cacbb;}div.dokuwiki div.toc{margin:1.2em 0 0 2em;float:right;width:200px;font-size:80%;clear:both;}div.dokuwiki div.tocheader{border:1px solid #8cacbb;background-color:#dee7ec;text-align:left;font-weight:bold;padding:3px;margin-bottom:2px;}div.dokuwiki span.toc_open,div.dokuwiki span.toc_close{border:0.4em solid #dee7ec;float:right;display:block;margin:0.4em 3px 0 0;}div.dokuwiki span.toc_open span,div.dokuwiki span.toc_close span{display:none;}div.dokuwiki span.toc_open{margin-top:0.4em;border-top:0.4em solid #000;}div.dokuwiki span.toc_close{margin-top:0;border-bottom:0.4em solid #000;}div.dokuwiki #toc__inside{border:1px solid #8cacbb;background-color:#fff;text-align:left;padding:0.5em 0 0.7em 0;}div.dokuwiki ul.toc{list-style-type:none;list-style-image:none;line-height:1.2em;padding-left:1em;margin:0;}div.dokuwiki ul.toc li{background:transparent url('../tpl/default/images/tocdot2.gif') 0 0.6em no-repeat;padding-left:0.4em;}div.dokuwiki ul.toc li.clear{background-image:none;padding-left:0.4em;}div.dokuwiki a.toc:link,div.dokuwiki a.toc:visited{color:#436976;}div.dokuwiki a.toc:hover,div.dokuwiki a.toc:active{color:#000;}div.dokuwiki table.diff{background-color:#fff;width:100%;}div.dokuwiki td.diff-blockheader{font-weight:bold;}div.dokuwiki table.diff th{border-bottom:1px solid #8cacbb;font-size:120%;width:50%;font-weight:normal;text-align:left;}div.dokuwiki table.diff td{font-family:monospace;font-size:100%;}div.dokuwiki td.diff-addedline{background-color:#dfd;}div.dokuwiki td.diff-deletedline{background-color:#ffb;}div.dokuwiki td.diff-context{background-color:#f5f5f5;}div.dokuwiki table.diff td.diff-addedline strong,div.dokuwiki table.diff td.diff-deletedline strong{color:red;}div.dokuwiki div.footnotes{clear:both;border-top:1px solid #8cacbb;padding-left:1em;margin-top:1em;}div.dokuwiki div.fn{font-size:90%;}div.dokuwiki a.fn_top{vertical-align:super;font-size:80%;}div.dokuwiki a.fn_bot{vertical-align:super;font-size:80%;font-weight:bold;}div.insitu-footnote{font-size:80%;line-height:1.2em;border:1px solid #8cacbb;background-color:#f7f9fa;text-align:left;padding:4px;max-width:40%;}* html .insitu-footnote pre.code,* html .insitu-footnote pre.file{padding-bottom:18px;}div.dokuwiki .search_result{margin-bottom:6px;padding:0 10px 0 30px;}div.dokuwiki .search_snippet{color:#ccc;font-size:12px;margin-left:20px;}div.dokuwiki .search_sep{color:#000;}div.dokuwiki .search_hit{color:#000;background-color:#ff9;}div.dokuwiki strong.search_hit{font-weight:normal;}div.dokuwiki div.search_quickresult{margin:0 0 15px 30px;padding:0 10px 10px 0;border-bottom:1px dashed #8cacbb;}div.dokuwiki div.search_quickresult h3{margin:0 0 1.0em 0;font-size:1em;font-weight:bold;}div.dokuwiki ul.search_quickhits{margin:0 0 0.5em 1.0em;}div.dokuwiki ul.search_quickhits li{margin:0 1.0em 0 1.0em;float:left;width:30%;}div.footerinc{text-align:center;}.footerinc a img{opacity:0.5;border:0;}.footerinc a:hover img{opacity:1;}div.dokuwiki div.ajax_qsearch{position:absolute;right:237px;;width:200px;opacity:0.9;display:none;font-size:80%;line-height:1.2em;border:1px solid #8cacbb;background-color:#f7f9fa;text-align:left;padding:4px;}button.toolbutton{background-color:#fff;padding:0px;margin:0 1px 0 0;border:1px solid #8cacbb;cursor:pointer;}html>body button.toolbutton{background:#fff url('../tpl/default/images/buttonshadow.png') repeat-x bottom;}div.picker{width:250px;border:1px solid #8cacbb;background-color:#dee7ec;}button.pickerbutton{padding:0px;margin:0 1px 1px 0;border:0;background-color:transparent;font-size:80%;cursor:pointer;}div.dokuwiki a.spell_error{color:#f00;text-decoration:underline;}div.dokuwiki div#spell__suggest{background-color:#fff;padding:2px;border:1px solid #000;font-size:80%;display:none;}div.dokuwiki div#spell__result{border:1px solid #8cacbb;color:#000;font-size:14px;padding:3px;background-color:#f7f9fa;display:none;}div.dokuwiki span.spell_noerr{color:#093;}div.dokuwiki span.spell_wait{color:#06c;}div.dokuwiki div.img_big{float:left;margin-right:0.5em;}div.dokuwiki dl.img_tags dt{font-weight:bold;background-color:#dee7ec;}div.dokuwiki dl.img_tags dd{background-color:#f5f5f5;}div.dokuwiki div.imagemeta{color:#666;font-size:70%;line-height:95%;}div.dokuwiki div.imagemeta img.thumb{float:left;margin-right:0.1em;}#media__manager{height:100%;overflow:hidden;}#media__left{width:30%;border-right:solid 1px #8cacbb;height:100%;overflow:auto;position:absolute;left:0;}#media__right{width:69.7%;height:100%;overflow:auto;position:absolute;right:0;}#media__manager h1{margin:0;padding:0;margin-bottom:0.5em;}#media__tree img{float:left;padding:0.5em 0.3em 0 0;}#media__tree ul{list-style-type:none;list-style-image:none;}#media__tree li{clear:left;list-style-type:none;list-style-image:none;}* html #media__tree li{border:1px solid #fff;}#media__opts{padding-left:1em;margin-bottom:0.5em;}#media__opts input{float:left;position:absolute;}* html #media__opts input{position:static;}#media__opts label{display:block;float:left;margin-left:30px;}* html #media__opts label{margin-left:10px;}#media__opts br{clear:left;}#media__content img.load{margin:1em auto;}#media__content #scroll__here{border:1px dashed #8cacbb;}#media__content .odd{background-color:#f7f9fa;padding:0.4em;}#media__content .even{padding:0.4em;}#media__content a.mediafile{margin-right:1.5em;font-weight:bold;}#media__content div.detail{padding:0.3em 0 0.3em 2em;}#media__content div.detail div.thumb{float:left;width:130px;text-align:center;margin-right:0.4em;}#media__content img.btn{vertical-align:text-bottom;}#media__content div.example{color:#666;margin-left:1em;}#media__content div.upload{font-size:90%;padding:0 0.5em 0.5em 0.5em;}#media__content form.upload{display:block;border-bottom:solid 1px #8cacbb;padding:0 0.5em 1em 0.5em;}#media__content form.upload fieldset{padding:0;margin:0;border:none;width:auto;}#media__content form.upload p{clear:left;text-align:left;padding:0.25em 0;margin:0;line-height:1.0em;}#media__content form.upload label{float:left;width:30%;}#media__content form.upload label.check{float:none;width:auto;}#media__content form.upload input.check{margin-left:30%;}#media__content form.meta{display:block;padding:0 0 1em 0;}#media__content form.meta label{display:block;width:25%;float:left;font-weight:bold;margin-left:1em;clear:left;}#media__content form.meta .edit{font:100% "Lucida Grande",Verdana,Lucida,Helvetica,Arial,sans-serif;float:left;width:70%;padding-right:0;padding-left:0.2em;margin:2px;}#media__content form.meta textarea.edit{height:8em;}#media__content form.meta div.metafield{clear:left;}#media__content form.meta div.buttons{clear:left;margin-left:20%;padding-left:1em;}
\ No newline at end of file
diff --git a/docs/wiki/lib/exe/002css b/docs/wiki/lib/exe/002css
index b105ade..632fd89 100644
--- a/docs/wiki/lib/exe/002css
+++ b/docs/wiki/lib/exe/002css
@@ -1 +1 @@
-a.interwiki{background:transparent url('../images/interwiki.png') 0px 1px no-repeat;padding-left:16px;}a.iw_wp{background-image:url('../images/interwiki/wp.gif')}a.iw_wpde{background-image:url('../images/interwiki/wpde.gif')}a.iw_wpmeta{background-image:url('../images/interwiki/wpmeta.gif')}a.iw_doku{background-image:url('../images/interwiki/doku.gif')}a.iw_sb{background-image:url('../images/interwiki/sb.gif')}a.iw_amazon{background-image:url('../images/interwiki/amazon.gif')}a.iw_amazon_de{background-image:url('../images/interwiki/amazon.de.gif')}a.iw_amazon_uk{background-image:url('../images/interwiki/amazon.uk.gif')}a.iw_phpfn{background-image:url('../images/interwiki/phpfn.gif')}a.iw_dokubug{background-image:url('../images/interwiki/dokubug.gif')}a.iw_coral{background-image:url('../images/interwiki/coral.gif')}a.iw_google{background-image:url('../images/interwiki/google.gif')}a.iw_meatball{background-image:url('../images/interwiki/meatball.gif')}a.iw_wiki{background-image:url('../images/interwiki/wiki.gif')}a.mediafile{background:transparent url('../images/fileicons/file.png') 0px 1px no-repeat;padding-left:18px;padding-bottom:1px;}a.mf_jpg{background-image:url('../images/fileicons/jpg.png')}a.mf_jpeg{background-image:url('../images/fileicons/jpeg.png')}a.mf_gif{background-image:url('../images/fileicons/gif.png')}a.mf_png{background-image:url('../images/fileicons/png.png')}a.mf_tgz{background-image:url('../images/fileicons/tgz.png')}a.mf_tar{background-image:url('../images/fileicons/tar.png')}a.mf_gz{background-image:url('../images/fileicons/gz.png')}a.mf_zip{background-image:url('../images/fileicons/zip.png')}a.mf_rar{background-image:url('../images/fileicons/rar.png')}a.mf_pdf{background-image:url('../images/fileicons/pdf.png')}a.mf_ps{background-image:url('../images/fileicons/ps.png')}a.mf_doc{background-image:url('../images/fileicons/doc.png')}a.mf_xls{background-image:url('../images/fileicons/xls.png')}a.mf_ppt{background-image:url('../images/fileicons/ppt.png')}a.mf_rtf{background-image:url('../images/fileicons/rtf.png')}a.mf_swf{background-image:url('../images/fileicons/swf.png')}a.mf_rpm{background-image:url('../images/fileicons/rpm.png')}a.mf_deb{background-image:url('../images/fileicons/deb.png')}a.mf_sxw{background-image:url('../images/fileicons/sxw.png')}a.mf_sxc{background-image:url('../images/fileicons/sxc.png')}a.mf_sxi{background-image:url('../images/fileicons/sxi.png')}a.mf_sxd{background-image:url('../images/fileicons/sxd.png')}a.mf_odc{background-image:url('../images/fileicons/odc.png')}a.mf_odf{background-image:url('../images/fileicons/odf.png')}a.mf_odg{background-image:url('../images/fileicons/odg.png')}a.mf_odi{background-image:url('../images/fileicons/odi.png')}a.mf_odp{background-image:url('../images/fileicons/odp.png')}a.mf_ods{background-image:url('../images/fileicons/ods.png')}a.mf_odt{background-image:url('../images/fileicons/odt.png')}body{font:10pt "Lucida Grande",Verdana,Lucida,Helvetica,Arial,sans-serif;background-color:White;color:Black;}table{font-size:100%;padding:0;margin:0;}tr,td,th{padding:0;margin:0;}img{border:0}a{color:#000;text-decoration:none;background:none !important;}div.meta{clear:both;margin-top:1em;font-size:70%;text-align:right;}div.notify,div.info,div.success,div.error,div.breadcrumbs,div.secedit{display:none;}a.urlextern:after{content:" [" attr(href) "]";font-size:90%;}a.interwiki:after{content:" [" attr(href) "]";font-size:90%;}a.mail:after{content:" [" attr(href) "]";font-size:90%;}a.wikilink1{text-decoration:underline}div.page{text-align:justify;}h1,h2,h3,h4,h5{color:Black;background-color:transparent;font-family:"Lucida Grande",Verdana,Lucida,Helvetica,Arial,sans-serif;font-size:100%;font-weight:normal;margin-left:0;margin-right:0;margin-top:0;margin-bottom:1em;padding-left:0;padding-right:0;padding-top:0.5em;padding-bottom:0;border-bottom:1px solid #000;clear:left;}h1{font-size:160%;font-weight:bold;}h2{font-size:150%;}h3{font-size:140%;border-bottom:none;}h4{font-size:120%;border-bottom:none;}h5{font-size:100%;border-bottom:none;}img.media{margin:3px;}img.medialeft{border:0;float:left;margin:0 1.5em 0 0;}img.mediaright{border:0;float:right;margin:0 0 0 1.5em;}ul{line-height:1.5em;list-style-type:square;margin:0 0 0.5em 1.5em;padding:0;}ol{line-height:1.5em;margin:0 0 0.5em 2.5em;padding:0;font-weight:normal;}ol ol{margin:0 0 0.5em 1.5em;}div.dokuwiki ol{list-style-type:decimal}div.dokuwiki ol ol{list-style-type:upper-roman}div.dokuwiki ol ol ol{list-style-type:lower-alpha}div.dokuwiki ol ol ol ol{list-style-type:lower-greek}span.li{font-weight:normal;}pre.pre{font-size:8pt;padding:0.5em;border:1px dashed #000;color:Black;overflow:visible;}pre.code{font-size:8pt;padding:0.5em;border:1px dashed #000;color:Black;overflow:visible;}code{font-size:120%;}pre.file{font-size:8pt;padding:0.5em;border:1px dotted #000;color:Black;overflow:visible;}div.footnotes{clear:both;border-top:1px solid #000;padding-left:1em;margin-top:1em;}div.fn{font-size:90%;}a.fn_top{vertical-align:super;font-size:80%;}a.fn_bot{vertical-align:super;font-size:80%;font-weight:bold;}acronym{border:0;}table.inline{font-size:80%;background-color:#fff;border-spacing:0px;border-collapse:collapse;}table.inline th{padding:3px;border:1px solid #000;border-bottom:2px solid #000;}table.inline td{padding:3px;border:1px solid #000;}.leftalign{text-align:left;}.centeralign{text-align:center;}.rightalign{text-align:right;}.toc,.footerinc,.header,.bar,.user{display:none}
\ No newline at end of file
+a.interwiki{background:transparent url('../images/interwiki.png') 0px 1px no-repeat;padding-left:16px;}a.iw_wp{background-image:url('../images/interwiki/wp.gif')}a.iw_wpde{background-image:url('../images/interwiki/wpde.gif')}a.iw_wpmeta{background-image:url('../images/interwiki/wpmeta.gif')}a.iw_doku{background-image:url('../images/interwiki/doku.gif')}a.iw_sb{background-image:url('../images/interwiki/sb.gif')}a.iw_amazon{background-image:url('../images/interwiki/amazon.gif')}a.iw_amazon_de{background-image:url('../images/interwiki/amazon.de.gif')}a.iw_amazon_uk{background-image:url('../images/interwiki/amazon.uk.gif')}a.iw_phpfn{background-image:url('../images/interwiki/phpfn.gif')}a.iw_dokubug{background-image:url('../images/interwiki/dokubug.gif')}a.iw_coral{background-image:url('../images/interwiki/coral.gif')}a.iw_google{background-image:url('../images/interwiki/google.gif')}a.iw_meatball{background-image:url('../images/interwiki/meatball.gif')}a.iw_wiki{background-image:url('../images/interwiki/wiki.gif')}a.mediafile{background:transparent url('../images/fileicons/file.png') 0px 1px no-repeat;padding-left:18px;padding-bottom:1px;}a.mf_jpg{background-image:url('../images/fileicons/jpg.png')}a.mf_jpeg{background-image:url('../images/fileicons/jpeg.png')}a.mf_gif{background-image:url('../images/fileicons/gif.png')}a.mf_png{background-image:url('../images/fileicons/png.png')}a.mf_tgz{background-image:url('../images/fileicons/tgz.png')}a.mf_tar{background-image:url('../images/fileicons/tar.png')}a.mf_gz{background-image:url('../images/fileicons/gz.png')}a.mf_zip{background-image:url('../images/fileicons/zip.png')}a.mf_rar{background-image:url('../images/fileicons/rar.png')}a.mf_pdf{background-image:url('../images/fileicons/pdf.png')}a.mf_ps{background-image:url('../images/fileicons/ps.png')}a.mf_doc{background-image:url('../images/fileicons/doc.png')}a.mf_xls{background-image:url('../images/fileicons/xls.png')}a.mf_ppt{background-image:url('../images/fileicons/ppt.png')}a.mf_rtf{background-image:url('../images/fileicons/rtf.png')}a.mf_swf{background-image:url('../images/fileicons/swf.png')}a.mf_rpm{background-image:url('../images/fileicons/rpm.png')}a.mf_deb{background-image:url('../images/fileicons/deb.png')}a.mf_sxw{background-image:url('../images/fileicons/sxw.png')}a.mf_sxc{background-image:url('../images/fileicons/sxc.png')}a.mf_sxi{background-image:url('../images/fileicons/sxi.png')}a.mf_sxd{background-image:url('../images/fileicons/sxd.png')}a.mf_odc{background-image:url('../images/fileicons/odc.png')}a.mf_odf{background-image:url('../images/fileicons/odf.png')}a.mf_odg{background-image:url('../images/fileicons/odg.png')}a.mf_odi{background-image:url('../images/fileicons/odi.png')}a.mf_odp{background-image:url('../images/fileicons/odp.png')}a.mf_ods{background-image:url('../images/fileicons/ods.png')}a.mf_odt{background-image:url('../images/fileicons/odt.png')}a.mf_src{background-image:url('../images/fileicons/src.png')}body{font:10pt "Lucida Grande",Verdana,Lucida,Helvetica,Arial,sans-serif;background-color:White;color:Black;}table{font-size:100%;padding:0;margin:0;}tr,td,th{padding:0;margin:0;}img{border:0}a{color:#000;text-decoration:none;background:none !important;}div.meta{clear:both;margin-top:1em;font-size:70%;text-align:right;}div.notify,div.info,div.success,div.error,div.breadcrumbs,div.secedit{display:none;}a.urlextern:after{content:" [" attr(href) "]";font-size:90%;}a.interwiki:after{content:" [" attr(href) "]";font-size:90%;}a.mail:after{content:" [" attr(href) "]";font-size:90%;}a.wikilink1{text-decoration:underline}div.page{text-align:justify;}h1,h2,h3,h4,h5{color:Black;background-color:transparent;font-family:"Lucida Grande",Verdana,Lucida,Helvetica,Arial,sans-serif;font-size:100%;font-weight:normal;margin-left:0;margin-right:0;margin-top:0;margin-bottom:1em;padding-left:0;padding-right:0;padding-top:0.5em;padding-bottom:0;border-bottom:1px solid #000;clear:left;}h1{font-size:160%;font-weight:bold;}h2{font-size:150%;}h3{font-size:140%;border-bottom:none;}h4{font-size:120%;border-bottom:none;}h5{font-size:100%;border-bottom:none;}img.media{margin:3px;}img.medialeft{border:0;float:left;margin:0 1.5em 0 0;}img.mediaright{border:0;float:right;margin:0 0 0 1.5em;}ul{line-height:1.5em;list-style-type:square;margin:0 0 0.5em 1.5em;padding:0;}ol{line-height:1.5em;margin:0 0 0.5em 2.5em;padding:0;font-weight:normal;}ol ol{margin:0 0 0.5em 1.5em;}div.dokuwiki ol{list-style-type:decimal}div.dokuwiki ol ol{list-style-type:upper-roman}div.dokuwiki ol ol ol{list-style-type:lower-alpha}div.dokuwiki ol ol ol ol{list-style-type:lower-greek}span.li{font-weight:normal;}pre.pre{font-size:8pt;padding:0.5em;border:1px dashed #000;color:Black;overflow:visible;}pre.code{font-size:8pt;padding:0.5em;border:1px dashed #000;color:Black;overflow:visible;}code{font-size:120%;}pre.file{font-size:8pt;padding:0.5em;border:1px dotted #000;color:Black;overflow:visible;}div.footnotes{clear:both;border-top:1px solid #000;padding-left:1em;margin-top:1em;}div.fn{font-size:90%;}a.fn_top{vertical-align:super;font-size:80%;}a.fn_bot{vertical-align:super;font-size:80%;font-weight:bold;}acronym{border:0;}table.inline{font-size:80%;background-color:#fff;border-spacing:0px;border-collapse:collapse;}table.inline th{padding:3px;border:1px solid #000;border-bottom:2px solid #000;}table.inline td{padding:3px;border:1px solid #000;}.leftalign{text-align:left;}.centeralign{text-align:center;}.rightalign{text-align:right;}.toc,.footerinc,.header,.bar,.user{display:none}
\ No newline at end of file
diff --git a/docs/wiki/lib/exe/css b/docs/wiki/lib/exe/css
index 98cf713..6501c40 100644
--- a/docs/wiki/lib/exe/css
+++ b/docs/wiki/lib/exe/css
@@ -1 +1 @@
-a.interwiki{background:transparent url('../images/interwiki.png') 0px 1px no-repeat;padding-left:16px;}a.iw_wp{background-image:url('../images/interwiki/wp.gif')}a.iw_wpde{background-image:url('../images/interwiki/wpde.gif')}a.iw_wpmeta{background-image:url('../images/interwiki/wpmeta.gif')}a.iw_doku{background-image:url('../images/interwiki/doku.gif')}a.iw_sb{background-image:url('../images/interwiki/sb.gif')}a.iw_amazon{background-image:url('../images/interwiki/amazon.gif')}a.iw_amazon_de{background-image:url('../images/interwiki/amazon.de.gif')}a.iw_amazon_uk{background-image:url('../images/interwiki/amazon.uk.gif')}a.iw_phpfn{background-image:url('../images/interwiki/phpfn.gif')}a.iw_dokubug{background-image:url('../images/interwiki/dokubug.gif')}a.iw_coral{background-image:url('../images/interwiki/coral.gif')}a.iw_google{background-image:url('../images/interwiki/google.gif')}a.iw_meatball{background-image:url('../images/interwiki/meatball.gif')}a.iw_wiki{background-image:url('../images/interwiki/wiki.gif')}a.mediafile{background:transparent url('../images/fileicons/file.png') 0px 1px no-repeat;padding-left:18px;padding-bottom:1px;}a.mf_jpg{background-image:url('../images/fileicons/jpg.png')}a.mf_jpeg{background-image:url('../images/fileicons/jpeg.png')}a.mf_gif{background-image:url('../images/fileicons/gif.png')}a.mf_png{background-image:url('../images/fileicons/png.png')}a.mf_tgz{background-image:url('../images/fileicons/tgz.png')}a.mf_tar{background-image:url('../images/fileicons/tar.png')}a.mf_gz{background-image:url('../images/fileicons/gz.png')}a.mf_zip{background-image:url('../images/fileicons/zip.png')}a.mf_rar{background-image:url('../images/fileicons/rar.png')}a.mf_pdf{background-image:url('../images/fileicons/pdf.png')}a.mf_ps{background-image:url('../images/fileicons/ps.png')}a.mf_doc{background-image:url('../images/fileicons/doc.png')}a.mf_xls{background-image:url('../images/fileicons/xls.png')}a.mf_ppt{background-image:url('../images/fileicons/ppt.png')}a.mf_rtf{background-image:url('../images/fileicons/rtf.png')}a.mf_swf{background-image:url('../images/fileicons/swf.png')}a.mf_rpm{background-image:url('../images/fileicons/rpm.png')}a.mf_deb{background-image:url('../images/fileicons/deb.png')}a.mf_sxw{background-image:url('../images/fileicons/sxw.png')}a.mf_sxc{background-image:url('../images/fileicons/sxc.png')}a.mf_sxi{background-image:url('../images/fileicons/sxi.png')}a.mf_sxd{background-image:url('../images/fileicons/sxd.png')}a.mf_odc{background-image:url('../images/fileicons/odc.png')}a.mf_odf{background-image:url('../images/fileicons/odf.png')}a.mf_odg{background-image:url('../images/fileicons/odg.png')}a.mf_odi{background-image:url('../images/fileicons/odi.png')}a.mf_odp{background-image:url('../images/fileicons/odp.png')}a.mf_ods{background-image:url('../images/fileicons/ods.png')}a.mf_odt{background-image:url('../images/fileicons/odt.png')}
\ No newline at end of file
+a.interwiki{background:transparent url('../images/interwiki.png') 0px 1px no-repeat;padding-left:16px;}a.iw_wp{background-image:url('../images/interwiki/wp.gif')}a.iw_wpde{background-image:url('../images/interwiki/wpde.gif')}a.iw_wpmeta{background-image:url('../images/interwiki/wpmeta.gif')}a.iw_doku{background-image:url('../images/interwiki/doku.gif')}a.iw_sb{background-image:url('../images/interwiki/sb.gif')}a.iw_amazon{background-image:url('../images/interwiki/amazon.gif')}a.iw_amazon_de{background-image:url('../images/interwiki/amazon.de.gif')}a.iw_amazon_uk{background-image:url('../images/interwiki/amazon.uk.gif')}a.iw_phpfn{background-image:url('../images/interwiki/phpfn.gif')}a.iw_dokubug{background-image:url('../images/interwiki/dokubug.gif')}a.iw_coral{background-image:url('../images/interwiki/coral.gif')}a.iw_google{background-image:url('../images/interwiki/google.gif')}a.iw_meatball{background-image:url('../images/interwiki/meatball.gif')}a.iw_wiki{background-image:url('../images/interwiki/wiki.gif')}a.mediafile{background:transparent url('../images/fileicons/file.png') 0px 1px no-repeat;padding-left:18px;padding-bottom:1px;}a.mf_jpg{background-image:url('../images/fileicons/jpg.png')}a.mf_jpeg{background-image:url('../images/fileicons/jpeg.png')}a.mf_gif{background-image:url('../images/fileicons/gif.png')}a.mf_png{background-image:url('../images/fileicons/png.png')}a.mf_tgz{background-image:url('../images/fileicons/tgz.png')}a.mf_tar{background-image:url('../images/fileicons/tar.png')}a.mf_gz{background-image:url('../images/fileicons/gz.png')}a.mf_zip{background-image:url('../images/fileicons/zip.png')}a.mf_rar{background-image:url('../images/fileicons/rar.png')}a.mf_pdf{background-image:url('../images/fileicons/pdf.png')}a.mf_ps{background-image:url('../images/fileicons/ps.png')}a.mf_doc{background-image:url('../images/fileicons/doc.png')}a.mf_xls{background-image:url('../images/fileicons/xls.png')}a.mf_ppt{background-image:url('../images/fileicons/ppt.png')}a.mf_rtf{background-image:url('../images/fileicons/rtf.png')}a.mf_swf{background-image:url('../images/fileicons/swf.png')}a.mf_rpm{background-image:url('../images/fileicons/rpm.png')}a.mf_deb{background-image:url('../images/fileicons/deb.png')}a.mf_sxw{background-image:url('../images/fileicons/sxw.png')}a.mf_sxc{background-image:url('../images/fileicons/sxc.png')}a.mf_sxi{background-image:url('../images/fileicons/sxi.png')}a.mf_sxd{background-image:url('../images/fileicons/sxd.png')}a.mf_odc{background-image:url('../images/fileicons/odc.png')}a.mf_odf{background-image:url('../images/fileicons/odf.png')}a.mf_odg{background-image:url('../images/fileicons/odg.png')}a.mf_odi{background-image:url('../images/fileicons/odi.png')}a.mf_odp{background-image:url('../images/fileicons/odp.png')}a.mf_ods{background-image:url('../images/fileicons/ods.png')}a.mf_odt{background-image:url('../images/fileicons/odt.png')}a.mf_src{background-image:url('../images/fileicons/src.png')}
\ No newline at end of file
diff --git a/docs/wiki/lib/images/fileicons/Makefile.am b/docs/wiki/lib/images/fileicons/Makefile.am
index 648a3b3..d826916 100644
--- a/docs/wiki/lib/images/fileicons/Makefile.am
+++ b/docs/wiki/lib/images/fileicons/Makefile.am
@@ -3,7 +3,7 @@
docname=wiki
docsdir = @GEDADOCDIR@/$(docname)/lib/images/fileicons
-docs_DATA = doc.png sxc.png .gitignore odc.png xls.png xml.png pdf.png gz.png tgz.png html.png jpeg.png jpg.png odi.png ps.png odt.png file.png sxi.png odg.png sxw.png ppt.png rar.png conf.png rtf.png sxd.png rpm.png htm.png odp.png png.png zip.png swf.png odf.png deb.png gif.png tar.png txt.png ods.png
+docs_DATA = doc.png sxc.png .gitignore odc.png xls.png pdf.png gz.png tgz.png jpeg.png jpg.png odi.png ps.png odt.png file.png sxi.png odg.png sxw.png ppt.png rar.png rtf.png sxd.png rpm.png odp.png png.png zip.png swf.png odf.png deb.png src.png gif.png tar.png ods.png
EXTRA_DIST = $(docs_DATA)
diff --git a/docs/wiki/lib/images/fileicons/conf.png b/docs/wiki/lib/images/fileicons/conf.png
deleted file mode 100644
index 7d9225e..0000000
Binary files a/docs/wiki/lib/images/fileicons/conf.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/htm.png b/docs/wiki/lib/images/fileicons/htm.png
deleted file mode 100644
index 0e3ee49..0000000
Binary files a/docs/wiki/lib/images/fileicons/htm.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/html.png b/docs/wiki/lib/images/fileicons/html.png
deleted file mode 100644
index 8a7163d..0000000
Binary files a/docs/wiki/lib/images/fileicons/html.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/src.png b/docs/wiki/lib/images/fileicons/src.png
new file mode 100644
index 0000000..da20009
Binary files /dev/null and b/docs/wiki/lib/images/fileicons/src.png differ
diff --git a/docs/wiki/lib/images/fileicons/txt.png b/docs/wiki/lib/images/fileicons/txt.png
deleted file mode 100644
index 1bc7f1c..0000000
Binary files a/docs/wiki/lib/images/fileicons/txt.png and /dev/null differ
diff --git a/docs/wiki/lib/images/fileicons/xml.png b/docs/wiki/lib/images/fileicons/xml.png
deleted file mode 100644
index 1286a5b..0000000
Binary files a/docs/wiki/lib/images/fileicons/xml.png and /dev/null differ
diff --git a/docs/wiki/libgeda3.html b/docs/wiki/libgeda3.html
index e28c67f..eea723f 100644
--- a/docs/wiki/libgeda3.html
+++ b/docs/wiki/libgeda3.html
@@ -7,7 +7,7 @@
<title>libgeda3</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:27-0400" />
+<meta name="date" content="2007-08-22T15:49:47-0400" />
<meta name="keywords" content="libgeda3" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -195,7 +195,7 @@ Pros:
</p>
</div>
-<!-- SECTION "glib" [2550-3349] -->
+<!-- SECTION "glib" [2550-3350] -->
<h3><a name="gobject" id="gobject">gobject</a></h3>
<div class="level3">
@@ -207,8 +207,12 @@ Pros:
gobject is often considered to be heavyweight, requiring lots of boilerplate code in order to use it effectively. Its use in libgeda has historically been opposed, though its use in future versions may ease creation of bindings for libgeda in more directly object-oriented languages such as Python, Java or C++.
</p>
+<p>
+GObject is currently used in libgeda for the GedaList class which wrapps a GList, and provides a notification signal when <acronym title="Application Programming Interface">API</acronym> is used to modify the list.
+</p>
+
</div>
-<!-- SECTION "gobject" [3350-4179] -->
+<!-- SECTION "gobject" [3351-4335] -->
<h2><a name="references" id="references">References</a></h2>
<div class="level2">
<ul>
@@ -217,6 +221,6 @@ gobject is often considered to be heavyweight, requiring lots of boilerplate cod
</ul>
</div>
-<!-- SECTION "References" [4180-] --></div>
+<!-- SECTION "References" [4336-] --></div>
</body>
</html>
diff --git a/docs/wiki/start_es.html b/docs/wiki/start_es.html
index a0e08c5..22ace54 100644
--- a/docs/wiki/start_es.html
+++ b/docs/wiki/start_es.html
@@ -7,7 +7,7 @@
<title>start_es</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:27-0400" />
+<meta name="date" content="2007-08-23T14:48:11-0400" />
<meta name="keywords" content="start_es" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -56,15 +56,15 @@
<div class="level2">
<p>
- <a href="http://el-directorio.org/ProyectoTale/Tutoriales/geda"; class="urlextern" title="http://el-directorio.org/ProyectoTale/Tutoriales/geda"; rel="nofollow"> Tutorial de gEDA</a>
+ <a href="http://slcolombia.org/ProyectoTale/Tutoriales/geda"; class="urlextern" title="http://slcolombia.org/ProyectoTale/Tutoriales/geda"; rel="nofollow"> Tutorial de gEDA</a>
</p>
<p>
-<a href="http://el-directorio.org/ProyectoTale/Tutoriales/gnucap"; class="urlextern" title="http://el-directorio.org/ProyectoTale/Tutoriales/gnucap"; rel="nofollow"> Tutorial de gnucap</a>
+<a href="http://slcolombia.org/ProyectoTale/Tutoriales/gnucap"; class="urlextern" title="http://slcolombia.org/ProyectoTale/Tutoriales/gnucap"; rel="nofollow"> Tutorial de gnucap</a>
</p>
</div>
-<!-- SECTION "Tutoriales" [174-357] -->
+<!-- SECTION "Tutoriales" [174-351] -->
<h2><a name="otros" id="otros">Otros</a></h2>
<div class="level2">
@@ -81,6 +81,6 @@
</p>
</div>
-<!-- SECTION "Otros" [358-] --></div>
+<!-- SECTION "Otros" [352-] --></div>
</body>
</html>
_______________________________________________
geda-cvs mailing list
geda-cvs@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-cvs