[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
gEDA-cvs: CVS update: 001geda_faq.html
User: ahvezda
Date: 06/09/06 21:58:27
Modified: . 001geda_faq.html geda_documentation.html
geda_faq-gsch2pcb.html geda_faq.html geda_fc4.html
geda_file_format_spec.html
geda_icarus_ieee1364.html geda_icarus_mp.html
geda_icarus_opcodes.html geda_icarus_vpi_mp.html
geda_icarus_vpi_within_vvp.html
geda_icarus_vvp_runtime.html
geda_icarus_vvp_simulation.html
geda_icarus_xnf.html geda_igarus_fpga_lcg.html
geda_installation.html
geda_master_attributes_list.html
geda_mcalc_readme.html
geda_pcb-quick_reference.html geda_pcb_tips.html
geda_scg.html geda_style_guide.html
geda_wcalc_readme.html
Log:
Updated the wiki snapshot to the latest version from the web.
Revision Changes Path
1.2 +82 -82 eda/geda/gaf/docs/wiki/001geda_faq.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: 001geda_faq.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/001geda_faq.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- 001geda_faq.html 22 Aug 2006 02:56:12 -0000 1.1
+++ 001geda_faq.html 7 Sep 2006 01:58:26 -0000 1.2
@@ -12,8 +12,8 @@
<link rel="alternate" type="application/rss+xml" title="Current Namespace" href="http://geda.seul.org/wiki/feed.php?mode=list&ns=geda"; />
<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/geda:faq.fr?do=export_xhtml"; />
<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/geda:faq.fr?do=export_raw"; />
- <meta name="date" content="2006-08-11T18:05:11-0400" />
- <meta name="robots" content="index,follow" />
+ <meta name="date" content="2006-09-04T16:53:40-0400" />
+ <meta name="robots" content="noindex,nofollow" />
<link rel="stylesheet" media="screen" type="text/css" href="lib/exe/css" />
<link rel="stylesheet" media="print" type="text/css" href="lib/exe/001css" />
</head>
@@ -27,15 +27,15 @@
<li class="level1"><div class="li"><span class="li"><a href="#faq_geda" class="toc">FAQ gEDA</a></span></div>
<ul class="toc">
<li class="level2"><div class="li"><span class="li"><a href="#qu_est_ce_que_le_projet_geda" class="toc">Qu'est ce que le projet gEDA?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#what_is_geda_gaf_and_how_does_it_relate_to_geda" class="toc">What is gEDA/gaf and how does it relate to gEDA?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#what_is_the_geda_suite" class="toc">What is the gEDA suite?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#why_what_makes_geda_so_different_from_other_eda_tools" class="toc">Why? What makes gEDA so different from other EDA tools?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#why_does_the_geda_suite_seem_like_a_collection_of_random_programs_and_not_a_single_integrated_application" class="toc">Why does the gEDA Suite seem like a collection of random programs, and not a single integrated application?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#so_which_is_better_a_suite_i.e._confederacy_of_programs_or_an_integrated_application" class="toc">So which is better, a suite (i.e. confederacy) of programs or an integrated application?</a></span></div>
+<li class="level2"><div class="li"><span class="li"><a href="#qu_est_ce_que_geda_gaf_et_quelle_est_sa_relation_avec_geda" class="toc">qu'est ce que gEDA/gaf et quelle est sa relation avec gEDA?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#qu_est_ce_que_la_suite_geda" class="toc">Qu'est ce que la suite gEDA?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#pourquoi_qu_est_ce_qui_rend_geda_si_different_des_autres_outils_d_eda" class="toc">Pourquoi? Qu'est ce qui rend gEDA si différent des autres outils d'EDA ?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#pourquoi_la_suite_geda_ressemble-t-elle_a_une_collection_de_programmes_epars_et_pas_une_seule_application_integree" class="toc">Pourquoi la Suite gEDA ressemble-t-elle à une collection de programmes épars et pas une seule application intégrée?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#qu_est_ce_qui_est_mieux_une_suite_i.e._confederee_de_programmes_ou_une_application_integree" class="toc">Qu'est ce qui est mieux, une suite (i.e. confédérée) de programmes ou une application intégrée?</a></span></div>
<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#suite_confederacy_pros" class="toc">Suite (confederacy) pros:</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#suite_confederacy_cons" class="toc">Suite (confederacy) cons:</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#monolithic_application_pros" class="toc">Monolithic application pros:</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#pour_la_suite_l_association" class="toc">Pour la Suite (l'association):</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#contre_la_suite_l_association" class="toc">Contre la Suite (l'association):</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#pour_les_applications_monolithiques" class="toc">Pour les applications monolithiques:</a></span></div></li>
<li class="level3"><div class="li"><span class="li"><a href="#monolithic_application_cons" class="toc">Monolithic application cons:</a></span></div></li>
</ul>
</li>
@@ -59,191 +59,191 @@
</p>
<p>
-The originator of gEDA project is Ales Hvezda. The gEDA project has grown quite a bit, since the Spring of 1998. It is no longer one person producing tools. Instead, there are many people involved. A few people are contributing to the original tools, while others are doing their own development on their own tools. So, gEDA does not refer to the original tools anymore (those tools now stand on their own now), but instead it refers to all the projects which are free and are somehow associated with this webpage or the geda-dev/geda-user mailing lists. By associating with gEDA, free software authors do not give up any control over their tools, but they gain a community which cares about quality and free (as in freedom) EDA tools.
+Ales Hvezda est à l’origine du projet gEDA. Le projet gEDA a quelque peu grossi, depuis le printemps 1998. Ces outils ne sont plus l’oeuvre d’une seule personne. De nombreuses personnes s’y sont impliquées. Quelques personnes contribuent aux outils originaux, alors que les autres développent leurs propres outils. C’est la raison pour laquelle gEDA ne se réfère plus aux outils originels (ils ont maintenant leurs propres vies) mais à tous les projets qui sont libres et qui sont associés quelque part dans ces pages web ou les listes de diffusion geda-dev/geda-user. En association avec gEDA, les auteurs de logiciels libres ne laissent pas le contrôle sur leurs outils mais ils sont aidés par la communauté pour maintenir la qualité et la liberté des outils EDA.
</p>
<p>
-gEDA can be pronounced â??gee-daahhhâ?? (rhymes with cheetah) or â??g-dahhh (short g).
+gEDA peut être prononcé « gee-daahhh » (rhymes with cheetah) ou â??g-dahhh (short g).
</p>
</div>
-<!-- SECTION [25-1540] -->
-<h2><a name="what_is_geda_gaf_and_how_does_it_relate_to_geda" id="what_is_geda_gaf_and_how_does_it_relate_to_geda">What is gEDA/gaf and how does it relate to gEDA?</a></h2>
+<!-- SECTION [25-1585] -->
+<h2><a name="qu_est_ce_que_geda_gaf_et_quelle_est_sa_relation_avec_geda" id="qu_est_ce_que_geda_gaf_et_quelle_est_sa_relation_avec_geda">qu'est ce que gEDA/gaf et quelle est sa relation avec gEDA?</a></h2>
<div class="level2">
<p>
-gaf stands for â??<em class="u">g</em>schem <em class="u">a</em>nd <em class="u">f</em>riendsâ??. 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 signifie « <em class="u">g</em>schem <em class="u">a</em>nd <em class="u">f</em>riends » (gschem et ses amis). C’est un sous-jeu de la suite d’outils complète groupée sous le nom de gEDA. gEDA/gaf est une collection d’outils qui inclut actuellement:
</p>
<ul>
-<li class="level1"><div class="li"> gschem: A schematic capture program</div>
+<li class="level1"><div class="li"> gschem: un programme de capture de schémas</div>
</li>
-<li class="level1"><div class="li"> gnetlist: A netlist generation program</div>
+<li class="level1"><div class="li"> gnetlist: un programme de génération de netlist</div>
</li>
-<li class="level1"><div class="li"> gsymcheck: A syntax checker for schematic symbols</div>
+<li class="level1"><div class="li"> gsymcheck: un vérificateur de syntaxe pour les symboles de schémas</div>
</li>
-<li class="level1"><div class="li"> gattrib: A spreadsheet programm that manipulates the properties of symbols of a schematic</div>
+<li class="level1"><div class="li"> gattrib: une feuille de calcul qui manipule les propriétés des symboles d’un schéma</div>
</li>
-<li class="level1"><div class="li"> libgeda: Libraries for gschem gnetlist and gsymcheck</div>
+<li class="level1"><div class="li"> libgeda: les bibliothèques pour gnetlist de gschem et gsymcheck</div>
</li>
-<li class="level1"><div class="li"> gsch2pcb: Forward annotation from your schematic to layout using <a href="http://geda.seul.org/wiki/geda:pcb"; class="wikilink2" title="geda:pcb">PCB</a>.</div>
+<li class="level1"><div class="li"> gsch2pcb: Annotation directe depuis votre schéma vers le circuit en utilisant <a href="http://geda.seul.org/wiki/geda:pcb"; class="wikilink2" title="geda:pcb">PCB</a>.</div>
</li>
-<li class="level1"><div class="li"> some minor utils</div>
+<li class="level1"><div class="li"> quelques utilitaires mineurs</div>
</li>
</ul>
<p>
- The gEDA/gaf tools share a common file format (.sch) and also share a common link library (libgeda.so). The gEDA/gaf source distribution can be found on this website (geda.seul.org).
+ Les outils gEDA/gaf partagent un format de fichier commun (.sch) et partagent aussi une bibliothèque commune (libgeda.so). Les sources de la distribution gEDA/gaf peuvent être trouvées sur ce site web (geda.seul.org).
</p>
<p>
-Even though gaf is very much a part of gEDA, the gEDA name does not necessarily only apply to gaf â?? tools gathered under the â??gEDAâ?? moniker include many other programs. Indeed, gEDA refers to <strong>any</strong> <acronym title="GNU General Public License">GPL</acronym>‘d EDA tool which decides to associate itself with the gEDA website/mailing list. Important examples of gEDA tools include the layout program <a href="http://geda.seul.org/wiki/geda:pcb"; class="wikilink2" title="geda:pcb">PCB</a>, the Verilog complier <a href="http://www.icarus.com/eda/verilog/"; class="urlextern" title="http://www.icarus.com/eda/verilog/"; rel="nofollow">Icarus Verilog</a>, the analog circuit simulator <a href="http://www.gnucap.org/"; class="urlextern" title="http://www.gnucap.org/"; rel="nofollow">gnucap</a>, and the open-source SPICE simulator <a href="http://www.ngspice.org/"; class="urlextern" title="http://www.ngspice.org/"; rel="nofollow">ngspice</a>. Many other gEDA programs also exist.
+Bien que gaf se réfère surtout à gEDA, le nom gEDA ne s’applique pas obligatoirement à gaf â?? les outils rassemblés sous la bannière de « gEDA » comprennent beaucoup d’autres programmes. En fait, gEDA fait référence à <strong>tout</strong> outil d’EDA sous <acronym title="GNU General Public License">GPL</acronym> qui décide de s’associer avec le site web/liste de diffusion. Des exemples importants d’outils gEDA incluent le programme de création de circuit imprimé <a href="http://geda.seul.org/wiki/geda:pcb"; class="wikilink2" title="geda:pcb">PCB</a>, le compilateur Verilog <a href="http://www.icarus.com/eda/verilog/"; class="urlextern" title="http://www.icarus.com/eda/verilog/"; rel="nofollow">Icarus Verilog</a>, le simulateur de circuits analogiques <a href="http://www.gnucap.org/"; class="urlextern" title="http://www.gnucap.org/"; rel="nofollow">gnucap</a> et le simulateur open-source SPICE <a href="http://www.ngspice.org/"; class="urlextern" title="http://www.ngspice.org/"; rel="nofollow">ngspice</a>. Il existe plusieurs autres programmes gEDA.
</p>
<p>
-For historical reasons, on <a href="http://freshmeat.net/"; class="urlextern" title="http://freshmeat.net/"; rel="nofollow">freshmeat</a> gaf is known as the package â??gEDAâ??.
+Pour des raisons historiques, sur <a href="http://freshmeat.net/"; class="urlextern" title="http://freshmeat.net/"; rel="nofollow">freshmeat</a>, gaf est connu comme le paquet â??gEDAâ??.
</p>
</div>
-<!-- SECTION [1541-3089] -->
-<h2><a name="what_is_the_geda_suite" id="what_is_the_geda_suite">What is the gEDA suite?</a></h2>
+<!-- SECTION [1586-3369] -->
+<h2><a name="qu_est_ce_que_la_suite_geda" id="qu_est_ce_que_la_suite_geda">Qu'est ce que la suite gEDA?</a></h2>
<div class="level2">
<p>
-The gEDA suite is a CDROM image (.iso) created by Stuart Brorson to make it easier to install all the various tools that are part of, associated with, or just plain work with the gEDA projectâ??s software. The vision is that the tools collected on the gEDA suite CDROM constitute a coherent, complete, open-source design environment gathered into one convenient download. Currently the gEDA suite CDROM includes:
+La suite gEDA est une image CDROM (.iso) crée par Stuart Brorson pour faciliter l’installation des divers outils qui forment, sont associés oiu fonctionnent totalement avec le projet gEDA. L’objectif est que les outils rassemblés sur la suite gEDA en CDROM constitue un environnement de conception cohérent, complet, open-source en un seul téléchargement. La suite gEDA sur CDROM inclut actuellement:
</p>
<ul>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/"; class="urlextern" title="http://geda.seul.org/tools/"; rel="nofollow">gEDA/gaf</a> â?? schematic capture and netlisting</div>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/"; class="urlextern" title="http://geda.seul.org/tools/"; rel="nofollow">gEDA/gaf</a> â?? saisie de schématic et netlisting</div>
</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/ngspice"; class="urlextern" title="http://geda.seul.org/tools/ngspice"; rel="nofollow">ngspice</a> â?? SPICE simulation</div>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/ngspice"; class="urlextern" title="http://geda.seul.org/tools/ngspice"; rel="nofollow">ngspice</a> â?? simulation SPICE</div>
</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gnucap"; class="urlextern" title="http://geda.seul.org/tools/gnucap"; rel="nofollow">gnucap</a> â?? Analog simulation</div>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gnucap"; class="urlextern" title="http://geda.seul.org/tools/gnucap"; rel="nofollow">gnucap</a> â?? simulation analogique</div>
</li>
<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gspiceui"; class="urlextern" title="http://geda.seul.org/tools/gspiceui"; rel="nofollow">gspiceui</a> â?? <acronym title="Graphical User Interface">GUI</acronym> front end for ngspice/gnucap</div>
</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/pcb"; class="urlextern" title="http://geda.seul.org/tools/pcb"; rel="nofollow">pcb</a> â?? PCB layout</div>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/pcb"; class="urlextern" title="http://geda.seul.org/tools/pcb"; rel="nofollow">pcb</a> â?? placement avec PCB</div>
</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gerbv"; class="urlextern" title="http://geda.seul.org/tools/gerbv"; rel="nofollow">gerbv</a> â?? Gerber viewer</div>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gerbv"; class="urlextern" title="http://geda.seul.org/tools/gerbv"; rel="nofollow">gerbv</a> â?? visualisation Gerber</div>
</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/icarus"; class="urlextern" title="http://geda.seul.org/tools/icarus"; rel="nofollow">Icarus Verilog</a> â?? Verilog simulator</div>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/icarus"; class="urlextern" title="http://geda.seul.org/tools/icarus"; rel="nofollow">Icarus Verilog</a> â?? simulateur Verilog</div>
</li>
-<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gtkwave"; class="urlextern" title="http://geda.seul.org/tools/gtkwave"; rel="nofollow">GTKWave</a> â?? Digitial waveform viewer</div>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/tools/gtkwave"; class="urlextern" title="http://geda.seul.org/tools/gtkwave"; rel="nofollow">GTKWave</a> â?? visualisation de forme d’onde numérique</div>
</li>
-<li class="level1"><div class="li"> <a href="http://wcalc.sourceforge.net/"; class="urlextern" title="http://wcalc.sourceforge.net/"; rel="nofollow">wcalc</a> â?? Transmission line and electromagnetic structure analysis</div>
+<li class="level1"><div class="li"> <a href="http://wcalc.sourceforge.net/"; class="urlextern" title="http://wcalc.sourceforge.net/"; rel="nofollow">wcalc</a> â?? analyse de ligne de transmission et structure électromagnetique</div>
</li>
</ul>
<p>
- At the center of the gEDA suite CDROM is an easy to use installer that automates the building and installing of all the various packages from source â?? making it easy to install the whole suite for the first time user. The gEDA suite CDROM image is available from the <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">download</a> page. <strong>Note: The installer works only with Linux!</strong>
+ Au centre de la suite gEDA en CDROM est la facilité d’utiliser l’installateur qui automatise la construction et l’installation des divers paquets depuis les sources - facilitant l’installation la suite complète pour les novices. La suite gEDA en CDROM est disponible sur la page de <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">téléchargement</a>. <strong>Note: L’installateur ne fonctionne qu’avec Linux!</strong>
</p>
</div>
-<!-- SECTION [3090-4612] -->
-<h2><a name="why_what_makes_geda_so_different_from_other_eda_tools" id="why_what_makes_geda_so_different_from_other_eda_tools">Why? What makes gEDA so different from other EDA tools?</a></h2>
+<!-- SECTION [3370-4962] -->
+<h2><a name="pourquoi_qu_est_ce_qui_rend_geda_si_different_des_autres_outils_d_eda" id="pourquoi_qu_est_ce_qui_rend_geda_si_different_des_autres_outils_d_eda">Pourquoi? Qu'est ce qui rend gEDA si différent des autres outils d'EDA ?</a></h2>
<div class="level2">
<p>
-Tools in the gEDA suite and associated tools have the following characteristics:
+Les outils de la suite gEDA et leurs associés ont les caractéristiques suivantes:
</p>
<ul>
-<li class="level1"><div class="li"> Free in the monetary sense (no cost).</div>
+<li class="level1"><div class="li"> Gratuit.</div>
</li>
-<li class="level1"><div class="li"> All the file formats and all the source codes are available via the <acronym title="GNU General Public License">GPL</acronym> license. This license grants specific rights to the authors and users of <acronym title="GNU General Public License">GPL</acronym>‘d software.</div>
+<li class="level1"><div class="li"> Tous les formats de fichiers et tous les codes sources sont disponibles en licence <acronym title="GNU General Public License">GPL</acronym>. Cette licence vous garantit des droits spécifiques aux auteurs et aux utilisateurs de logiciels <acronym title="GNU General Public License">GPL</acronym>.</div>
</li>
-<li class="level1"><div class="li"> 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 <acronym title="GNU General Public License">GPL</acronym>) the tools.</div>
+<li class="level1"><div class="li"> L’indépendence vis à vis de toute entreprise. Tous les outils gEDA sont fournis avec les sources complètes. Vous pouvez les changer, les améliorer, les porter (sur d’autres systèmes) et même les distribuer (si vous respectez les termes de la <acronym title="GNU General Public License">GPL</acronym>).</div>
</li>
-<li class="level1"><div class="li"> 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).</div>
+<li class="level1"><div class="li"> Aucun mécanisme n’est utilisé pour restreindre l’utilisation de ces outils (comme l’utilisation de numéros de série du disque dur ou des adresses ethernet pour forcer le logiciel à ne fonctionner que sur un machine).</div>
</li>
-<li class="level1"><div class="li"> 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.</div>
+<li class="level1"><div class="li"> Aucunes limitations arbitraires, imposées par les marketing ou les ingénieurs. Les versions gratuites des outils commerciaux incluent des limitations capricieuses (i.e. une taille de carte limité, l’impossibilité d’imprimer, l’impossibilité d’exporter des netlists, etc.) qui verrouille le programme et force les utilisateurs sérieux à acheter les outils complets. Par contraste, les outils gEDA sont pleinement fonctionnels et n’imposent aucune limitation arbitraire sur la conception pour vous soutirer de l’argent.</div>
</li>
-<li class="level1"><div class="li"> 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).</div>
+<li class="level1"><div class="li"> Garanties de protection de conception. Comme le logiciel fonctionnera pour toujours (pour les raisons citées ci-dessus), les fichiers de conception de gEDA sera toujours visualisable/éditable (avec les bonnes versions du logiciel).</div>
</li>
-<li class="level1"><div class="li"> 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.</div>
+<li class="level1"><div class="li"> Flux de conception ouverts. Cela signifie que les outils correspondent les uns avec les autres par des moyens connus et documentés (fichiers / <acronym title="Application Programming Interface">API</acronym>). Il est facile de remplacer un outil ou de l’améliorer avec quelque chose d’autre si vous le désirez.</div>
</li>
-<li class="level1"><div class="li"> Stability - Bugs which cause crashes are investigated immediately and fixed as soon as possible.</div>
+<li class="level1"><div class="li"> Stabilité - Les bogues qui plantent sont étudiés immediatement et réparés dès que possible.</div>
</li>
-<li class="level1"><div class="li"> Minimize bloat and unnecessary features.</div>
+<li class="level1"><div class="li"> Minimise les fonctionnalités gourmandes et inutiles.</div>
</li>
-<li class="level1"><div class="li"> Run on as many platforms as possible. For gEDA/gaf: GNU/Linux, various other Unix systems.</div>
+<li class="level1"><div class="li"> Fonctionne sur autant de plates-formes que possible. Pour gEDA/gaf: GNU/Linux et d’autres systèmes Unix.</div>
</li>
-<li class="level1"><div class="li"> Developed in an open (no secrets) fashion.</div>
+<li class="level1"><div class="li"> Dévelopé d’une manière ouverte (pas de secrets).</div>
</li>
-<li class="level1"><div class="li"> Strive to be documented.</div>
+<li class="level1"><div class="li"> Les programmes sont documentées.</div>
</li>
</ul>
<p>
- 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 n’aura peut être pas les dernières fonctionnalités les plus pointues que l’on pourrait trouver dans d’autres paquets et peut, quelques fois, être vu comme à la traîne de la technique EDA mais les outils sont devenus utiles à beaucoup de personnes à cause des raisons mentionnées ci-dessus.
</p>
</div>
-<!-- SECTION [4613-6695] -->
-<h2><a name="why_does_the_geda_suite_seem_like_a_collection_of_random_programs_and_not_a_single_integrated_application" id="why_does_the_geda_suite_seem_like_a_collection_of_random_programs_and_not_a_single_integrated_application">Why does the gEDA Suite seem like a collection of random programs, and not a single integrated application?</a></h2>
+<!-- SECTION [4963-7518] -->
+<h2><a name="pourquoi_la_suite_geda_ressemble-t-elle_a_une_collection_de_programmes_epars_et_pas_une_seule_application_integree" id="pourquoi_la_suite_geda_ressemble-t-elle_a_une_collection_de_programmes_epars_et_pas_une_seule_application_integree">Pourquoi la Suite gEDA ressemble-t-elle à une collection de programmes épars et pas une seule application intégrée?</a></h2>
<div class="level2">
<p>
-The gEDA suite is indeed a confederacy of somewhat independent programs. This happened for reasons of history: Ales Hvezda started the gEDA project more or less on his own. The original vision was to produce an end-to-end software suite for creating PC boards so that robotics hobbiests could design their own boards. However, as the gEDA project progressed the large magnitude of this task became clear â?? and coding many of the proposed apps had not even begun!
+La Suite gEDA est un rassemblement de programmes independants. Cela s’est produit pour des raisons historiques: Ales Hvezda a débuté le programme gEDA plus ou moins seul. La vision originelle était de produire une suite intégrée complète pour créer des circuits imprimés de telle manière que les passionnés de robots puissent concevoir leurs propres cartes. Néanmoins, au fur et à mesure de la progression du projet gEDA, l’ampleur de la tâche est devenu claire - et le codage des nombreuses applications proposées n’avait pas encore commencé!
</p>
<p>
-Meanwhile, other software developers â?? with their own independently written applications â?? found the gEDA project vision compelling. The authors of those applications joined Ales and contributed their programs to the gEDA project. Amongst the contributed projects was â??pcbâ??, a ten year old (at that time) PCB layout program. With the contribution of â??pcbâ??, gEDAâ??s originally planned layout tool â??gpcbâ?? was scuttled. At the same time, other developers contributed analog and digital simulators, waveform viewers, and so on.
+Pendant ce temps, d’autres développeurs de logiciels -avec leurs propres applications écrites indépendament - ont trouvé que la vision du projet permettait de les compléter. Les auteurs de ces applications se sont joints à Ales et ont fait contribuer leur programme au projet gEDA. Parmi des projets, on trouve « pcb », un programme de création de circuits imprimés vieux de 10 ans (à ce moment). Avec cette contribution de « pcb », l’outil originel pour circuits imprimés de gEDA, « gpcb » a été abandonné. Au même moment, d’autres développeurs ont ajouté des simulateurs analogiques et numériques, des visualiseurs de formes de signal, ainsi de suite.
</p>
<p>
-In this way the gEDA suite came together. It is not shared code, or a common user interface which distinguishes the gEDA suite. Rather, the shared vision of an open-source EDA environment is the thread which holds the project together. Today, the gEDA Suite is a collection of many different programs contributed by many different authors. The apps strive to work together, and usually succeed. But the separate beginnings of each program in the suite are still observable. Nonetheless, with a little work the various components of the suite are interoperable, and many people have completed quite complex board designs using the gEDA suite.
+C’est de cette manière que s’est agglomérée la suite gEDA. Ce n’est pas un code partagé ou une interface utilisateur commune qui distingue la suite gEDA. C’est plutôt la vision partagée d’un environnement EDA open-source qui maintient la cohérence du projet. Aujourd’hui, la Suite gEDA est un ensemble de différents programmes réalisés par plusieurs auteurs. Les applications tentent de fonctionner ensemble et réussissent généralement. Mais les démarrages séparés de chaque programme de la suite sont encore observables. Néanmoins, avec un peu de travail, les divers composants de la Suite sont intéropérables et plusieurs personnes ont achevé des circuits imprimés assez compliqués en utilisant la Suite gEDA.
</p>
</div>
-<!-- SECTION [6696-8466] -->
-<h2><a name="so_which_is_better_a_suite_i.e._confederacy_of_programs_or_an_integrated_application" id="so_which_is_better_a_suite_i.e._confederacy_of_programs_or_an_integrated_application">So which is better, a suite (i.e. confederacy) of programs or an integrated application?</a></h2>
+<!-- SECTION [7519-9623] -->
+<h2><a name="qu_est_ce_qui_est_mieux_une_suite_i.e._confederee_de_programmes_ou_une_application_integree" id="qu_est_ce_qui_est_mieux_une_suite_i.e._confederee_de_programmes_ou_une_application_integree">Qu'est ce qui est mieux, une suite (i.e. confédérée) de programmes ou une application intégrée?</a></h2>
<div class="level2">
<p>
-This is ultimately a matter of religion. Iâ??ll summarize some of the pros and cons (as I see them) of each approach here.
+C’est plus une question de religion. Je vais résumer quelques pour et contre (tel que je les vois) de chaque approche ici.
</p>
</div>
-<!-- SECTION [8467-8690] -->
-<h3><a name="suite_confederacy_pros" id="suite_confederacy_pros">Suite (confederacy) pros:</a></h3>
+<!-- SECTION [9624-9861] -->
+<h3><a name="pour_la_suite_l_association" id="pour_la_suite_l_association">Pour la Suite (l'association):</a></h3>
<div class="level3">
<ul>
-<li class="level1"><div class="li"> 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 <a href="http://www.viasic.com/opensource/"; class="urlextern" title="http://www.viasic.com/opensource/"; rel="nofollow">gnetman</a>, as well as the <a href="http://web.comhem.se/~u31829222/"; class="urlextern" title="http://web.comhem.se/~u31829222/"; rel="nofollow">HEC</a> project. As a general rule, the suite approach offers the greatest freedom to the user.</div>
+<li class="level1"><div class="li"> Vous pouvez utiliser les « meilleures des espèces » d’applications pour chaque partie de la conception. Ceci étant, vous pouvez utiliser le flux standard de gEDA gschem â??gsch2pcb â??pcb pour créer un circuit imprimé. Néanmoins, si vous pensez que l’application open-source « PCB » craint, vous pouvez utiliser le flux gschem â??gnetlist â??Protel (par exemple). Rappelez-vous que gnetlist peut sortir plus de vingt différents formats de netlist! De plus, si vous n’aimez pas un des composants du flux, vous pouvez écrire un autre outil qui le remplacera. Maintenant, il est vrai, qu’en ce moment, en général, qu’il n’existe qu’une seule application pour effectuer une tâche particulière. Cette situation devrait néanmoins changer avec le temps â?? comme en témoigne la nouvelle branche du projet « pcb », le netlister supplémentaire <a href="http://www.viasic.com/opensource/"; class="urlextern" title="http://www.viasic.com/opensource/"; rel="nofollow">gnetman</a>, de même que le projet <a href="http://web.comhem.se/~u31829222/"; class="urlextern" title="http://web.comhem.se/~u31829222/"; rel="nofollow">HEC</a>. En règle générale, l’approche de la suite offre la plus grande liberté à l’utilisateur.</div>
</li>
-<li class="level1"><div class="li"> 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.</div>
+<li class="level1"><div class="li"> Le flux de la conception possède quelques points d’arrêts naturels. Cela se produit lorsqu’un des outils achève son travail et l’écrit dans un dans un fichier (i.e. gschem écrit un fichier .sch ou gnetlist écrit une netlist SPICE). A ce point, vous pouvez facilement casser le flux et écrire des scripts qui traite totalement et/ou partiellement les données de l’étude. Pour les grands développements, c’est un avantage réel d’avoir une approche de « suite de conception ». Cet avantage peut peut ne parler qu’aux « utilisateurs intensifs » mais notez son importance: toutes les suites d’EDA de rang professionnel (Synopsys, Xilinx) travaillent de la même manière.</div>
</li>
-<li class="level1"><div class="li"> Usage of an applications suite can be automated using a Makefile, or even a <acronym title="Practical Extraction and Report Language">Perl</acronym> 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.</div>
+<li class="level1"><div class="li"> L’utilisation d’une suite d’applications peut être automatisé en utilisant un Makefile ou même un script <acronym title="Practical Extraction and Report Language">Perl</acronym>. Les concepteur d’ASIC le font en permanence avec leurs outils de schémas et de synthèse. Quelques utilisateurs gEDA ont publiquement annoncé (sur la liste de diffusion) qu’ils le faisaient aussi et soulignent que c’est une fonctionnalité importante de la suite gEDA.</div>
</li>
-<li class="level1"><div class="li"> 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 enviornment indeed.</div>
+<li class="level1"><div class="li"> Extensibilité: une application monolithique est presque toujours développée un seul développeur qui a une vision unique de son programme. Ce développeur peut assurer un standard de style et d’interface utilisateur pour tous ses outils. Le problème avec ceci est qu’un développeur seul ne peut écrire - même s’il est particulièrement doué - qu’un (ou quelques) partie d’une application EDA. C’est la raison pour laquelle toute application EDA monolithique, open-source, sera toujours limitée dans son champ et ses fonctionnalités par les aptitudes d’un développeur seul. (J’aimerais que l’on me prouve que j’ai tord sur ce point. Les contres-exemples sont les bienvenus mais aucun n’a attiré mon attention lors de l’écriture de cette partie.) D’un autre côté, une assemblée de développeurs travaillant indépendamment sur leurs propres applications - tout en contribuant à l’oeuvre dans son ensemble â?? peuvent donc créer un environnement EDA très grand et très capable.</div>
</li>
</ul>
</div>
-<!-- SECTION [8691-11362] -->
-<h3><a name="suite_confederacy_cons" id="suite_confederacy_cons">Suite (confederacy) cons:</a></h3>
+<!-- SECTION [9862-13042] -->
+<h3><a name="contre_la_suite_l_association" id="contre_la_suite_l_association">Contre la Suite (l'association):</a></h3>
<div class="level3">
<ul>
-<li class="level1"><div class="li"> More confusing to newbies, since they donâ??t know the flow right off the bat. That is, they actually need to <acronym title="Read The Fine Manual">RTFM</acronym> 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.</div>
+<li class="level1"><div class="li"> C’est plus difficile pour les nouveaux car ils ne connaissent pas le flux d’avance. Ceci étant, ils ont réellement besoin de <acronym title="Read The Fine Manual">RTFM</acronym> pour savoir quel est l’outil qu’ils devront faire ensuite fonctionner. Une bonne documentation aide (c’est la raison pour laquelle vous lisez ceci) mais elle reste toujours un second choix après le développement d’une interface intuitive.</div>
</li>
-<li class="level1"><div class="li"> Different programs have different UI conventions (i.e. menu organization is different, keyboard or mouse bindings are different). This can be uncomfortable to those who arenâ??t familiar with the programs.</div>
+<li class="level1"><div class="li"> Les différents programmes peuvent avoir diverses conventions d’interfaces utilisateur (i.e. l’organisation du menu est différente, la fonctionnalité des touches ou de la souris sont différents). Ceci peut être désagréable pour ceux qui ne sont pas familiers avec les programmes.</div>
</li>
-<li class="level1"><div class="li"> Since no assumptions are made about the design flow, schematic symbols are necessarily <a href="http://geda.seul.org/wiki/geda:faq-gschem#what_s_this_business_about_heavy_vs._light_symbols"; class="wikilink1" title="geda:faq-gschem">light</a>. This forces the user to spend more time attaching e.g. footprint attributes to his design. Moreover, the user must spend more time actually researching which footprints to use. However, a good suite (like the gEDA suite) will offer multiple methods to perform this task (e.g. gattrib, <acronym title="Practical Extraction and Report Language">Perl</acronym> scripts to populate footprints, etc.).</div>
+<li class="level1"><div class="li"> Comme aucune supposition n’est faite dans le flux de la conception, les symboles <a href="http://geda.seul.org/wiki/geda:faq-gschem#what_s_this_business_about_heavy_vs._light_symbols"; class="wikilink1" title="geda:faq-gschem">légers</a> de schémas sont nécessaires. Cela impose à l’utilisateur de passer plus de temps à ajouter, par exemple, des attributs d’empreintes de composants à son schéma. De plus, l’utilisateur doit passer réellement plus de temps à trouver quelle empreinte utiliser. Néanmoins, une bonne suite (comme la suite gEDA) offrira de multiples méthodes pour effectuer cette tâche (i.e. gattrib, des scripts <acronym title="Practical Extraction and Report Language">Perl</acronym> pour faciliter les empreintes, etc.).</div>
</li>
-<li class="level1"><div class="li"> Some developers are more energetic than others, or have more free time. Therefore, some programs in a suite will be more developed (and less buggy) than others. Unfortunately, a single buggy program in a suite can unfairly taint a new userâ??s perception of the entire suite.</div>
+<li class="level1"><div class="li"> Quelques développeurs sont plus énergiques que d’autres ou ont plus de temps libre. C’est la raison pour laquelle quelques programmes de la suite seront plus développés (et moins bogués) que d’autres. Malheureusement, un seul programme bogué dans une suite peut entacher la perception d’un nouvel utilisateur sur la suite complète.</div>
</li>
</ul>
</div>
-<!-- SECTION [11363-12696] -->
-<h3><a name="monolithic_application_pros" id="monolithic_application_pros">Monolithic application pros:</a></h3>
+<!-- SECTION [13043-14705] -->
+<h3><a name="pour_les_applications_monolithiques" id="pour_les_applications_monolithiques">Pour les applications monolithiques:</a></h3>
<div class="level3">
<ul>
-<li class="level1"><div class="li"> 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 <acronym title="Read The Fine Manual">RTFM</acronym>.</div>
+<li class="level1"><div class="li"> Un environnement unique, unifié est plus facile à apréhender pour les utilisateurs. Les conventions d’interfaces utilisateur peuvent être harmonisées. L’outil peut être suffisamment intuitif de telle manière qu’il puisse être utilisé sans <acronym title="Read The Fine Manual">RTFM</acronym>.</div>
</li>
-<li class="level1"><div class="li"> Schematic capture symbols can be heavy, so less work is required in attaching attributes to each symbol in a schematic.</div>
+<li class="level1"><div class="li"> Les symboles de schémas peuvent être complets, avec moins de travail nécessaire pour l’attachement des attributs à chaque symbole dans un schéma.</div>
</li>
</ul>
</div>
-<!-- SECTION [12697-13049] -->
+<!-- SECTION [14706-15166] -->
<h3><a name="monolithic_application_cons" id="monolithic_application_cons">Monolithic application cons:</a></h3>
<div class="level3">
<ul>
@@ -256,7 +256,7 @@
</ul>
</div>
-<!-- SECTION [13050-14497] -->
+<!-- SECTION [15167-16614] -->
<h2><a name="what_license_does_geda_use" id="what_license_does_geda_use">What license does gEDA use?</a></h2>
<div class="level2">
@@ -281,7 +281,7 @@
</p>
</div>
-<!-- SECTION [14498-15776] -->
+<!-- SECTION [16615-17893] -->
<h2><a name="where_can_i_get_more_information_about_and_download_geda" id="where_can_i_get_more_information_about_and_download_geda">Where can I get more information about and download gEDA?</a></h2>
<div class="level2">
@@ -306,7 +306,7 @@
</p>
</div>
-<!-- SECTION [15777-16977] -->
+<!-- SECTION [17894-19094] -->
<h2><a name="okay_how_do_i_start_using_geda" id="okay_how_do_i_start_using_geda">Okay, how do I start using gEDA?</a></h2>
<div class="level2">
@@ -319,6 +319,6 @@
</p>
</div>
-<!-- SECTION [16978-] --></div>
+<!-- SECTION [19095-] --></div>
</body>
</html>
1.2 +9 -7 eda/geda/gaf/docs/wiki/geda_documentation.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: geda_documentation.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/geda_documentation.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- geda_documentation.html 22 Aug 2006 02:56:12 -0000 1.1
+++ geda_documentation.html 7 Sep 2006 01:58:26 -0000 1.2
@@ -12,8 +12,8 @@
<link rel="alternate" type="application/rss+xml" title="Current Namespace" href="http://geda.seul.org/wiki/feed.php?mode=list&ns=geda"; />
<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/geda:documentation?do=export_xhtml"; />
<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/geda:documentation?do=export_raw"; />
- <meta name="date" content="2006-05-20T12:37:40-0400" />
- <meta name="robots" content="index,follow" />
+ <meta name="date" content="2006-09-05T22:09:14-0400" />
+ <meta name="robots" content="noindex,nofollow" />
<link rel="stylesheet" media="screen" type="text/css" href="lib/exe/css" />
<link rel="stylesheet" media="print" type="text/css" href="lib/exe/001css" />
</head>
@@ -271,6 +271,8 @@
<ul>
<li class="level1"><div class="li"> <a href="geda_icarus_quick_start.html" class="wikilink1" title="geda:icarus_quick_start">Getting Started with Icarus Verilog</a></div>
</li>
+<li class="level1"><div class="li"> <a href="http://www.rowetel.com/blog/?p=13"; class="urlextern" title="http://www.rowetel.com/blog/?p=13"; rel="nofollow">Icarus Verilog Mini How To</a></div>
+</li>
<li class="level1"><div class="li"> <a href="geda_icarus_mp.html" class="wikilink1" title="geda:icarus_mp">Icarus Verilog compiler man-page</a></div>
</li>
<li class="level1"><div class="li"> <a href="geda_icarus_vpi_mp.html" class="wikilink1" title="geda:icarus_vpi_mp">Compile front end for VPI modules man-page</a></div>
@@ -302,7 +304,7 @@
</ul>
</div>
-<!-- SECTION [4347-5272] -->
+<!-- SECTION [4347-5341] -->
<h1><a name="gtkwave" id="gtkwave">GTKWave</a></h1>
<div class="level1">
<ul>
@@ -336,7 +338,7 @@
</ul>
</div>
-<!-- SECTION [5273-6304] -->
+<!-- SECTION [5342-6373] -->
<h1><a name="wcalc" id="wcalc">Wcalc</a></h1>
<div class="level1">
<ul>
@@ -349,7 +351,7 @@
</ul>
</div>
-<!-- SECTION [6305-6451] -->
+<!-- SECTION [6374-6520] -->
<h1><a name="mcalc" id="mcalc">mcalc</a></h1>
<div class="level1">
<ul>
@@ -360,7 +362,7 @@
</ul>
</div>
-<!-- SECTION [6452-6631] -->
+<!-- SECTION [6521-6700] -->
<h1><a name="covered" id="covered">covered</a></h1>
<div class="level1">
<ul>
@@ -373,6 +375,6 @@
</ul>
</div>
-<!-- SECTION [6632-] --></div>
+<!-- SECTION [6701-] --></div>
</body>
</html>
1.2 +1 -1 eda/geda/gaf/docs/wiki/geda_faq-gsch2pcb.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: geda_faq-gsch2pcb.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/geda_faq-gsch2pcb.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- geda_faq-gsch2pcb.html 22 Aug 2006 02:56:12 -0000 1.1
+++ geda_faq-gsch2pcb.html 7 Sep 2006 01:58:26 -0000 1.2
@@ -13,7 +13,7 @@
<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/geda:faq-gsch2pcb?do=export_xhtml"; />
<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/geda:faq-gsch2pcb?do=export_raw"; />
<meta name="date" content="2006-08-21T21:10:54-0400" />
- <meta name="robots" content="noindex,nofollow" />
+ <meta name="robots" content="index,follow" />
<link rel="stylesheet" media="screen" type="text/css" href="lib/exe/css" />
<link rel="stylesheet" media="print" type="text/css" href="lib/exe/001css" />
</head>
1.2 +14 -14 eda/geda/gaf/docs/wiki/geda_faq.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: geda_faq.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/geda_faq.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- geda_faq.html 22 Aug 2006 02:56:12 -0000 1.1
+++ geda_faq.html 7 Sep 2006 01:58:26 -0000 1.2
@@ -12,8 +12,8 @@
<link rel="alternate" type="application/rss+xml" title="Current Namespace" href="http://geda.seul.org/wiki/feed.php?mode=list&ns=geda"; />
<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/geda:faq?do=export_xhtml"; />
<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/geda:faq?do=export_raw"; />
- <meta name="date" content="2006-05-08T16:37:10-0400" />
- <meta name="robots" content="index,follow" />
+ <meta name="date" content="2006-09-04T16:05:25-0400" />
+ <meta name="robots" content="noindex,nofollow" />
<link rel="stylesheet" media="screen" type="text/css" href="lib/exe/css" />
<link rel="stylesheet" media="print" type="text/css" href="lib/exe/001css" />
</head>
@@ -96,7 +96,7 @@
</p>
<p>
-Even though gaf is very much a part of gEDA, the gEDA name does not necessarily only apply to gaf â?? tools gathered under the â??gEDAâ?? moniker include many other programs. Indeed, gEDA refers to <strong>any</strong> <acronym title="GNU General Public License">GPL</acronym>‘d EDA tool which decides to associate itself with the gEDA website/mailing list. Important examples of gEDA tools include the layout program <a href="geda_pcb.html" class="wikilink2" title="geda:pcb">PCB</a>, the Verilog complier <a href="http://www.icarus.com/eda/verilog/"; class="urlextern" title="http://www.icarus.com/eda/verilog/"; rel="nofollow">Icarus Verilog</a>, the analog circuit simulator <a href="http://www.gnucap.org/"; class="urlextern" title="http://www.gnucap.org/"; rel="nofollow">gnucap</a>, and the open-source SPICE simulator <a href="http://www.ngspice.org/"; class="urlextern" title="http://www.ngspice.org/"; rel="nofollow">ngspice</a>. Many other gEDA programs also exist.
+Even though gaf is very much a part of gEDA, the gEDA name does not necessarily only apply to gaf â?? tools gathered under the â??gEDAâ?? moniker include many other programs. Indeed, gEDA refers to <strong>any</strong> <acronym title="GNU General Public License">GPL</acronym>‘d EDA tool which decides to associate itself with the gEDA website/mailing list. Important examples of gEDA tools include the layout program <a href="geda_pcb.html" class="wikilink2" title="geda:pcb">PCB</a>, the Verilog compiler <a href="http://www.icarus.com/eda/verilog/"; class="urlextern" title="http://www.icarus.com/eda/verilog/"; rel="nofollow">Icarus Verilog</a>, the analog circuit simulator <a href="http://www.gnucap.org/"; class="urlextern" title="http://www.gnucap.org/"; rel="nofollow">gnucap</a>, and the open-source SPICE simulator <a href="http://www.ngspice.org/"; class="urlextern" title="http://www.ngspice.org/"; rel="nofollow">ngspice</a>. Many other gEDA programs also exist.
</p>
<p>
@@ -202,7 +202,7 @@
</p>
</div>
-<!-- SECTION [8347-8570] -->
+<!-- SECTION [8347-8571] -->
<h3><a name="suite_confederacy_pros" id="suite_confederacy_pros">Suite (confederacy) pros:</a></h3>
<div class="level3">
<ul>
@@ -212,12 +212,12 @@
</li>
<li class="level1"><div class="li"> Usage of an applications suite can be automated using a Makefile, or even a <acronym title="Practical Extraction and Report Language">Perl</acronym> 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.</div>
</li>
-<li class="level1"><div class="li"> 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 enviornment indeed.</div>
+<li class="level1"><div class="li"> 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.</div>
</li>
</ul>
</div>
-<!-- SECTION [8571-11242] -->
+<!-- SECTION [8572-11243] -->
<h3><a name="suite_confederacy_cons" id="suite_confederacy_cons">Suite (confederacy) cons:</a></h3>
<div class="level3">
<ul>
@@ -225,14 +225,14 @@
</li>
<li class="level1"><div class="li"> Different programs have different UI conventions (i.e. menu organization is different, keyboard or mouse bindings are different). This can be uncomfortable to those who arenâ??t familiar with the programs.</div>
</li>
-<li class="level1"><div class="li"> Since no assumptions are made about the design flow, schematic symbols are necessarily <a href="http://geda.seul.org/wiki/geda:faq-gschem#what_s_this_business_about_heavy_vs._light_symbols"; class="wikilink1" title="geda:faq-gschem">light</a>. This forces the user to spend more time attaching e.g. footprint attributes to his design. Moreover, the user must spend more time actually researching which footprints to use. However, a good suite (like the gEDA suite) will offer multiple methods to perform this task (e.g. gattrib, <acronym title="Practical Extraction and Report Language">Perl</acronym> scripts to populate footprints, etc.).</div>
+<li class="level1"><div class="li"> Since no assumptions are made about the design flow, schematic symbols are necessarily <a href="geda_faq-gschem.html" class="wikilink1" title="geda:faq-gschem">light</a>. This forces the user to spend more time attaching e.g. footprint attributes to his design. Moreover, the user must spend more time actually researching which footprints to use. However, a good suite (like the gEDA suite) will offer multiple methods to perform this task (e.g. gattrib, <acronym title="Practical Extraction and Report Language">Perl</acronym> scripts to populate footprints, etc.).</div>
</li>
<li class="level1"><div class="li"> Some developers are more energetic than others, or have more free time. Therefore, some programs in a suite will be more developed (and less buggy) than others. Unfortunately, a single buggy program in a suite can unfairly taint a new userâ??s perception of the entire suite.</div>
</li>
</ul>
</div>
-<!-- SECTION [11243-12576] -->
+<!-- SECTION [11244-12577] -->
<h3><a name="monolithic_application_pros" id="monolithic_application_pros">Monolithic application pros:</a></h3>
<div class="level3">
<ul>
@@ -243,7 +243,7 @@
</ul>
</div>
-<!-- SECTION [12577-12929] -->
+<!-- SECTION [12578-12930] -->
<h3><a name="monolithic_application_cons" id="monolithic_application_cons">Monolithic application cons:</a></h3>
<div class="level3">
<ul>
@@ -256,7 +256,7 @@
</ul>
</div>
-<!-- SECTION [12930-14377] -->
+<!-- SECTION [12931-14378] -->
<h2><a name="what_license_does_geda_use" id="what_license_does_geda_use">What license does gEDA use?</a></h2>
<div class="level2">
@@ -281,7 +281,7 @@
</p>
</div>
-<!-- SECTION [14378-15656] -->
+<!-- SECTION [14379-15657] -->
<h2><a name="where_can_i_get_more_information_about_and_download_geda" id="where_can_i_get_more_information_about_and_download_geda">Where can I get more information about and download gEDA?</a></h2>
<div class="level2">
@@ -306,7 +306,7 @@
</p>
</div>
-<!-- SECTION [15657-16857] -->
+<!-- SECTION [15658-16858] -->
<h2><a name="okay_how_do_i_start_using_geda" id="okay_how_do_i_start_using_geda">Okay, how do I start using gEDA?</a></h2>
<div class="level2">
@@ -319,6 +319,6 @@
</p>
</div>
-<!-- SECTION [16858-] --></div>
+<!-- SECTION [16859-] --></div>
</body>
</html>
1.2 +30 -4 eda/geda/gaf/docs/wiki/geda_fc4.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: geda_fc4.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/geda_fc4.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- geda_fc4.html 22 Aug 2006 02:56:12 -0000 1.1
+++ geda_fc4.html 7 Sep 2006 01:58:26 -0000 1.2
@@ -12,7 +12,7 @@
<link rel="alternate" type="application/rss+xml" title="Current Namespace" href="http://geda.seul.org/wiki/feed.php?mode=list&ns=geda"; />
<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/geda:fc4?do=export_xhtml"; />
<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/geda:fc4?do=export_raw"; />
- <meta name="date" content="2006-05-05T23:09:06-0400" />
+ <meta name="date" content="2006-08-28T07:34:11-0400" />
<meta name="robots" content="index,follow" />
<link rel="stylesheet" media="screen" type="text/css" href="lib/exe/css" />
<link rel="stylesheet" media="print" type="text/css" href="lib/exe/001css" />
@@ -24,6 +24,7 @@
<div id="toc__inside">
<ul class="toc">
+<li class="level1"><div class="li"><span class="li"><a href="#installer_20060825_on_fedora_core_4_install_notes" class="toc">Installer 20060825 on Fedora Core 4 install notes</a></span></div></li>
<li class="level1"><div class="li"><span class="li"><a href="#installer_2005080x_on_fedora_core_4_install_notes" class="toc">Installer 2005080X on Fedora Core 4 install notes</a></span></div>
<ul class="toc">
<li class="level2"><div class="li"><span class="li"><a href="#prerequisites" class="toc">Prerequisites:</a></span></div></li>
@@ -32,11 +33,36 @@
</div>
</div>
+<h1><a name="installer_20060825_on_fedora_core_4_install_notes" id="installer_20060825_on_fedora_core_4_install_notes">Installer 20060825 on Fedora Core 4 install notes</a></h1>
+<div class="level1">
+
+<p>
+The latest CD installer will work fine on Fedora Core 4. All gEDA Suite programs now compile happily with gcc-4.X. When you build your FC4 system, make sure you select “devlopement worstation” as your system type, and include as many -devel packages into the build as you can. The following packages are particularly important:
+</p>
+<ul>
+<li class="level1"><div class="li"> gtk-devel</div>
+</li>
+<li class="level1"><div class="li"> gnome-devel</div>
+</li>
+<li class="level1"><div class="li"> guile-devel</div>
+</li>
+<li class="level1"><div class="li"> tcl-devel</div>
+</li>
+<li class="level1"><div class="li"> tk-devel</div>
+</li>
+</ul>
+
+<p>
+If you are missing most of these -devel packages, the installer will do the right thing, but it’s better to pre-install them so the installer doesn’t have to become root to do it.
+</p>
+
+</div>
+<!-- SECTION [1-650] -->
<h1><a name="installer_2005080x_on_fedora_core_4_install_notes" id="installer_2005080x_on_fedora_core_4_install_notes">Installer 2005080X on Fedora Core 4 install notes</a></h1>
<div class="level1">
</div>
-<!-- SECTION [1-64] -->
+<!-- SECTION [651-714] -->
<h2><a name="prerequisites" id="prerequisites">Prerequisites:</a></h2>
<div class="level2">
@@ -69,7 +95,7 @@
</p>
</div>
-<!-- SECTION [65-1201] -->
+<!-- SECTION [715-1851] -->
<h2><a name="problems" id="problems">Problems:</a></h2>
<div class="level2">
@@ -120,6 +146,6 @@
</p>
</div>
-<!-- SECTION [1202-] --></div>
+<!-- SECTION [1852-] --></div>
</body>
</html>
1.3 +19 -19 eda/geda/gaf/docs/wiki/geda_file_format_spec.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: geda_file_format_spec.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/geda_file_format_spec.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- geda_file_format_spec.html 25 Aug 2006 00:57:36 -0000 1.2
+++ geda_file_format_spec.html 7 Sep 2006 01:58:26 -0000 1.3
@@ -12,7 +12,7 @@
<link rel="alternate" type="application/rss+xml" title="Current Namespace" href="http://geda.seul.org/wiki/feed.php?mode=list&ns=geda"; />
<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/geda:file_format_spec?do=export_xhtml"; />
<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/geda:file_format_spec?do=export_raw"; />
- <meta name="date" content="2006-08-21T21:18:08-0400" />
+ <meta name="date" content="2006-09-06T21:42:48-0400" />
<meta name="robots" content="noindex,nofollow" />
<link rel="stylesheet" media="screen" type="text/css" href="lib/exe/css" />
<link rel="stylesheet" media="print" type="text/css" href="lib/exe/001css" />
@@ -195,7 +195,7 @@
</li>
<li class="level1"><div class="li"> fileformat version is just an integer with no minor number.</div>
</li>
-<li class="level1"><div class="li"> 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</div>
+<li class="level1"><div class="li"> 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</div>
</li>
<li class="level1"><div class="li"> <acronym title="Concurrent Versions System">CVS</acronym> or test versions (should not be used): 20030921, 20031004, 20031019, 20031231, 20050814</div>
</li>
@@ -210,7 +210,7 @@
<pre class="code">v 20040111 1</pre>
</div>
-<!-- SECTION [3505-5249] -->
+<!-- SECTION [3505-5259] -->
<h3><a name="line" id="line">line</a></h3>
<div class="level3">
@@ -299,7 +299,7 @@
</p>
</div>
-<!-- SECTION [5250-6484] -->
+<!-- SECTION [5260-6494] -->
<h3><a name="picture" id="picture">picture</a></h3>
<div class="level3">
@@ -407,7 +407,7 @@
</p>
</div>
-<!-- SECTION [6485-9270] -->
+<!-- SECTION [6495-9280] -->
<h3><a name="box" id="box">box</a></h3>
<div class="level3">
@@ -537,7 +537,7 @@
</p>
</div>
-<!-- SECTION [9271-11477] -->
+<!-- SECTION [9281-11487] -->
<h3><a name="circle" id="circle">circle</a></h3>
<div class="level3">
@@ -654,7 +654,7 @@
</p>
</div>
-<!-- SECTION [11478-13603] -->
+<!-- SECTION [11488-13613] -->
<h2><a name="arc" id="arc">arc</a></h2>
<div class="level2">
@@ -751,7 +751,7 @@
</p>
</div>
-<!-- SECTION [13604-15121] -->
+<!-- SECTION [13614-15131] -->
<h3><a name="text" id="text">text</a></h3>
<div class="level3">
@@ -882,7 +882,7 @@
</p>
</div>
-<!-- SECTION [15122-17765] -->
+<!-- SECTION [15132-17775] -->
<h3><a name="net" id="net">net</a></h3>
<div class="level3">
@@ -932,7 +932,7 @@
</p>
</div>
-<!-- SECTION [17766-18291] -->
+<!-- SECTION [17776-18301] -->
<h3><a name="bus" id="bus">bus</a></h3>
<div class="level3">
@@ -989,7 +989,7 @@
</p>
</div>
-<!-- SECTION [18292-19223] -->
+<!-- SECTION [18302-19233] -->
<h3><a name="pin" id="pin">pin</a></h3>
<div class="level3">
@@ -1057,7 +1057,7 @@
</p>
</div>
-<!-- SECTION [19224-20220] -->
+<!-- SECTION [19234-20230] -->
<h3><a name="component" id="component">component</a></h3>
<div class="level3">
@@ -1116,11 +1116,11 @@
<pre class="code">C 18600 19900 1 0 0 7400-1.sym</pre>
<p>
-A component whos origin is at (18600,19900), is selectable, not rotated, not mirrored, and the basename of the component is 7400-1.sym.
+A component who’s origin is at (18600,19900), is selectable, not rotated, not mirrored, and the basename of the component is 7400-1.sym.
</p>
</div>
-<!-- SECTION [20221-21223] -->
+<!-- SECTION [20231-21234] -->
<h3><a name="font" id="font">font</a></h3>
<div class="level3">
@@ -1164,7 +1164,7 @@
</p>
</div>
-<!-- SECTION [21224-21744] -->
+<!-- SECTION [21235-21755] -->
<h2><a name="colors" id="colors">Colors</a></h2>
<div class="level2">
@@ -1234,7 +1234,7 @@
</p>
</div>
-<!-- SECTION [21745-22622] -->
+<!-- SECTION [21756-22633] -->
<h2><a name="attributes" id="attributes">Attributes</a></h2>
<div class="level2">
@@ -1256,7 +1256,7 @@
</p>
</div>
-<!-- SECTION [22623-23598] -->
+<!-- SECTION [22634-23609] -->
<h2><a name="embedded_components" id="embedded_components">Embedded Components</a></h2>
<div class="level2">
@@ -1275,7 +1275,7 @@
</p>
</div>
-<!-- SECTION [23599-24358] -->
+<!-- SECTION [23610-24369] -->
<h2><a name="document_revision_history" id="document_revision_history">Document Revision History</a></h2>
<div class="level2">
<table class="inline">
@@ -1295,6 +1295,6 @@
<br />
</div>
-<!-- SECTION [24359-] --></div>
+<!-- SECTION [24370-] --></div>
</body>
</html>
1.2 +0 -0 eda/geda/gaf/docs/wiki/geda_icarus_ieee1364.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: geda_icarus_ieee1364.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/geda_icarus_ieee1364.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- geda_icarus_ieee1364.html 22 Aug 2006 02:56:12 -0000 1.1
+++ geda_icarus_ieee1364.html 7 Sep 2006 01:58:26 -0000 1.2
@@ -521,10 +521,10 @@
when viewed by reasonable viewers.
-$Id: geda_icarus_ieee1364.html,v 1.1 2006/08/22 02:56:12 ahvezda Exp $
+$Id: geda_icarus_ieee1364.html,v 1.2 2006/09/07 01:58:26 ahvezda Exp $
$Log: geda_icarus_ieee1364.html,v $
-Revision 1.1 2006/08/22 02:56:12 ahvezda
-First checkin of the wiki snapshot, prep work for new version of gEDA/gaf
+Revision 1.2 2006/09/07 01:58:26 ahvezda
+Updated the wiki snapshot to the latest version from the web.
Revision 1.17 2003/07/15 03:49:22 steve
Spelling fixes.
1.2 +0 -0 eda/geda/gaf/docs/wiki/geda_icarus_mp.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: geda_icarus_mp.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/geda_icarus_mp.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- geda_icarus_mp.html 22 Aug 2006 02:56:12 -0000 1.1
+++ geda_icarus_mp.html 7 Sep 2006 01:58:26 -0000 1.2
@@ -22,7 +22,7 @@
<h1><a name="icarus_verilog_compiler_man-page" id="icarus_verilog_compiler_man-page">Icarus Verilog compiler man-page</a></h1>
<div class="level1">
-<pre class="code">iverilog(1) $Date: 2006/08/22 02:56:12 $ iverilog(1)
+<pre class="code">iverilog(1) $Date: 2006/09/07 01:58:26 $ iverilog(1)
@@ -376,7 +376,7 @@
-Version $Date: 2006/08/22 02:56:12 $ iverilog(1)</pre>
+Version $Date: 2006/09/07 01:58:26 $ iverilog(1)</pre>
</div>
</div>
1.2 +0 -0 eda/geda/gaf/docs/wiki/geda_icarus_opcodes.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: geda_icarus_opcodes.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/geda_icarus_opcodes.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- geda_icarus_opcodes.html 22 Aug 2006 02:56:12 -0000 1.1
+++ geda_icarus_opcodes.html 7 Sep 2006 01:58:26 -0000 1.2
@@ -25,7 +25,7 @@
<pre class="code">/*
* Copyright (c) 2001-2003 Stephen Williams (steve@xxxxxxxxxx)
*
- * $Id: geda_icarus_opcodes.html,v 1.1 2006/08/22 02:56:12 ahvezda Exp $
+ * $Id: geda_icarus_opcodes.html,v 1.2 2006/09/07 01:58:26 ahvezda Exp $
*/
1.2 +0 -0 eda/geda/gaf/docs/wiki/geda_icarus_vpi_mp.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: geda_icarus_vpi_mp.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/geda_icarus_vpi_mp.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- geda_icarus_vpi_mp.html 22 Aug 2006 02:56:12 -0000 1.1
+++ geda_icarus_vpi_mp.html 7 Sep 2006 01:58:26 -0000 1.2
@@ -22,7 +22,7 @@
<h1><a name="compile_front_end_for_vpi_modules_man-page" id="compile_front_end_for_vpi_modules_man-page">Compile front end for VPI modules man-page</a></h1>
<div class="level1">
-<pre class="code">iverilog-vpi(1) $Date: 2006/08/22 02:56:12 $ iverilog-vpi(1)
+<pre class="code">iverilog-vpi(1) $Date: 2006/09/07 01:58:26 $ iverilog-vpi(1)
@@ -142,7 +142,7 @@
-Version $Date: 2006/08/22 02:56:12 $ iverilog-vpi(1)</pre>
+Version $Date: 2006/09/07 01:58:26 $ iverilog-vpi(1)</pre>
</div>
</div>
1.2 +0 -0 eda/geda/gaf/docs/wiki/geda_icarus_vpi_within_vvp.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: geda_icarus_vpi_within_vvp.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/geda_icarus_vpi_within_vvp.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- geda_icarus_vpi_within_vvp.html 22 Aug 2006 02:56:12 -0000 1.1
+++ geda_icarus_vpi_within_vvp.html 7 Sep 2006 01:58:26 -0000 1.2
@@ -25,7 +25,7 @@
<pre class="code">/*
* Copyright (c) 2001 Stephen Williams (steve@xxxxxxxxxx)
*
- * $Id: geda_icarus_vpi_within_vvp.html,v 1.1 2006/08/22 02:56:12 ahvezda Exp $
+ * $Id: geda_icarus_vpi_within_vvp.html,v 1.2 2006/09/07 01:58:26 ahvezda Exp $
*/
1.2 +0 -0 eda/geda/gaf/docs/wiki/geda_icarus_vvp_runtime.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: geda_icarus_vvp_runtime.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/geda_icarus_vvp_runtime.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- geda_icarus_vvp_runtime.html 22 Aug 2006 02:56:12 -0000 1.1
+++ geda_icarus_vvp_runtime.html 7 Sep 2006 01:58:26 -0000 1.2
@@ -22,7 +22,7 @@
<h1><a name="icarus_verilog_vvp_runtime_engine_man-page" id="icarus_verilog_vvp_runtime_engine_man-page">Icarus Verilog vvp runtime engine man-page</a></h1>
<div class="level1">
-<pre class="code">vvp(1) $Date: 2006/08/22 02:56:12 $ vvp(1)
+<pre class="code">vvp(1) $Date: 2006/09/07 01:58:26 $ vvp(1)
@@ -166,7 +166,7 @@
-Version $Date: 2006/08/22 02:56:12 $ vvp(1)</pre>
+Version $Date: 2006/09/07 01:58:26 $ vvp(1)</pre>
</div>
</div>
1.2 +0 -0 eda/geda/gaf/docs/wiki/geda_icarus_vvp_simulation.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: geda_icarus_vvp_simulation.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/geda_icarus_vvp_simulation.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- geda_icarus_vvp_simulation.html 22 Aug 2006 02:56:12 -0000 1.1
+++ geda_icarus_vvp_simulation.html 7 Sep 2006 01:58:26 -0000 1.2
@@ -25,7 +25,7 @@
<pre class="code">/*
* Copyright (c) 2001 Stephen Williams (steve@xxxxxxxxxx)
*
- * $Id: geda_icarus_vvp_simulation.html,v 1.1 2006/08/22 02:56:12 ahvezda Exp $
+ * $Id: geda_icarus_vvp_simulation.html,v 1.2 2006/09/07 01:58:26 ahvezda Exp $
*/
VVP SIMULATION ENGINE
1.2 +0 -0 eda/geda/gaf/docs/wiki/geda_icarus_xnf.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: geda_icarus_xnf.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/geda_icarus_xnf.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- geda_icarus_xnf.html 22 Aug 2006 02:56:12 -0000 1.1
+++ geda_icarus_xnf.html 7 Sep 2006 01:58:26 -0000 1.2
@@ -268,8 +268,8 @@
$Log: geda_icarus_xnf.html,v $
- Revision 1.1 2006/08/22 02:56:12 ahvezda
- First checkin of the wiki snapshot, prep work for new version of gEDA/gaf
+ Revision 1.2 2006/09/07 01:58:26 ahvezda
+ Updated the wiki snapshot to the latest version from the web.
Revision 1.16 2003/07/15 03:49:22 steve
Spelling fixes.
1.2 +0 -0 eda/geda/gaf/docs/wiki/geda_igarus_fpga_lcg.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: geda_igarus_fpga_lcg.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/geda_igarus_fpga_lcg.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- geda_igarus_fpga_lcg.html 22 Aug 2006 02:56:12 -0000 1.1
+++ geda_igarus_fpga_lcg.html 7 Sep 2006 01:58:26 -0000 1.2
@@ -25,7 +25,7 @@
<pre class="code">FPGA LOADABLE CODE GENERATOR FOR Icarus Verilog
Copyright 2001 Stephen Williams
- $Id: geda_igarus_fpga_lcg.html,v 1.1 2006/08/22 02:56:12 ahvezda Exp $
+ $Id: geda_igarus_fpga_lcg.html,v 1.2 2006/09/07 01:58:26 ahvezda Exp $
The FPGA code generator supports a variety of FPGA devices, writing
XNF or EDIF depending on the target. You can select the architecture
@@ -211,8 +211,8 @@
---
$Log: geda_igarus_fpga_lcg.html,v $
-Revision 1.1 2006/08/22 02:56:12 ahvezda
-First checkin of the wiki snapshot, prep work for new version of gEDA/gaf
+Revision 1.2 2006/09/07 01:58:26 ahvezda
+Updated the wiki snapshot to the latest version from the web.
Revision 1.12 2005/09/19 21:45:36 steve
Spelling patches from Larry.
1.2 +22 -2 eda/geda/gaf/docs/wiki/geda_installation.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: geda_installation.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/geda_installation.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- geda_installation.html 22 Aug 2006 02:56:12 -0000 1.1
+++ geda_installation.html 7 Sep 2006 01:58:26 -0000 1.2
@@ -12,7 +12,7 @@
<link rel="alternate" type="application/rss+xml" title="Current Namespace" href="http://geda.seul.org/wiki/feed.php?mode=list&ns=geda"; />
<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/geda:installation?do=export_xhtml"; />
<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/geda:installation?do=export_raw"; />
- <meta name="date" content="2006-06-27T07:20:06-0400" />
+ <meta name="date" content="2006-08-29T06:52:43-0400" />
<meta name="robots" content="index,follow" />
<link rel="stylesheet" media="screen" type="text/css" href="lib/exe/css" />
<link rel="stylesheet" media="print" type="text/css" href="lib/exe/001css" />
@@ -38,6 +38,8 @@
<li class="level2"><div class="li"><span class="li"><a href="#fedora_core_1_install_notes" class="toc">Fedora Core 1 install notes</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#suse_9.3_install_notes" class="toc">Suse 9.3 install notes</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#suse_10.0_install_notes" class="toc">Suse 10.0 install notes</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#suse_10.1_install_notes" class="toc">Suse 10.1 install notes</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#debian_install_notes" class="toc">Debian install notes</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#windows_install_notes" class="toc">Windows install notes</a></span></div></li></ul>
</li></ul>
</div>
@@ -243,6 +245,24 @@
</div>
<!-- SECTION [9105-9191] -->
+<h2><a name="suse_10.1_install_notes" id="suse_10.1_install_notes">Suse 10.1 install notes</a></h2>
+<div class="level2">
+
+<p>
+<a href="001geda_suse_10.html" class="wikilink1" title="geda:suse_10.1">SuSE 10.1 notes available here</a>
+</p>
+
+</div>
+<!-- SECTION [9192-9278] -->
+<h2><a name="debian_install_notes" id="debian_install_notes">Debian install notes</a></h2>
+<div class="level2">
+
+<p>
+<a href="geda_debian.html" class="wikilink1" title="geda:debian">Debian notes available here</a>
+</p>
+
+</div>
+<!-- SECTION [9279-9356] -->
<h2><a name="windows_install_notes" id="windows_install_notes">Windows install notes</a></h2>
<div class="level2">
@@ -251,6 +271,6 @@
</p>
</div>
-<!-- SECTION [9192-] --></div>
+<!-- SECTION [9357-] --></div>
</body>
</html>
1.2 +38 -38 eda/geda/gaf/docs/wiki/geda_master_attributes_list.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: geda_master_attributes_list.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/geda_master_attributes_list.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- geda_master_attributes_list.html 22 Aug 2006 02:56:12 -0000 1.1
+++ geda_master_attributes_list.html 7 Sep 2006 01:58:26 -0000 1.2
@@ -12,7 +12,7 @@
<link rel="alternate" type="application/rss+xml" title="Current Namespace" href="http://geda.seul.org/wiki/feed.php?mode=list&ns=geda"; />
<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/geda:master_attributes_list?do=export_xhtml"; />
<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/geda:master_attributes_list?do=export_raw"; />
- <meta name="date" content="2006-04-22T11:15:17-0400" />
+ <meta name="date" content="2006-08-29T00:05:36-0400" />
<meta name="robots" content="index,follow" />
<link rel="stylesheet" media="screen" type="text/css" href="lib/exe/css" />
<link rel="stylesheet" media="print" type="text/css" href="lib/exe/001css" />
@@ -108,38 +108,38 @@
<p>
Attributes in the gEDA/gaf system are nothing more than text items which take on the form: <strong>name</strong>=value. Name can be anything just as long as it doesn’t contain a equals sign. Value can also be anything just as long as it is something (vs nothing). <strong>name</strong>= (without a value part) is not a valid attribute. Also, there cannot be any spaces immediately before or after the equals sign.<br/>
- Attributes can be attached to some part of the symbol. If the attribute conveys information specific to an object, then the attribute should be attached directly to the object, otherwise the attribute should be free standing or oating. Free standing attributes just exist in the symbol file as text items which take on the form <strong>name</strong>=value.
+ Attributes can be attached to some part of the symbol. If the attribute conveys information specific to an object, then the attribute should be attached directly to the object, otherwise the attribute should be free standing or floating. Free standing attributes just exist in the symbol file as text items which take on the form <strong>name</strong>=value.
</p>
</div>
-<!-- SECTION [655-1423] -->
+<!-- SECTION [655-1425] -->
<h2><a name="symbol_only_attributes" id="symbol_only_attributes">Symbol only Attributes</a></h2>
<div class="level2">
</div>
-<!-- SECTION [1424-1458] -->
+<!-- SECTION [1426-1461] -->
<h3><a name="device" id="device">device</a></h3>
<div class="level3">
<p>
<strong>device</strong>= is the device name of the symbol and is required by gnetlist.<br/>
- <strong>device</strong>= should be placed somewhere in the symbol and made invisible. This is a free standing or oating attribute. If the object is a graphic then <strong>device</strong>= should be set to none (<strong>device</strong>=none) and attach a <a href="#graphical" title="geda:master_attributes_list ↵" class="wikilink1">graphical</a>= attribute. Do not confuse this attribute with just having a text label which the device name. Do not put spaces into the device name; there are some programs which dislike spaces in the device specifier. Generally the device name is in all caps.<br/>
+ <strong>device</strong>= should be placed somewhere in the symbol and made invisible. This is a free standing or floating attribute. If the object is a graphic then <strong>device</strong>= should be set to none (<strong>device</strong>=none) and attach a <a href="#graphical" title="geda:master_attributes_list ↵" class="wikilink1">graphical</a>= attribute. Do not confuse this attribute with just having a text label which the device name. Do not put spaces into the device name; there are some programs which dislike spaces in the device specifier. Generally the device name is in all caps.<br/>
Examples: <code>device=7400 device=CONNECTOR 10 device=NPN TRANSISTOR</code>
</p>
</div>
-<!-- SECTION [1459-2100] -->
+<!-- SECTION [1462-2105] -->
<h3><a name="graphical" id="graphical">graphical</a></h3>
<div class="level3">
<p>
Symbols which have no electrical or circuit significance need a <strong>graphical</strong>=1 attribute. Symbols like titleboxes are purely graphical symbols. Any symbol which has <strong>graphical</strong>=1 is ignored by gnetlist.<br/>
- <strong>graphical</strong>=1 should exist somewhere in the symbol and made invisible. This is a free standing or oating attribute. Don’t forget to set <a href="#device" title="geda:master_attributes_list ↵" class="wikilink1">device</a>=none.<br/>
+ <strong>graphical</strong>=1 should exist somewhere in the symbol and made invisible. This is a free standing or floating attribute. Don’t forget to set <a href="#device" title="geda:master_attributes_list ↵" class="wikilink1">device</a>=none.<br/>
Example: <code>graphical=1</code>
</p>
</div>
-<!-- SECTION [2101-2513] -->
+<!-- SECTION [2106-2520] -->
<h3><a name="description" id="description">description</a></h3>
<div class="level3">
@@ -149,7 +149,7 @@
</p>
</div>
-<!-- SECTION [2514-2704] -->
+<!-- SECTION [2521-2711] -->
<h3><a name="author" id="author">author</a></h3>
<div class="level3">
@@ -159,7 +159,7 @@
</p>
</div>
-<!-- SECTION [2705-3301] -->
+<!-- SECTION [2712-3308] -->
<h3><a name="comment" id="comment">comment</a></h3>
<div class="level3">
@@ -169,7 +169,7 @@
</p>
</div>
-<!-- SECTION [3302-3575] -->
+<!-- SECTION [3309-3582] -->
<h3><a name="pinseq" id="pinseq">pinseq</a></h3>
<div class="level3">
@@ -185,7 +185,7 @@
</p>
</div>
-<!-- SECTION [3576-4268] -->
+<!-- SECTION [3583-4275] -->
<h3><a name="pinnumber" id="pinnumber">pinnumber</a></h3>
<div class="level3">
@@ -201,7 +201,7 @@
</p>
</div>
-<!-- SECTION [4269-4691] -->
+<!-- SECTION [4276-4698] -->
<h3><a name="pintype" id="pintype">pintype</a></h3>
<div class="level3">
@@ -249,7 +249,7 @@
<br />
</div>
-<!-- SECTION [4692-5210] -->
+<!-- SECTION [4699-5217] -->
<h3><a name="pinlabel" id="pinlabel">pinlabel</a></h3>
<div class="level3">
@@ -261,7 +261,7 @@
</p>
</div>
-<!-- SECTION [5211-5544] -->
+<!-- SECTION [5218-5551] -->
<h3><a name="numslots" id="numslots">numslots</a></h3>
<div class="level3">
@@ -271,13 +271,13 @@
</p>
</div>
-<!-- SECTION [5545-6008] -->
+<!-- SECTION [5552-6015] -->
<h3><a name="slotdef" id="slotdef">slotdef</a></h3>
<div class="level3">
<p>
If a component has multiple slots in a physical package then you must attach a <strong>slotdef</strong>=slotnumber:#,#,#... for every device inside the physical package.<br/>
- The slotnumber corresponds to the slot number. The colon after the slot number is required. For example, if a device has 4 slots then there would be <strong>slotdef</strong>=1:..., <strong>slotdef</strong>=2:..., <strong>slotdef</strong>=3:..., and slotdef=4:... attributes somewhere in the symbol and be made invisible. This is a free standing or oating attribute.<br/>
+ The slotnumber corresponds to the slot number. The colon after the slot number is required. For example, if a device has 4 slots then there would be <strong>slotdef</strong>=1:..., <strong>slotdef</strong>=2:..., <strong>slotdef</strong>=3:..., and slotdef=4:... attributes somewhere in the symbol and be made invisible. This is a free standing or floating attribute.<br/>
The #’s have a one-to-one correspondence to the <strong>pinseq</strong> attributes and specify which <strong>pinnumber</strong>=# is used during display (gschem) or netlisting (gnetlist).<br/>
It is recommended that all symbols which have slots have a <a href="#slot" title="geda:master_attributes_list ↵" class="wikilink1">slot</a>=1 attribute attached in the same fashion as the <a href="#device" title="geda:master_attributes_list ↵" class="wikilink1">device</a>= attribute.<br/>
See 7400-1.sym as a concrete example.<br/>
@@ -286,7 +286,7 @@
</p>
</div>
-<!-- SECTION [6009-6987] -->
+<!-- SECTION [6016-6996] -->
<h3><a name="footprint" id="footprint">footprint</a></h3>
<div class="level3">
@@ -298,7 +298,7 @@
</p>
</div>
-<!-- SECTION [6988-7946] -->
+<!-- SECTION [6997-7955] -->
<h3><a name="documentation" id="documentation">documentation</a></h3>
<div class="level3">
@@ -311,12 +311,12 @@
</p>
</div>
-<!-- SECTION [7947-8705] -->
+<!-- SECTION [7956-8714] -->
<h2><a name="schematic_only_attributes" id="schematic_only_attributes">Schematic only Attributes</a></h2>
<div class="level2">
</div>
-<!-- SECTION [8706-8743] -->
+<!-- SECTION [8715-8752] -->
<h3><a name="netname" id="netname">netname</a></h3>
<div class="level3">
@@ -327,7 +327,7 @@
</p>
</div>
-<!-- SECTION [8744-9103] -->
+<!-- SECTION [8753-9112] -->
<h3><a name="source" id="source">source</a></h3>
<div class="level3">
@@ -338,12 +338,12 @@
</p>
</div>
-<!-- SECTION [9104-9725] -->
+<!-- SECTION [9113-9734] -->
<h2><a name="symbol_and_schematic_attributes" id="symbol_and_schematic_attributes">Symbol and Schematic Attributes</a></h2>
<div class="level2">
</div>
-<!-- SECTION [9726-9769] -->
+<!-- SECTION [9735-9778] -->
<h3><a name="refdes" id="refdes">refdes</a></h3>
<div class="level3">
@@ -354,7 +354,7 @@
</p>
</div>
-<!-- SECTION [9770-10201] -->
+<!-- SECTION [9779-10210] -->
<h3><a name="slot" id="slot">slot</a></h3>
<div class="level3">
@@ -363,7 +363,7 @@
</p>
</div>
-<!-- SECTION [10202-10499] -->
+<!-- SECTION [10211-10508] -->
<h3><a name="net" id="net">net</a></h3>
<div class="level3">
@@ -372,7 +372,7 @@
</p>
</div>
-<!-- SECTION [10500-10903] -->
+<!-- SECTION [10509-10912] -->
<h3><a name="value" id="value">value</a></h3>
<div class="level3">
@@ -383,7 +383,7 @@
</p>
</div>
-<!-- SECTION [10904-11119] -->
+<!-- SECTION [10913-11128] -->
<h3><a name="symversion" id="symversion">symversion</a></h3>
<div class="level3">
@@ -401,12 +401,12 @@
</p>
</div>
-<!-- SECTION [11120-12988] -->
+<!-- SECTION [11129-12997] -->
<h2><a name="obsolete_attributes" id="obsolete_attributes">Obsolete Attributes</a></h2>
<div class="level2">
</div>
-<!-- SECTION [12989-13020] -->
+<!-- SECTION [12998-13029] -->
<h3><a name="uref" id="uref">uref</a></h3>
<div class="level3">
@@ -415,7 +415,7 @@
</p>
</div>
-<!-- SECTION [13021-13152] -->
+<!-- SECTION [13030-13161] -->
<h3><a name="name" id="name">name</a></h3>
<div class="level3">
@@ -424,7 +424,7 @@
</p>
</div>
-<!-- SECTION [13153-13306] -->
+<!-- SECTION [13162-13315] -->
<h3><a name="label" id="label">label</a></h3>
<div class="level3">
@@ -433,7 +433,7 @@
</p>
</div>
-<!-- SECTION [13307-13522] -->
+<!-- SECTION [13316-13531] -->
<h3><a name="pin" id="pin">pin#</a></h3>
<div class="level3">
@@ -442,7 +442,7 @@
</p>
</div>
-<!-- SECTION [13523-13731] -->
+<!-- SECTION [13532-13740] -->
<h3><a name="slot1" id="slot1">slot#</a></h3>
<div class="level3">
@@ -451,7 +451,7 @@
</p>
</div>
-<!-- SECTION [13732-13917] -->
+<!-- SECTION [13741-13926] -->
<h3><a name="type" id="type">type</a></h3>
<div class="level3">
@@ -460,7 +460,7 @@
</p>
</div>
-<!-- SECTION [13918-14090] -->
+<!-- SECTION [13927-14099] -->
<h3><a name="email" id="email">email</a></h3>
<div class="level3">
@@ -469,7 +469,7 @@
</p>
</div>
-<!-- SECTION [14091-14175] -->
+<!-- SECTION [14100-14184] -->
<h2><a name="document_revision_history" id="document_revision_history">Document Revision History</a></h2>
<div class="level2">
<table class="inline">
@@ -501,6 +501,6 @@
<br />
</div>
-<!-- SECTION [14176-] --></div>
+<!-- SECTION [14185-] --></div>
</body>
</html>
1.2 +0 -0 eda/geda/gaf/docs/wiki/geda_mcalc_readme.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: geda_mcalc_readme.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/geda_mcalc_readme.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- geda_mcalc_readme.html 22 Aug 2006 02:56:12 -0000 1.1
+++ geda_mcalc_readme.html 7 Sep 2006 01:58:26 -0000 1.2
@@ -22,7 +22,7 @@
<h1><a name="mcalc_readme" id="mcalc_readme">mcalc README</a></h1>
<div class="level1">
-<pre class="code">$Id: geda_mcalc_readme.html,v 1.1 2006/08/22 02:56:12 ahvezda Exp $
+<pre class="code">$Id: geda_mcalc_readme.html,v 1.2 2006/09/07 01:58:26 ahvezda Exp $
WHAT IS IT?
------------
1.2 +64 -65 eda/geda/gaf/docs/wiki/geda_pcb-quick_reference.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: geda_pcb-quick_reference.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/geda_pcb-quick_reference.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- geda_pcb-quick_reference.html 22 Aug 2006 02:56:12 -0000 1.1
+++ geda_pcb-quick_reference.html 7 Sep 2006 01:58:26 -0000 1.2
@@ -12,8 +12,8 @@
<link rel="alternate" type="application/rss+xml" title="Current Namespace" href="http://geda.seul.org/wiki/feed.php?mode=list&ns=geda"; />
<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/geda:pcb-quick_reference?do=export_xhtml"; />
<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/geda:pcb-quick_reference?do=export_raw"; />
- <meta name="date" content="2006-05-08T16:35:30-0400" />
- <meta name="robots" content="index,follow" />
+ <meta name="date" content="2006-09-06T15:43:12-0400" />
+ <meta name="robots" content="noindex,nofollow" />
<link rel="stylesheet" media="screen" type="text/css" href="lib/exe/css" />
<link rel="stylesheet" media="print" type="text/css" href="lib/exe/001css" />
</head>
@@ -54,156 +54,159 @@
<div class="level2">
</div>
-<!-- SECTION [36-59] -->
+<!-- SECTION [36-60] -->
<h3><a name="pcb_keystrokes" id="pcb_keystrokes">PCB Keystrokes</a></h3>
<div class="level3">
<table class="inline">
<tr>
- <th class="centeralign"> KEY </th><th class="centeralign"> MNEMONIC </th><th class="centeralign"> DESCRIPTION </th>
+ <th class="centeralign"> KEY </th><th class="leftalign"> MNEMONIC </th><th class="centeralign"> DESCRIPTION </th>
+ </tr>
+ <tr>
+ <td class="centeralign"> space </td><td class="leftalign"> select </td><td class="leftalign"> enter select mode </td>
</tr>
<tr>
- <td class="centeralign"> space </td><td class="centeralign"> select </td><td class="leftalign">enter select mode </td>
+ <td class="centeralign"> esc </td><td class="leftalign"> panner </td><td class="leftalign"> enter panning mode </td>
</tr>
<tr>
- <td class="centeralign"> esc </td><td class="centeralign"> panner </td><td class="leftalign">enter panning mode </td>
+ <td class="centeralign"> tab </td><td class="leftalign"> flip view </td><td class="leftalign"> view: flip board </td>
</tr>
<tr>
- <td class="centeralign"> tab </td><td class="centeralign"> flip view </td><td class="leftalign">view: flip board </td>
+ <td class="centeralign"> shift-del </td><td class="leftalign"> del-cu </td><td class="leftalign"> deletes electrically connected copper (including power and signal planes) </td>
</tr>
<tr>
- <td class="centeralign"> shift-del </td><td class="centeralign"> del-cu </td><td class="leftalign">deletes electrically connected copper (including power and signal planes) </td>
+ <td class="centeralign"> \ </td><td class="leftalign"> thin-draw </td><td class="leftalign"> toggles thin draw mode </td>
</tr>
<tr>
- <td class="centeralign"> \ </td><td class="centeralign"> thin-draw on/off </td><td class="leftalign">toggles thin draw mode </td>
+ <td class="centeralign"> shift-alt-a </td><td class="leftalign"> unselect </td><td class="leftalign"> clear selection </td>
</tr>
<tr>
- <td class="centeralign"> shift-alt-a </td><td class="centeralign"> unselect </td><td class="leftalign">clear selection </td>
+ <td class="centeralign"> b </td><td class="leftalign"> to other side </td><td class="leftalign"> flip object to the other side of the board </td>
</tr>
<tr>
- <td class="centeralign"> b </td><td class="centeralign"> to other side </td><td class="leftalign">flip object to the other side of the board </td>
+ <td class="centeralign"> shift-b </td><td class="leftalign"> flip view </td><td class="leftalign"> view: flip board </td>
</tr>
<tr>
- <td class="centeralign"> shift-b </td><td class="centeralign"> flip view </td><td class="leftalign">view: flip board </td>
+ <td class="centeralign"> c </td><td class="leftalign"> center </td><td class="leftalign"> view: center display at cursor position </td>
</tr>
<tr>
- <td class="centeralign"> c </td><td class="centeralign"> center </td><td class="leftalign">view: center display at cursor position </td>
+ <td class="centeralign"> ctrl-c </td><td> copy to buffer</td><td class="leftalign"> copy selection to buffer and unselect </td>
</tr>
<tr>
- <td class="centeralign"> ctrl-c </td><td class="centeralign"> copy to buffer </td><td class="leftalign">copy selection to buffer and unselect </td>
+ <td class="centeralign"> d </td><td class="leftalign"> display name </td><td class="leftalign"> display pin or pad name </td>
</tr>
<tr>
- <td class="centeralign"> d </td><td class="centeralign"> display name </td><td class="leftalign">display pin or pad name </td>
+ <td class="centeralign"> shift-d </td><td class="leftalign"> pinout dialog </td><td class="leftalign"> open pinout window for element under mouse cursor </td>
</tr>
<tr>
- <td class="centeralign"> shift-d </td><td class="centeralign"> pinout dialog </td><td class="leftalign">open pinout window for element under mouse cursor </td>
+ <td class="centeralign"> e </td><td> eliminate rats</td><td class="leftalign"> delete all rats </td>
</tr>
<tr>
- <td class="centeralign"> e </td><td class="centeralign"> extinguish rats </td><td class="leftalign">delete all rats </td>
+ <td class="centeralign"> shift-e </td><td class="leftalign"> eliminate some rats </td><td class="leftalign"> delete selected rats </td>
</tr>
<tr>
- <td class="centeralign"> shift-e </td><td class="centeralign"> eliminate some rats </td><td class="leftalign">delete selected rats </td>
+ <td class="centeralign"> f </td><td class="leftalign"> find </td><td class="leftalign"> highlight connections to object under mouse cursor </td>
</tr>
<tr>
- <td class="centeralign"> f </td><td class="centeralign"> find connections </td><td class="leftalign">highlight connections to object under mouse cursor </td>
+ <td class="centeralign"> shift-f </td><td class="leftalign"> un-find </td><td class="leftalign"> un-highlight found connections </td>
</tr>
<tr>
- <td class="centeralign"> shift-f </td><td class="centeralign"> no find-connections </td><td class="leftalign">un-highlight found connections </td>
+ <td class="centeralign"> g </td><td class="leftalign"> increase grid </td><td class="leftalign"> increment grid by configured grid increment </td>
</tr>
<tr>
- <td class="centeralign"> g </td><td class="centeralign"> increase grid </td><td class="leftalign">increment grid by configured grid increment </td>
+ <td class="centeralign"> shift-g </td><td class="leftalign"> decrease grid </td><td class="leftalign"> decrement grid by configured grid increment </td>
</tr>
<tr>
- <td class="centeralign"> shift-g </td><td class="centeralign"> decrease grid </td><td class="leftalign">decrement grid by configured grid increment </td>
+ <td class="centeralign"> h </td><td class="leftalign"> hide </td><td class="leftalign"> toggle the visiblity of the refdes or value attached to the current component </td>
</tr>
<tr>
- <td class="centeralign"> h </td><td class="centeralign"> hide </td><td class="leftalign">toggle the visiblity of the refdes or value attached to the current component </td>
+ <td class="centeralign"> ctrl-h </td><td class="leftalign"> holeplate </td><td class="leftalign"> toggle plating of a via. Used to produce non metalized mounting holes </td>
</tr>
<tr>
- <td class="centeralign"> ctrl-h </td><td class="centeralign"> holeplate </td><td class="leftalign">toggle plating of a via. Used to produce non metalized mounting holes </td>
+ <td class="centeralign"> k </td><td class="leftalign"> klearance </td><td class="leftalign"> increment clearance (soldermask to copper edge) </td>
</tr>
<tr>
- <td class="centeralign"> k </td><td class="centeralign"> klearance </td><td class="leftalign">increment clearance (soldermask to copper edge) </td>
+ <td class="centeralign"> shift-k </td><td class="leftalign"> klear (-) </td><td class="leftalign"> decrement clearance (soldermask to copper edge (NOTE: can go negative!)) </td>
</tr>
<tr>
- <td class="centeralign"> shift-k </td><td class="centeralign"> klear (-) </td><td class="leftalign">decrement clearance (soldermask to copper edge (NOTE: can go negative!)) </td>
+ <td class="centeralign"> m </td><td class="leftalign"> move to layer </td><td class="leftalign"> move the object under the cursor to the current layer </td>
</tr>
<tr>
- <td class="centeralign"> m </td><td class="centeralign"> move to layer </td><td class="leftalign">move the object under the cursor to the current layer </td>
+ <td class="centeralign"> shift-m </td><td class="leftalign"> move selection to layer </td><td class="leftalign"> move selected objects to the current working layer (see <a href="http://geda.seul.org/wiki/geda:pcb_tips#how_do_i_move_one_set_of_layer_tracks_to_another_layer"; class="wikilink1" title="geda:pcb_tips">pcb tip</a>) </td>
</tr>
<tr>
- <td class="centeralign"> shift-m </td><td class="centeralign"> move selection to layer </td><td class="leftalign">move selected objects to the current working layer (see <a href="http://geda.seul.org/wiki/geda:pcb_tips#how_do_i_move_one_set_of_layer_tracks_to_another_layer"; class="wikilink1" title="geda:pcb_tips">pcb tip</a>) </td>
+ <td class="centeralign"> ctrl-m </td><td class="leftalign"> move origin </td><td> set the origin to the current position of the mouse pointer </td>
</tr>
<tr>
- <td class="centeralign"> n </td><td class="centeralign"> name </td><td class="leftalign">show object refdes / pin number (depends on whatâ??s selected) </td>
+ <td class="centeralign"> n </td><td class="leftalign"> name </td><td class="leftalign"> show object refdes / pin number (depends on whatâ??s selected) </td>
</tr>
<tr>
- <td class="centeralign"> shift-p </td><td class="centeralign"> polygon close </td><td class="leftalign">connect the first point of a polygon with the last </td>
+ <td class="centeralign"> shift-p </td><td class="leftalign"> polygon close </td><td class="leftalign"> connect the first point of a polygon with the last </td>
</tr>
<tr>
- <td class="centeralign"> q </td><td class="centeralign"> square toggle </td><td class="leftalign">toggle square/round corners on pads </td>
+ <td class="centeralign"> q </td><td class="leftalign"> square toggle </td><td class="leftalign"> toggle square/round corners on pads </td>
</tr>
<tr>
- <td class="centeralign"> ctrl-r </td><td class="centeralign"> report </td><td class="leftalign">show object report </td>
+ <td class="centeralign"> ctrl-r </td><td class="leftalign"> report </td><td class="leftalign"> show object report </td>
</tr>
<tr>
- <td class="centeralign"> s </td><td class="centeralign"> size </td><td class="leftalign">increment size </td>
+ <td class="centeralign"> s </td><td class="leftalign"> size </td><td class="leftalign"> increment size </td>
</tr>
<tr>
- <td class="centeralign"> shift-s </td><td class="centeralign"> size (-) </td><td class="leftalign">decrement size </td>
+ <td class="centeralign"> shift-s </td><td class="leftalign"> size (-) </td><td class="leftalign"> decrement size </td>
</tr>
<tr>
- <td class="centeralign"> alt-s </td><td class="centeralign"> sizehole </td><td class="leftalign">increase the hole size </td>
+ <td class="centeralign"> alt-s </td><td class="leftalign"> sizehole </td><td class="leftalign"> increase the hole size </td>
</tr>
<tr>
- <td class="centeralign"> alt-shift-s </td><td class="centeralign"> sizehole (-) </td><td class="leftalign">decrease the hole size </td>
+ <td class="centeralign"> alt-shift-s </td><td class="leftalign"> sizehole (-) </td><td class="leftalign"> decrease the hole size </td>
</tr>
<tr>
- <td class="centeralign"> ctrl-s </td><td class="centeralign"> sizehole </td><td class="leftalign">increase the hole size </td>
+ <td class="centeralign"> ctrl-s </td><td class="leftalign"> sizehole </td><td class="leftalign"> increase the hole size </td>
</tr>
<tr>
- <td class="centeralign"> ctrl-shift-s </td><td class="centeralign"> sizehole (-) </td><td class="leftalign">decrease the hole size </td>
+ <td class="centeralign"> ctrl-shift-s </td><td class="leftalign"> sizehole (-) </td><td class="leftalign"> decrease the hole size </td>
</tr>
<tr>
- <td class="centeralign"> v </td><td class="centeralign"> view extents </td><td class="leftalign">global view of working area </td>
+ <td class="centeralign"> v </td><td class="leftalign"> view extents </td><td class="leftalign"> global view of working area </td>
</tr>
<tr>
- <td class="centeralign"> z </td><td class="centeralign"> zoom </td><td class="leftalign">view: zoom in </td>
+ <td class="centeralign"> z </td><td class="leftalign"> zoom </td><td class="leftalign"> view: zoom in </td>
</tr>
<tr>
- <td class="centeralign"> shift-z </td><td class="centeralign"> un-zoom </td><td class="leftalign">view: zoom out </td>
+ <td class="centeralign"> shift-z </td><td class="leftalign"> un-zoom </td><td class="leftalign"> view: zoom out </td>
</tr>
<tr>
- <td class="centeralign"> F1 </td><td class="rightalign"> </td><td class="leftalign">via tool </td>
+ <td class="centeralign"> F1 </td><td class="leftalign"> via </td><td> via tool </td>
</tr>
<tr>
- <td class="centeralign"> F2 </td><td class="centeralign"> line </td><td class="leftalign">tool </td>
+ <td class="centeralign"> F2 </td><td class="leftalign"> line </td><td class="leftalign"> line tool </td>
</tr>
<tr>
- <td class="centeralign"> F3 </td><td class="centeralign"> arc </td><td class="leftalign">tool </td>
+ <td class="centeralign"> F3 </td><td class="leftalign"> arc </td><td> arc tool </td>
</tr>
<tr>
- <td class="centeralign"> F4 </td><td class="centeralign"> text </td><td class="leftalign">tool </td>
+ <td class="centeralign"> F4 </td><td class="leftalign"> text </td><td> text tool </td>
</tr>
<tr>
- <td class="centeralign"> F5 </td><td class="centeralign"> rectangle </td><td class="leftalign">tool </td>
+ <td class="centeralign"> F5 </td><td class="leftalign"> rectangle </td><td> rectangle tool</td>
</tr>
<tr>
- <td class="centeralign"> F6 </td><td class="centeralign"> polygon </td><td class="leftalign">tool </td>
+ <td class="centeralign"> F6 </td><td class="leftalign"> polygon </td><td> polygon tool </td>
</tr>
<tr>
- <td class="centeralign"> F7 </td><td class="rightalign"> </td><td class="rightalign"> </td>
+ <td class="centeralign"> F7 </td><td class="leftalign"> buffer </td><td> buffer mode </td>
</tr>
<tr>
- <td class="centeralign"> F8 </td><td class="rightalign"> </td><td class="rightalign"> </td>
+ <td class="centeralign"> F8 </td><td class="leftalign"> delete </td><td> remove mode </td>
</tr>
<tr>
- <td class="centeralign"> F9 </td><td class="centeralign"> rotate </td><td class="leftalign">rotate mode </td>
+ <td class="centeralign"> F9 </td><td class="leftalign"> rotate </td><td class="leftalign"> rotate mode </td>
</tr>
<tr>
- <td class="centeralign"> F10 </td><td class="centeralign"> file menu </td><td class="rightalign"> </td>
+ <td class="centeralign"> F10 </td><td class="leftalign"> file menu </td><td> file menu </td>
</tr>
<tr>
- <td class="centeralign"> F11 </td><td class="centeralign"> select </td><td class="leftalign">enter select mode (same as [space]) </td>
+ <td class="centeralign"> F11 </td><td class="leftalign"> select </td><td class="leftalign"> select mode (same as [space]) </td>
</tr>
<tr>
<td class="centeralign"> F12 </td><td class="rightalign"> </td><td class="rightalign"> </td>
@@ -212,7 +215,7 @@
<br />
</div>
-<!-- SECTION [60-2923] -->
+<!-- SECTION [61-3017] -->
<h2><a name="viewport_keystrokes" id="viewport_keystrokes">Viewport Keystrokes</a></h2>
<div class="level2">
<table class="inline">
@@ -247,7 +250,7 @@
<br />
</div>
-<!-- SECTION [2924-3297] -->
+<!-- SECTION [3018-3391] -->
<h1><a name="footprint_reference" id="footprint_reference">Footprint Reference</a></h1>
<div class="level1">
@@ -256,7 +259,7 @@
</p>
</div>
-<!-- SECTION [3298-3591] -->
+<!-- SECTION [3392-3685] -->
<h2><a name="general_syntax" id="general_syntax">General syntax</a></h2>
<div class="level2">
@@ -279,7 +282,7 @@
</ul>
</div>
-<!-- SECTION [3592-4204] -->
+<!-- SECTION [3686-4298] -->
<h2><a name="elements" id="elements">Elements</a></h2>
<div class="level2">
@@ -327,7 +330,7 @@
<br />
</div>
-<!-- SECTION [4205-5032] -->
+<!-- SECTION [4299-5126] -->
<h2><a name="pads" id="pads">Pads</a></h2>
<div class="level2">
@@ -372,7 +375,7 @@
<br />
</div>
-<!-- SECTION [5033-5937] -->
+<!-- SECTION [5127-6031] -->
<h2><a name="pins" id="pins">Pins</a></h2>
<div class="level2">
@@ -414,7 +417,7 @@
<br />
</div>
-<!-- SECTION [5938-6636] -->
+<!-- SECTION [6032-6730] -->
<h2><a name="examples" id="examples">Examples</a></h2>
<div class="level2">
<ul>
@@ -432,11 +435,7 @@
</li>
</ul>
-<p>
- <span class="hilited">This page is new, it is not complete, post comments/additions to geda-user w/ title â??PCB Quick Referenceâ??. Remember, subscribe to geda-user before you post to the geda-user e-mail list.</span>
-</p>
-
</div>
-<!-- SECTION [6637-] --></div>
+<!-- SECTION [6731-] --></div>
</body>
</html>
1.2 +58 -48 eda/geda/gaf/docs/wiki/geda_pcb_tips.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: geda_pcb_tips.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/geda_pcb_tips.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- geda_pcb_tips.html 22 Aug 2006 02:56:12 -0000 1.1
+++ geda_pcb_tips.html 7 Sep 2006 01:58:26 -0000 1.2
@@ -12,7 +12,7 @@
<link rel="alternate" type="application/rss+xml" title="Current Namespace" href="http://geda.seul.org/wiki/feed.php?mode=list&ns=geda"; />
<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/geda:pcb_tips?do=export_xhtml"; />
<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/geda:pcb_tips?do=export_raw"; />
- <meta name="date" content="2006-08-03T10:04:54-0400" />
+ <meta name="date" content="2006-08-30T14:30:43-0400" />
<meta name="robots" content="index,follow" />
<link rel="stylesheet" media="screen" type="text/css" href="lib/exe/css" />
<link rel="stylesheet" media="print" type="text/css" href="lib/exe/001css" />
@@ -55,6 +55,7 @@
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_change_the_size_of_a_graphical_object_such_as_text_silkscreen_lines_etc" class="toc">How do I change the size of a graphical object (such as text, silkscreen lines, etc)?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_put_components_on_both_faces_in_pcb" class="toc">How do I put components on both faces in PCB?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_set_the_origin_in_pcb" class="toc">How do I set the origin in pcb?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_measure_distances_and_dimensions_of_components" class="toc">How do I measure distances and dimensions of components?</a></span></div></li>
</ul>
</li>
<li class="level1"><div class="li"><span class="li"><a href="#routing" class="toc">Routing</a></span></div>
@@ -312,15 +313,13 @@
<div class="level2">
<p>
-Adding footprint libraries to PCB is easy: <strong><em>File</em></strong> menu â??> <strong><em>Preferences</em></strong> â??> <strong><em>Library</em></strong> â??> <strong>FOOTPRINTDIRECTORY</strong>
-</p>
-
-<p>
-Donâ??t forget to include the new directory into your gsch2pcb resource file (if you are using gsch2pcb, that is).
+Adding footprint libraries can be done from the <acronym title="Graphical User Interface">GUI</acronym>:<br/>
+ <strong><em>File</em></strong> â??> <strong><em>Preferences</em></strong> â??> <strong><em>Library</em></strong> â??> <strong>FOOTPRINTDIRECTORY</strong><br/>
+ Alternatively you can edit the file <code>$HOME/.pcb/preferences</code>. Look for the line that starts with “library-newlib”. Donâ??t forget to include the new directory into your gsch2pcb resource file (if you are using gsch2pcb, that is).
</p>
</div>
-<!-- SECTION [10481-10785] -->
+<!-- SECTION [10481-10913] -->
<h2><a name="pcb_is_not_finding_my_footprints._why" id="pcb_is_not_finding_my_footprints._why">PCB is not finding my footprints. Why?</a></h2>
<div class="level2">
@@ -329,7 +328,7 @@
</p>
</div>
-<!-- SECTION [10786-11133] -->
+<!-- SECTION [10914-11261] -->
<h2><a name="now_that_i_have_all_of_these_footprints_where_do_i_put_them" id="now_that_i_have_all_of_these_footprints_where_do_i_put_them">Now that I have all of these footprints where do I put them?</a></h2>
<div class="level2">
@@ -345,15 +344,15 @@
To use the <strong><code>sch2pcb</code></strong> script that is listed below replace the string <strong><code>FOOTPRINT_DIR</code></strong> with your footprint directory:
</p>
<pre class="code">#!/bin/bash
-gsch2pcb ���������elements-dir FOOTPRINT_DIR $@</pre>
+gsch2pcb �������������elements-dir FOOTPRINT_DIR $@</pre>
</div>
-<!-- SECTION [11134-12011] -->
+<!-- SECTION [11262-12151] -->
<h1><a name="component_placement" id="component_placement">Component placement</a></h1>
<div class="level1">
</div>
-<!-- SECTION [12012-12046] -->
+<!-- SECTION [12152-12186] -->
<h2><a name="how_do_i_rotate_a_selection_i.e._of_more_than_one_item" id="how_do_i_rotate_a_selection_i.e._of_more_than_one_item">How do I rotate a selection (i.e. of more than one item)?</a></h2>
<div class="level2">
<ol>
@@ -368,7 +367,7 @@
</ol>
</div>
-<!-- SECTION [12047-12306] -->
+<!-- SECTION [12187-12446] -->
<h2><a name="how_do_i_change_the_size_of_a_graphical_object_such_as_text_silkscreen_lines_etc" id="how_do_i_change_the_size_of_a_graphical_object_such_as_text_silkscreen_lines_etc">How do I change the size of a graphical object (such as text, silkscreen lines, etc)?</a></h2>
<div class="level2">
<ul>
@@ -383,7 +382,7 @@
</p>
</div>
-<!-- SECTION [12307-12756] -->
+<!-- SECTION [12447-12896] -->
<h2><a name="how_do_i_put_components_on_both_faces_in_pcb" id="how_do_i_put_components_on_both_faces_in_pcb">How do I put components on both faces in PCB?</a></h2>
<div class="level2">
@@ -398,7 +397,7 @@
</ul>
</div>
-<!-- SECTION [12757-13225] -->
+<!-- SECTION [12897-13365] -->
<h2><a name="how_do_i_set_the_origin_in_pcb" id="how_do_i_set_the_origin_in_pcb">How do I set the origin in pcb?</a></h2>
<div class="level2">
@@ -407,12 +406,21 @@
</p>
</div>
-<!-- SECTION [13226-13840] -->
+<!-- SECTION [13366-13980] -->
+<h2><a name="how_do_i_measure_distances_and_dimensions_of_components" id="how_do_i_measure_distances_and_dimensions_of_components">How do I measure distances and dimensions of components?</a></h2>
+<div class="level2">
+
+<p>
+Use [<strong><code>ctrl-m</code></strong>] to set the origin and read the distance of the mouse pointer relative to this point on the upper left of the pcb window. Some objects like vias and tracks yield usefull information in object reports. Access the report of the object currently under the mouse pointer with [<strong><code>ctrl-r</code></strong>].
+</p>
+
+</div>
+<!-- SECTION [13981-14360] -->
<h1><a name="routing" id="routing">Routing</a></h1>
<div class="level1">
</div>
-<!-- SECTION [13841-13862] -->
+<!-- SECTION [14361-14382] -->
<h2><a name="how_do_i_route_a_connection_from_solder_to_component_side_and_back" id="how_do_i_route_a_connection_from_solder_to_component_side_and_back">How do I route a connection from solder to component side and back?</a></h2>
<div class="level2">
@@ -421,7 +429,7 @@
</p>
</div>
-<!-- SECTION [13863-14112] -->
+<!-- SECTION [14383-14632] -->
<h2><a name="how_do_i_change_the_routing_style" id="how_do_i_change_the_routing_style">How do I change the routing style?</a></h2>
<div class="level2">
@@ -442,7 +450,7 @@
</p>
</div>
-<!-- SECTION [14113-14845] -->
+<!-- SECTION [14633-15365] -->
<h2><a name="i_got_stuck_how_do_i_go_back" id="i_got_stuck_how_do_i_go_back">I got stuck! How do I go back?</a></h2>
<div class="level2">
@@ -451,7 +459,7 @@
</p>
</div>
-<!-- SECTION [14846-15118] -->
+<!-- SECTION [15366-15638] -->
<h2><a name="how_do_i_move_one_set_of_layer_tracks_to_another_layer" id="how_do_i_move_one_set_of_layer_tracks_to_another_layer">How do I move one set of layer tracks to another layer?</a></h2>
<div class="level2">
<ol>
@@ -464,7 +472,7 @@
</ol>
</div>
-<!-- SECTION [15119-15555] -->
+<!-- SECTION [15639-16075] -->
<h2><a name="how_do_i_change_the_soldermask_clearance_around_a_hole_via" id="how_do_i_change_the_soldermask_clearance_around_a_hole_via">How do I change the soldermask clearance around a hole/via?</a></h2>
<div class="level2">
@@ -473,7 +481,7 @@
</p>
</div>
-<!-- SECTION [15556-15831] -->
+<!-- SECTION [16076-16351] -->
<h2><a name="how_do_i_change_the_size_of_my_tracks" id="how_do_i_change_the_size_of_my_tracks">How do I change the size of my tracks?</a></h2>
<div class="level2">
@@ -490,7 +498,7 @@
</ol>
</div>
-<!-- SECTION [15832-16769] -->
+<!-- SECTION [16352-17289] -->
<h2><a name="how_do_i_drive_a_via_to_connect_a_track_to_a_ground_plane_on_a_different_layer" id="how_do_i_drive_a_via_to_connect_a_track_to_a_ground_plane_on_a_different_layer">How do I drive a via to connect a track to a ground plane on a different layer?</a></h2>
<div class="level2">
<ol>
@@ -513,7 +521,7 @@
</ol>
</div>
-<!-- SECTION [16770-17255] -->
+<!-- SECTION [17290-17775] -->
<h2><a name="i_want_to_draw_a_track_between_two_segments_on_the_same_net_but_pcb_won_t_let_me_why" id="i_want_to_draw_a_track_between_two_segments_on_the_same_net_but_pcb_won_t_let_me_why">I want to draw a track between two segments on the same net, but PCB won't let me! Why?</a></h2>
<div class="level2">
@@ -527,15 +535,17 @@
</li>
<li class="level1"><div class="li"> It is also possible that you will experience this situation when drawing tracks between pins in a connector. In this case, it is possible that your track width violates the clearance requirements of the pin field. Try decreasing the pin-to-metal clearance, or use a narrower track width.</div>
</li>
+<li class="level1"><div class="li"> Sometimes this route-blocking behaviour can come about from an error in your netlist. Don’t end refdes’s with lower case letters - they’re reserved for gates within devices. End with upper case or a digit; the lowercase letters are simply ignored.</div>
+</li>
</ul>
</div>
-<!-- SECTION [17256-18320] -->
+<!-- SECTION [17776-19094] -->
<h1><a name="beyond_tracks_and_footprints" id="beyond_tracks_and_footprints">Beyond tracks and footprints</a></h1>
<div class="level1">
</div>
-<!-- SECTION [18321-18363] -->
+<!-- SECTION [19095-19137] -->
<h2><a name="i_can_t_copy_component_pads_in_a_layout._what_gives" id="i_can_t_copy_component_pads_in_a_layout._what_gives">I can't copy component pads in a layout. What gives?</a></h2>
<div class="level2">
@@ -560,7 +570,7 @@
</p>
</div>
-<!-- SECTION [18364-19019] -->
+<!-- SECTION [19138-19793] -->
<h2><a name="how_do_i_fill_areas_with_copper" id="how_do_i_fill_areas_with_copper">How do I fill areas with copper?</a></h2>
<div class="level2">
@@ -569,7 +579,7 @@
</p>
</div>
-<!-- SECTION [19020-19267] -->
+<!-- SECTION [19794-20041] -->
<h2><a name="the_polygons_are_shorting_my_tracks_what_can_i_do_about_it" id="the_polygons_are_shorting_my_tracks_what_can_i_do_about_it">The polygons are shorting my tracks! What can I do about it?</a></h2>
<div class="level2">
@@ -578,7 +588,7 @@
</p>
</div>
-<!-- SECTION [19268-19637] -->
+<!-- SECTION [20042-20411] -->
<h2><a name="how_do_i_change_polygon_clearance" id="how_do_i_change_polygon_clearance">How do I change polygon clearance?</a></h2>
<div class="level2">
@@ -591,7 +601,7 @@
</p>
</div>
-<!-- SECTION [19638-20138] -->
+<!-- SECTION [20412-20912] -->
<h2><a name="how_do_i_hide_the_polygons_while_i_edit_the_layout" id="how_do_i_hide_the_polygons_while_i_edit_the_layout">How do I hide the polygons while I edit the layout?</a></h2>
<div class="level2">
@@ -600,7 +610,7 @@
</p>
</div>
-<!-- SECTION [20139-20547] -->
+<!-- SECTION [20913-21321] -->
<h2><a name="how_do_i_edit_polygons" id="how_do_i_edit_polygons">How do I edit polygons?</a></h2>
<div class="level2">
@@ -613,7 +623,7 @@
</p>
</div>
-<!-- SECTION [20548-21733] -->
+<!-- SECTION [21322-22507] -->
<h2><a name="how_do_i_place_vias_that_connect_to_a_polygon_for_full_thermal_dissipation_or_full_shielding_integrity" id="how_do_i_place_vias_that_connect_to_a_polygon_for_full_thermal_dissipation_or_full_shielding_integrity">How do I place vias that connect to a polygon for full thermal dissipation or full shielding integrity?</a></h2>
<div class="level2">
@@ -642,7 +652,7 @@
</p>
</div>
-<!-- SECTION [21734-23663] -->
+<!-- SECTION [22508-24437] -->
<h2><a name="can_polygons_be_un-masked_can_a_polygon_be_made_bare-copper_with_no_solder_mask" id="can_polygons_be_un-masked_can_a_polygon_be_made_bare-copper_with_no_solder_mask">Can polygons be un-masked? (Can a polygon be made bare-copper with no solder mask?)</a></h2>
<div class="level2">
@@ -651,7 +661,7 @@
</p>
</div>
-<!-- SECTION [23664-24221] -->
+<!-- SECTION [24438-24995] -->
<h2><a name="how_do_i_place_mounting_holes" id="how_do_i_place_mounting_holes">How do I place mounting holes?</a></h2>
<div class="level2">
@@ -672,7 +682,7 @@
</p>
</div>
-<!-- SECTION [24222-24886] -->
+<!-- SECTION [24996-25660] -->
<h2><a name="why_is_it_possible_to_make_a_thermal_for_pin_but_not_for_a_pad" id="why_is_it_possible_to_make_a_thermal_for_pin_but_not_for_a_pad">Why is it possible to make a thermal for pin, but not for a pad?</a></h2>
<div class="level2">
@@ -681,7 +691,7 @@
</p>
</div>
-<!-- SECTION [24887-25517] -->
+<!-- SECTION [25661-26291] -->
<h2><a name="can_pcb_be_used_to_make_single_layer_boards" id="can_pcb_be_used_to_make_single_layer_boards">Can PCB be used to make single layer boards?</a></h2>
<div class="level2">
@@ -700,7 +710,7 @@
</p>
</div>
-<!-- SECTION [25518-26315] -->
+<!-- SECTION [26292-27089] -->
<h2><a name="what_resources_exist_to_process_pcb_files_using_scripts" id="what_resources_exist_to_process_pcb_files_using_scripts">What resources exist to process PCB files using scripts?</a></h2>
<div class="level2">
@@ -717,7 +727,7 @@
</ol>
</div>
-<!-- SECTION [26316-27279] -->
+<!-- SECTION [27090-28053] -->
<h2><a name="how_do_i_import_external_vector_graphics" id="how_do_i_import_external_vector_graphics">How do I import external vector graphics?</a></h2>
<div class="level2">
@@ -730,12 +740,12 @@
</p>
</div>
-<!-- SECTION [27280-28358] -->
+<!-- SECTION [28054-29132] -->
<h1><a name="auto_router" id="auto_router">Auto Router</a></h1>
<div class="level1">
</div>
-<!-- SECTION [28359-28384] -->
+<!-- SECTION [29133-29158] -->
<h2><a name="how_do_i_force_the_autorouter_to_only_put_traces_on_a_particular_layer" id="how_do_i_force_the_autorouter_to_only_put_traces_on_a_particular_layer">How do I force the autorouter to only put traces on a particular layer?</a></h2>
<div class="level2">
@@ -744,7 +754,7 @@
</p>
</div>
-<!-- SECTION [28385-28596] -->
+<!-- SECTION [29159-29370] -->
<h2><a name="how_do_i_force_the_autorouter_to_route_only_within_my_pcb_outline" id="how_do_i_force_the_autorouter_to_route_only_within_my_pcb_outline">How do I force the autorouter to route only within my pcb outline?</a></h2>
<div class="level2">
@@ -753,7 +763,7 @@
</p>
</div>
-<!-- SECTION [28597-29028] -->
+<!-- SECTION [29371-29802] -->
<h2><a name="how_do_i_route_power_and_ground_planes_with_the_autorouter" id="how_do_i_route_power_and_ground_planes_with_the_autorouter">How do I route power and ground planes with the autorouter?</a></h2>
<div class="level2">
@@ -762,7 +772,7 @@
</p>
</div>
-<!-- SECTION [29029-29310] -->
+<!-- SECTION [29803-30084] -->
<h2><a name="the_layout_produced_by_the_autorouter_is_inefficient" id="the_layout_produced_by_the_autorouter_is_inefficient">The layout produced by the autorouter is inefficient!</a></h2>
<div class="level2">
@@ -771,7 +781,7 @@
</p>
</div>
-<!-- SECTION [29311-29491] -->
+<!-- SECTION [30085-30265] -->
<h2><a name="the_layout_produced_by_the_autorouter_is_ugly" id="the_layout_produced_by_the_autorouter_is_ugly">The layout produced by the autorouter is ugly!</a></h2>
<div class="level2">
@@ -780,12 +790,12 @@
</p>
</div>
-<!-- SECTION [29492-29617] -->
+<!-- SECTION [30266-30391] -->
<h1><a name="gerber_generation_and_file_i_o_issues" id="gerber_generation_and_file_i_o_issues">Gerber generation and file I/O issues</a></h1>
<div class="level1">
</div>
-<!-- SECTION [29618-29670] -->
+<!-- SECTION [30392-30444] -->
<h2><a name="how_do_i_make_a_board_outline_to_go_with_my_gerbers_to_the_board_maker" id="how_do_i_make_a_board_outline_to_go_with_my_gerbers_to_the_board_maker">How do I make a board outline to go with my gerbers to the board maker?</a></h2>
<div class="level2">
@@ -810,7 +820,7 @@
)</pre>
</div>
-<!-- SECTION [29671-30517] -->
+<!-- SECTION [30445-31291] -->
<h2><a name="i_m_done_with_my_layout._how_should_i_check_my_design" id="i_m_done_with_my_layout._how_should_i_check_my_design">I'm done with my layout. How should I check my design?</a></h2>
<div class="level2">
@@ -839,7 +849,7 @@
</ul>
</div>
-<!-- SECTION [30518-32494] -->
+<!-- SECTION [31292-33268] -->
<h1><a name="you_didn_t_answer_my_question._what_other_resources_exist_for_pcb_information" id="you_didn_t_answer_my_question._what_other_resources_exist_for_pcb_information">You didn't answer my question. What other resources exist for PCB information?</a></h1>
<div class="level1">
@@ -854,6 +864,6 @@
</p>
</div>
-<!-- SECTION [32495-] --></div>
+<!-- SECTION [33269-] --></div>
</body>
</html>
1.2 +1 -1 eda/geda/gaf/docs/wiki/geda_scg.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: geda_scg.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/geda_scg.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- geda_scg.html 22 Aug 2006 02:56:12 -0000 1.1
+++ geda_scg.html 7 Sep 2006 01:58:26 -0000 1.2
@@ -13,7 +13,7 @@
<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/geda:scg?do=export_xhtml"; />
<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/geda:scg?do=export_raw"; />
<meta name="date" content="2006-08-21T21:15:35-0400" />
- <meta name="robots" content="noindex,nofollow" />
+ <meta name="robots" content="index,follow" />
<link rel="stylesheet" media="screen" type="text/css" href="lib/exe/css" />
<link rel="stylesheet" media="print" type="text/css" href="lib/exe/001css" />
</head>
1.2 +1 -1 eda/geda/gaf/docs/wiki/geda_style_guide.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: geda_style_guide.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/geda_style_guide.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- geda_style_guide.html 22 Aug 2006 02:56:12 -0000 1.1
+++ geda_style_guide.html 7 Sep 2006 01:58:26 -0000 1.2
@@ -13,7 +13,7 @@
<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/geda:style_guide?do=export_xhtml"; />
<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/geda:style_guide?do=export_raw"; />
<meta name="date" content="2006-08-17T02:00:16-0400" />
- <meta name="robots" content="noindex,nofollow" />
+ <meta name="robots" content="index,follow" />
<link rel="stylesheet" media="screen" type="text/css" href="lib/exe/css" />
<link rel="stylesheet" media="print" type="text/css" href="lib/exe/001css" />
</head>
1.2 +0 -0 eda/geda/gaf/docs/wiki/geda_wcalc_readme.html
(In the diff below, changes in quantity of whitespace are not shown.)
Index: geda_wcalc_readme.html
===================================================================
RCS file: /home/cvspsrv/cvsroot/eda/geda/gaf/docs/wiki/geda_wcalc_readme.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- geda_wcalc_readme.html 22 Aug 2006 02:56:12 -0000 1.1
+++ geda_wcalc_readme.html 7 Sep 2006 01:58:26 -0000 1.2
@@ -22,7 +22,7 @@
<h1><a name="wcalc_readme" id="wcalc_readme">Wcalc README</a></h1>
<div class="level1">
-<pre class="code">$Id: geda_wcalc_readme.html,v 1.1 2006/08/22 02:56:12 ahvezda Exp $
+<pre class="code">$Id: geda_wcalc_readme.html,v 1.2 2006/09/07 01:58:26 ahvezda 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
_______________________________________________
geda-cvs mailing list
geda-cvs@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-cvs