From 24bc0f38e5eedc7f67c33f52c7395236d62d24de Mon Sep 17 00:00:00 2001 From: Ales Hvezda Date: Thu, 5 Jul 2007 01:27:02 -0400 Subject: [PATCH] Downloaded and integrated latest wiki documentation from the geda website. Also updated some of the wiki scripts a little. Fetching and integrating the latest wiki version isn't fully automated yet, but getting there. --- docs/scripts/copygitignores.sh | 19 + docs/scripts/populatemkfiles.sh | 11 +- docs/wiki/001geda_debian.html | 2 +- docs/wiki/001geda_documentation.html | 34 +- docs/wiki/001geda_faq-attribs.html | 2 +- docs/wiki/001geda_faq-gnetlist.html | 2 +- docs/wiki/001geda_faq-gsch2pcb.html | 14 +- docs/wiki/001geda_faq-gschem.html | 2 +- docs/wiki/001geda_faq-simulation.html | 2 +- docs/wiki/001geda_faq.html | 6 +- docs/wiki/001geda_gschem_ug.html | 294 +++++++-------- docs/wiki/001geda_installation.html | 2 +- docs/wiki/001geda_pcb-quick_reference.html | 2 +- docs/wiki/001geda_pcb_tips.html | 2 +- docs/wiki/001geda_scg.html | 2 +- docs/wiki/001geda_suse_10.html | 2 +- docs/wiki/001geda_tragesym_tutorial.html | 2 +- docs/wiki/001geda_usage.html | 18 +- docs/wiki/Makefile.am | 26 +- docs/wiki/_detail/Makefile.am | 22 +- docs/wiki/_media/Makefile.am | 22 +- .../{geda_pcb_mp.html => geda_bill_wilson_s.html} | 49 +-- docs/wiki/geda_bom_readme.html | 2 +- .../wiki/geda_circuit_simulation_improvements.html | 2 +- docs/wiki/geda_covered_mp.html | 2 +- docs/wiki/geda_csygas.html | 2 +- docs/wiki/geda_cygwin.html | 2 +- docs/wiki/geda_data_plotting_improvements.html | 2 +- .../geda_data_structure_design_discussion.html | 2 +- docs/wiki/geda_debian.html | 2 +- .../geda_design_flow_and_hierarchy_roadmap.html | 2 +- docs/wiki/geda_devel-tips.html | 2 +- docs/wiki/geda_documentation.html | 4 +- docs/wiki/geda_eagle_pcb_netlister_readme.html | 2 +- docs/wiki/geda_example_hsm.html | 2 +- docs/wiki/geda_example_usbjtag.html | 2 +- docs/wiki/geda_faq-attribs.html | 2 +- docs/wiki/geda_faq-gnetlist.html | 2 +- docs/wiki/geda_faq-gsch2pcb.html | 13 +- docs/wiki/geda_faq-gschem.html | 145 +++++--- docs/wiki/geda_faq-pcb.html | 2 +- docs/wiki/geda_faq-simulation.html | 2 +- docs/wiki/geda_faq.html | 94 ++--- docs/wiki/geda_fbabgapp.html | 2 +- docs/wiki/geda_fc1.html | 2 +- docs/wiki/geda_fc2.html | 2 +- docs/wiki/geda_fc3.html | 2 +- docs/wiki/geda_fc4.html | 2 +- docs/wiki/geda_fedora_rpm_installation.html | 2 +- docs/wiki/geda_file_format_spec.html | 40 +- docs/wiki/geda_gattrib_readme.html | 2 +- docs/wiki/geda_gedasuite_installation.html | 2 +- docs/wiki/geda_gerbv_mp.html | 2 +- docs/wiki/geda_gerbv_pnp_readme.html | 2 +- docs/wiki/geda_gfdl.html | 2 +- docs/wiki/geda_glossaire.html | 2 +- docs/wiki/geda_glossary.html | 2 +- docs/wiki/geda_gnetlist_mp.html | 2 +- docs/wiki/geda_gnetlist_ug.html | 2 +- docs/wiki/geda_grcsan.html | 2 +- docs/wiki/geda_grenum_mp.html | 2 +- docs/wiki/geda_gsch2pcb_readme.html | 2 +- docs/wiki/geda_gsch2pcb_tutorial.html | 36 +- docs/wiki/geda_gsch2pcb_tutorial_releasenotes.html | 2 +- docs/wiki/geda_gschem2pcb_readme.html | 2 +- docs/wiki/geda_gschem_mp.html | 2 +- docs/wiki/geda_gschem_ug.html | 2 +- docs/wiki/geda_gschem_warmup.html | 2 +- docs/wiki/geda_gsymcheck_mp.html | 2 +- docs/wiki/geda_gtkwave_lxt2miner_mp.html | 2 +- docs/wiki/geda_gtkwave_lxt2vcd_mp.html | 2 +- docs/wiki/geda_gtkwave_mp.html | 2 +- docs/wiki/geda_gtkwave_mvl2lxt_mp.html | 2 +- docs/wiki/geda_gtkwave_mvl2vcd_mp.html | 2 +- docs/wiki/geda_gtkwave_tex2vcd_mp.html | 2 +- docs/wiki/geda_gtkwave_tla2vcd_mp.html | 2 +- docs/wiki/geda_gtkwave_vcd2lxt2_mp.html | 2 +- docs/wiki/geda_gtkwave_vcd2lxt_mp.html | 2 +- docs/wiki/geda_gtkwave_vcd2vzt_mp.html | 2 +- docs/wiki/geda_gtkwave_vzt2vcd_mp.html | 2 +- docs/wiki/geda_gtkwave_vztminer_mp.html | 2 +- docs/wiki/geda_hse_howto.html | 2 +- docs/wiki/geda_icarus_anc.html | 2 +- docs/wiki/geda_icarus_extensions.html | 2 +- docs/wiki/geda_icarus_glossary.html | 2 +- docs/wiki/geda_icarus_ieee1364.html | 9 +- docs/wiki/geda_icarus_mp.html | 6 +- docs/wiki/geda_icarus_opcodes.html | 4 +- docs/wiki/geda_icarus_quick_start.html | 2 +- docs/wiki/geda_icarus_readme.html | 2 +- docs/wiki/geda_icarus_vpi_mp.html | 6 +- docs/wiki/geda_icarus_vpi_within_vvp.html | 4 +- docs/wiki/geda_icarus_vvp_runtime.html | 6 +- docs/wiki/geda_icarus_vvp_simulation.html | 4 +- docs/wiki/geda_icarus_xilinx_hints.html | 2 +- docs/wiki/geda_icarus_xnf.html | 7 +- docs/wiki/geda_igarus_fpga_lcg.html | 9 +- docs/wiki/geda_installation.html | 2 +- docs/wiki/geda_installed_plugins.html | 2 +- docs/wiki/geda_kig_howto.html | 2 +- docs/wiki/geda_master_attributes_list.html | 2 +- docs/wiki/geda_mcalc_readme.html | 4 +- docs/wiki/geda_na_howto.html | 2 +- docs/wiki/geda_ngnutmeg_mp.html | 2 +- docs/wiki/geda_ngsconvert_mp.html | 2 +- docs/wiki/geda_ngspice_mp.html | 2 +- docs/wiki/geda_olib_readme.html | 2 +- docs/wiki/geda_pcb-quick_reference.html | 4 +- docs/wiki/geda_pcb_footprints.html | 10 +- docs/wiki/geda_pcb_mp.html | 2 +- docs/wiki/geda_pcb_tips.html | 80 ++-- docs/wiki/geda_scg.html | 2 +- docs/wiki/geda_scm.html | 407 +++++++++++++++++++++ docs/wiki/geda_sdb_howto.html | 2 +- docs/wiki/geda_sn_readme.html | 2 +- docs/wiki/geda_ssan.html | 2 +- docs/wiki/geda_style_guide.html | 2 +- docs/wiki/geda_suse_10.html | 2 +- docs/wiki/geda_suse_9.html | 2 +- docs/wiki/geda_suse_rpm_installation.html | 42 +-- docs/wiki/geda_syntax_features.html | 2 +- docs/wiki/geda_systemc_netlister_readme.html | 2 +- docs/wiki/geda_tasks.html | 57 ++- docs/wiki/geda_todos.html | 16 +- docs/wiki/geda_tragesym_readme.html | 2 +- docs/wiki/geda_tragesym_tutorial.html | 2 +- docs/wiki/geda_transistor_guide.html | 2 +- docs/wiki/geda_ubuntu.html | 2 +- docs/wiki/geda_usage.html | 22 +- docs/wiki/geda_vams_netlister_readme.html | 2 +- docs/wiki/geda_verilog_netlister_readme.html | 2 +- docs/wiki/geda_version_control_migration.html | 2 +- docs/wiki/geda_vhdl_netlister_readme.html | 2 +- docs/wiki/geda_wcalc_mp.html | 2 +- docs/wiki/geda_wcalc_readme.html | 4 +- docs/wiki/geda_wcalc_stdio_mp.html | 2 +- docs/wiki/index.html | 32 +- docs/wiki/lib/Makefile.am | 4 + docs/wiki/lib/exe/Makefile.am | 2 +- docs/wiki/lib/exe/opensearch | 7 + docs/wiki/lib/images/Makefile.am | 2 +- docs/wiki/lib/images/fileicons/Makefile.am | 22 +- docs/wiki/lib/images/interwiki/Makefile.am | 2 +- docs/wiki/lib/images/smileys/Makefile.am | 2 +- docs/wiki/lib/plugins/Makefile.am | 4 + docs/wiki/lib/plugins/definitionlist/Makefile.am | 4 + .../lib/plugins/definitionlist/images/Makefile.am | 2 +- docs/wiki/lib/plugins/note/Makefile.am | 4 + docs/wiki/lib/plugins/note/images/Makefile.am | 2 +- docs/wiki/lib/tpl/Makefile.am | 4 + docs/wiki/lib/tpl/default/Makefile.am | 4 + docs/wiki/lib/tpl/default/images/Makefile.am | 2 +- docs/wiki/libgeda3.html | 2 +- docs/wiki/playground_transistor_guide.html | 2 +- docs/wiki/start_es.html | 2 +- docs/wiki/start_fr.html | 2 +- 156 files changed, 1169 insertions(+), 686 deletions(-) create mode 100755 docs/scripts/copygitignores.sh rewrite docs/wiki/Makefile.am (89%) rewrite docs/wiki/_detail/Makefile.am (90%) rewrite docs/wiki/_media/Makefile.am (87%) copy docs/wiki/{geda_pcb_mp.html => geda_bill_wilson_s.html} (51%) create mode 100644 docs/wiki/geda_scm.html create mode 100644 docs/wiki/lib/exe/opensearch rewrite docs/wiki/lib/images/fileicons/Makefile.am (65%) diff --git a/docs/scripts/copygitignores.sh b/docs/scripts/copygitignores.sh new file mode 100755 index 000000000..e7da5a185 --- /dev/null +++ b/docs/scripts/copygitignores.sh @@ -0,0 +1,19 @@ +#!/bin/sh + +if [ ! -d "wiki" -a ! -d "wip" ] +then + echo "You must start this program in the toplevel docs directory" + echo "wherever wiki and wip live." + exit 1 +fi + +files=`find wiki -name .gitignore -print` + +for i in $files +do + src=$i + dest=`echo $i | sed "s/^wiki/wip/"` + echo Copying $src to $dest + cp -f $src $dest +done + diff --git a/docs/scripts/populatemkfiles.sh b/docs/scripts/populatemkfiles.sh index 0dc63d391..b6e7613eb 100755 --- a/docs/scripts/populatemkfiles.sh +++ b/docs/scripts/populatemkfiles.sh @@ -1,5 +1,10 @@ #!/bin/sh +# Issues: +# +# * dot files (like .gitignore) aren't handled correctly. +# + # $1 is the name of the directory do_work() { @@ -17,7 +22,7 @@ do_work() thisdir=`echo $thisdir | sed "s%//%/%g"` - mv -f Makefile.am Makefile.am.old + mv -f Makefile.am Makefile.am.old >& /dev/null echo "" > Makefile.am echo "" >> Makefile.am @@ -65,8 +70,8 @@ do_work() } pwd=`pwd` -thisprogram=/home/ahvezda/2gaf/docs/scripts/populatemkfiles.sh -basedir=/home/ahvezda/2gaf/docs/wip +thisprogram=/home/ahvezda/gaf/docs/scripts/populatemkfiles.sh +basedir=/home/ahvezda/gaf/docs/wip subdir=`echo $pwd | awk -F$basedir '{print $2}'` diff --git a/docs/wiki/001geda_debian.html b/docs/wiki/001geda_debian.html index d4e3149c6..d5c32fb51 100644 --- a/docs/wiki/001geda_debian.html +++ b/docs/wiki/001geda_debian.html @@ -6,7 +6,7 @@ geda:debian.fr - + diff --git a/docs/wiki/001geda_documentation.html b/docs/wiki/001geda_documentation.html index 54f9aa47f..ef342a60b 100644 --- a/docs/wiki/001geda_documentation.html +++ b/docs/wiki/001geda_documentation.html @@ -6,8 +6,8 @@ geda:documentation.fr - - + + @@ -144,7 +144,7 @@ New features are available for document authors: - +

Examples

- +

Attribute/File Format Details

- +

SPICE

- +

ngspice

- +

gnucap

- +

gSpiceUI

- +

PCB

- +

gerbv

- +

Icarus Verilog

- +

GTKWave

- +

Wcalc

- +

mcalc

- +

covered

- + diff --git a/docs/wiki/001geda_faq-attribs.html b/docs/wiki/001geda_faq-attribs.html index 043a90f8c..041af9a2f 100644 --- a/docs/wiki/001geda_faq-attribs.html +++ b/docs/wiki/001geda_faq-attribs.html @@ -6,7 +6,7 @@ geda:faq-attribs.fr - + diff --git a/docs/wiki/001geda_faq-gnetlist.html b/docs/wiki/001geda_faq-gnetlist.html index 4d82bffd0..ee67599c3 100644 --- a/docs/wiki/001geda_faq-gnetlist.html +++ b/docs/wiki/001geda_faq-gnetlist.html @@ -6,7 +6,7 @@ geda:faq-gnetlist.fr - + diff --git a/docs/wiki/001geda_faq-gsch2pcb.html b/docs/wiki/001geda_faq-gsch2pcb.html index d65de2554..fc33c79c6 100644 --- a/docs/wiki/001geda_faq-gsch2pcb.html +++ b/docs/wiki/001geda_faq-gsch2pcb.html @@ -6,8 +6,8 @@ geda:faq-gsch2pcb.fr - - + + @@ -47,16 +47,16 @@

- Actuellement, la meilleure information à ce propos est dans le outstanding tutorial de Bill Wilson.
+ Actuellement, la meilleure information à ce propos est dans le tutorial de Bill Wilson.
Cette page grossira plus tard pour contenir les réponses aux FAQ postées sur la liste des geda-user.

-C’est un script de gestion pour gsch2pcb appelé sch2pcb. Vous pouvez y trouver des informations dans la section pcb_tips.fr de ce wiki. +C’est un script de gestion pour gsch2pcb appelé sch2pcb. Vous pouvez y trouver des informations dans la section pcb_tips.fr de ce wiki.

- +

Où puis-je télécharger gsch2pcb?

@@ -77,7 +77,7 @@ gsch2pcb est une part de gEDA/gaf, dans les utils. Il est normalement installé
- +

gsch2pcb ne peut pas trouver quelques uns de mes empreintes ou génère une erreur. Comment puis-je diagnostiquer mon problème?

@@ -86,6 +86,6 @@ Tentez de lancer gsch2pcb en mode bavard double: “gsch2pcb -v -v”. Cela prod

- + diff --git a/docs/wiki/001geda_faq-gschem.html b/docs/wiki/001geda_faq-gschem.html index 00948b7d3..3e61c6016 100644 --- a/docs/wiki/001geda_faq-gschem.html +++ b/docs/wiki/001geda_faq-gschem.html @@ -6,7 +6,7 @@ geda:faq-gschem.fr - + diff --git a/docs/wiki/001geda_faq-simulation.html b/docs/wiki/001geda_faq-simulation.html index 448b1b0a9..dda12309d 100644 --- a/docs/wiki/001geda_faq-simulation.html +++ b/docs/wiki/001geda_faq-simulation.html @@ -6,7 +6,7 @@ geda:faq-simulation.fr - + diff --git a/docs/wiki/001geda_faq.html b/docs/wiki/001geda_faq.html index e6e2b4725..8ddc4e968 100644 --- a/docs/wiki/001geda_faq.html +++ b/docs/wiki/001geda_faq.html @@ -6,8 +6,8 @@ geda:faq.fr - - + + @@ -316,7 +316,7 @@ Venez à la réunion des « Free EDA Users Group » (Freedog) de Cambridge, MA.

-La chose la plus importante à faire est de lire et de comprendre l’excellent tutoriel de Bill Wilson gschem -> gsch2pcb -> PCB. Cela vous permettra de débuter. +La chose la plus importante à faire est de lire et de comprendre l’excellent tutoriel de Bill Wilson gschem -> gsch2pcb -> PCB. Cela vous permettra de débuter.

diff --git a/docs/wiki/001geda_gschem_ug.html b/docs/wiki/001geda_gschem_ug.html index 729577931..8e0405977 100644 --- a/docs/wiki/001geda_gschem_ug.html +++ b/docs/wiki/001geda_gschem_ug.html @@ -6,8 +6,8 @@ geda:gschem_ug.fr - - + + @@ -281,9 +281,9 @@ This document describes the installation, configuration, and operation of the

- +

Overview

@@ -368,7 +368,7 @@ This document describes the installation, configuration, and operation of the
- +

Resources

@@ -378,7 +378,7 @@ The following on-line resources are useful for designers using gschem
  • Bill Wilson's gschem warmup tutorial – If you are new to the gEDA tools, read this before you read Bill’s “Bill Wilson’s gsch2pcb tutorial”.
    • -
  • Bill Wilson's gsch2pcb tutorial – If you are new to the gEDA tools, this tutorial will bring you up to speed quickly.
    +
  • Bill Wilson's gschem and pcb tutorial – If you are new to the gEDA tools, this tutorial will bring you up to speed quickly.
  • Circuit Cellar Magazine – Practical, hands-on applications and solutions for embedded designers:
      @@ -441,7 +441,7 @@ The following on-line resources are useful for designers using gschem
    • - +

    How To Ask Questions

    @@ -477,7 +477,7 @@ The following on-line resources are useful for designers using gschem
    - +

    Installing gschem

    @@ -486,7 +486,7 @@ As a mature OpenSource project, the gEDA Tools Suite and its components have bee

    - +

    Latest Stable

    @@ -496,7 +496,7 @@ As a mature OpenSource project, the gEDA Tools Suite and its components have bee

    - +

    "gEDA Tools Suite" CD-ROM

    @@ -517,7 +517,7 @@ If the installation wizzard did not launch, enter as follows to install the gEDA

    - +

    Debian distributions

    @@ -526,7 +526,7 @@ For Debian distributions, you may wish to download the +

    Red Hat distributions

    @@ -535,7 +535,7 @@ For Red Hat distributions (and possibly others) you may wish to download the lat

    - +

    Mac OSX distributions

    @@ -544,7 +544,7 @@ For Mac OSX distributions you may wish to download the +

    CVS Unstable/Testing

    @@ -560,7 +560,7 @@ For those already familiar with the gEDA/gaf applications on the “gEDA Tools S
    - +

    Configuring gschem

    @@ -628,7 +628,7 @@ Now that we know the above, we can configure gschem.
    - +

    gschemrc

    @@ -638,7 +638,7 @@ The {binary-install-path}/share/gEDA/system-gschemrc file is well commented. Rea

    - +

    gafrc

    @@ -648,12 +648,12 @@ The {binary-install-path}/share/gEDA/system-gafrc file is well commented. Read t

    - +

    Lancer gschem

    - +

    Confirming gschem is installed

    @@ -750,7 +750,7 @@ If these commands do not return the expected results, then most likely the gEDA

    - +

    The Shell Prompt

    @@ -831,7 +831,7 @@ As operations are performed in the gschem +

    Backups

    @@ -840,7 +840,7 @@ There are two basic mechanisms in gschem for backing up schemat

    - +

    Classic Linux backups

    @@ -894,12 +894,12 @@ When the user does finally manually save the file, the original file (i.e., the

    - +

    Incremental backups

    - +

    Relevant configuration settings

    @@ -918,7 +918,7 @@ There are the following configuration settings in the {binary-install-path}/shar
    - +

    On-line documentation

    @@ -1050,7 +1050,7 @@ Version December 31st, 2003 gschem(1)

    - +

    Electrical Connectivity

    @@ -1062,7 +1062,7 @@ As you draw schematics you need be aware of what is considered to be electricall

    - +

    Components & Symbols & Objects & Attributes

    @@ -1071,7 +1071,7 @@ There is a hierarchical association between components, symbols, objects, and at

    - +

    Components

    @@ -1094,7 +1094,7 @@ A component is the instantiation of a specific symbol, as placed on the schemati

    - +

    Symbols

    @@ -1105,7 +1105,7 @@ Symbols are just a collection of objects and attributes.

    - +

    Objects

    @@ -1130,7 +1130,7 @@ The following are objects:
    - +

    Attributes

    @@ -1184,7 +1184,7 @@ So, to summarize, attribute promotion takes unattached attributes inside symbols

    - +

    The Main Window

    @@ -1213,7 +1213,7 @@ So, to summarize, attribute promotion takes unattached attributes inside symbols

    - +

    The Status Window

    @@ -1227,7 +1227,7 @@ So, to summarize, attribute promotion takes unattached attributes inside symbols

    - +

    The Schematic File

    @@ -1248,7 +1248,7 @@ Schematic files. These files contain components, nets, text, and sometimes primi

    - +

    The Symbol File

    @@ -1271,7 +1271,7 @@ Symbol files. The schematic and symbol file formats are identical. gsche

    - +

    Symbol Libraries

    @@ -1280,7 +1280,7 @@ Components are searched for by specifying (component-library "…”)

    - +

    The Log File

    @@ -1289,7 +1289,7 @@ Log file. This file contains informative, error, warnings etc… messages w

    - +

    Grips

    @@ -1312,12 +1312,12 @@ Using grips is easy:
    - +

    Menu Operations

    - +

    File

    @@ -1344,7 +1344,7 @@ The following are available from the gschem main window’s men

    - +

    New Window (fw)

    @@ -1353,7 +1353,7 @@ The following are available from the gschem main window’s men

    - +

    New Page (fn)

    @@ -1362,7 +1362,7 @@ The following are available from the gschem main window’s men

    - +

    Open Page... (fo)

    @@ -1388,7 +1388,7 @@ The following are available from the gschem main window’s men
    - +

    Close Page (pc)

    @@ -1397,7 +1397,7 @@ The following are available from the gschem main window’s men

    - +

    Revert Page (pr)

    @@ -1406,7 +1406,7 @@ The following are available from the gschem main window’s men

    - +

    Save Page (fs)

    @@ -1424,7 +1424,7 @@ The following are available from the gschem main window’s men
    - +

    Save Page As... (fa)

    @@ -1436,7 +1436,7 @@ The following are available from the gschem main window’s men

    - +

    Save All (fl) (fl)

    @@ -1445,7 +1445,7 @@ The following are available from the gschem main window’s men

    - +

    Print... (fp)

    @@ -1488,7 +1488,7 @@ The following are available from the gschem main window’s men
    - +

    Write PNG... (fi)

    @@ -1525,7 +1525,7 @@ The following are available from the gschem main window’s men

    - +

    Execute Script... (ft)

    @@ -1534,7 +1534,7 @@ The following are available from the gschem main window’s men

    - +

    Close Window (fc)

    @@ -1543,7 +1543,7 @@ The following are available from the gschem main window’s men

    - +

    Quit (Alt-q)

    @@ -1552,7 +1552,7 @@ The following are available from the gschem main window’s men

    - +

    Edit

    @@ -1561,7 +1561,7 @@ The following are available from the gschem main window’s men

    - +

    Undo (shift-u)

    @@ -1582,7 +1582,7 @@ After every action (including zooming and panning) the schematic is saved to dis

    - +

    Redo (shift-r)

    @@ -1592,7 +1592,7 @@ After every action (including zooming and panning) the schematic is saved to dis

    - +

    Select Mode (s)

    @@ -1615,7 +1615,7 @@ After every action (including zooming and panning) the schematic is saved to dis

    - +

    Edit... (ee)

    @@ -1664,7 +1664,7 @@ First, select the object to be edited (i.e., in Select Mode).
    - +

    Edit Text... (ex)

    @@ -1702,7 +1702,7 @@ First, select the text object to be edited (i.e., in Select Mode
    - +

    Copy Mode (ec)

    @@ -1735,7 +1735,7 @@ First, select the text object to be edited (i.e., in Select Mode
    - +

    Move Mode (em)

    @@ -1781,7 +1781,7 @@ Since version 20060906, there is another way to move object(s):
    - +

    Delete (Delete-key)

    @@ -1801,7 +1801,7 @@ Since version 20060906, there is another way to move object(s):

    - +

    Rotate 90 Mode (er)

    @@ -1825,7 +1825,7 @@ Since version 20060906, there is another way to move object(s):

    - +

    Mirror Mode (ei)

    @@ -1849,7 +1849,7 @@ Since version 20060906, there is another way to move object(s):

    - +

    Slot... (e shift-s)

    @@ -1874,7 +1874,7 @@ Some physical packages (e.g., the classic 7400 Quad NAND gate) contain more than

    - +

    Color... (eo)

    @@ -1931,7 +1931,7 @@ Some physical packages (e.g., the classic 7400 Quad NAND gate) contain more than

    - +

    Lock (el) / Unlock (e shift-l)

    @@ -1955,7 +1955,7 @@ Some physical packages (e.g., the classic 7400 Quad NAND gate) contain more than

    - +

    Line Width & Type... (ew)

    @@ -1991,7 +1991,7 @@ The Edit | Line Width & Type… dialog box lets you co

    - +

    Fill Type... (ef)

    @@ -2025,7 +2025,7 @@ The Edit | Line Width & Type… dialog box lets you co
    - +

    Symbol Translate... (et)

    @@ -2065,7 +2065,7 @@ The Edit | Line Width & Type… dialog box lets you co

    - +

    Embed Component/Picture (eb)

    @@ -2088,7 +2088,7 @@ The Edit | Line Width & Type… dialog box lets you co

    - +

    Unembed Component/Picture (eu)

    @@ -2108,7 +2108,7 @@ The Edit | Line Width & Type… dialog box lets you co

    - +

    Update Component (ep)

    @@ -2148,7 +2148,7 @@ The Edit | Line Width & Type… dialog box lets you co
    - +

    Show/Hide Inv Text (en)

    @@ -2214,7 +2214,7 @@ The Edit | Line Width & Type… dialog box lets you co

    - +

    Make Inv Text Vis (ev)

    @@ -2235,7 +2235,7 @@ The Edit | Line Width & Type… dialog box lets you co

    - +

    Buffer

    @@ -2244,7 +2244,7 @@ The Edit | Line Width & Type… dialog box lets you co

    - +

    Copy into 1/2/3/4/5 (yc)

    @@ -2259,7 +2259,7 @@ To copy something into a buffer:
    - +

    Cut into 1/2/3/4/5 (yu)

    @@ -2268,7 +2268,7 @@ Cut is like copy in that it removes the objects from the schematic

    - +

    Paste from 1/2/3/4/5 (yp)

    @@ -2291,12 +2291,12 @@ To paste a buffer into the current schematic:
    - +

    View

    - +

    Redraw (vr)

    @@ -2306,7 +2306,7 @@ To paste a buffer into the current schematic:

    - +

    Pan (x)

    @@ -2353,7 +2353,7 @@ to either your user’s ~/gschemrc file or local ‘pwd’/gschemrc file, whenev

    - +

    Zoom Box (w)

    @@ -2380,7 +2380,7 @@ to either your user’s ~/gschemrc file or local ‘pwd’/gschemrc file, whenev

    - +

    Zoom Extents (ve)

    @@ -2399,7 +2399,7 @@ to either your user’s ~/gschemrc file or local ‘pwd’/gschemrc file, whenev

    - +

    Zoom In (z)

    @@ -2436,7 +2436,7 @@ in either your user’s ~/gschemrc file or local ‘pwd’/gschemrc file, whenev

    - +

    Zoom Out (Z)

    @@ -2473,7 +2473,7 @@ in either your user’s ~/gschemrc file or local ‘pwd’/gschemrc file, whenev

    - +

    Zoom Full (vf)

    @@ -2513,52 +2513,52 @@ To view the maximum displayable area using the keyboard shortcut (i.e., “
    - +

    Page

    - +

    Manager... (pm)

    - +

    - +

    - +

    New (pe)

    - +

    Revert (pr)

    - +

    Close (pc)

    - +

    Discard (pd)

    - +

    Add

    - +

    Component... (i)

    @@ -2611,7 +2611,7 @@ Pour placer un composant:

    - +

    Net (n)

    @@ -2693,7 +2693,7 @@ Pour placer un composant:

    - +

    Bus (u)

    @@ -2703,7 +2703,7 @@ Pour placer un composant:

    - +

    Attribute... (aa)

    @@ -2734,7 +2734,7 @@ Pour placer un composant:

    - +

    Text... (at)

    @@ -2785,7 +2785,7 @@ la souris)

    - +

    Line (l)

    @@ -2829,7 +2829,7 @@ la souris)

    - +

    Box (b)

    @@ -2859,7 +2859,7 @@ la souris)

    - +

    Circle (ai)

    @@ -2891,7 +2891,7 @@ la souris)

    - +

    Arc (ar)

    @@ -2927,7 +2927,7 @@ la souris)

    - +

    Pin (ap)

    @@ -2960,7 +2960,7 @@ la souris)

    - +

    Picture... (ag)

    @@ -2994,12 +2994,12 @@ la souris)

    - +

    Hierarchy

    - +

    Down Schematic (Hd)

    @@ -3021,7 +3021,7 @@ la souris)

    - +

    Down Symbol (Hs)

    @@ -3032,7 +3032,7 @@ Cette option ouvrira le symbole du composant sélectionné.

    - +

    Up (Hu)

    @@ -3041,7 +3041,7 @@ Cette option permettra de remonter dans la hiérarchie (s’il y a des pages au-

    - +

    Documentation (Ho)

    @@ -3056,12 +3056,12 @@ Open any documentation available for the selected symbol/component.

    - +

    Attributes

    - +

    Attach (ta)

    @@ -3084,7 +3084,7 @@ The Attach command allows you to take a text item (in the proper form; nam

    - +

    Detach (td)

    @@ -3105,7 +3105,7 @@ Detach allows you to deassociate attributes from objects.

    - +

    Show Value (tv)

    @@ -3126,7 +3126,7 @@ These operations allow you to control which part of the attribute string is visi

    - +

    Show Name (tn)

    @@ -3147,7 +3147,7 @@ These operations allow you to control which part of the attribute string is visi

    - +

    Show Both (tb)

    @@ -3168,7 +3168,7 @@ These operations allow you to control which part of the attribute string is visi

    - +

    Toggle Visibility (tt)

    @@ -3190,32 +3190,32 @@ This operation allows you to toggle the visibility of attributes.

    - +

    Find Specific Text... (t shift-f)

    - +

    Hide Specific Text... (th)

    - +

    Show Specific Text... (t shift-h)

    - +

    Autonumber Text... (tu)

    - +

    Options

    - +

    Text Size... (ot)

    @@ -3225,7 +3225,7 @@ This operation allows you to toggle the visibility of attributes.

    - +

    Toggle Grid On/Off (og)

    @@ -3234,7 +3234,7 @@ This operation allows you to toggle the visibility of attributes.

    - +

    Toggle Snap On/Off (os)

    @@ -3245,7 +3245,7 @@ This operation allows you to toggle the visibility of attributes.

    - +

    Snap Grid Spacing... (oS)

    @@ -3255,7 +3255,7 @@ This operation allows you to toggle the visibility of attributes.

    - +

    Toggle Outline/Box (oa)

    @@ -3264,7 +3264,7 @@ This operation allows you to toggle the visibility of attributes.

    - +

    Toggle Net/Rubberband (or)

    @@ -3273,7 +3273,7 @@ This operation allows you to toggle the visibility of attributes.

    - +

    Show Log Window (ol)

    @@ -3282,7 +3282,7 @@ This operation allows you to toggle the visibility of attributes.

    - +

    Show Coord Window... (oc)

    @@ -3291,12 +3291,12 @@ This operation allows you to toggle the visibility of attributes.

    - +

    Help

    - +

    About... (ha)

    @@ -3313,7 +3313,7 @@ Every GUI application needs
    - +

    Manual... (hm)

    @@ -3322,7 +3322,7 @@ Every GUI application needs

    - +

    Hotkeys... (hh)

    @@ -3331,7 +3331,7 @@ Every GUI application needs

    - +

    Component... (Ho)

    @@ -3346,7 +3346,7 @@ If you select a component on the schematic, and select Help | Component&
    - +

    Appendix A -- Heavy vs Light Symbol Libraries

    @@ -3355,7 +3355,7 @@ A short discussion of Light Symbol Libraries as the default for gschem
    - +

    Appendix B -- Printing Schematics and Symbols

    @@ -3364,7 +3364,7 @@ To be supplied…

    - +

    Appendix C -- Writing guile Scripts

    @@ -3373,7 +3373,7 @@ To be supplied…

    - +

    Appendix D -- I Want To Build A Printed Circuit Board

    @@ -3406,7 +3406,7 @@ To be supplied…
    - +

    Appendix E -- I Want To Simulate My Design

    @@ -3441,7 +3441,7 @@ To be supplied…
    - +

    Appendix F -- Change gschemdoc User-Defined Preferences

    @@ -3469,7 +3469,7 @@ To select a different application launcher, simply edit the {binary-install-path

    - +

    Appendix G -- Breaking a Large Symbol Into Smaller Symbols

    @@ -3478,7 +3478,7 @@ To be supplied…

    - +

    Appendix H -- Definition of Terms

    @@ -3554,6 +3554,6 @@ Some terms used in the art of schematic capture:

    - + diff --git a/docs/wiki/001geda_installation.html b/docs/wiki/001geda_installation.html index aea55c398..0cba62e93 100644 --- a/docs/wiki/001geda_installation.html +++ b/docs/wiki/001geda_installation.html @@ -6,7 +6,7 @@ geda:installation.fr - + diff --git a/docs/wiki/001geda_pcb-quick_reference.html b/docs/wiki/001geda_pcb-quick_reference.html index 63149c6f8..34666bff8 100644 --- a/docs/wiki/001geda_pcb-quick_reference.html +++ b/docs/wiki/001geda_pcb-quick_reference.html @@ -6,7 +6,7 @@ geda:pcb-quick_reference.fr - + diff --git a/docs/wiki/001geda_pcb_tips.html b/docs/wiki/001geda_pcb_tips.html index ae37d8f1c..91993bc1d 100644 --- a/docs/wiki/001geda_pcb_tips.html +++ b/docs/wiki/001geda_pcb_tips.html @@ -6,7 +6,7 @@ geda:pcb_tips.fr - + diff --git a/docs/wiki/001geda_scg.html b/docs/wiki/001geda_scg.html index 94274f888..15c4ca07e 100644 --- a/docs/wiki/001geda_scg.html +++ b/docs/wiki/001geda_scg.html @@ -6,7 +6,7 @@ geda:scg.fr - + diff --git a/docs/wiki/001geda_suse_10.html b/docs/wiki/001geda_suse_10.html index fb23937e9..14a8ba9ae 100644 --- a/docs/wiki/001geda_suse_10.html +++ b/docs/wiki/001geda_suse_10.html @@ -6,7 +6,7 @@ geda:suse_10.1 - + diff --git a/docs/wiki/001geda_tragesym_tutorial.html b/docs/wiki/001geda_tragesym_tutorial.html index dcc33c051..e3f6c3c69 100644 --- a/docs/wiki/001geda_tragesym_tutorial.html +++ b/docs/wiki/001geda_tragesym_tutorial.html @@ -6,7 +6,7 @@ geda:tragesym_tutorial.fr - + diff --git a/docs/wiki/001geda_usage.html b/docs/wiki/001geda_usage.html index 0b624e00b..51eb5d72b 100644 --- a/docs/wiki/001geda_usage.html +++ b/docs/wiki/001geda_usage.html @@ -6,8 +6,8 @@ geda:usage.fr - - + + @@ -44,7 +44,7 @@

    -La première chose à faire est de lire et comprendre l’excellent gschem -> gsch2pcb -> PCB tutoriel de Bill Wilson. Cela devrait vous permettre de débuter. +La première chose à faire est de lire et comprendre l’excellent gschem -> gsch2pcb -> PCB tutoriel de Bill Wilson. Cela devrait vous permettre de débuter.

    @@ -56,7 +56,7 @@ Néanmoins, peut être que la meilleure voie pour apprendre la suite gEDA est de

    - +

    À quoi ressemble de le flux de conception de gEDA?

    @@ -109,7 +109,7 @@ Mis en mots, le flux de conception pour un PCB simple se fait de la manière sui

    - +

    Quelles sont les limitations pour les outils gEDA?

    @@ -130,7 +130,7 @@ La chose la plus importante à garder en mémoire à propos des limitations de g
    - +

    Quels fichiers de configuration locaux sont utilisés pour un projet?

    @@ -151,7 +151,7 @@ Une conception typique de PCB nécessite les fichiers de config suivants dans vo

    - +

    Quels sont les noms et les emplacements des fichiers RC utilisés avec les applications gEDA/gaf?

    @@ -228,7 +228,7 @@ Finalement, notez que les applications gEDA/gaf recherchent jusqu’à six fichi

    - +

    Qu'en est-il du gestionnaire de projet?

    @@ -241,6 +241,6 @@ Malheureusement, le développement de « geda » n’a pas suivi le reste de gED

    - + diff --git a/docs/wiki/Makefile.am b/docs/wiki/Makefile.am dissimilarity index 89% index 1ec4c8670..ca08df9bb 100644 --- a/docs/wiki/Makefile.am +++ b/docs/wiki/Makefile.am @@ -1,13 +1,13 @@ - - -docname=wiki -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 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 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_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 playground_transistor_guide.html geda_faq.html geda_pcb_ug.html - -EXTRA_DIST = $(docs_DATA) - -MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in - + + +docname=wiki +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 playground_transistor_guide.html geda_faq.html geda_pcb_ug.html + +EXTRA_DIST = $(docs_DATA) + +MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in + diff --git a/docs/wiki/_detail/Makefile.am b/docs/wiki/_detail/Makefile.am dissimilarity index 90% index d37894e26..e7725e2b1 100644 --- a/docs/wiki/_detail/Makefile.am +++ b/docs/wiki/_detail/Makefile.am @@ -1,11 +1,11 @@ - - -docname=wiki -docsdir = @GEDADOCDIR@/$(docname)/_detail - -docs_DATA = geda_net.html geda_faq_attrib.html geda_board-4.html 001tragesym_xemacs_modifiedselection.html geda_warmup_gschem03.html geda_gschem_screenshot_001.html geda_pcb-el-1.html tragesym_gschem_finished.html geda_rf_cascade_figure1.html geda_geda_flow.html 001tragesym_acroread_selectiontable.html geda_board-2.html geda_one-sch-3.html 001geda_terminal_screenshot_001.html 001tragesym_gschem_finished.html 001tragesym_xemacs_rawselection.html tragesym_ooo_rearanged.html tragesym_gschem_showhidden.html 001tragesym_kpdf_pinconfiguration.html tragesym_acroread_selectiontable.html geda_design_flow.html geda_switcap_figure1.html geda_two-sch-1.html geda_two-sch-2.html geda_status_screenshot.html 001geda_gschem_screenshot_001.html geda_symbol_7400-1.html geda_board-3.html geda_gschem-sym-1.html geda_switcap_figure4.html 001geda_ambiguous1.html geda_board-6.html 001geda_gschem_workflow_01.html 001geda_ambiguous1_fixed.html geda_warmup_gschem02.html 001geda_symbol_7400-1.html geda_board-1.html geda_gschem-sym-3.html geda_switcap_figure3.html geda_one-sch-1.html geda_pcb-el-2.html 001tragesym_ooo_selection.html geda_nets.html geda_coordinatespace.html 001tragesym_ooo_rearanged.html geda_warmup_add_component.html geda_ambiguous1.html 001geda_status_screenshot.html geda_ambiguous1_fixed.html tragesym_ooo_attributes.html tragesym_kpdf_pinconfiguration.html geda_one-sch-2.html geda_terminal_screenshot_001.html 001tragesym_ooo_changedpins.html geda_rf_cascade_figure2.html 001tragesym_kpdf_pindescription.html geda_gschem-sym-2.html geda_switcap_figure2.html 001geda_faq_attrib.html tragesym_xemacs_rawselection.html devel_tips_dialog_picture.html geda_warmup_gschem01.html tragesym_xemacs_modifiedselection.html geda_board-5.html geda_fileformat_textgraphic.html 001geda_design_flow.html geda_symbol_7400-1_hidden.html tragesym_ooo_changedpins.html 001geda_nets.html geda_gschem_workflow_01.html 001geda_symbol_7400-1_hidden.html 001tragesym_ooo_attributes.html 001tragesym_gschem_showhidden.html tragesym_kpdf_pindescription.html tragesym_ooo_selection.html - -EXTRA_DIST = $(docs_DATA) - -MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in - + + +docname=wiki +docsdir = @GEDADOCDIR@/$(docname)/_detail + +docs_DATA = geda_net.html geda_faq_attrib.html geda_board-4.html .gitignore 001tragesym_xemacs_modifiedselection.html geda_warmup_gschem03.html geda_gschem_screenshot_001.html geda_pcb-el-1.html tragesym_gschem_finished.html geda_rf_cascade_figure1.html geda_geda_flow.html 001tragesym_acroread_selectiontable.html geda_board-2.html geda_one-sch-3.html 001geda_terminal_screenshot_001.html 001tragesym_gschem_finished.html 001tragesym_xemacs_rawselection.html tragesym_ooo_rearanged.html tragesym_gschem_showhidden.html 001tragesym_kpdf_pinconfiguration.html tragesym_acroread_selectiontable.html geda_design_flow.html geda_switcap_figure1.html geda_two-sch-1.html geda_two-sch-2.html geda_status_screenshot.html 001geda_gschem_screenshot_001.html geda_symbol_7400-1.html geda_board-3.html geda_gschem-sym-1.html geda_switcap_figure4.html 001geda_ambiguous1.html geda_board-6.html 001geda_gschem_workflow_01.html 001geda_ambiguous1_fixed.html geda_warmup_gschem02.html 001geda_symbol_7400-1.html geda_board-1.html geda_gschem-sym-3.html geda_switcap_figure3.html geda_one-sch-1.html geda_pcb-el-2.html 001tragesym_ooo_selection.html geda_nets.html geda_coordinatespace.html 001tragesym_ooo_rearanged.html geda_warmup_add_component.html geda_ambiguous1.html 001geda_status_screenshot.html geda_ambiguous1_fixed.html tragesym_ooo_attributes.html tragesym_kpdf_pinconfiguration.html geda_one-sch-2.html geda_terminal_screenshot_001.html 001tragesym_ooo_changedpins.html geda_rf_cascade_figure2.html 001tragesym_kpdf_pindescription.html geda_gschem-sym-2.html geda_switcap_figure2.html 001geda_faq_attrib.html tragesym_xemacs_rawselection.html devel_tips_dialog_picture.html geda_warmup_gschem01.html tragesym_xemacs_modifiedselection.html geda_board-5.html geda_fileformat_textgraphic.html 001geda_design_flow.html geda_symbol_7400-1_hidden.html tragesym_ooo_changedpins.html 001geda_nets.html geda_gschem_workflow_01.html 001geda_symbol_7400-1_hidden.html 001tragesym_ooo_attributes.html 001tragesym_gschem_showhidden.html tragesym_kpdf_pindescription.html tragesym_ooo_selection.html + +EXTRA_DIST = $(docs_DATA) + +MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in + diff --git a/docs/wiki/_media/Makefile.am b/docs/wiki/_media/Makefile.am dissimilarity index 87% index c549444c9..d731a1fe0 100644 --- a/docs/wiki/_media/Makefile.am +++ b/docs/wiki/_media/Makefile.am @@ -1,11 +1,11 @@ - - -docname=wiki -docsdir = @GEDADOCDIR@/$(docname)/_media - -docs_DATA = geda_one-sch-2.png geda_fileformat_textgraphic.jpg geda_switcap_figure2.jpg geda_board-2.png geda_pcb-el-2.png geda_gschem-sym-3.png tragesym_ooo_changedpins.png geda_faq_attrib.jpg geda_warmup_add_component.png geda_gschem-sym-2.png geda_one-sch-1.png geda_board-5.png geda_gschem_screenshot_001.jpg geda_gschem_workflow_01.jpg geda_terminal_screenshot_001.jpg geda_ambiguous1_fixed.png geda_nets.jpg 002tragesym_template tragesym_ooo_rearanged.png geda_one-sch-3.png geda_board-6.png geda_ambiguous1.png geda_design_flow.jpg tragesym_ooo_selection.png geda_two-sch-2.png geda_pcb-el-1.png tragesym_gschem_showhidden.png geda_net.jpg tragesym_ooo_attributes.png geda_two-sch-1.png geda_switcap_figure3.jpg geda_rf_cascade_figure2.jpg geda_status_screenshot.jpg 001tragesym_template geda_switcap_figure4.jpg geda_switcap_figure1.jpg geda_board-3.png tragesym_xemacs_rawselection.png geda_warmup_gschem01.png tragesym_kpdf_pinconfiguration.png geda_gschem-sym-1.png geda_geda_flow.png geda_symbol_7400-1.png devel_tips_dialog_picture.png geda_board-4.png tragesym_acroread_selectiontable.png geda_coordinatespace.jpg tragesym_xemacs_modifiedselection.png geda_warmup_gschem02.png geda_warmup_gschem03.png 003tragesym_template tragesym_template geda_symbol_7400-1_hidden.png geda_rf_cascade_figure1.jpg tragesym_gschem_finished.png tragesym_kpdf_pindescription.png geda_board-1.png 001tragesym_template.txt tragesym_template.txt - -EXTRA_DIST = $(docs_DATA) - -MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in - + + +docname=wiki +docsdir = @GEDADOCDIR@/$(docname)/_media + +docs_DATA = geda_one-sch-2.png geda_fileformat_textgraphic.jpg geda_switcap_figure2.jpg geda_board-2.png geda_pcb-el-2.png .gitignore geda_gschem-sym-3.png tragesym_ooo_changedpins.png geda_faq_attrib.jpg geda_warmup_add_component.png geda_gschem-sym-2.png geda_one-sch-1.png geda_board-5.png geda_gschem_screenshot_001.jpg geda_gschem_workflow_01.jpg tragesym_template.txt geda_terminal_screenshot_001.jpg geda_ambiguous1_fixed.png geda_nets.jpg 002tragesym_template tragesym_ooo_rearanged.png geda_one-sch-3.png geda_board-6.png geda_ambiguous1.png geda_design_flow.jpg tragesym_ooo_selection.png geda_two-sch-2.png 001tragesym_template.txt geda_pcb-el-1.png tragesym_gschem_showhidden.png geda_net.jpg tragesym_ooo_attributes.png geda_two-sch-1.png geda_switcap_figure3.jpg geda_rf_cascade_figure2.jpg geda_status_screenshot.jpg 001tragesym_template geda_switcap_figure4.jpg geda_switcap_figure1.jpg geda_board-3.png tragesym_xemacs_rawselection.png geda_warmup_gschem01.png tragesym_kpdf_pinconfiguration.png geda_gschem-sym-1.png geda_geda_flow.png geda_symbol_7400-1.png devel_tips_dialog_picture.png geda_board-4.png tragesym_acroread_selectiontable.png geda_coordinatespace.jpg tragesym_xemacs_modifiedselection.png geda_warmup_gschem02.png geda_warmup_gschem03.png 003tragesym_template tragesym_template geda_symbol_7400-1_hidden.png geda_rf_cascade_figure1.jpg tragesym_gschem_finished.png tragesym_kpdf_pindescription.png geda_board-1.png + +EXTRA_DIST = $(docs_DATA) + +MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in + diff --git a/docs/wiki/geda_pcb_mp.html b/docs/wiki/geda_bill_wilson_s.html similarity index 51% copy from docs/wiki/geda_pcb_mp.html copy to docs/wiki/geda_bill_wilson_s.html index e91751362..d7f8f44db 100644 --- a/docs/wiki/geda_pcb_mp.html +++ b/docs/wiki/geda_bill_wilson_s.html @@ -4,59 +4,24 @@ lang="en" dir="ltr"> - geda:pcb_mp + geda:bill_wilson_s - - - + + + - + - - + +
    - - - -

    PCB man-page

    -
    -
    PCB(1)									PCB(1)
-
-
-
-NAME
-       pcb - Printed circuit board layout tool
-
-
-SYNOPSIS
-       pcb [options] [pcb file]
-
-
-DESCRIPTION
-       The  pcb	 program  is  a tool for the layout of printed circuit boards.
-       The complete manual for pcb is provided in a GNU texinfo format as well
-       as HTML and PDF.	 The texinfo version of the manual is typically viewed
-       with the info program or alternatively with emacs or a  graphical  info
-       viewer	  such	  as	tkinfo	  /usr/local/share/pcb/pcb.html	   and
-       /usr/local/share/pcb/pcb.pdf.  The prefix "/usr/local" may vary at your
-       site.
-
-
-
-
-
-
-
-									PCB(1)
    - -
    diff --git a/docs/wiki/geda_bom_readme.html b/docs/wiki/geda_bom_readme.html index d4bc25550..5e42f23c3 100644 --- a/docs/wiki/geda_bom_readme.html +++ b/docs/wiki/geda_bom_readme.html @@ -6,7 +6,7 @@ geda:bom_readme - + diff --git a/docs/wiki/geda_circuit_simulation_improvements.html b/docs/wiki/geda_circuit_simulation_improvements.html index c8c84505b..7fc3ebf4f 100644 --- a/docs/wiki/geda_circuit_simulation_improvements.html +++ b/docs/wiki/geda_circuit_simulation_improvements.html @@ -6,7 +6,7 @@ geda:circuit_simulation_improvements - + diff --git a/docs/wiki/geda_covered_mp.html b/docs/wiki/geda_covered_mp.html index ff5400a50..524c00952 100644 --- a/docs/wiki/geda_covered_mp.html +++ b/docs/wiki/geda_covered_mp.html @@ -6,7 +6,7 @@ geda:covered_mp - + diff --git a/docs/wiki/geda_csygas.html b/docs/wiki/geda_csygas.html index dec2fb105..967364c71 100644 --- a/docs/wiki/geda_csygas.html +++ b/docs/wiki/geda_csygas.html @@ -6,7 +6,7 @@ geda:csygas - + diff --git a/docs/wiki/geda_cygwin.html b/docs/wiki/geda_cygwin.html index 8f38fa66e..c82c2b552 100644 --- a/docs/wiki/geda_cygwin.html +++ b/docs/wiki/geda_cygwin.html @@ -6,7 +6,7 @@ geda:cygwin - + diff --git a/docs/wiki/geda_data_plotting_improvements.html b/docs/wiki/geda_data_plotting_improvements.html index 51df829a1..b2dfa129b 100644 --- a/docs/wiki/geda_data_plotting_improvements.html +++ b/docs/wiki/geda_data_plotting_improvements.html @@ -6,7 +6,7 @@ geda:data_plotting_improvements - + diff --git a/docs/wiki/geda_data_structure_design_discussion.html b/docs/wiki/geda_data_structure_design_discussion.html index 4cb090cb4..00c8abd16 100644 --- a/docs/wiki/geda_data_structure_design_discussion.html +++ b/docs/wiki/geda_data_structure_design_discussion.html @@ -6,7 +6,7 @@ geda:data_structure_design_discussion - + diff --git a/docs/wiki/geda_debian.html b/docs/wiki/geda_debian.html index 20d23ee69..2355f06e1 100644 --- a/docs/wiki/geda_debian.html +++ b/docs/wiki/geda_debian.html @@ -6,7 +6,7 @@ geda:debian - + diff --git a/docs/wiki/geda_design_flow_and_hierarchy_roadmap.html b/docs/wiki/geda_design_flow_and_hierarchy_roadmap.html index 99502a86e..f3d53dc17 100644 --- a/docs/wiki/geda_design_flow_and_hierarchy_roadmap.html +++ b/docs/wiki/geda_design_flow_and_hierarchy_roadmap.html @@ -6,7 +6,7 @@ geda:design_flow_and_hierarchy_roadmap - + diff --git a/docs/wiki/geda_devel-tips.html b/docs/wiki/geda_devel-tips.html index f24b5371e..04b9a0b40 100644 --- a/docs/wiki/geda_devel-tips.html +++ b/docs/wiki/geda_devel-tips.html @@ -6,7 +6,7 @@ geda:devel-tips - + diff --git a/docs/wiki/geda_documentation.html b/docs/wiki/geda_documentation.html index ae03f86c3..05128c2f7 100644 --- a/docs/wiki/geda_documentation.html +++ b/docs/wiki/geda_documentation.html @@ -6,7 +6,7 @@ geda:documentation - + @@ -247,7 +247,7 @@

    PCB

      -
    • The pcb FAQ: faq-pcb
      +
    • The pcb FAQ: faq-pcb
    • The official manual of pcb
      • diff --git a/docs/wiki/geda_eagle_pcb_netlister_readme.html b/docs/wiki/geda_eagle_pcb_netlister_readme.html index ee8dd29bf..fdf9c19f2 100644 --- a/docs/wiki/geda_eagle_pcb_netlister_readme.html +++ b/docs/wiki/geda_eagle_pcb_netlister_readme.html @@ -6,7 +6,7 @@ geda:eagle_pcb_netlister_readme - + diff --git a/docs/wiki/geda_example_hsm.html b/docs/wiki/geda_example_hsm.html index 419c56db1..1fb1dec68 100644 --- a/docs/wiki/geda_example_hsm.html +++ b/docs/wiki/geda_example_hsm.html @@ -6,7 +6,7 @@ geda:example_hsm - + diff --git a/docs/wiki/geda_example_usbjtag.html b/docs/wiki/geda_example_usbjtag.html index 9c1326c15..f0a413ae7 100644 --- a/docs/wiki/geda_example_usbjtag.html +++ b/docs/wiki/geda_example_usbjtag.html @@ -6,7 +6,7 @@ geda:example_usbjtag - + diff --git a/docs/wiki/geda_faq-attribs.html b/docs/wiki/geda_faq-attribs.html index 401d94cf7..66622730c 100644 --- a/docs/wiki/geda_faq-attribs.html +++ b/docs/wiki/geda_faq-attribs.html @@ -6,7 +6,7 @@ geda:faq-attribs - + diff --git a/docs/wiki/geda_faq-gnetlist.html b/docs/wiki/geda_faq-gnetlist.html index 7d9acc6aa..805433549 100644 --- a/docs/wiki/geda_faq-gnetlist.html +++ b/docs/wiki/geda_faq-gnetlist.html @@ -6,7 +6,7 @@ geda:faq-gnetlist - + diff --git a/docs/wiki/geda_faq-gsch2pcb.html b/docs/wiki/geda_faq-gsch2pcb.html index a30506c09..6acc3f6aa 100644 --- a/docs/wiki/geda_faq-gsch2pcb.html +++ b/docs/wiki/geda_faq-gsch2pcb.html @@ -6,8 +6,8 @@ geda:faq-gsch2pcb - - + + @@ -47,8 +47,7 @@

      -Currently, the best information about this is contained in Bill Wilson’s outstanding tutorial.
      - This page will grow later to contain answers to FAQs posted on the geda-user list. +Currently, the best information about how to get started with gsch2pcb is contained in Bill Wilson’s outstanding tutorial.

      @@ -56,7 +55,7 @@ There is a wrapper script for gsch2pcb called sch2pcb. Read about it in the

      - +

      Where can I download gsch2pcb?

      @@ -77,7 +76,7 @@ gsch2pcb is part of gEDA/gaf, in the utils. It is normally installed by default
    - +

    gsch2pcb can't find some of my footprints, or errors out. What can I do to diagnose my problem?

    @@ -86,6 +85,6 @@ Try running gsch2pcb in double verbose mode: “gsch2pcb -v -v”. This will pro

    - + diff --git a/docs/wiki/geda_faq-gschem.html b/docs/wiki/geda_faq-gschem.html index c73ff5f24..f0c85770c 100644 --- a/docs/wiki/geda_faq-gschem.html +++ b/docs/wiki/geda_faq-gschem.html @@ -7,7 +7,7 @@ geda:faq-gschem - + @@ -27,9 +27,15 @@
      +
    • General
      + +
    • Gschem usage
    • Gschem installation/run-time problems
      @@ -78,11 +84,31 @@ +

      General

      +
      + +
      + +

      I found a bug! What can I do about it?

      +
      +
        +
      1. See if you can reproduce the bug.
        +
        2. +
      2. Ask on the geda-user mailing list if there is a work around, or has been dealt with in the bleeding edge version of gEDA/gaf. Note, that you must subscribe to the geda-user e-mail list before you can post to this list.
        +
        3. +
      3. See whether the issue is already in the bug tracking system of geda/gaf. If not, file a bug report. Make sure to give all information necessary to reproduce the bug and add the version of gEDA/gaf that contains the bug.
        +
        4. +
      4. Finally, as with all open source projects, you may flex your programming muscles and try to fix the bug yourself. Please file a patch of the changes you had to make to the BTS of geda/gaf. The patch will be gladly accepted to improve the next release of gEDA/gaf.
        +
        5. +
      + +
      +

      Gschem usage

      - +

      How do I move a component?

      @@ -143,7 +169,16 @@ One:
      - + +

      How do I move components without dragging a tail of connectet nets?

      +
      + +

      +Type [or] to toggle this behaviour. That is, the “o” key followed by the “r” key. The status window will report if the toggle command was performed. The command can also be accessed via the Options menu. +

      + +
      +

      How do I change the size of the text on a symbol?

        @@ -172,16 +207,16 @@ One:

      - +

      How do I unlock a locked component

      -When a component is locked it is unselectable using the middle mouse button however it is selectable using a window select. To window select a component click and hold the left mouse button and drag the mouse to create a rectangular region containing the component to be unlocked. Execute the command Edit → unLock to unlock the component. +When a component is locked it cannot be selected with the middle mouse button; however it is selectable using a window select. To window select a component, click and hold the left mouse button and drag the mouse to create a rectangular region containing the component to be unlocked. Execute the command Edit → unLock to unlock the component.

      - +

      How can I get refdes automatically numbered when I draw a schematic?

      @@ -199,7 +234,7 @@ Please substitute $YOUR_INSTALL_PATH by the path where geda is installed.

      - +

      What is a Bus and how do I use it?

      @@ -212,16 +247,16 @@ Some users have found it helpful to organize their nets by incorporating a bus n

      - +

      How can I change Key Bindings in gschem?

      -Key accels are determined by configuration files read on start-up. The default key bindings are set in the file system-gschemrc. If you want to chenge them, it is recommended to copy and modify the corresponding keymap section to a local config file ($HOME/.gEDA/gschemrc, or $PWD/gschemrc). The modified section will override the the definitions given in system-gschemrc. +Key accels are determined by configuration files read on start-up. The default key bindings are set in the file system-gschemrc. If you want to change them, it is recommended to copy and modify the corresponding keymap section to a local config file ($HOME/.gEDA/gschemrc, or $PWD/gschemrc). The modified section will override the the definitions given in system-gschemrc.

      - +

      What are the mouse bindings in gschem?

      @@ -229,7 +264,7 @@ Key accels are determined by configuration files read on start-up. The default k By default you get:

        -
      • Left mouse button is used for picking and drawing
        +
      • Left mouse button is used for picking and drawing.
      • Middle mouse button is either move object (just hold down the middle button over an object and move the mouse) or copy object (ALT key held down while holding down the middle button over object and move the mouse).
        • @@ -267,12 +302,12 @@ For more information on these options, please see the ${install_prefix}/sh

      - +

      Can gschem do hierarchical designs with sub sheets?

      -Yes. Sub sheets are represented by special symbols on the top level schematic. You can find an example for a hierarchical design in the doc section of gschem (geda-doc/examples/gTAG/gTAG.sch).Currently, there is no way to automatically build a sub sheet symbol from an actual sub sheet. The sub sheet symbol has to be drawn manually. Any patches or external scripts that get the job done would be greatly appreciated. +Yes. Sub sheets are represented by special symbols on the top level schematic. You can find an example for a hierarchical design in the doc section of gschem (geda-doc/examples/gTAG/gTAG.sch). Currently, there is no way to automatically build a sub sheet symbol from an actual sub sheet. The sub sheet symbol has to be drawn manually. Any patches or external scripts that get the job done would be greatly appreciated.

      @@ -280,16 +315,16 @@ A source attribute attached to the sub sheet symbol gives the path to the sub sh

      -To convert a hierarchy to a netlist just call gsch2pcb on the top level schematic. By default, net names and refdes’s of components are strictly local to the subsheet. They get the sub sheet symbol refdes as a prefix when inserted into the net list. You can even use multiple instances of a sub sheet symbol without undue short cuts. Whether or not net names and refdes’s are mangled and thus local to the sub sheet can be configured in a the config file gnetlistrc. Copy the corresponding lines from system-gnetlistrc to gnetlistrc in the current working directory or to $HOME/.gEDA/gnetlistrc. A convinient configuration is to make nets delivered by power symbols global while ordinary nets remain local to the sub sheet. This can be achieved with “hierarchy-netattrib-mangle” enabled. +To convert a hierarchy to a netlist just call gsch2pcb on the top level schematic. By default, net names and refdes’s of components are strictly local to the subsheet. They get the sub sheet symbol refdes as a prefix when inserted into the net list. You can even use multiple instances of a sub sheet symbol without undue short cuts. Whether or not net names and refdes’s are mangled and thus local to the sub sheet can be configured in the config file gnetlistrc. Copy the corresponding lines from system-gnetlistrc to gnetlistrc in the current working directory or to $HOME/.gEDA/gnetlistrc. A convenient configuration is to make nets delivered by power symbols global while ordinary nets remain local to the sub sheet. This can be achieved with “hierarchy-netattrib-mangle” enabled.

      - +

      gschem symbols

      - +

      What's this business about heavy vs. light symbols?

      @@ -298,7 +333,7 @@ This nomenclature arose from a discussion which frequently appears on the geda-u

      -The debate between proponents of heavy and light symbols is very detailed and involved. In caricature, proponents of heavy symbols belive that they provide better integration between gschem and PCB since the important layout attributes (such as footprint name) are already built into the symbol. This is considered a good thing for new users (noobs) who just want to design a simple board and don’t appreciate or don’t care about the zillions of variations that even a simple resistor might have (e.g. different footprint, TCR, precision, material composition, etc). Proponents of light symbols prefer to deal with attributes at the schematic level because they believe it to be more flexible. They are quick to point out that a library of heavy symbols will quickly grow into the thousands of parts with grotesquely long names trying to distinguish between the different variations of the part. They also point out that the utility “gattrib” is the preferred tool for dealing with attributes at the schematic level (i.e. in the .sch file). +The debate between proponents of heavy and light symbols is very detailed and involved. Briefly, proponents of heavy symbols believe that they provide better integration between gschem and PCB since the important layout attributes (such as footprint name) are already built into the symbol. This is considered a good thing for new users (noobs) who just want to design a simple board and don’t appreciate or don’t care about the zillions of variations that even a simple resistor might have (e.g. different footprint, TCR, precision, material composition, etc). Proponents of light symbols prefer to deal with attributes at the schematic level because they believe it to be more flexible. They are quick to point out that a library of heavy symbols will quickly grow into the thousands of parts with grotesquely long names trying to distinguish between the different variations of the part. They also point out that the utility “gattrib” is the preferred tool for dealing with attributes at the schematic level (i.e. in the .sch file).

      @@ -314,12 +349,12 @@ GEDA/gaf, as default configured, uses light symbols, although it can be configur

      - +

      I am using a symbol out of the library. How come it's not aligned to the grid?

      -The symbols in the symbol library, like those available at the gedasymbols website are contributed by users just like you. Some people use different grid settings than other people (e.g. 50mil vs. 100mil). If you discover a symbol which seems to be off the grid, try reducing your grid spacing, move the symbol so that it sits on your grid, then revert to your preferred grid settings. +The symbols in the symbol library, like those available at the gedasymbols website are contributed by users just like you. Some people use different grid settings than other people (e.g. 50mil vs. 100mil). If you discover a symbol which seems to be off the grid, try reducing your grid spacing, move the symbol so that it sits on your grid, then revert to your preferred grid settings.

      @@ -327,7 +362,7 @@ Yes, the gEDA docs suggest that you use a 100mil grid spacing. But everybody li

      - +

      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?

      @@ -344,28 +379,28 @@ If you want an entire symbol to be graphical (no elec. connections) , add a “g

      - +

      How do I promote an invisible symbol attribute into the schematic?

      Most attributes living in the symbol do not get promoted to the schematic unless they are visible. To promote invisible symbol attributes, look for the following keywords in the system-gschemrc file:

      -
      (attribute-promotion “enabled”);
-(promote-invisible “disabled”) ; ⇐ This one
-(keep-invisible “enabled”)
      +
      (attribute-promotion "enabled");
+(promote-invisible "disabled") ; ⇐ This one
+(keep-invisible "enabled")

      Add to your gschemrc file:

      -
      (promote-invisible “enabled”)
      +
      (promote-invisible "enabled")

      and you will get all the attributes promoted. The “keep-invisible” keyword will keep hidden those attributes that are hidden in the symbol file.

      - +

      What should I do about power pins on my symbols: Make them visible (explicit) or invisible (implicit)?

      @@ -390,11 +425,11 @@ To paraphrase Nancy Reagan: Just say “no” to hidden power pins.

      -That said, it may still be usefull to detach the power pins from the functional part of the symbol. To do so, define a seperate power symbol and give it the same refdes as the functional part. A run of gsch2pcb will treat the siblings properly as one single component. As neither gschem nor gsch2pcb explicitely know that the component is only complete with both symbols defined, you have to check yourself. With this workaround, you can draw all power related circuitry in one corner of the schematic where it does not interfere with the signal nets. In many cases this is advantageous with analog circuits. +That said, it may still be useful to detach the power pins from the functional part of the symbol. To do so, define a seperate power symbol and give it the same refdes as the functional part. A run of gsch2pcb will treat the siblings properly as one single component. As neither gschem nor gsch2pcb explicitely know that the component is only complete with both symbols defined, you have to check yourself. With this workaround, you can draw all power related circuitry in one corner of the schematic where it does not interfere with the signal nets. In many cases this is advantageous with analog circuits.

      - +

      Is there a specification or manual for creating gschem symbols? Where is it?

      @@ -403,7 +438,7 @@ Yes. It is the Symbol

      - +

      Gschem configuration/customization

      @@ -412,7 +447,7 @@ Gschem is configurable in more ways than can be describe here. Look at “system

      - +

      How do I configure my local gafrc to find my local symbol directory?

        @@ -448,7 +483,7 @@ gschem myschematic.sch
    - +

    How can I change the default size of floating text?

    @@ -462,7 +497,7 @@ Put

    - +

    How can I have a different background color other than black?

    @@ -492,7 +527,7 @@ A dark background is preferred by many users.

    - +

    Each time I start gschem, the log message window is shown. Can I disable it?

    @@ -517,12 +552,12 @@ Comment out the startup line (with a ;) and commen 
    (log-window "later")
    - +

    Printing/Output

    - +

    How do I print schematics from the command line?

    @@ -536,7 +571,7 @@ The command line below creates a Postscript file from a schematic file (replace 
    gschem -p -oMY_SCH.ps -sGEDA_SCHEME_DIR/gschem-print.scm MY_SCH.sch

    -The BASH script below, which I name gschem-print, creates a Postscript file for each schematic file that is specified on the command line and then outputs each Postscript file to the default printer: +The bash script below, which I name gschem-print, creates a Postscript file for each schematic file that is specified on the command line and then outputs each Postscript file to the default printer: 

    #!/bin/bash
 
@@ -547,13 +582,13 @@ The BASH script below, which I name gschem-print,
 
 for name in $*
 do
-base=”${name%.*}”
-gschem -p -o$base.ps -sGEDA_SCHEME_DIR/gschem-print.scm $base.sch
-lpr -P$PRINTER $base.ps
+    base="${name%.*}"
+    gschem -p -o$base.ps -sGEDA_SCHEME_DIR/gschem-print.scm $base.sch
+    lpr -P$PRINTER $base.ps
 done
    - +

    How can I get color postscript/PNG output?

    @@ -569,7 +604,7 @@ To control the background of the PS output, change the following line in either 
    (output-color-background 16 "black" "null" "0 0 0" 0 0 0)

    -The “0 0 0��� is the RGB components (between 0..1) for the background color of the PS output. +The “0 0 0” is the RGB components (between 0..1) for the background color of the PS output.

    @@ -582,7 +617,7 @@ The 255 255 255 are the RGB components for the background color of the

    - +

    How can I get black and white postscript/PNG output?

    @@ -597,7 +632,7 @@ For black and white PNG ima 
    (image-color "disabled")       ; for monochromoe PNG output
    - +

    How can I insert schematics into my LaTex document?

      @@ -605,7 +640,7 @@ For black and white PNG ima
    1. Convert the postscript file to epsi with the tool ps2epsi. This is a script from the ghostscript suite.
      2. -
    2. Include usepackage{graphicx} to the preamble of your latex document. Use the comand includegraphics to place your schematic.
      +
    3. Include usepackage{graphicx} to the preamble of your latex document. Use the command includegraphics to place your schematic.
    @@ -621,8 +656,8 @@ For black and white PNG ima \end{document}
    - -

    How can I split postscript output over multiple pages?

    + +

    How can I split Postscript output over multiple pages?

    @@ -630,12 +665,12 @@ gschem does not provide this functionality internally, however there is a progra

    - +

    Gschem installation/run-time problems

    - +

    Gschem segfaults when I delete components on FC5 (and other Linux distributions)! Is there a work-around?

    @@ -658,7 +693,7 @@ csh: 
    setenv G_SLICE always-malloc
    - +

    After installation gschem does not work!? What could be wrong?

    @@ -696,7 +731,7 @@ Also, some older releases of gEDA/gaf had some bugs when the rc files were insta

    - +

    "Add Components" offers no symbols! What can I do about it?

    @@ -714,7 +749,7 @@ Make sure that at least one of your config files contains a valid path to a symb
  • user gschemrc file: ~/.gEDA/gschemrc
    • -
  • local gschemrc file: $PWD/gschemrc]
    +
  • local gschemrc file: $PWD/gschemrc
    • @@ -728,7 +763,7 @@ All of these config files may or may not append paths to the library search list

    - +

    I'm using gschem/gaf through a SSH connection and I get an error like: 'Xlib: extension "RENDER" missing on display "localhost:10.0".'

    @@ -738,7 +773,7 @@ All of these config files may or may not append paths to the library search list 
    $ ssh -X your_username@your_remote_machine

    -and afterwards you get the Xlib RENDER message, then try to get into by doing: +and afterwards you get the Xlib RENDER message, then try using: 

    $ ssh -Y your_username@your_remote_machine
    @@ -747,6 +782,6 @@ The latter enables trusted X11 forwarding.

    - + diff --git a/docs/wiki/geda_faq-pcb.html b/docs/wiki/geda_faq-pcb.html index 60787ae68..9da78f9b0 100644 --- a/docs/wiki/geda_faq-pcb.html +++ b/docs/wiki/geda_faq-pcb.html @@ -6,7 +6,7 @@ geda:faq-pcb - + diff --git a/docs/wiki/geda_faq-simulation.html b/docs/wiki/geda_faq-simulation.html index c59d77935..049877932 100644 --- a/docs/wiki/geda_faq-simulation.html +++ b/docs/wiki/geda_faq-simulation.html @@ -6,7 +6,7 @@ geda:faq-simulation - + diff --git a/docs/wiki/geda_faq.html b/docs/wiki/geda_faq.html index 8e6835e84..00b4d3593 100644 --- a/docs/wiki/geda_faq.html +++ b/docs/wiki/geda_faq.html @@ -6,8 +6,8 @@ geda:faq - - + + @@ -65,7 +65,7 @@ The gEDA project is working on producing a full +

    What is gEDA/gaf and how does it relate to gEDA?

    -gaf stands for “gschem and friends”. It is a subset of the entire tool suite grouped together under the gEDA name. gEDA/gaf is a collection of tools which currently includes: +gaf stands for “gschem and friends”. It is a subset of the entire tool suite grouped together under the gEDA name. gEDA/gaf is a collection of tools which currently includes:

    • gschem: A schematic capture program
      @@ -91,9 +91,9 @@ gaf stands for “gschem and
    • libgeda: Libraries for gschem gnetlist and gsymcheck
      • -
    • gsch2pcb: Forward annotation from your schematic to layout using PCB.
      +
    • gsch2pcb: A tool to forward annotation from your schematic to layout using PCB
      • -
    • some minor utils
      +
    • some minor utilities
    @@ -106,11 +106,11 @@ Even though gaf is very much a part of gEDA, the gEDA name does not necessarily

    -For historical reasons, on freshmeat gaf is known as the package ‘gEDA’. +For historical reasons, on freshmeat gaf is known as the package “gEDA”.

    - +

    What is the gEDA suite?

    @@ -122,7 +122,7 @@ The gEDA suite is a CDROM image (.iso) created by Stuart Brorson to make it easi
  • ngspice – SPICE simulation
    • -
  • gnucap – Analog simulation
    +
  • gnucap – analog simulation
  • gspiceui – GUI front end for ngspice/gnucap
    • @@ -132,7 +132,7 @@ The gEDA suite is a CDROM image (.iso) created by Stuart Brorson to make it easi
  • Icarus Verilog – Verilog simulator
    • -
  • GTKWave – Digitial waveform viewer
    +
  • GTKWave – Digital waveform viewer
  • wcalc – Transmission line and electromagnetic structure analysis
    • @@ -143,7 +143,7 @@ The gEDA suite is a CDROM image (.iso) created by Stuart Brorson to make it easi

    - +

    Why? What makes gEDA so different from other EDA tools?

    @@ -153,15 +153,15 @@ Tools in the gEDA suite and associated tools have the following characteristics:
    • Free in the monetary sense (no cost).
      • -
    • All the file formats and all the source codes are available via the GPL license. This license grants specific rights to the authors and users of GPL‘d software.
      +
    • All the file formats and source code are available via the GPL license. This license grants specific rights to the authors and users of GPL‘d software.
      • -
    • Independence from any one vendor. All gEDA tools come with full source. You can change, improve, port, and even distribute (if you follow the terms of the GPL) the tools.
      +
    • Independence from any one vendor. All gEDA tools come with full source. You may freely redistribute, change, improve and port the tools. You may also distribute your changes, if you follow the terms of the GPL.
    • No mechanism is used to restrict the use of the tools (like making use of hard disk serial numbers or ethernet addresses to force the software to only run on one machine).
    • No arbitrary, marketeering-driven limitations. Free versions of commercial tools usually include capricious limitations (i.e. limited design size, inability to print, inability to export netlists, etc.) which cripple the program, and force the serious user to buy the real tool. In contrast, the gEDA tools are fully-featured, and do not arbitrarily impose limits on design as a way of extracting money from you.
      • -
    • Legacy design protection. Since the software will always run forever (because of above), gEDA tool design files will always be viewable/editable (with the right versions of the software).
      +
    • Legacy design protection. Since the software will always be available, and can always be updated to work with updated operating systems or libraries, gEDA tool design files will always be viewable and editable.
    • Open design flow. This means that the tools talk to each other via known and documented means (files / APIs). It is easy to replace a tool or augment the tools with something else if you so desire.
      • @@ -178,11 +178,11 @@ Tools in the gEDA suite and associated tools have the following characteristics:

    - gEDA may not have all the latest cutting edge features found in other packages and may be viewed sometimes as being on the trailing edge of EDA technology, but the tools are becoming useful to a lot of people because the above mentioned reasons. + gEDA may not have all the latest cutting edge features found in other packages and may be viewed sometimes as being on the trailing edge of EDA technology, but the tools are becoming useful to a lot of people for the above mentioned reasons.

    - +

    Why does the gEDA Suite seem like a collection of random programs, and not a single integrated application?

    @@ -199,7 +199,7 @@ In this way the gEDA suite came together. It is not shared code, or a common use

    - +

    So which is better, a suite (i.e. confederacy) of programs or an integrated application?

    @@ -208,48 +208,48 @@ This is ultimately a matter of religion. I’ll summarize some of the pros and c

    - +

    Suite (confederacy) pros:

    • You can use “best of breed” applications for each part of the design flow. That is, you can use the standard gEDA flow gschem → gsch2pcb → pcb to create a PC Board. However, if you think that the open-source application “pcb” stinks, you can use the flow gschem → gnetlist → Protel (for example). Recall that gnetlist can output more than twenty different netlist formats! Moreover, if you don’t like one component of the flow, you can write another tool to replace it. Now at this time it is true that only a single application generally exists to perform a particular task. However, this situation will likely change with time – witness the forking of the “pcb” project, the contributed netlister gnetman, as well as the HEC project. As a general rule, the suite approach offers the greatest freedom to the user.
      • -
    • The design flow has a lot of natural breakpoints. These occur where one design tool completes its job and writes out a file (i.e. gschem writes out a .sch file, or gnetlist writes out a SPICE netlist). At this point, you can easily break into the flow and write scripts which process and/or munge the design data. For big, advanced designs, this is a real advantage to the “design suite” approach. This advantage may appeal only to the “power user”, but note it’s importance: professional-grade EDA suites (Synopsys, Xilinx) also work the same way.
      +
    • The design flow has a lot of natural breakpoints. These occur where one design tool completes its job and writes out a file (i.e. gschem writes out a .sch file, or gnetlist writes out a SPICE netlist). At this point, you can easily break into the flow and write scripts which process and/or munge the design data. For big, advanced designs, this is a real advantage to the “design suite” approach. This advantage may appeal only to the “power user”, but note its importance: professional-grade EDA suites (Synopsys, Xilinx) also work the same way.
      • -
    • Usage of an applications suite can be automated using a Makefile, or even a Perl script. ASIC designers do this all the time with their design and synthesis tools. Some gEDA users have publically disclosed (on the e-mail list) that they do this too, and point to it as an important feature of the gEDA suite.
      +
    • Usage of an applications suite can be automated using a Makefile, or even a Perl script. ASIC designers do this all the time with their design and synthesis tools. Some gEDA users have stated on the e-mail list that they do this too, and point to it as an important feature of the gEDA suite.
      • -
    • Scalability: A monolithic application is almost always developed by a lone developer who has a single-minded vision for his program. This developer can enforce stylistic and UI standards throughout all his tools. The problem with this is that a single developer – even one who is uniquely gifted – can only write one (or a couple of) parts of an EDA application. Therefore, any open-source, monolithic EDA app will likely always be limited in scope & features by the abilities of a single developer. (I would love to be proven wrong on this point. I welcome counter-examples, but none have come to my attention as of this writing.) On the other hand, a confederacy of developers working independently on their own apps – but meanwhile contributing to a greater whole – can create a very large and capable EDA environment indeed.
      +
    • Scalability: A monolithic application is almost always developed by a lone developer who has a single-minded vision for his program. This developer can enforce stylistic and UI standards throughout all his tools. The problem with this is that a single developer – even one who is uniquely gifted – can only write one or two parts of an EDA application. Therefore, any open-source, monolithic EDA app will likely always be limited in scope and features by the abilities of a single developer. (I would love to be proven wrong on this point. I welcome counter-examples, but none have come to my attention as of this writing.) On the other hand, a confederacy of developers working independently on their own apps – but meanwhile contributing to a greater whole – can create a very large and capable EDA environment indeed.
    - +

    Suite (confederacy) cons:

      -
    • More confusing to newbies, since they don’t know the flow right off the bat. That is, they actually need to RTFM to know what tool to run next. Good documentation helps (that’s why you’re reading this), but documentation is always second choice behind developing an intuitive application interface.
      +
    • More confusing to new users, since they don’t know the flow right off the bat. That is, they actually need to RTFM to know what tool to run next. Good documentation helps (that’s why you’re reading this), but documentation is always second choice behind developing an intuitive application interface.
    • 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.
      • -
    • Since no assumptions are made about the design flow, schematic symbols are necessarily light. 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, Perl scripts to populate footprints, etc.).
      +
    • Since no assumptions are made about the design flow, schematic symbols are necessarily light. 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, Perl scripts to populate footprints, etc.).
    • 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.
    - +

    Monolithic application pros:

      -
    • A single, unified design environment is easier for newbies to grasp. UI conventions may be harmonized. The tool might be intuitive enough that it can be driven without needing to RTFM.
      +
    • A single, unified design environment is easier for new users to grasp. UI conventions may be harmonized. The tool might be intuitive enough that it can be driven without needing to RTFM.
    • Schematic capture symbols can be heavy, so less work is required in attaching attributes to each symbol in a schematic.
    - +

    Monolithic application cons:

      @@ -257,12 +257,12 @@ This is ultimately a matter of religion. I’ll summarize some of the pros and c
    • Lack of choice. If the developer doesn’t like your way of doing things, you have no choice. Even if you submit patches to enable your way of performing a task, there is a chance the main developer will ignore or reject your patches. This is probably not an issue for newbies, but for “power users” it represents a problem.
      • -
    • Risk. If the apps developer quits, the code becomes abandoned, and the users suffer. This effectively happened to the program XTrkCAD, a CAD program for designing model railroads. The author of this program quit developing it, but thankfully placed his stuff on Sourceforge so that the program wouldn’t simply disappear. Unfortunately, without the original developer’s involvement, the code languished. Patches contributed to the project went to /dev/null. Eventually, a coalition of concerned user/developers created a fork of the code to enable further development. However, work on the forked code has been piecemeal and sporadic. (Hopefully, this will change someday.) Meanwhile, for the ordinary user, the fact that the original developer quit represents a catastrophe.
      +
    • Risk. If the developer quits, the code becomes abandoned, and the users suffer. This effectively happened to the program XTrkCAD, a CAD program for designing model railroads. The author of this program quit developing it, but thankfully placed his stuff on Sourceforge so that the program wouldn’t simply disappear. Unfortunately, without the original developer’s involvement, the code languished. Patches contributed to the project went to /dev/null. Eventually, a coalition of concerned user/developers created a fork of the code to enable further development. However, work on the forked code has been piecemeal and sporadic. (Hopefully, this will change someday.) Meanwhile, for the ordinary user, the fact that the original developer quit represents a catastrophe.
    - +

    Tool XXX is missing critical feature YYY! What can I do?

    @@ -278,21 +278,21 @@ If you need a new feature implemented in one of the gEDA tools, here are your op
      -
    • Ask politely on the gEDA e-mail lists. If your feature request is simple, or of interest to one of the developers, it’s possible that somebody will implement your feature. If it’s more complicated, its likely that the feature is already under discussion amongst the developers, but nobody has enough spare time to implement it. (You can also submit feature requests via the SourceForge feature requests tracker.) Please don’t rant or flame on the e-mail lists, since you will likely be flamed right back and you won’t get your feature either. Why waste your time?
      +
    • Ask politely on the gEDA e-mail lists. If your feature request is simple, or of interest to one of the developers, it’s possible that somebody will implement your feature. If it’s more complicated, it’s likely that the feature is already under discussion amongst the developers, but nobody has enough spare time to implement it. (You can also submit feature requests via the SourceForge feature requests tracker.) Please don’t rant or flame on the e-mail lists, since you will likely be flamed right back and you won’t get your feature either. Why waste your time?
      -
    • If the above possibilites don’t work for you, hire an open-source developer to write the feature for you! It’s amazing how often this possibility is ignored. People willing to pay $25,000 – $100,000 for commercial EDA tools will balk at paying a teen-age programming whiz $10/hr to re-create the same features in the gEDA Suite. Why? If you’re an educator, consider hiring some students for a UROP project to work on gEDA. If you’re a businessman, hire a teenager or somebody fresh out of school! And if you want seasoned help, you can (soon) turn to some of the main gEDA developers who do consulting. Find them at www.gedaconsulting.com. FIXME
      +
    • If the above possibilities don’t work for you, hire an open-source developer to write the feature for you! It’s amazing how often this possibility is ignored. People willing to pay $25,000 – $100,000 for commercial EDA tools will balk at paying a teen-age programming whiz $10/hr to re-create the same features in the gEDA Suite. Why? If you’re an educator, consider hiring some students for a UROP project to work on gEDA. If you run a business, hire a teenager or somebody fresh out of school! And if you want seasoned help, you can (soon) turn to some of the main gEDA developers who do consulting. Find them at www.gedaconsulting.com. FIXME
    - +

    What license does gEDA use?

    -All of the tools and associated files in gEDA will be released under the GNU General Public License version 2 (GPL), from Free Software Foundation +All of the tools and associated files in gEDA will be released under the GNU General Public License version 2 (GPL), from the Free Software Foundation.

    @@ -300,56 +300,56 @@ From the license:

    -When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. +“When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things."

    -This cannot be stressed enough: gEDA is GPLed software. Therefore nothing proprietary can be distributed with gEDA like part libraries from proprietary EDA products. Conversion program for proprietary libraries will be available, but any converted files which are part of a proprietary product must never find their way into gEDA. Contributed files must be GPLable (or be placed under another free license). Please keep this in mind if you wish to contribute something. +This cannot be stressed enough: gEDA is GPLed software. Therefore nothing proprietary can be distributed with gEDA like part libraries from proprietary EDA products. Conversion programs for proprietary libraries will be available, but any converted files which are part of a proprietary product must never find their way into gEDA. Contributed files must be GPLable (or be placed under another free license). Please keep this in mind if you wish to contribute something.

    -Even though the focus of gEDA is GPLed software, other software licenses are more than welcome to be mixed with the existing software, just as long as they are compatible with the GPL. +Even though the focus of gEDA is GPLed software, other software licenses are more than welcome to be mixed with the existing software, as long as they are compatible with the GPL.

    - +

    Where can I get more information about and download gEDA?

    -The official website is gEDA Project hosted by the SEUL Project. The European mirror is at European gEDA Project mirror hosted by Swedish University Network - Sweden, Nothern Europe. +The official website is gEDA Project hosted by the SEUL Project. The European mirror is at European gEDA Project mirror hosted by Swedish University Network - Sweden, Northern Europe.

    -There are several mailing lists. Please look at the mailing list’s info page for how to subscribe and post. +There are several mailing lists. Please look at the mailing list info page for how to subscribe and post.

    -You can download all the software, including the gEDA suite CDROM from the download page. +You can download all the software, including the gEDA suite CDROM, from the download page.

    -You can find the latest set of documentation on the toplevel documentation page. +You can find the latest set of documentation on the top-level documentation page.

    -Come to the Free EDA Users Group (Freedog) meeeting in Cambridge, MA. The meeting is at 7PM on the first Wednesday of each month at the Kendal Square Starbucks. +Come to the Free EDA Users Group (Freedog) meeeting in Cambridge, MA. The meeting is at 7 PM on the first Wednesday of each month at the Kendal Square Starbucks.

    - +

    Okay, how do I start using gEDA?

    -The most important thing to do is to read and understand Bill Wilson’s excellent gschem -> gsch2pcb -> PCB tutorial. This should get you started. +The most important thing to do is to read and understand Bill Wilson’s excellent gschem -> gsch2pcb -> PCB tutorial. This should get you started.

    -Also be sure to check out the other gEDA documentation. An installation guide is contained in this Wiki, as is some general information about how to use the tools. Spend some time browsing, download the gEDA Suite, and try it out for yourself! +Also be sure to check out the other gEDA documentation. An installation guide is contained in this Wiki, as is some general information about how to use the tools. Spend some time browsing, download the gEDA Suite, and try it out for yourself!

    - + diff --git a/docs/wiki/geda_fbabgapp.html b/docs/wiki/geda_fbabgapp.html index 20734a634..a68338055 100644 --- a/docs/wiki/geda_fbabgapp.html +++ b/docs/wiki/geda_fbabgapp.html @@ -6,7 +6,7 @@ geda:fbabgapp - + diff --git a/docs/wiki/geda_fc1.html b/docs/wiki/geda_fc1.html index e7de566a6..c33a92437 100644 --- a/docs/wiki/geda_fc1.html +++ b/docs/wiki/geda_fc1.html @@ -6,7 +6,7 @@ geda:fc1 - + diff --git a/docs/wiki/geda_fc2.html b/docs/wiki/geda_fc2.html index 5265b768b..e93dff08b 100644 --- a/docs/wiki/geda_fc2.html +++ b/docs/wiki/geda_fc2.html @@ -6,7 +6,7 @@ geda:fc2 - + diff --git a/docs/wiki/geda_fc3.html b/docs/wiki/geda_fc3.html index 0a094fdae..436db2dd0 100644 --- a/docs/wiki/geda_fc3.html +++ b/docs/wiki/geda_fc3.html @@ -6,7 +6,7 @@ geda:fc3 - + diff --git a/docs/wiki/geda_fc4.html b/docs/wiki/geda_fc4.html index b905f0bc6..08e58a4e9 100644 --- a/docs/wiki/geda_fc4.html +++ b/docs/wiki/geda_fc4.html @@ -6,7 +6,7 @@ geda:fc4 - + diff --git a/docs/wiki/geda_fedora_rpm_installation.html b/docs/wiki/geda_fedora_rpm_installation.html index 5ca3e5add..2985d41c1 100644 --- a/docs/wiki/geda_fedora_rpm_installation.html +++ b/docs/wiki/geda_fedora_rpm_installation.html @@ -6,7 +6,7 @@ geda:fedora_rpm_installation - + diff --git a/docs/wiki/geda_file_format_spec.html b/docs/wiki/geda_file_format_spec.html index c07891a18..6cb74c529 100644 --- a/docs/wiki/geda_file_format_spec.html +++ b/docs/wiki/geda_file_format_spec.html @@ -6,8 +6,8 @@ geda:file_format_spec - - + + @@ -154,7 +154,7 @@ A schematic/symbol file for gEDA/gaf consists of:

    - +

    version

    @@ -195,7 +195,7 @@ Valid in: Schematic and Symbol files
  • fileformat version is just an integer with no minor number.
    • -
  • Valid 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
    +
  • Valid 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, 20070526, 20070626
  • CVS or test versions (should not be used): 20030921, 20031004, 20031019, 20031231, 20050814
    • @@ -210,7 +210,7 @@ Valid in: Schematic and Symbol files
    v 20040111 1
    - +

    line

    @@ -298,7 +298,7 @@ A line segment from (23000, 69000) to (28000, 69000) with color index 3, 40 mils

    - +

    picture

    @@ -408,7 +408,7 @@ A picture object with the lower left corner at (16900, 35800). The width of the

    - +

    box

    @@ -537,7 +537,7 @@ A box with the lower left hand corner at (33000, 67300) and a width and height o

    - +

    circle

    @@ -653,7 +653,7 @@ A circle with the center at (38000, 67000) and a radius of 900 mils, color index

    - +

    arc

    @@ -749,7 +749,7 @@ dashlength dashspace

    - +

    text

    @@ -883,7 +883,7 @@ This is a similar text object as the above example, however here there are five

    - +

    net

    @@ -932,7 +932,7 @@ A net segment from (12700, 29400) to (32900, 29400) with color index 4.

    - +

    bus

    @@ -988,7 +988,7 @@ A bus segment from (27300, 37400) to (27300, 35300) with color index 3 and no ne

    - +

    pin

    @@ -1055,7 +1055,7 @@ A pin from (0, 200) to (200, 200) with color index 1, a regular pin, and the fir

    - +

    component

    @@ -1117,7 +1117,7 @@ A component who’s origin is at (18600,19900), is selectable, not rotated, not

    - +

    font

    @@ -1160,7 +1160,7 @@ The above font definition is for the space character.

    - +

    Colors

    @@ -1229,7 +1229,7 @@ In the gEDA/gaf schematic and symbol file format colors are specified via an int

    - +

    Attributes

    @@ -1251,7 +1251,7 @@ The object is a pin which has an attribute pinnumber=3 and pinseq=3 (name=value)

    - +

    Embedded Components

    @@ -1270,7 +1270,7 @@ In the example above, 555-1.sym is the component. The EMBEDDED

    - +

    Document Revision History

    @@ -1289,6 +1289,6 @@ In the example above, 555-1.sym is the component. The EMBEDDED
    -
    +
    diff --git a/docs/wiki/geda_gattrib_readme.html b/docs/wiki/geda_gattrib_readme.html index 009145db7..e81d77240 100644 --- a/docs/wiki/geda_gattrib_readme.html +++ b/docs/wiki/geda_gattrib_readme.html @@ -6,7 +6,7 @@ geda:gattrib_readme - + diff --git a/docs/wiki/geda_gedasuite_installation.html b/docs/wiki/geda_gedasuite_installation.html index 856cb189f..9665e1789 100644 --- a/docs/wiki/geda_gedasuite_installation.html +++ b/docs/wiki/geda_gedasuite_installation.html @@ -6,7 +6,7 @@ geda:gedasuite_installation - + diff --git a/docs/wiki/geda_gerbv_mp.html b/docs/wiki/geda_gerbv_mp.html index a22ac5fc7..7de8951f3 100644 --- a/docs/wiki/geda_gerbv_mp.html +++ b/docs/wiki/geda_gerbv_mp.html @@ -6,7 +6,7 @@ geda:gerbv_mp - + diff --git a/docs/wiki/geda_gerbv_pnp_readme.html b/docs/wiki/geda_gerbv_pnp_readme.html index 28b5b15ef..8a72f5efe 100644 --- a/docs/wiki/geda_gerbv_pnp_readme.html +++ b/docs/wiki/geda_gerbv_pnp_readme.html @@ -6,7 +6,7 @@ geda:gerbv_pnp_readme - + diff --git a/docs/wiki/geda_gfdl.html b/docs/wiki/geda_gfdl.html index f947d05f8..4deaaa591 100644 --- a/docs/wiki/geda_gfdl.html +++ b/docs/wiki/geda_gfdl.html @@ -6,7 +6,7 @@ geda:gfdl - + diff --git a/docs/wiki/geda_glossaire.html b/docs/wiki/geda_glossaire.html index 4d34749ed..35de765d5 100644 --- a/docs/wiki/geda_glossaire.html +++ b/docs/wiki/geda_glossaire.html @@ -6,7 +6,7 @@ geda:glossaire.fr - + diff --git a/docs/wiki/geda_glossary.html b/docs/wiki/geda_glossary.html index 3f66d6eae..6eb4317bb 100644 --- a/docs/wiki/geda_glossary.html +++ b/docs/wiki/geda_glossary.html @@ -6,7 +6,7 @@ geda:glossary - + diff --git a/docs/wiki/geda_gnetlist_mp.html b/docs/wiki/geda_gnetlist_mp.html index 95049f786..1214a1a29 100644 --- a/docs/wiki/geda_gnetlist_mp.html +++ b/docs/wiki/geda_gnetlist_mp.html @@ -6,7 +6,7 @@ geda:gnetlist_mp - + diff --git a/docs/wiki/geda_gnetlist_ug.html b/docs/wiki/geda_gnetlist_ug.html index 6a8ea57c9..8fad7c529 100644 --- a/docs/wiki/geda_gnetlist_ug.html +++ b/docs/wiki/geda_gnetlist_ug.html @@ -6,7 +6,7 @@ geda:gnetlist_ug - + diff --git a/docs/wiki/geda_grcsan.html b/docs/wiki/geda_grcsan.html index f04af281c..dabb12090 100644 --- a/docs/wiki/geda_grcsan.html +++ b/docs/wiki/geda_grcsan.html @@ -6,7 +6,7 @@ geda:grcsan - + diff --git a/docs/wiki/geda_grenum_mp.html b/docs/wiki/geda_grenum_mp.html index bf19bef5a..b3330d74b 100644 --- a/docs/wiki/geda_grenum_mp.html +++ b/docs/wiki/geda_grenum_mp.html @@ -6,7 +6,7 @@ geda:grenum_mp - + diff --git a/docs/wiki/geda_gsch2pcb_readme.html b/docs/wiki/geda_gsch2pcb_readme.html index ab3e92e33..004457805 100644 --- a/docs/wiki/geda_gsch2pcb_readme.html +++ b/docs/wiki/geda_gsch2pcb_readme.html @@ -6,7 +6,7 @@ geda:gsch2pcb_readme - + diff --git a/docs/wiki/geda_gsch2pcb_tutorial.html b/docs/wiki/geda_gsch2pcb_tutorial.html index 87e2297b7..edcf76a07 100644 --- a/docs/wiki/geda_gsch2pcb_tutorial.html +++ b/docs/wiki/geda_gsch2pcb_tutorial.html @@ -6,8 +6,8 @@ geda:gsch2pcb_tutorial - - + + @@ -179,17 +179,13 @@ output-name board

    - If you are using gschem for the first time, try stepping through this simple gschem warmup. + If you are using gschem for the first time, try stepping through this simple gschem warmup.

    one.sch Run gschem one.sch and create this schematic (the second opamp is redundant, but this is just a tutorial):

      -
    • Add component title-B.sym from the titleblock library.
      -
      • -
    • Hit keys ve to zoom to the titleblock extents. Lock the titleblock with the menu Edit→Lock.
      -
    • Add components:
      • From the analog library three resistor-1.sym and two dual-opamp-1.sym.
        @@ -206,8 +202,12 @@ output-name board
      +

      + The large frame of the titleblock is a component too. It has been locked for convienience to prevent the mouse from catching it all the time. To unlock it, select it by dragging with left mouse button held down and press [e - shift-L]. You can find title blocks with different sizes in the default library. Remember, to lock the new title block with [el] while the tiotle block is selected. +

      +
    - +

    Edit the attributes of the components on the schematic.

    @@ -235,7 +235,7 @@ Anyway, we’re done for now with one.sch, so save it with the

    - +

    Create schematic: two.sch

    @@ -290,7 +290,7 @@ Now we are done with the schematics except for assigning refdes

    - +

    Generate PCB Files from Schematics

    @@ -314,7 +314,7 @@ We have to fix one thing in one.sch before we can proceed. Run

    - +

    Layout PCB Files

    @@ -416,7 +416,7 @@ You will want more information on using PCB and there is a set of html docs in t

    - +

    Modifying Schematics

    @@ -473,7 +473,7 @@ board.pcb is backed up as board.pcb.bak1.

    - +

    Custom gschem Symbols

    @@ -572,7 +572,7 @@ For complete details on making symbols, read through the Symbol Creation Documen

    - +

    Custom //file elements//

    @@ -653,7 +653,7 @@ Pin(0 0 70 20 70 42 "" "1" 0x00000101)

    - +

    Custom //m4 elements// (Requires gsch2pcb >= 1.0)

    @@ -792,7 +792,7 @@ Mark(50 50)

    - +

    Multi-user Setup (requires gsch2pcb >= 1.0)

    @@ -833,7 +833,7 @@ With the above, users will have access to site wide libraries and only need to p

    - +

    PC Board Fabrication

    @@ -842,6 +842,6 @@ The tutorial should cover pcb fabrication too.

    - + diff --git a/docs/wiki/geda_gsch2pcb_tutorial_releasenotes.html b/docs/wiki/geda_gsch2pcb_tutorial_releasenotes.html index 30ce33989..cee89aab1 100644 --- a/docs/wiki/geda_gsch2pcb_tutorial_releasenotes.html +++ b/docs/wiki/geda_gsch2pcb_tutorial_releasenotes.html @@ -6,7 +6,7 @@ geda:gsch2pcb_tutorial_releasenotes - + diff --git a/docs/wiki/geda_gschem2pcb_readme.html b/docs/wiki/geda_gschem2pcb_readme.html index 5f7f22aa8..5c7d4e251 100644 --- a/docs/wiki/geda_gschem2pcb_readme.html +++ b/docs/wiki/geda_gschem2pcb_readme.html @@ -6,7 +6,7 @@ geda:gschem2pcb_readme - + diff --git a/docs/wiki/geda_gschem_mp.html b/docs/wiki/geda_gschem_mp.html index b194de4dd..8677d80ca 100644 --- a/docs/wiki/geda_gschem_mp.html +++ b/docs/wiki/geda_gschem_mp.html @@ -6,7 +6,7 @@ geda:gschem_mp - + diff --git a/docs/wiki/geda_gschem_ug.html b/docs/wiki/geda_gschem_ug.html index 596ea7a45..28468630f 100644 --- a/docs/wiki/geda_gschem_ug.html +++ b/docs/wiki/geda_gschem_ug.html @@ -6,7 +6,7 @@ geda:gschem_ug - + diff --git a/docs/wiki/geda_gschem_warmup.html b/docs/wiki/geda_gschem_warmup.html index 5fc53182e..363216976 100644 --- a/docs/wiki/geda_gschem_warmup.html +++ b/docs/wiki/geda_gschem_warmup.html @@ -6,7 +6,7 @@ geda:gschem_warmup - + diff --git a/docs/wiki/geda_gsymcheck_mp.html b/docs/wiki/geda_gsymcheck_mp.html index 4d03c5bca..f25fb182e 100644 --- a/docs/wiki/geda_gsymcheck_mp.html +++ b/docs/wiki/geda_gsymcheck_mp.html @@ -6,7 +6,7 @@ geda:gsymcheck_mp - + diff --git a/docs/wiki/geda_gtkwave_lxt2miner_mp.html b/docs/wiki/geda_gtkwave_lxt2miner_mp.html index fa20236c6..e24dd7a8d 100644 --- a/docs/wiki/geda_gtkwave_lxt2miner_mp.html +++ b/docs/wiki/geda_gtkwave_lxt2miner_mp.html @@ -6,7 +6,7 @@ geda:gtkwave_lxt2miner_mp - + diff --git a/docs/wiki/geda_gtkwave_lxt2vcd_mp.html b/docs/wiki/geda_gtkwave_lxt2vcd_mp.html index 19b5acbe0..acbe10e64 100644 --- a/docs/wiki/geda_gtkwave_lxt2vcd_mp.html +++ b/docs/wiki/geda_gtkwave_lxt2vcd_mp.html @@ -6,7 +6,7 @@ geda:gtkwave_lxt2vcd_mp - + diff --git a/docs/wiki/geda_gtkwave_mp.html b/docs/wiki/geda_gtkwave_mp.html index 3d87f4187..01f8f6b1a 100644 --- a/docs/wiki/geda_gtkwave_mp.html +++ b/docs/wiki/geda_gtkwave_mp.html @@ -6,7 +6,7 @@ geda:gtkwave_mp - + diff --git a/docs/wiki/geda_gtkwave_mvl2lxt_mp.html b/docs/wiki/geda_gtkwave_mvl2lxt_mp.html index c166e15a4..96d2a32ac 100644 --- a/docs/wiki/geda_gtkwave_mvl2lxt_mp.html +++ b/docs/wiki/geda_gtkwave_mvl2lxt_mp.html @@ -6,7 +6,7 @@ geda:gtkwave_mvl2lxt_mp - + diff --git a/docs/wiki/geda_gtkwave_mvl2vcd_mp.html b/docs/wiki/geda_gtkwave_mvl2vcd_mp.html index ec508a25e..195f8bf41 100644 --- a/docs/wiki/geda_gtkwave_mvl2vcd_mp.html +++ b/docs/wiki/geda_gtkwave_mvl2vcd_mp.html @@ -6,7 +6,7 @@ geda:gtkwave_mvl2vcd_mp - + diff --git a/docs/wiki/geda_gtkwave_tex2vcd_mp.html b/docs/wiki/geda_gtkwave_tex2vcd_mp.html index df8aca162..6ab0dcdc2 100644 --- a/docs/wiki/geda_gtkwave_tex2vcd_mp.html +++ b/docs/wiki/geda_gtkwave_tex2vcd_mp.html @@ -6,7 +6,7 @@ geda:gtkwave_tex2vcd_mp - + diff --git a/docs/wiki/geda_gtkwave_tla2vcd_mp.html b/docs/wiki/geda_gtkwave_tla2vcd_mp.html index 92f5a73a9..c6aa055c4 100644 --- a/docs/wiki/geda_gtkwave_tla2vcd_mp.html +++ b/docs/wiki/geda_gtkwave_tla2vcd_mp.html @@ -6,7 +6,7 @@ geda:gtkwave_tla2vcd_mp - + diff --git a/docs/wiki/geda_gtkwave_vcd2lxt2_mp.html b/docs/wiki/geda_gtkwave_vcd2lxt2_mp.html index 21df8acf1..6feddebb8 100644 --- a/docs/wiki/geda_gtkwave_vcd2lxt2_mp.html +++ b/docs/wiki/geda_gtkwave_vcd2lxt2_mp.html @@ -6,7 +6,7 @@ geda:gtkwave_vcd2lxt2_mp - + diff --git a/docs/wiki/geda_gtkwave_vcd2lxt_mp.html b/docs/wiki/geda_gtkwave_vcd2lxt_mp.html index 87b97186a..49ea70616 100644 --- a/docs/wiki/geda_gtkwave_vcd2lxt_mp.html +++ b/docs/wiki/geda_gtkwave_vcd2lxt_mp.html @@ -6,7 +6,7 @@ geda:gtkwave_vcd2lxt_mp - + diff --git a/docs/wiki/geda_gtkwave_vcd2vzt_mp.html b/docs/wiki/geda_gtkwave_vcd2vzt_mp.html index b2d130781..612fdaab9 100644 --- a/docs/wiki/geda_gtkwave_vcd2vzt_mp.html +++ b/docs/wiki/geda_gtkwave_vcd2vzt_mp.html @@ -6,7 +6,7 @@ geda:gtkwave_vcd2vzt_mp - + diff --git a/docs/wiki/geda_gtkwave_vzt2vcd_mp.html b/docs/wiki/geda_gtkwave_vzt2vcd_mp.html index b1256fdb1..55d1b1f6e 100644 --- a/docs/wiki/geda_gtkwave_vzt2vcd_mp.html +++ b/docs/wiki/geda_gtkwave_vzt2vcd_mp.html @@ -6,7 +6,7 @@ geda:gtkwave_vzt2vcd_mp - + diff --git a/docs/wiki/geda_gtkwave_vztminer_mp.html b/docs/wiki/geda_gtkwave_vztminer_mp.html index 7d28c3ff4..1388a7a8a 100644 --- a/docs/wiki/geda_gtkwave_vztminer_mp.html +++ b/docs/wiki/geda_gtkwave_vztminer_mp.html @@ -6,7 +6,7 @@ geda:gtkwave_vztminer_mp - + diff --git a/docs/wiki/geda_hse_howto.html b/docs/wiki/geda_hse_howto.html index ff8437876..4138f617e 100644 --- a/docs/wiki/geda_hse_howto.html +++ b/docs/wiki/geda_hse_howto.html @@ -6,7 +6,7 @@ geda:hse_howto - + diff --git a/docs/wiki/geda_icarus_anc.html b/docs/wiki/geda_icarus_anc.html index 85d61c194..53db13762 100644 --- a/docs/wiki/geda_icarus_anc.html +++ b/docs/wiki/geda_icarus_anc.html @@ -6,7 +6,7 @@ geda:icarus_anc - + diff --git a/docs/wiki/geda_icarus_extensions.html b/docs/wiki/geda_icarus_extensions.html index 215b37985..5add6c6b2 100644 --- a/docs/wiki/geda_icarus_extensions.html +++ b/docs/wiki/geda_icarus_extensions.html @@ -6,7 +6,7 @@ geda:icarus_extensions - + diff --git a/docs/wiki/geda_icarus_glossary.html b/docs/wiki/geda_icarus_glossary.html index c88cc985d..933afe577 100644 --- a/docs/wiki/geda_icarus_glossary.html +++ b/docs/wiki/geda_icarus_glossary.html @@ -6,7 +6,7 @@ geda:icarus_glossary - + diff --git a/docs/wiki/geda_icarus_ieee1364.html b/docs/wiki/geda_icarus_ieee1364.html index 5be005c53..00ddca7bf 100644 --- a/docs/wiki/geda_icarus_ieee1364.html +++ b/docs/wiki/geda_icarus_ieee1364.html @@ -6,7 +6,7 @@ geda:icarus_ieee1364 - + @@ -526,11 +526,8 @@ of 4-value behavior in the dead zone, and appears more user friendly when viewed by reasonable viewers. -$Id$ -$Log$ -Revision 1.7 2007-05-26 02:35:20 ahvezda -Updated wiki from the website. Fixed wikifetch.sh to not download forever. - +$Id: ieee1364-notes.txt,v 1.17 2003/07/15 03:49:22 steve Exp $ +$Log: ieee1364-notes.txt,v $ Revision 1.17 2003/07/15 03:49:22 steve Spelling fixes. diff --git a/docs/wiki/geda_icarus_mp.html b/docs/wiki/geda_icarus_mp.html index c60cd86f6..f931da480 100644 --- a/docs/wiki/geda_icarus_mp.html +++ b/docs/wiki/geda_icarus_mp.html @@ -6,7 +6,7 @@ geda:icarus_mp - + @@ -27,7 +27,7 @@

    Icarus Verilog compiler man-page

    -
    iverilog(1)		 $Date$		   iverilog(1)
+
    iverilog(1)		 $Date: 2005/06/28 04:25:55 $		   iverilog(1)
 
 
 
@@ -381,7 +381,7 @@ COPYRIGHT
 
 
 
-Version			 $Date$		   iverilog(1)
    
+Version			 $Date: 2005/06/28 04:25:55 $		   iverilog(1)
    diff --git a/docs/wiki/geda_icarus_opcodes.html b/docs/wiki/geda_icarus_opcodes.html index 7a3161142..265dabe21 100644 --- a/docs/wiki/geda_icarus_opcodes.html +++ b/docs/wiki/geda_icarus_opcodes.html @@ -6,7 +6,7 @@ geda:icarus_opcodes - + @@ -30,7 +30,7 @@ 
    /*
  * Copyright (c) 2001-2003 Stephen Williams (steve@icarus.com)
  *
- *  $Id$
+ *  $Id: opcodes.txt,v 1.69 2005/11/26 17:16:05 steve Exp $
  */
 
 
diff --git a/docs/wiki/geda_icarus_quick_start.html b/docs/wiki/geda_icarus_quick_start.html
index d5253e920..6ee2a8896 100644
--- a/docs/wiki/geda_icarus_quick_start.html
+++ b/docs/wiki/geda_icarus_quick_start.html
@@ -6,7 +6,7 @@
   
   geda:icarus_quick_start
 
-
+
 
 
 
diff --git a/docs/wiki/geda_icarus_readme.html b/docs/wiki/geda_icarus_readme.html
index 7d4da7eca..5b33825b8 100644
--- a/docs/wiki/geda_icarus_readme.html
+++ b/docs/wiki/geda_icarus_readme.html
@@ -6,7 +6,7 @@
   
   geda:icarus_readme
 
-
+
 
 
 
diff --git a/docs/wiki/geda_icarus_vpi_mp.html b/docs/wiki/geda_icarus_vpi_mp.html
index 5ab58b84a..4d0941494 100644
--- a/docs/wiki/geda_icarus_vpi_mp.html
+++ b/docs/wiki/geda_icarus_vpi_mp.html
@@ -6,7 +6,7 @@
   
   geda:icarus_vpi_mp
 
-
+
 
 
 
@@ -27,7 +27,7 @@
 
 
    Compile front end for VPI modules man-page
    
 
    
-
    iverilog-vpi(1)		 $Date$	       iverilog-vpi(1)
+
    iverilog-vpi(1)		 $Date: 2004/10/04 01:10:53 $	       iverilog-vpi(1)
 
 
 
@@ -147,7 +147,7 @@ COPYRIGHT
 
 
 
-Version			 $Date$	       iverilog-vpi(1)
    
+Version			 $Date: 2004/10/04 01:10:53 $	       iverilog-vpi(1)
    
 
 
    
 
diff --git a/docs/wiki/geda_icarus_vpi_within_vvp.html b/docs/wiki/geda_icarus_vpi_within_vvp.html
index b40ad4e29..764366649 100644
--- a/docs/wiki/geda_icarus_vpi_within_vvp.html
+++ b/docs/wiki/geda_icarus_vpi_within_vvp.html
@@ -6,7 +6,7 @@
   
   geda:icarus_vpi_within_vvp
 
-
+
 
 
 
@@ -30,7 +30,7 @@
 
    /*
  * Copyright (c) 2001 Stephen Williams (steve@icarus.com)
  *
- *  $Id$
+ *  $Id: vpi.txt,v 1.7 2003/02/09 23:33:26 steve Exp $
  */
 
 
diff --git a/docs/wiki/geda_icarus_vvp_runtime.html b/docs/wiki/geda_icarus_vvp_runtime.html
index 055a4a6a5..0eee6c88c 100644
--- a/docs/wiki/geda_icarus_vvp_runtime.html
+++ b/docs/wiki/geda_icarus_vvp_runtime.html
@@ -6,7 +6,7 @@
   
   geda:icarus_vvp_runtime
 
-
+
 
 
 
@@ -27,7 +27,7 @@
 
 
    Icarus Verilog vvp runtime engine man-page
    
 
    
-
    vvp(1)			 $Date$			vvp(1)
+
    vvp(1)			 $Date: 2005/01/29 06:28:19 $			vvp(1)
 
 
 
@@ -171,7 +171,7 @@ COPYRIGHT
 
 
 
-Version			 $Date$			vvp(1)
    
+Version			 $Date: 2005/01/29 06:28:19 $			vvp(1)
    
 
 
    
 
diff --git a/docs/wiki/geda_icarus_vvp_simulation.html b/docs/wiki/geda_icarus_vvp_simulation.html
index 0e73877ac..11617e841 100644
--- a/docs/wiki/geda_icarus_vvp_simulation.html
+++ b/docs/wiki/geda_icarus_vvp_simulation.html
@@ -6,7 +6,7 @@
   
   geda:icarus_vvp_simulation
 
-
+
 
 
 
@@ -30,7 +30,7 @@
 
    /*
  * Copyright (c) 2001 Stephen Williams (steve@icarus.com)
  *
- *  $Id$
+ *  $Id: README.txt,v 1.74 2005/11/25 17:55:26 steve Exp $
  */
 
 VVP SIMULATION ENGINE
diff --git a/docs/wiki/geda_icarus_xilinx_hints.html b/docs/wiki/geda_icarus_xilinx_hints.html
index 3ffef0109..d7d0ce524 100644
--- a/docs/wiki/geda_icarus_xilinx_hints.html
+++ b/docs/wiki/geda_icarus_xilinx_hints.html
@@ -6,7 +6,7 @@
   
   geda:icarus_xilinx_hints
 
-
+
 
 
 
diff --git a/docs/wiki/geda_icarus_xnf.html b/docs/wiki/geda_icarus_xnf.html
index 480021c41..6b2ca0998 100644
--- a/docs/wiki/geda_icarus_xnf.html
+++ b/docs/wiki/geda_icarus_xnf.html
@@ -6,7 +6,7 @@
   
   geda:icarus_xnf
 
-
+
 
 
 
@@ -272,10 +272,7 @@ IBUF, NOT gates cannot be absorbed as in the OPAD case.
  */
 
 
- $Log$
- Revision 1.7  2007-05-26 02:35:20  ahvezda
- Updated wiki from the website.  Fixed wikifetch.sh to not download forever.
-
+ $Log: xnf.txt,v $
  Revision 1.16  2003/07/15 03:49:22  steve
   Spelling fixes.
 
diff --git a/docs/wiki/geda_igarus_fpga_lcg.html b/docs/wiki/geda_igarus_fpga_lcg.html
index a217e53f1..20af6ee68 100644
--- a/docs/wiki/geda_igarus_fpga_lcg.html
+++ b/docs/wiki/geda_igarus_fpga_lcg.html
@@ -6,7 +6,7 @@
   
   geda:igarus_fpga_lcg
 
-
+
 
 
 
@@ -30,7 +30,7 @@
 
    FPGA LOADABLE CODE GENERATOR FOR Icarus Verilog
 
   Copyright 2001 Stephen Williams
-  $Id$
+  $Id: fpga.txt,v 1.12 2005/09/19 21:45:36 steve Exp $
 
 The FPGA code generator supports a variety of FPGA devices, writing
 XNF or EDIF depending on the target. You can select the architecture
@@ -215,10 +215,7 @@ Compile a single-file design with command line tools like so:
 	% par -w map.ncd foo.ncd
 
 ---
-$Log$
-Revision 1.7  2007-05-26 02:35:20  ahvezda
-Updated wiki from the website.  Fixed wikifetch.sh to not download forever.
-
+$Log: fpga.txt,v $
 Revision 1.12  2005/09/19 21:45:36  steve
  Spelling patches from Larry.
 
diff --git a/docs/wiki/geda_installation.html b/docs/wiki/geda_installation.html
index e0700bcd5..f1af94227 100644
--- a/docs/wiki/geda_installation.html
+++ b/docs/wiki/geda_installation.html
@@ -6,7 +6,7 @@
   
   geda:installation
 
-
+
 
 
 
diff --git a/docs/wiki/geda_installed_plugins.html b/docs/wiki/geda_installed_plugins.html
index 4a3bc6600..ae82ef775 100644
--- a/docs/wiki/geda_installed_plugins.html
+++ b/docs/wiki/geda_installed_plugins.html
@@ -6,7 +6,7 @@
   
   geda:installed_plugins
 
-
+
 
 
 
diff --git a/docs/wiki/geda_kig_howto.html b/docs/wiki/geda_kig_howto.html
index b30e60a6d..0d998b244 100644
--- a/docs/wiki/geda_kig_howto.html
+++ b/docs/wiki/geda_kig_howto.html
@@ -6,7 +6,7 @@
   
   geda:kig_howto
 
-
+
 
 
 
diff --git a/docs/wiki/geda_master_attributes_list.html b/docs/wiki/geda_master_attributes_list.html
index f5e2953ca..f6cf8a9bc 100644
--- a/docs/wiki/geda_master_attributes_list.html
+++ b/docs/wiki/geda_master_attributes_list.html
@@ -6,7 +6,7 @@
   
   geda:master_attributes_list
 
-
+
 
 
 
diff --git a/docs/wiki/geda_mcalc_readme.html b/docs/wiki/geda_mcalc_readme.html
index 9726c5c6c..084128f43 100644
--- a/docs/wiki/geda_mcalc_readme.html
+++ b/docs/wiki/geda_mcalc_readme.html
@@ -6,7 +6,7 @@
   
   geda:mcalc_readme
 
-
+
 
 
 
@@ -27,7 +27,7 @@
 
 
    mcalc README
    
 
    
-
    $Id$
+
    $Id: README,v 1.1 2001/08/16 11:19:01 dan Exp $
 
 WHAT IS IT?
 ------------
diff --git a/docs/wiki/geda_na_howto.html b/docs/wiki/geda_na_howto.html
index e17f56018..a59dad5dc 100644
--- a/docs/wiki/geda_na_howto.html
+++ b/docs/wiki/geda_na_howto.html
@@ -6,7 +6,7 @@
   
   geda:na_howto
 
-
+
 
 
 
diff --git a/docs/wiki/geda_ngnutmeg_mp.html b/docs/wiki/geda_ngnutmeg_mp.html
index 78d8324c7..293f2badb 100644
--- a/docs/wiki/geda_ngnutmeg_mp.html
+++ b/docs/wiki/geda_ngnutmeg_mp.html
@@ -6,7 +6,7 @@
   
   geda:ngnutmeg_mp
 
-
+
 
 
 
diff --git a/docs/wiki/geda_ngsconvert_mp.html b/docs/wiki/geda_ngsconvert_mp.html
index 25ce10b13..905a30e73 100644
--- a/docs/wiki/geda_ngsconvert_mp.html
+++ b/docs/wiki/geda_ngsconvert_mp.html
@@ -6,7 +6,7 @@
   
   geda:ngsconvert_mp
 
-
+
 
 
 
diff --git a/docs/wiki/geda_ngspice_mp.html b/docs/wiki/geda_ngspice_mp.html
index 43636e4eb..ab477819c 100644
--- a/docs/wiki/geda_ngspice_mp.html
+++ b/docs/wiki/geda_ngspice_mp.html
@@ -6,7 +6,7 @@
   
   geda:ngspice_mp
 
-
+
 
 
 
diff --git a/docs/wiki/geda_olib_readme.html b/docs/wiki/geda_olib_readme.html
index 2d0ee2983..84d72fae5 100644
--- a/docs/wiki/geda_olib_readme.html
+++ b/docs/wiki/geda_olib_readme.html
@@ -6,7 +6,7 @@
   
   geda:olib_readme
 
-
+
 
 
 
diff --git a/docs/wiki/geda_pcb-quick_reference.html b/docs/wiki/geda_pcb-quick_reference.html
index bfd38e839..ffc888588 100644
--- a/docs/wiki/geda_pcb-quick_reference.html
+++ b/docs/wiki/geda_pcb-quick_reference.html
@@ -6,7 +6,7 @@
   
   geda:pcb-quick_reference
 
-
+
 
 
 
@@ -145,7 +145,7 @@
 		  m  		 move to layer	 move the object under the cursor to the current layer  
 	
 	
-		  shift-m  	 move selection to layer	 move selected objects to the current working layer (see pcb tip)  
+		  shift-m  	 move selection to layer	 move selected objects to the current working layer (see pcb tip)  
 	
 	
 		  ctrl-m	 move origin	 set the origin to the current position of the mouse pointer 
diff --git a/docs/wiki/geda_pcb_footprints.html b/docs/wiki/geda_pcb_footprints.html
index 882a59d52..7639db8b0 100644
--- a/docs/wiki/geda_pcb_footprints.html
+++ b/docs/wiki/geda_pcb_footprints.html
@@ -7,7 +7,7 @@
   geda:pcb_footprints
 
 
-
+
 
 
 
@@ -85,11 +85,15 @@
 
    
 
 
    
- * You can share  gEDA footprints at Open Circuits.
+ * The place to share symbols and footprints is  gedasymbols.org
 
    
 
 
    
-* The  "Open Symbol Project" with Mark Whitis has many footprints. (What can we do to help him?)
+* You can find many PCB footprints at John Luciani's footprint page 
+
    
+
+
    
+* You can share  gEDA footprints at Open Circuits.
 
    
 
 
    
diff --git a/docs/wiki/geda_pcb_mp.html b/docs/wiki/geda_pcb_mp.html
index e91751362..308d2dd99 100644
--- a/docs/wiki/geda_pcb_mp.html
+++ b/docs/wiki/geda_pcb_mp.html
@@ -6,7 +6,7 @@
   
   geda:pcb_mp
 
-
+
 
 
 
diff --git a/docs/wiki/geda_pcb_tips.html b/docs/wiki/geda_pcb_tips.html
index cfd219638..cae794baa 100644
--- a/docs/wiki/geda_pcb_tips.html
+++ b/docs/wiki/geda_pcb_tips.html
@@ -6,8 +6,8 @@
   
   geda:pcb_tips
 
-
-
+
+
 
 
 
@@ -74,7 +74,7 @@
 
  • How do I route a connection from solder to component side and back?
    • 
 
  • How do I change the routing style?
    • 
 
  • I got stuck! How do I go back?
    • 
-
  • How do I move one set of layer tracks to another layer?
    • 
+
  • How do I move one set of layer tracks to a different layer?
    • 
 
  • How do I change the soldermask clearance around a hole/via?
    • 
 
  • How do I change the size of my tracks?
    • 
 
  • How do I drive a via to connect a track to a ground plane on a different layer?
    • 
@@ -564,7 +564,7 @@ The universal undo key [U] works even while in the
 
 
    
 
-
    How do I move one set of layer tracks to another layer?
    
+
    How do I move one set of layer tracks to a different layer?
    
 
    
 
      
 
    1.  Select the tracks. It’s easiest to do this if you shut off everything but that layer first (i.e. silk, pins, other layers, etc).
      
@@ -576,7 +576,7 @@ The universal undo key [U] works even while in the
 
    
 
 
    
-
+
 
    How do I change the soldermask clearance around a hole/via?
    
 
    
 
@@ -585,7 +585,7 @@ You can increase the soldermask clearance from any hole/via by positioning the c
 
    
 
 
    
-
+
 
    How do I change the size of my tracks?
    
 
    
 
@@ -602,7 +602,7 @@ There are a number of ways to change the size of already laid down tracks:
 
 
 
    
-
+
 
    How do I drive a via to connect a track to a ground plane on a different layer?
    
 
    
 
      
@@ -625,7 +625,7 @@ There are a number of ways to change the size of already laid down tracks:
 
    
 
 
    
-
+
 
    What is the easiest way to create a "thermal via"?
    
 
    
 
@@ -644,7 +644,7 @@ Here are some suggestions:
 
 
 
    
-
+
 
    I want to draw a track between two segments on the same net, but PCB won't let me! Why?
    
 
    
 
@@ -663,7 +663,7 @@ You are likely drawing tracks with auto-DRC on. To connect the two segments, her
 
 
 
    
-
+
 
    PCB seems to munge my components names and complains that it can't find proper nets for the pins! How come?
    
 
    
 
@@ -673,7 +673,7 @@ Most likely you named them such that pcb believes they are one part. Lower case
 
    
 
 
    
-
+
 
    How can I set color and thickness of the rats nests?
    
 
    
 
@@ -686,12 +686,12 @@ There is currently no GUI wa
 
    
 
 
    
-
+
 
    Beyond tracks and footprints
    
 
    
 
 
    
-
+
 
    How do I trace a drawing, a print, or another PCB?
    
 
    
 
@@ -708,7 +708,7 @@ If you don’t like to use PCB confined to the area of the board, i.e. if you wa
 
    
 
 
    
-
+
 
    I can't copy component pads in a layout.  What gives?
    
 
    
 
@@ -733,7 +733,7 @@ Then I go to paste the copied area… and all that moves are a couple of tr
 
    
 
 
    
-
+
 
    How do I fill areas with copper?
    
 
    
 
@@ -742,7 +742,7 @@ Use rectangles and polygon planes. These items will always avoid vias, pads and
 
    
 
 
    
-
+
 
    The polygons are shorting my tracks! What can I do about it?
    
 
    
 
@@ -751,7 +751,7 @@ You didn’t have “Enable_new_lines_clear_polygons” checked in the settings
 
    
 
 
    
-
+
 
    How do I change polygon clearance?
    
 
    
 
@@ -764,7 +764,7 @@ The amount of the increment can be configured in the dialog File/Preference/Incr
 
    
 
 
    
-
+
 
    How do I hide the polygons while I edit the layout?
    
 
    
 
@@ -773,7 +773,7 @@ Put the polygons (and rectangles) on a separate layer. Use the preference to mak
 
    
 
 
    
-
+
 
    How do I edit polygons?
    
 
    
 
@@ -786,7 +786,7 @@ There are four basic ways to edit polygon outlines. You can move and delete vert
 
    
 
 
    
-
+
 
    How do I place vias that connect to a polygon for full thermal dissipation or full shielding integrity?
    
 
    
 
@@ -815,7 +815,7 @@ You can also add another polygon on-top of the polygon to which you want to conn
 
    
 
 
    
-
+
 
    Can polygons be un-masked? (Can a polygon be made bare-copper with no solder mask?)
    
 
    
 
@@ -824,7 +824,7 @@ Currently this is not possible in PCB. The usual workaround (for example if you
 
    
 
 
    
-
+
 
    How do I place mounting holes?
    
 
    
 
@@ -845,7 +845,7 @@ For footprint examples see 
+
 
    Why is it possible to make a thermal for pin, but not for a pad?
    
 
    
 
@@ -854,7 +854,7 @@ The reason is that pins usually have sufficient spacing that the plane surroundi
 
    
 
 
    
-
+
 
    Can PCB be used to make single layer boards?
    
 
    
 
@@ -873,7 +873,7 @@ Yes. Just plot your gerbers and toss any layers that are not needed. You can jus
 
    
 
 
    
-
+
 
    What resources exist to process PCB files using scripts?
    
 
    
 
@@ -892,7 +892,7 @@ One of PCB’s great features is that it uses an easily understood 
 
 
    
-
+
 
    How do I import external vector graphics?
    
 
    
 
@@ -905,7 +905,7 @@ Import of external vector graphics is usefull if an irregular shape of the pcb i
 
    
 
 
    
-
+
 
    How Do I attach a name to my layout?
    
 
    
 
@@ -914,12 +914,12 @@ You can set the name of the current pcb with Menu Edit - Edit name of - la
 
    
 
 
    
-
+
 
    Auto Router
    
 
    
 
 
    
-
+
 
    How do I force the autorouter to only put traces on a particular layer?
    
 
    
 
@@ -928,7 +928,7 @@ Just unselect the layers you don’t want (usually green and blue) by clicking o
 
    
 
 
    
-
+
 
    How do I force the autorouter to route only within my pcb outline?
    
 
    
 
@@ -937,7 +937,7 @@ You can have the autorouter work only within a given area by drawing a copper po
 
    
 
 
    
-
+
 
    How do I route power and ground planes with the autorouter?
    
 
    
 
@@ -946,7 +946,7 @@ Connect the polygon that will become your power planes to a net and the autorout
 
    
 
 
    
-
+
 
    The layout produced by the autorouter is inefficient!
    
 
    
 
@@ -955,7 +955,7 @@ This is a technological limitation of the current auto router. It is gridless an
 
    
 
 
    
-
+
 
    The layout produced by the autorouter is ugly!
    
 
    
 
@@ -964,12 +964,12 @@ Have you tried the various clean-up tools under connects–>optimize rout
 
    
 
 
    
-
+
 
    Gerber generation and file I/O issues
    
 
    
 
 
    
-
+
 
    How do I make a board outline to go with my gerbers to the board maker?
    
 
    
 
@@ -994,7 +994,7 @@ It’s also possible to edit the native .pcb file format of your layout. I usual
 )
    
 
 
-
+
 
    I'm done with my layout. How should I check my design?
    
 
    
 
      
@@ -1027,12 +1027,12 @@ Besides running the DRC checker, it is essential to check your Gerber files. The
 
    
 
 
    
-
+
 
    Exporting Other Formats: Raster and PS Files
    
 
    
 
 
    
-
+
 
    What is xy-max in the PNG export dialog box?
    
 
    
 
@@ -1041,7 +1041,7 @@ It limits the size of the image to NxN pixels, but maintains the aspect ratio.
 
    
 
 
    
-
+
 
    You didn't answer my question. What other resources exist for PCB information?
    
 
    
 
@@ -1056,6 +1056,6 @@ You can get fast responses from the geda-user email list. If you haven’t found
 
    
 
 
    
-
+
 
 
diff --git a/docs/wiki/geda_scg.html b/docs/wiki/geda_scg.html
index 4a773bac4..2f471b3f2 100644
--- a/docs/wiki/geda_scg.html
+++ b/docs/wiki/geda_scg.html
@@ -6,7 +6,7 @@
   
   geda:scg
 
-
+
 
 
 
diff --git a/docs/wiki/geda_scm.html b/docs/wiki/geda_scm.html
new file mode 100644
index 000000000..499b15f34
--- /dev/null
+++ b/docs/wiki/geda_scm.html
@@ -0,0 +1,407 @@
+
+
+
+  
+  geda:scm
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    
+
    
+
    Table of Contents
    
+
    
+
+
+
    
+
    
+
+
+
+
    gEDA/gaf's Source Control Management
    
+
    
+
+
    
+ gEDA uses git for source code management.  git is a distributed version control system, where every user has his or her own full copy of the revision history. 
+
    
+
+
+
    
+ The web interface to the gEDA git repository is at http://git.gpleda.org/.
+
    
+
+
    
+
+
    Installing git & related tools
    
+
    
+
+
    
+ 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: 
+
    
+
      
+
    •  gitk, a visual history repository browser
      
+
      • 
+
    •  Cogito, a more user-friendly front-end to git
      
+
      • 
+
    •  Stacked Git, for working with patchsets
      
+
      • 
+
    
+
+
    
+ Make sure that you install at least version 1.5.x of git if you are planning on pushing changes to the central git repository.  
+
    
+
+
    
+
+
    Debian-based
    
+
    
+
    apt-get install git-core git-doc gitk cogito stgit
    
+
+
    
+ you may also want: 
+
    
+
    apt-get install git-email git-completion
    
+
+
    
+ Note, as of 2007/06/25, Debian stable (etch) and Debian testing (lenny) have git version 1.4.x.  Debian unstable (sid) has 1.5.2.2.
+
    
+
+
    
+
+
    Fedora Linux
    
+
    
+
    yum install git cogito stgit
    
+
+
    
+
+
    Learning to use git
    
+
    
+
+
    
+ The toplevel documentation for git can be found at:
+
    
+
+
    
+Official git docs
+
    
+
+
    
+The user’s manual for git can be found at:
+
    
+
+
    
+git user manual
+
    
+
+
    
+A current tutorial can be found at:
+
    
+
+
    
+git core tutorial
+
    
+
+
    
+Other nice tutorials/webpages: 
+
    
+
+
    
+Git Guide
    
+ Cogito Guide
    
+ git Crash Courses
    
+ Cogito for CVS Users
    
+ Git for Everyone
    
+
+
    
+
+
    
+Keep in mind that some of these tutorials are a little dated and may not cover current git syntax.
+
    
+
+
    
+
+
    Accessing the repository
    
+
    
+
+
    
+ To clone the gaf.git repository using anonymous git access: 
+
    
+
    git clone git://git.gpleda.org/gaf.git
    
+
+
    
+ For developer git access, you should contact Ales Hvezda to get an SSH public key installed and an account; having done so, the git URL to push to is: 
+
    
+
    git clone ssh://<username>@git.gpleda.org/home/git/gaf.git
    
+
+
    
+ If you have ssh access you will also need to edit your ~/.ssh/config file (create it if it doesn’t exist) and put the following text into it: 
+
    
+
    Host git.gpleda.org
+Port 5022
    
+
+
    
+ Finally, it is possible to access the repository using CVS, as there is a git-cvsserver running.  This is read-only access. 
+
    
+
     export CVSROOT=:pserver:anonymous@git.gpleda.org/home/git/gaf.git
+ cvs co master    
    
+
+
    
+ You can only checkout exported heads (for example: master).
+
    
+
+
    
+
+
    Making and committing changes
    
+
    
+
+
    
+
+
    Setting up user information
    
+
    
+
+
    
+ You should make sure that your username & e-mail address are set in your git configuration file. 
+
    
+
    $ git config --global user.name "Your Name Comes Here"
+$ git config --global user.email you@yourdomain.example.com
    
+
+
    
+
+
    Committing patches from other contributors
    
+
    
+
+
    
+ If you apply a patch from someone else (e.g. from a SourceForge patch record) there are a few things to consider. Git stores two different names and e-mail addresses for a given commit: the “author” of the patch, and the “committer” of the patch, so these details must be set correctly when making the commit.
+
    
+
+
    
+First of all, check a few things:
+
    
+
      
+
    •  You have the latest version of the patch.
      
+
      • 
+
    •  The author of the patch is happy for it to be committed (and wasn’t still working on it)
      
+
      • 
+
    •  That the you’re happy with the patch, and taking responsibility for committing those changes.
      
+
      • 
+
    
+
+
    
+ For simplicity, start from an unmodified up-to date tree (git status shows no changes).
+
    
+
+
    
+Apply the patch as usual (as an example): 
+
    
+
    $ patch -p1 < example_changes.patch
    
+
+
    
+ 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.
+
    
+
+
    
+Note: This is easy to miss accidentally if your editor introduces tabs. Please avoid letting it do so!
+
    
+
+
    
+For every file changed, added or removed, you need to inform git before it will commit the changes. To see the modified files, run: 
+
    
+
    $ git status
    
+
+
    
+ For speed, the command: 
+
    
+
    $ git add -u
    
+
+
    
+ will update all files which git tracks, including any files which were deleted.
+
    
+
+
    
+For adding any new files the patch introduced, use the command 
+
    
+
    $ git add new_file.c
    
+
+
    
+ Note: git add also takes wild-cards.
+
    
+
+
    
+Commit the patch, making sure that the Author’s name and e-mail address are specified: 
+
    
+
    $ git commit --author "Author's Name Comes Here <author@example.com>"
    
+
+
    
+ As an alternative, you can set the GIT_AUTHOR_NAME and GIT_AUTHOR_EMAIL environment variables before issuing the normal commit command
+
    
+
+
    
+
+
    Writing good commit messages
    
+
    
+
+
    
+ The commit message format is as follows: a *strictly* one-line summary of the patch, followed by a blank line, followed by a long description.  If you can fit the whole description of the patch on one line, that’s fine; don’t bother with the long description.
+
    
+
+
    
+The one-line summary is used for generating e-mail subject lines, and for the gitk & gitweb log displays.  Having a good one-line summary is really useful, because it means those tools can be used to quickly find a commit of interest.
+
    
+
+
    
+Do not put a list of files changed into commit messages.  This information can be trivially obtained using the git tools.
+
    
+
+
    
+Example:
+
    
+
    +Added new GedaList class derived from GObject
+
+This abstracts a GList with API for write access. Its main use is in list
+change notification, as it emits a "changed" g_signal when modified.
+Read only access to the underlying GList is provided by an accessor,
+currenly implemented as a macro.
+
    
+
+
    
+
+
    Push is Destructive
    
+
    
+
+
    
+ Warning: pushing changes to the remote repository is destructive
+
    
+
+
    
+Unlike CVS, 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.
+
    
+
+
    
+
+
    How Do I ... ?
    
+
    
+
+
    
+ For a more information please checkout the Git Guide.
+
    
+
+
    
+
+
    ... get a copy of gEDA/gaf git repository?
    
+
    
+
+
    
+ For anonymous read-only access: 
+
    
+
    $ git clone git://git.gpleda.org/gaf
    
+
+
    
+ For developers with read/write access: 
+
    
+
    $ git clone git://git.gpleda.org/home/git/gaf.git
    
+
+
    
+
+
    ... keep my local copy current?
    
+
    
+
+
    
+ For those who are are not merging changes back into the central git repository you can run: 
+
    
+
    $ git pull
    
+
+
    
+ However, for those of you who are going to be pushing your changes back into the central git repository, using git pull will clutter up the history with merge messages (“Merge branch ‘master’”).  To avoid this you should run: 
+
    
+
    $ git fetch
+$ git rebase origin
    
+
+
    
+
+
    ... commit my changes to the local git repository?
    
+
    
+
    $ git commit -a 
    
+
+
    
+ This command will find all changed files that git knows about (added with git-add) and prompt you for a commit message.  Be sure to follow the above commit message convention if you plan on pushing your changes to the central repository.
+
    
+
+
    
+If you want to commit files in the current directory or want to explicitly commit only certain files, do not specify the -a flag and/or specify the individual filenames on the command line like: 
+
    
+
    $ git commit filename1 filename2
    
+
+
    
+
+
    ... undo any uncommitted local changes?
    
+
    
+
    $ git checkout -f 
    
+
+
    
+ Note this will discard any changes to any files that are being tracked by git.
+
    
+
+
    
+
+
    ... fix/change my last commit?
    
+
    
+
    $ Edit whatever files
+$ git commit --amend filename1..filenameN 
    
+
+
    
+ This will pickup any changes you made and recommit them again with the previous commit message.
+
    
+
+
    
+
    
+
+
diff --git a/docs/wiki/geda_sdb_howto.html b/docs/wiki/geda_sdb_howto.html
index 8b89c4f7e..5f3a06aa1 100644
--- a/docs/wiki/geda_sdb_howto.html
+++ b/docs/wiki/geda_sdb_howto.html
@@ -6,7 +6,7 @@
   
   geda:sdb_howto
 
-
+
 
 
 
diff --git a/docs/wiki/geda_sn_readme.html b/docs/wiki/geda_sn_readme.html
index 268e39213..70f3fefbe 100644
--- a/docs/wiki/geda_sn_readme.html
+++ b/docs/wiki/geda_sn_readme.html
@@ -6,7 +6,7 @@
   
   geda:sn_readme
 
-
+
 
 
 
diff --git a/docs/wiki/geda_ssan.html b/docs/wiki/geda_ssan.html
index a21e6ac0f..9ebdf5301 100644
--- a/docs/wiki/geda_ssan.html
+++ b/docs/wiki/geda_ssan.html
@@ -6,7 +6,7 @@
   
   geda:ssan
 
-
+
 
 
 
diff --git a/docs/wiki/geda_style_guide.html b/docs/wiki/geda_style_guide.html
index 10d56e55d..3b742a65c 100644
--- a/docs/wiki/geda_style_guide.html
+++ b/docs/wiki/geda_style_guide.html
@@ -6,7 +6,7 @@
   
   geda:style_guide
 
-
+
 
 
 
diff --git a/docs/wiki/geda_suse_10.html b/docs/wiki/geda_suse_10.html
index 99098d278..ab05eb61c 100644
--- a/docs/wiki/geda_suse_10.html
+++ b/docs/wiki/geda_suse_10.html
@@ -6,7 +6,7 @@
   
   geda:suse_10.0
 
-
+
 
 
 
diff --git a/docs/wiki/geda_suse_9.html b/docs/wiki/geda_suse_9.html
index a22ac276f..b924f988a 100644
--- a/docs/wiki/geda_suse_9.html
+++ b/docs/wiki/geda_suse_9.html
@@ -6,7 +6,7 @@
   
   geda:suse_9.3
 
-
+
 
 
 
diff --git a/docs/wiki/geda_suse_rpm_installation.html b/docs/wiki/geda_suse_rpm_installation.html
index a19596447..b788e599a 100644
--- a/docs/wiki/geda_suse_rpm_installation.html
+++ b/docs/wiki/geda_suse_rpm_installation.html
@@ -6,8 +6,8 @@
   
   geda:suse_rpm_installation
 
-
-
+
+
 
 
 
@@ -33,7 +33,6 @@
 
  • Installing Packages from the SuSE Build Service
    • 
 
  • Distribution specific notes
    
 
@@ -52,23 +51,23 @@
 
    Available rpm packages
    
 
    
 
      
-
    •  libgeda (20070216)
      
+
    •  libgeda (20070526)
      
 
      • 
-
    •  geda-docs (20070216)
      
+
    •  geda-docs (20070526)
      
 
      • 
-
    •  geda-examples (20070216)
      
+
    •  geda-examples (20070526)
      
 
      • 
-
    •  geda-gattrib (20070216)
      
+
    •  geda-gattrib (20070526)
      
 
      • 
-
    •  geda-gnetlist (20070216)
      
+
    •  geda-gnetlist (20070526)
      
 
      • 
-
    •  geda-gschem (20070216)
      
+
    •  geda-gschem (20070526)
      
 
      • 
-
    •  geda-gsymcheck (20070216)
      
+
    •  geda-gsymcheck (20070526)
      
 
      • 
-
    •  geda-symbols (20070216)
      
+
    •  geda-symbols (20070526)
      
 
      • 
-
    •  geda-utils (20070216)
      
+
    •  geda-utils (20070526)
      
 
      • 
 
    •  gerbv (1.0.2)
      
 
      • 
@@ -82,7 +81,7 @@
 
 
    •  gwave (20051222)
      
 
      • 
-
    •  gtkwave (3.0.23)
      
+
    •  gtkwave (3.0.28)
      
 
      • 
 
    •  dinotrace (9.3e)
      
 
      • 
@@ -126,17 +125,6 @@
 
 
    
 
-
    SuSE 9.3
    
-
    
-
      
-
    •  YaST of SuSE 9.3 does not support yum repositories. Please use another installation utility like yum or smart instead.
      
-
      • 
-
    •  gSpiceUI not build for SuSE9.3. wxwidget package is missing.
      
-
      • 
-
    
-
-
    
-
 
    SuSE 10.0
    
 
    
 
      
@@ -145,7 +133,7 @@
 
    
 
 
    
-
+
 
    SuSE 10.1
    
 
    
 
      
@@ -154,7 +142,7 @@
 
    
 
 
    
-
+
 
    SuSE 10.2
    
 
    
 
      
@@ -163,6 +151,6 @@
 
    
 
 
    
-
+
 
 
diff --git a/docs/wiki/geda_syntax_features.html b/docs/wiki/geda_syntax_features.html
index 00d360dbf..e4d5cd859 100644
--- a/docs/wiki/geda_syntax_features.html
+++ b/docs/wiki/geda_syntax_features.html
@@ -6,7 +6,7 @@
   
   geda:syntax_features
 
-
+
 
 
 
diff --git a/docs/wiki/geda_systemc_netlister_readme.html b/docs/wiki/geda_systemc_netlister_readme.html
index a8ef60eb3..98df74171 100644
--- a/docs/wiki/geda_systemc_netlister_readme.html
+++ b/docs/wiki/geda_systemc_netlister_readme.html
@@ -6,7 +6,7 @@
   
   geda:systemc_netlister_readme
 
-
+
 
 
 
diff --git a/docs/wiki/geda_tasks.html b/docs/wiki/geda_tasks.html
index f372dd6b1..dfde14294 100644
--- a/docs/wiki/geda_tasks.html
+++ b/docs/wiki/geda_tasks.html
@@ -6,8 +6,8 @@
   
   geda:tasks
 
-
-
+
+
 
 
 
@@ -22,6 +22,18 @@
 
 
 
    
+
    
+
    Table of Contents
    
+
    
+
+
+
    
+
    
 
 
 
@@ -29,15 +41,40 @@
 
    
 
 
    
-gEDA is run by volunteers, so these are volunteer (read: unpaid) tasks. Please consider helping out. Thank you.
+gEDA is run by volunteers, so these are volunteer (read: unpaid) tasks. Please consider helping out. Thank you. 
 
    
+
+
    
+
+
    important tasks for normal volunteers
    
+
    
 
      
 
    •  Documentation Writers/Editors
      
- Somebody is needed to act as an editor for the gEDA documentation effort. Basically this person would take whatever documentation already exists and/or is currently being written and formats it into something presentable. This individual does not write the actual documentation, but would instead perform editorial work. People who want to write the actual documentation are also needed.
      
+ Somebody is needed to act as an editor for the gEDA documentation effort. Basically this person would take whatever documentation already exists and/or is currently being written and formats it into something presentable. This individual does not write the actual documentation, but would instead perform editorial work. People who want to write the actual documentation are also needed. (The  start page explains how to get started editing the documentation on the wiki).
    
+
    • 
+
  •  PCB Publicity Manager
    
+ Somebody is needed to do publicity for the gEDA project. This consists of posting release updates to the various PCB design websites (such as http://CircuitCalculator.com/ ,  Olimex,  Advanced Circuits,  Open Circuits, http://www.ePanorama.net/ ,  gumstix,  RepRap, etc.)
    
 
    • 
-
  •  Publicity Manager
    
- Somebody is needed to do publicity for the gEDA project. This consists of posting release updates to the various Linux/Unix websites (like Freshmeat or LWN)
    
+
  •  Linux Publicity Manager
    
+ Somebody is needed to do publicity for the gEDA project. This consists of posting release updates to the various Linux/Unix websites (like Freshmeat or  LWN or http://LinuxRobots.org/ )
    
 
    • 
+
  •  UNIX Port Testers
    
+ People are always needed to test gEDA on different and new UNIX like operating systems. This person would basically download a new release and make sure it works on their platform of choice. Any problems found would be then submitted to the appropriate gEDA author.
    
+
    • 
+
  •  Website/Mirror Hacker
    
+ Somebody to watch over the mirrors and maybe do some HTML hacking is needed. There are currently three websites which need to be monitored and occasionally fixed. The person would also have influence in the changing/expansion of the gEDA website. Duties would be split among the current webmasters.
    
+
    • 
+
+
+
+
+
    tasks for programmers
    
+
    
+
+
    
+ FIXME: should this list be combined with todos ? 
+
    
+
      
 
    •  Netlist Hacker
      
  Somebody who is familiar with the generation/management of netlists is needed to help work on and improve gnetlist. Whether the existing gnetlist is used or if a total rewrite is needed is always an open option. Must be extremely familiar with UNIX/C/C++ programming.
      
 
      • 
@@ -47,21 +84,15 @@ gEDA is run by volunteers, so these are volunteer (read: unpaid) tasks. Please c
 
    •  geda GUI Hacker
      
  Somebody who knows C, UNIX, and gtk+ programming is needed to work on the gEDA GUI (the program named geda). This program has been stalled for the past year due to the lack of manpower. Whether the existing geda is used or a total rewrite is needed is always an open option.
      
 
      • 
-
    •  UNIX Port Testers
      
- People are always needed to test gEDA on different and new UNIX like operating systems. This person would basically download a new release and make sure it works on their platform of choice. Any problems found would be then submitted to the appropriate gEDA author.
      
-
      • 
 
    •  Windows Port Hacker/Manager
      
  Somebody with expertise building and testing gEDA on UNIX systems and familiarity with the MS 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 MS Windows programming. The Windows port will NOT move forward if this task is not filled.
      
 
      • 
 
    •  Release Hacker
      
  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.
      
 
      • 
-
    •  Website/Mirror Hacker
      
- Somebody to watch over the mirrors and maybe do some HTML hacking is needed. There are currently three websites which need to be monitored and occasionally fixed. The person would also have influence in the changing/expansion of the gEDA website. Duties would be split among the current webmasters.
      
-
      • 
 
    
 
 
    
-
+
 
 
diff --git a/docs/wiki/geda_todos.html b/docs/wiki/geda_todos.html
index e102cd391..a5f6a0796 100644
--- a/docs/wiki/geda_todos.html
+++ b/docs/wiki/geda_todos.html
@@ -6,8 +6,8 @@
   
   geda:todos
 
-
-
+
+
 
 
 
@@ -45,8 +45,12 @@
 These lists are meant to provide developers a reminder of undone projects. It is also a wish list capturing user’s desires for new features. New developers can also look here for projects which they might be interested in working on.
 
    
 
+
    
+See tasks for non-programmer tasks.
+
    
+
 
-
+
 
    Things to be done before the next release
    
 
    
 
      
@@ -55,7 +59,7 @@ These lists are meant to provide developers a reminder of undone projects. It is
 
    
 
 
    
-
+
 
    Longer term upgrades desired for specific tools
    
 
    
 
      
@@ -116,7 +120,7 @@ These lists are meant to provide developers a reminder of undone projects. It is
 
    
 
 
    
-
+
 
    Ideas for new tools or gEDA Suite-wide enhancements
    
 
    
 
      
@@ -129,6 +133,6 @@ These lists are meant to provide developers a reminder of undone projects. It is
 
    
 
 
    
-
+
 
 
diff --git a/docs/wiki/geda_tragesym_readme.html b/docs/wiki/geda_tragesym_readme.html
index b9600606f..0388a1a7e 100644
--- a/docs/wiki/geda_tragesym_readme.html
+++ b/docs/wiki/geda_tragesym_readme.html
@@ -6,7 +6,7 @@
   
   geda:tragesym_readme
 
-
+
 
 
 
diff --git a/docs/wiki/geda_tragesym_tutorial.html b/docs/wiki/geda_tragesym_tutorial.html
index f297bffd9..aeda1cbcb 100644
--- a/docs/wiki/geda_tragesym_tutorial.html
+++ b/docs/wiki/geda_tragesym_tutorial.html
@@ -6,7 +6,7 @@
   
   geda:tragesym_tutorial
 
-
+
 
 
 
diff --git a/docs/wiki/geda_transistor_guide.html b/docs/wiki/geda_transistor_guide.html
index 83c10d149..e482d0a6f 100644
--- a/docs/wiki/geda_transistor_guide.html
+++ b/docs/wiki/geda_transistor_guide.html
@@ -6,7 +6,7 @@
   
   geda:transistor_guide
 
-
+
 
 
 
diff --git a/docs/wiki/geda_ubuntu.html b/docs/wiki/geda_ubuntu.html
index 160c32839..0663520fd 100644
--- a/docs/wiki/geda_ubuntu.html
+++ b/docs/wiki/geda_ubuntu.html
@@ -6,7 +6,7 @@
   
   geda:ubuntu
 
-
+
 
 
 
diff --git a/docs/wiki/geda_usage.html b/docs/wiki/geda_usage.html
index c961a4048..a8b310d2f 100644
--- a/docs/wiki/geda_usage.html
+++ b/docs/wiki/geda_usage.html
@@ -6,8 +6,8 @@
   
   geda:usage
 
-
-
+
+
 
 
 
@@ -43,7 +43,7 @@
 
    
 
 
    
-The first thing to do is to read and understand Bill Wilson’s excellent gschem -> gsch2pcb -> PCB tutorial. This should get you started.
+The first thing to do is to read and understand Bill Wilson’s excellent gschem -> gsch2pcb -> PCB tutorial. This should get you started.
 
    
 
 
    
@@ -51,11 +51,11 @@ Also be sure to check out the other tutorial while trying the suite for yourself, you will become an expert in no time!
+However, the best way to learn the gEDA Suite is to download it and try it out yourself! If you consult Bill Wilson’s tutorial while trying the suite for yourself, you will become an expert in no time!
 
    
 
 
    
-
+
 
    What does the design flow in gEDA look like?
    
 
    
 
@@ -108,7 +108,7 @@ In words, the design flow for a simple PCB proceeds as follows:
 
    
 
 
    
-
+
 
    What limitations exist for the gEDA tools?
    
 
    
 
@@ -129,7 +129,7 @@ The most important thing to keep in mind about gEDA’s limitations is this: GED
 
 
 
    
-
+
 
    What local configuration files are used for a project?
    
 
    
 
@@ -150,7 +150,7 @@ A typical PCB design requires the following config files in your local directory
 
    
 
 
    
-
+
 
    What are the names and locations of the RC files used with gEDA/gaf applications?
    
 
    
 
@@ -227,7 +227,7 @@ Finally, note that gEDA/gaf applications will look for up to six configuration f
 
    
 
 
    
-
+
 
    What about a project manager?
    
 
    
 
@@ -240,7 +240,7 @@ Unfortunately, development of “geda” has not kept up with the rest of gEDA/g
 
    
 
 
    
-
+
 
    Can we change gEDA to use an XML file format?
    
 
    
 
@@ -269,6 +269,6 @@ It’s unlikely the gEDA Project will ever switch to an 
    
+
 
 
diff --git a/docs/wiki/geda_vams_netlister_readme.html b/docs/wiki/geda_vams_netlister_readme.html
index f6f074d08..5da308c92 100644
--- a/docs/wiki/geda_vams_netlister_readme.html
+++ b/docs/wiki/geda_vams_netlister_readme.html
@@ -6,7 +6,7 @@
   
   geda:vams_netlister_readme
 
-
+
 
 
 
diff --git a/docs/wiki/geda_verilog_netlister_readme.html b/docs/wiki/geda_verilog_netlister_readme.html
index 5f3558c10..206114b80 100644
--- a/docs/wiki/geda_verilog_netlister_readme.html
+++ b/docs/wiki/geda_verilog_netlister_readme.html
@@ -6,7 +6,7 @@
   
   geda:verilog_netlister_readme
 
-
+
 
 
 
diff --git a/docs/wiki/geda_version_control_migration.html b/docs/wiki/geda_version_control_migration.html
index 7dedd6f61..850a192d1 100644
--- a/docs/wiki/geda_version_control_migration.html
+++ b/docs/wiki/geda_version_control_migration.html
@@ -6,7 +6,7 @@
   
   geda:version_control_migration
 
-
+
 
 
 
diff --git a/docs/wiki/geda_vhdl_netlister_readme.html b/docs/wiki/geda_vhdl_netlister_readme.html
index 126af77b2..eb53fb0c7 100644
--- a/docs/wiki/geda_vhdl_netlister_readme.html
+++ b/docs/wiki/geda_vhdl_netlister_readme.html
@@ -6,7 +6,7 @@
   
   geda:vhdl_netlister_readme
 
-
+
 
 
 
diff --git a/docs/wiki/geda_wcalc_mp.html b/docs/wiki/geda_wcalc_mp.html
index a242255f2..71232ee80 100644
--- a/docs/wiki/geda_wcalc_mp.html
+++ b/docs/wiki/geda_wcalc_mp.html
@@ -6,7 +6,7 @@
   
   geda:wcalc_mp
 
-
+
 
 
 
diff --git a/docs/wiki/geda_wcalc_readme.html b/docs/wiki/geda_wcalc_readme.html
index 9ca802de2..3e195a94d 100644
--- a/docs/wiki/geda_wcalc_readme.html
+++ b/docs/wiki/geda_wcalc_readme.html
@@ -6,7 +6,7 @@
   
   geda:wcalc_readme
 
-
+
 
 
 
@@ -27,7 +27,7 @@
 
 
    Wcalc README
    
 
    
-
    $Id$
+
    $Id: README,v 1.2 2005/10/24 21:12:42 dan Exp $
 
 Wcalc is a tool for the analysis and synthesis of transmission line structures and 
 related components.  Wcalc provides the ability to analyze the electrical parameters
diff --git a/docs/wiki/geda_wcalc_stdio_mp.html b/docs/wiki/geda_wcalc_stdio_mp.html
index 1503b6b66..5b9415538 100644
--- a/docs/wiki/geda_wcalc_stdio_mp.html
+++ b/docs/wiki/geda_wcalc_stdio_mp.html
@@ -6,7 +6,7 @@
   
   geda:wcalc_stdio_mp
 
-
+
 
 
 
diff --git a/docs/wiki/index.html b/docs/wiki/index.html
index 0803f8361..7d7915dff 100644
--- a/docs/wiki/index.html
+++ b/docs/wiki/index.html
@@ -6,8 +6,8 @@
   
   start
 
-
-
+
+
 
 
 
@@ -103,7 +103,7 @@ These are FAQs, HOWTOs, and tips/tricks to help you with the practical details o
 
 
  •  FAQ-gsch2pcb : How to take your design to layout using PCB.
    
 
    • 
-
  •  FAQ-pcb : questions about “pcb”.
    
+
  •  FAQ-pcb : Questions about the printed circuit board tool “pcb”.
    
 
    • 
 
  •  PCB-quick reference : PCB Quick Reference Sheet.
    
 
    • 
@@ -111,12 +111,12 @@ These are FAQs, HOWTOs, and tips/tricks to help you with the practical details o
 
 
  •  PCB footprints : The ins and outs of using, creating, and sharing footprints.
    
 
    • 
-
  •  Tasks : A toplevel jobs/tasks that need help. 
    
+
  •  Tasks : Top-level list of jobs/tasks that need help.
    
 
    • 
 
 
 
    
-
+
 
    Developer Documentation
    
 
    
 
@@ -124,6 +124,10 @@ These are FAQs, HOWTOs, and tips/tricks to help you with the practical details o
 These are pages concerning the development of the gEDA suite. 
 
    
 
      
+
    •   developer.html : Where to submit bug reports, feature requests and contributions.  
      
+
      • 
+
    •  scm : Information on gEDA/gaf’s source control management (SCM) system and process.
      
+
      • 
 
    •  devel-tips : For developers only: various tips and tricks when doing gEDA development.
      
 
      • 
 
    •  ToDos : For developers only: lists of pending project enhancements and to-dos.
      
@@ -132,16 +136,16 @@ These are pages concerning the development of the gEDA suite.
 
      • 
 
    •  Circuit Simulation Improvements : For developers only: Discussion on how to better integrate circuit simulations, gschem and gnetlist.
      
 
      • 
-
    •  Data Plotting Improvements : For developers only: Discussion on how to better plot simulation data
      
+
    •  Data Plotting Improvements : For developers only: Discussion on how to better plot simulation data.
      
 
      • 
-
    •  Design Flow and Hierarchy Roadmap : users and developers: Discussion of wants for circuit design, reusing modules in a hierarchy.
      
+
    •  Design Flow and Hierarchy Roadmap : For users and developers: Discussion of wants for circuit design, reusing modules in a hierarchy.
      
 
      • 
-
    •  Version Control Migration : proposed schedule for migrating away from CVS to another version control system
      
+
    •  Version Control Migration : Proposed schedule for migrating away from CVS to another version control system.
      
 
      • 
 
    
 
 
    
-
+
 
    Talks
    
 
    
 
@@ -154,7 +158,7 @@ These are slides of presentations done about gEDA.  They provide a good top-leve
 
 
 
    
-
+
 
    Translations
    
 
    
 
      
@@ -165,7 +169,7 @@ These are slides of presentations done about gEDA.  They provide a good top-leve
 
    
 
 
    
-
+
 
    gEDA Users
    
 
    
 
@@ -178,7 +182,7 @@ The so-called “Free Dog” organization ( 
 
 
    
-
+
 
    About this Wiki
    
 
    
 
@@ -187,10 +191,10 @@ This section of the gEDA website is dedicated to documentation that is contribut
 
    
 
 
    
-Anyone is welcome to contribute. Unlike wikipedia there is no button to create a login by yourself. This is because nobody at the gEDA site has the nerves to deal with anonymous vandalism. Consequently, you have to write an email to the site admin (ahvezda AT geda.seul.org) to gain access. He will gladly send you a login.  
+Anyone is welcome to contribute. Unlike wikipedia there is no button to create a login by yourself. This is because nobody at the gEDA site has the nerves to deal with anonymous vandalism. Consequently, you have to write an email to the site admin (ahvezda AT geda.seul.org) to gain access. He will gladly send you a login. 
 
    
 
 
    
-
+
 
 
diff --git a/docs/wiki/lib/Makefile.am b/docs/wiki/lib/Makefile.am
index 8353060e8..6a9b0fd4d 100644
--- a/docs/wiki/lib/Makefile.am
+++ b/docs/wiki/lib/Makefile.am
@@ -5,5 +5,9 @@ docsdir = @GEDADOCDIR@/$(docname)/lib
 
 SUBDIRS = exe tpl images plugins 
 
+docs_DATA = .gitignore 
+
+EXTRA_DIST = $(docs_DATA)
+
 MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
 
diff --git a/docs/wiki/lib/exe/Makefile.am b/docs/wiki/lib/exe/Makefile.am
index 0a9c1e640..a76ae7c5a 100644
--- a/docs/wiki/lib/exe/Makefile.am
+++ b/docs/wiki/lib/exe/Makefile.am
@@ -3,7 +3,7 @@
 docname=wiki
 docsdir = @GEDADOCDIR@/$(docname)/lib/exe
 
-docs_DATA = css 002css 001css 
+docs_DATA = .gitignore css 002css 001css opensearch 
 
 EXTRA_DIST = $(docs_DATA)
 
diff --git a/docs/wiki/lib/exe/opensearch b/docs/wiki/lib/exe/opensearch
new file mode 100644
index 000000000..e4f68f7fa
--- /dev/null
+++ b/docs/wiki/lib/exe/opensearch
@@ -0,0 +1,7 @@
+
+
+  geda Wiki
+  http://geda.seul.org/wiki/lib/tpl/default/images/favicon.ico
+  
+  
+
diff --git a/docs/wiki/lib/images/Makefile.am b/docs/wiki/lib/images/Makefile.am
index ceae56850..56b57607b 100644
--- a/docs/wiki/lib/images/Makefile.am
+++ b/docs/wiki/lib/images/Makefile.am
@@ -5,7 +5,7 @@ docsdir = @GEDADOCDIR@/$(docname)/lib/images
 
 SUBDIRS = smileys interwiki fileicons 
 
-docs_DATA = info.png interwiki.png success.png notify.png error.png 
+docs_DATA = .gitignore info.png interwiki.png success.png notify.png error.png 
 
 EXTRA_DIST = $(docs_DATA)
 
diff --git a/docs/wiki/lib/images/fileicons/Makefile.am b/docs/wiki/lib/images/fileicons/Makefile.am
dissimilarity index 65%
index 840b2c151..648a3b38c 100644
--- a/docs/wiki/lib/images/fileicons/Makefile.am
+++ b/docs/wiki/lib/images/fileicons/Makefile.am
@@ -1,11 +1,11 @@
-
-
-docname=wiki
-docsdir = @GEDADOCDIR@/$(docname)/lib/images/fileicons
-
-docs_DATA = doc.png sxc.png 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 gif.png tar.png ods.png conf.png html.png htm.png txt.png xml.png 
-
-EXTRA_DIST = $(docs_DATA)
-
-MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
-
+
+
+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 
+
+EXTRA_DIST = $(docs_DATA)
+
+MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
+
diff --git a/docs/wiki/lib/images/interwiki/Makefile.am b/docs/wiki/lib/images/interwiki/Makefile.am
index 95abd0227..0fbc8474c 100644
--- a/docs/wiki/lib/images/interwiki/Makefile.am
+++ b/docs/wiki/lib/images/interwiki/Makefile.am
@@ -3,7 +3,7 @@
 docname=wiki
 docsdir = @GEDADOCDIR@/$(docname)/lib/images/interwiki
 
-docs_DATA = dokubug.gif coral.gif amazon.de.gif google.gif amazon.gif wpmeta.gif sb.gif doku.gif wiki.gif amazon.uk.gif wp.gif wpde.gif meatball.gif phpfn.gif bug.gif
+docs_DATA = .gitignore bug.gif dokubug.gif coral.gif amazon.de.gif google.gif amazon.gif wpmeta.gif sb.gif doku.gif wiki.gif amazon.uk.gif wp.gif wpde.gif meatball.gif phpfn.gif 
 
 EXTRA_DIST = $(docs_DATA)
 
diff --git a/docs/wiki/lib/images/smileys/Makefile.am b/docs/wiki/lib/images/smileys/Makefile.am
index 82046efc2..f3c323d34 100644
--- a/docs/wiki/lib/images/smileys/Makefile.am
+++ b/docs/wiki/lib/images/smileys/Makefile.am
@@ -3,7 +3,7 @@
 docname=wiki
 docsdir = @GEDADOCDIR@/$(docname)/lib/images/smileys
 
-docs_DATA = icon_wink.gif fixme.gif icon_smile.gif icon_smile2.gif 
+docs_DATA = .gitignore icon_wink.gif fixme.gif icon_smile.gif icon_smile2.gif 
 
 EXTRA_DIST = $(docs_DATA)
 
diff --git a/docs/wiki/lib/plugins/Makefile.am b/docs/wiki/lib/plugins/Makefile.am
index c21986b86..6fe326bf7 100644
--- a/docs/wiki/lib/plugins/Makefile.am
+++ b/docs/wiki/lib/plugins/Makefile.am
@@ -5,5 +5,9 @@ docsdir = @GEDADOCDIR@/$(docname)/lib/plugins
 
 SUBDIRS = note definitionlist 
 
+docs_DATA = .gitignore 
+
+EXTRA_DIST = $(docs_DATA)
+
 MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
 
diff --git a/docs/wiki/lib/plugins/definitionlist/Makefile.am b/docs/wiki/lib/plugins/definitionlist/Makefile.am
index 163e9694a..440e78f0e 100644
--- a/docs/wiki/lib/plugins/definitionlist/Makefile.am
+++ b/docs/wiki/lib/plugins/definitionlist/Makefile.am
@@ -5,5 +5,9 @@ docsdir = @GEDADOCDIR@/$(docname)/lib/plugins/definitionlist
 
 SUBDIRS = images 
 
+docs_DATA = .gitignore 
+
+EXTRA_DIST = $(docs_DATA)
+
 MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
 
diff --git a/docs/wiki/lib/plugins/definitionlist/images/Makefile.am b/docs/wiki/lib/plugins/definitionlist/images/Makefile.am
index 623a04e4b..db55a8d6d 100644
--- a/docs/wiki/lib/plugins/definitionlist/images/Makefile.am
+++ b/docs/wiki/lib/plugins/definitionlist/images/Makefile.am
@@ -3,7 +3,7 @@
 docname=wiki
 docsdir = @GEDADOCDIR@/$(docname)/lib/plugins/definitionlist/images
 
-docs_DATA = bullet.gif 
+docs_DATA = .gitignore bullet.gif 
 
 EXTRA_DIST = $(docs_DATA)
 
diff --git a/docs/wiki/lib/plugins/note/Makefile.am b/docs/wiki/lib/plugins/note/Makefile.am
index 7d0085564..96e7cd080 100644
--- a/docs/wiki/lib/plugins/note/Makefile.am
+++ b/docs/wiki/lib/plugins/note/Makefile.am
@@ -5,5 +5,9 @@ docsdir = @GEDADOCDIR@/$(docname)/lib/plugins/note
 
 SUBDIRS = images 
 
+docs_DATA = .gitignore 
+
+EXTRA_DIST = $(docs_DATA)
+
 MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
 
diff --git a/docs/wiki/lib/plugins/note/images/Makefile.am b/docs/wiki/lib/plugins/note/images/Makefile.am
index a3fab241e..9d351408e 100644
--- a/docs/wiki/lib/plugins/note/images/Makefile.am
+++ b/docs/wiki/lib/plugins/note/images/Makefile.am
@@ -3,7 +3,7 @@
 docname=wiki
 docsdir = @GEDADOCDIR@/$(docname)/lib/plugins/note/images
 
-docs_DATA = warning.png important.png tip.png note.png 
+docs_DATA = .gitignore warning.png important.png tip.png note.png 
 
 EXTRA_DIST = $(docs_DATA)
 
diff --git a/docs/wiki/lib/tpl/Makefile.am b/docs/wiki/lib/tpl/Makefile.am
index 9c731718b..8152f5c2f 100644
--- a/docs/wiki/lib/tpl/Makefile.am
+++ b/docs/wiki/lib/tpl/Makefile.am
@@ -5,5 +5,9 @@ docsdir = @GEDADOCDIR@/$(docname)/lib/tpl
 
 SUBDIRS = default 
 
+docs_DATA = .gitignore 
+
+EXTRA_DIST = $(docs_DATA)
+
 MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
 
diff --git a/docs/wiki/lib/tpl/default/Makefile.am b/docs/wiki/lib/tpl/default/Makefile.am
index c37d2c535..a35eb1a0f 100644
--- a/docs/wiki/lib/tpl/default/Makefile.am
+++ b/docs/wiki/lib/tpl/default/Makefile.am
@@ -5,5 +5,9 @@ docsdir = @GEDADOCDIR@/$(docname)/lib/tpl/default
 
 SUBDIRS = images 
 
+docs_DATA = .gitignore 
+
+EXTRA_DIST = $(docs_DATA)
+
 MAINTAINERCLEANFILES = *.log core FILE *~ Makefile.in
 
diff --git a/docs/wiki/lib/tpl/default/images/Makefile.am b/docs/wiki/lib/tpl/default/images/Makefile.am
index 3ef3d5afb..0df751309 100644
--- a/docs/wiki/lib/tpl/default/images/Makefile.am
+++ b/docs/wiki/lib/tpl/default/images/Makefile.am
@@ -3,7 +3,7 @@
 docname=wiki
 docsdir = @GEDADOCDIR@/$(docname)/lib/tpl/default/images
 
-docs_DATA = link_icon.gif open.gif closed.gif mail_icon.gif tocdot2.gif inputshadow.png favicon buttonshadow.png windows.gif 
+docs_DATA = .gitignore link_icon.gif open.gif closed.gif mail_icon.gif tocdot2.gif inputshadow.png favicon buttonshadow.png windows.gif 
 
 EXTRA_DIST = $(docs_DATA)
 
diff --git a/docs/wiki/libgeda3.html b/docs/wiki/libgeda3.html
index d502d1e66..e28c67fe0 100644
--- a/docs/wiki/libgeda3.html
+++ b/docs/wiki/libgeda3.html
@@ -6,7 +6,7 @@
   
   libgeda3
 
-
+
 
 
 
diff --git a/docs/wiki/playground_transistor_guide.html b/docs/wiki/playground_transistor_guide.html
index 7be00d94c..eedf96abb 100644
--- a/docs/wiki/playground_transistor_guide.html
+++ b/docs/wiki/playground_transistor_guide.html
@@ -6,7 +6,7 @@
   
   playground:transistor_guide
 
-
+
 
 
 
diff --git a/docs/wiki/start_es.html b/docs/wiki/start_es.html
index 4136281e1..a0e08c5d6 100644
--- a/docs/wiki/start_es.html
+++ b/docs/wiki/start_es.html
@@ -6,7 +6,7 @@
   
   start_es
 
-
+
 
 
 
diff --git a/docs/wiki/start_fr.html b/docs/wiki/start_fr.html
index 2859f911f..ba5c00a95 100644
--- a/docs/wiki/start_fr.html
+++ b/docs/wiki/start_fr.html
@@ -6,7 +6,7 @@
   
   start_fr
 
-
+
 
 
 
-- 
2.11.4.GIT