[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
gEDA-cvs: CVS update: 001geda_tragesym_tutorial.html
User: ahvezda
Date: 07/02/12 21:26:14
Added: . 001geda_tragesym_tutorial.html geda_devel-tips.html
geda_fedora_rpm_installation.html
geda_gedasuite_installation.html
geda_glossaire.html geda_suse_rpm_installation.html
Log:
Added new wiki content (Makefiles not updated yet)
Revision Changes Path
1.1 eda/geda/gaf/docs/wiki/001geda_tragesym_tutorial.html
Index: 001geda_tragesym_tutorial.html
===================================================================
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en"
lang="en" dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>geda:tragesym_tutorial.fr</title>
<meta name="generator" content="DokuWiki Release 2006-03-09" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
<link rel="contents" href="http://geda.seul.org/wiki/geda:tragesym_tutorial.fr?do=index"; title="" />
<link rel="alternate" type="application/rss+xml" title="Recent Changes" href="http://geda.seul.org/wiki/feed.php"; />
<link rel="alternate" type="application/rss+xml" title="Current Namespace" href="http://geda.seul.org/wiki/feed.php?mode=list&ns=geda"; />
<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/geda:tragesym_tutorial.fr?do=export_xhtml"; />
<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/geda:tragesym_tutorial.fr?do=export_raw"; />
<meta name="date" content="2006-12-05T11:32:26-0500" />
<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>
<body>
<div class="dokuwiki export">
<div class="toc">
<div class="tocheader toctoggle" id="toc__header">Table of Contents</div>
<div id="toc__inside">
<ul class="toc">
<li class="level1"><div class="li"><span class="li"><a href="#creer_des_symboles_gschem_rapidement_et_facilement_en_utilisant_tragesym_et_un_tableur" class="toc">Créer des symboles gschem rapidement et facilement en utilisant tragesym et un tableur</a></span></div>
<ul class="toc">
<li class="level2"><div class="li"><span class="li"><a href="#etapes_necessaires" class="toc">�tapes nécessaires</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#etape_1ouvrir_un_fichier_de_formulaire_tragesym" class="toc">Ã?tape 1: Ouvrir un fichier de formulaire tragesym</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#etape_2telecharger_le_fichier_technique_du_composant_et_trouver_la_liste_des_broches" class="toc">�tape 2: Télécharger le fichier technique du composant et trouver la liste des broches</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#etape_3copier_la_liste_des_broches_dans_un_editeur_et_la_preparer" class="toc">�tape 3: Copier la liste des broches dans un éditeur et la préparer</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#etape_4inserer_toutes_les_donnees_manquantes_dans_la_feuille_de_calcul" class="toc">�tape 4: Insérer toutes les données manquantes dans la feuille de calcul</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#etape_5exporter_la_feuille_de_calcul_dans_un_fichier_texte_avec_separation_par_tabulation" class="toc">�tape 5: Exporter la feuille de calcul dans un fichier texte avec séparation par tabulation</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#etape_6lancer_tragesym_et_creer_le_symbole" class="toc">�tape 6: Lancer tragesym et créer le symbole</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#etape_7controler_le_resultat_avec_gschem_et_peaufiner_le_symbole" class="toc">�tape 7: Contrôler le résultat avec gschem et peaufiner le symbole</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#conclusion" class="toc">Conclusion</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#credits" class="toc">Crédits</a></span></div></li></ul>
</li></ul>
</div>
</div>
<h1><a name="creer_des_symboles_gschem_rapidement_et_facilement_en_utilisant_tragesym_et_un_tableur" id="creer_des_symboles_gschem_rapidement_et_facilement_en_utilisant_tragesym_et_un_tableur">Créer des symboles gschem rapidement et facilement en utilisant tragesym et un tableur</a></h1>
<div class="level1">
<p>
La création de symboles pour le dessin de schémas peut prendre beaucoup de temps, générer beaucoup d’erreurs et de frustrations. Heureusement, gschem utilise un format de fichier texte ouvert qui est très facile à utiliser avec des scripts. Ce tutoriel succint décrit comment utiliser tragesym, un outil extérieur, pour créer des symboles très rapidement (probablement plus rapidement qu’avec tout paquet commercial).
</p>
</div>
<!-- SECTION [1-532] -->
<h2><a name="etapes_necessaires" id="etapes_necessaires">�tapes nécessaires</a></h2>
<div class="level2">
<ul>
<li class="level1"><div class="li"> Ã?tape 1: Ouvrir un fichier de formulaire tragesym</div>
</li>
<li class="level1"><div class="li"> �tape 2: Télécharger le fichier technique du composant et trouver la liste des broches</div>
</li>
<li class="level1"><div class="li"> �tape 3: Copier la liste des broches dans un éditeur et la préparer</div>
</li>
<li class="level1"><div class="li"> �tape 4: Insérer toutes les données manquantes dans la feuille de calcul</div>
</li>
<li class="level1"><div class="li"> �tape 5: Exporter la feuille de calcul dans un fichier texte avec séparation par tabulation</div>
</li>
<li class="level1"><div class="li"> �tape 6: Lancer tragesym et créer le symbole</div>
</li>
<li class="level1"><div class="li"> �tape 7: Contrôler le résultat avec gschem et peaufiner le symbole</div>
</li>
</ul>
</div>
<!-- SECTION [533-1094] -->
<h2><a name="etape_1ouvrir_un_fichier_de_formulaire_tragesym" id="etape_1ouvrir_un_fichier_de_formulaire_tragesym">Ã?tape 1: Ouvrir un fichier de formulaire tragesym</a></h2>
<div class="level2">
<p>
tragesym est fourni avec deux fichiers de formulaires. L’un est en <a href="_media/001tragesym_template.txt" class="media mediafile mf_txt" title="tragesym:template.txt">texte ASCII</a>, le second est une <a href="_media/001tragesym_template" class="media mediafile mf_ods" title="tragesym:template.ods">feuille de calcul OpenOffice</a>. Vous pouvez aussi les obtenir depuis le paquet d’utilitaires gEDA (utils/examples/tragesym/template.src et utils/examples/tragesym/template.ods). Si vous préférez un tableur différent, comme gnumeric ou kspread, créez simplement votre propre fichier formulaire texte à partir de celui qui est fourni. La seule différence entre les formulaires texte et calcul est la syntaxe des valeurs dans les sections [options] et [geda_attr]. Le fichier texte les sépare avec un signe (clé=valeur), la feuille de calcul obtient la valeur dans la seconde colonne (qui devient une tabulation après avoir été exportée).
</p>
</div>
<!-- SECTION [1095-1958] -->
<h2><a name="etape_2telecharger_le_fichier_technique_du_composant_et_trouver_la_liste_des_broches" id="etape_2telecharger_le_fichier_technique_du_composant_et_trouver_la_liste_des_broches">�tape 2: Télécharger le fichier technique du composant et trouver la liste des broches</a></h2>
<div class="level2">
<p>
Pour cet exemple, nous allons créer un symbole avec les ports IO du PCA9555 16-bit IIC IO de Philips Semiconductor. La description du produit et la fiche technique sont disponibles sur Philips : [<a href="http://www-us.semiconductors.philips.com/cgi-bin/pldb/pip/pca9555.html"; class="urlextern" title="http://www-us.semiconductors.philips.com/cgi-bin/pldb/pip/pca9555.html"; rel="nofollow">http://www-us.semiconductors.philips.com/cgi-bin/pldb/pip/pca9555.html</a>]. Téléchargez la fiche technique et ouvrez-la avec un visualiseur pdf qui permet la copie du texte à l’extérieur du <acronym title="Portable Document Format">PDF</acronym>, tel que xpdf (téléchargeable sur [<a href="http://www.foolabs.com/xpdf/home.html"; class="urlextern" title="http://www.foolabs.com/xpdf/home.html"; rel="nofollow">http://www.foolabs.com/xpdf/home.html</a>]). Passez les pages jusqu’à ce que vous ayez trouvé le brochage ou le composant·:
</p>
<p>
<a href="_detail/001tragesym_kpdf_pinconfiguration.html" class="media" title="tragesym:kpdf_pinconfiguration.png"><img src="http://geda.seul.org/wiki/_media/tragesym:kpdf_pinconfiguration.png?w=&h=&cache=cache"; class="media" alt="" /></a> <a href="_detail/001tragesym_acroread_selectiontable.html" class="media" title="tragesym:acroread_selectiontable.png"><img src="http://geda.seul.org/wiki/_media/tragesym:acroread_selectiontable.png?w=&h=&cache=cache"; class="media" alt="" /></a>
</p>
<p>
Dans la feuille de calcul, la liste des broches peut être seulement présente dans le dessin du boîtier. S’il existe une belle table, comme dans la second image, d’un autre fichie technique, utilisez-la.
</p>
</div>
<!-- SECTION [1959-2906] -->
<h2><a name="etape_3copier_la_liste_des_broches_dans_un_editeur_et_la_preparer" id="etape_3copier_la_liste_des_broches_dans_un_editeur_et_la_preparer">�tape 3: Copier la liste des broches dans un éditeur et la préparer</a></h2>
<div class="level2">
<p>
Sélectionnez la liste des broches et copiez-la dans un éditeur de texte. C’est une étape intermédiaire nécessaire car votre tableur a besoin de champs séparateurs spéciaux, comme les virgules ou les tabulations. Vous pouvez avoir à enlever les séparateurs en double ou de les remplacer avec des tabulations.
</p>
<p>
<strong>Note:</strong> Le comportement lors de la sélection de kpdf est différent de celui de acroread. kpdf semble vous donner une copie qui ressemble plus à une présentation graphique, alors que acroread fournit une sortie qui est plus «·orientée fichier·». Si vous devez créer beaucoup de symboles, testez les deux et comparez les résultats (NdT: xpdf semble fonctionner très bien au 04/12/2006 et reste très léger).
</p>
<p>
<a href="_detail/001tragesym_xemacs_rawselection.html" class="media" title="tragesym:xemacs_rawselection.png"><img src="http://geda.seul.org/wiki/_media/tragesym:xemacs_rawselection.png?w=&h=&cache=cache"; class="media" alt="" /></a> <a href="_detail/001tragesym_xemacs_modifiedselection.html" class="media" title="tragesym:xemacs_modifiedselection.png"><img src="http://geda.seul.org/wiki/_media/tragesym:xemacs_modifiedselection.png?w=&h=&cache=cache"; class="media" alt="" /></a> <a href="_detail/001tragesym_ooo_selection.html" class="media" title="tragesym:ooo_selection.png"><img src="http://geda.seul.org/wiki/_media/tragesym:ooo_selection.png?w=&h=&cache=cache"; class="media" alt="" /></a>
</p>
<p>
L’image ci-dessus illustre les étapes·:
</p>
<ul>
<li class="level1"><div class="li"> insérez la sélection depuis votre visualiseur pdf vers un éditeur de texte</div>
</li>
<li class="level1"><div class="li"> modifiez la liste des broches pour rendre votre tableur heureux </div>
<ul>
<li class="level2"><div class="li"> coupez la liste de 24 à 13 avec la sélection rectangulaire</div>
</li>
<li class="level2"><div class="li"> insérez la sélection rectangulaire sous les broches 1 à 12</div>
</li>
<li class="level2"><div class="li"> triez les lignes (xemacs peut le faire <img src="http://geda.seul.org/wiki/lib/images/smileys/icon_wink.gif"; class="middle" alt=";-)" />)</div>
</li>
<li class="level2"><div class="li"> enlevez ou réparez les lignes avec les numéros 2,3,... Ils ne sont pas sur la même ligne. Vous pouvez facilement recréer les numéros de broche plus tard</div>
</li>
<li class="level2"><div class="li"> remplacez les espaces avec des tabulations (pas réellement nécessaire en utilisant OpenOffice)</div>
</li>
</ul>
</li>
<li class="level1"><div class="li"> copiez les données modifiées dans le formulaire feuille de calcul quelque part en dessous</div>
</li>
</ul>
</div>
<!-- SECTION [2907-4587] -->
<h2><a name="etape_4inserer_toutes_les_donnees_manquantes_dans_la_feuille_de_calcul" id="etape_4inserer_toutes_les_donnees_manquantes_dans_la_feuille_de_calcul">�tape 4: Insérer toutes les données manquantes dans la feuille de calcul</a></h2>
<div class="level2">
<p>
Déplacez maintenant les étiquettes et les numéros de broches dans leurs colonnes respectives. Vous pouvez aussi utiliser la fonctionnalité d’autoremplissage de votre tableur pour créer les numéros de broche.
</p>
<p>
<a href="_detail/001tragesym_ooo_rearanged.html" class="media" title="tragesym:ooo_rearanged.png"><img src="http://geda.seul.org/wiki/_media/tragesym:ooo_rearanged.png?w=&h=&cache=cache"; class="media" alt="" /></a>
</p>
<p>
Remplissez les colonens de type, de style et de position aux valeurs les plus habituelles. Vous pouvez à nouveau utiliser la fonctionnalité d’autoremplissage Maintenant vous allez changer quelques unes de ces valeurs. Jetez un coup d’oeil sur le tableau descriptif de la fiche technique:
</p>
<p>
<a href="_detail/001tragesym_kpdf_pindescription.html" class="media" title="tragesym:kpdf_pindescription.png"><img src="http://geda.seul.org/wiki/_media/tragesym:kpdf_pindescription.png?w=&h=&cache=cache"; class="media" alt="" /></a>
</p>
<p>
Selon ce tableau, nous changeons les éléments suivants (voir le résultat ci-dessus):
</p>
<ul>
<li class="level1"><div class="li"> La broche 1 est une sortie, nous voudrions avoir un rond d’inversion (NdT: trad à revoir) et une barre de négation</div>
</li>
<li class="level1"><div class="li"> A1 à A3 sont des entrées, nous changeons le type et les déplaçons sur le côté gauche</div>
</li>
<li class="level1"><div class="li"> mettez le type de SCL en entrée et déplacez aussi SCL et SDA sur le côté gauche </div>
</li>
<li class="level1"><div class="li"> changez le type des broches d’alimentations VSS et VDD et ajoutez des noms de net. Nous utilisons les habituels GND et Vcc.</div>
</li>
</ul>
<p>
<strong>Note:</strong> Si une de vos étiquettes contient un backslash «·\·», vous devez le remplacer par sa séquence d’échapement «·\\·».
</p>
<p>
<a href="_detail/001tragesym_ooo_changedpins.html" class="media" title="tragesym:ooo_changedpins.png"><img src="http://geda.seul.org/wiki/_media/tragesym:ooo_changedpins.png?w=&h=&cache=cache"; class="media" alt="" /></a>
</p>
<p>
Avant de configurer les attributs et les options aux valeurs appropriées.
</p>
<p>
<a href="_detail/001tragesym_ooo_attributes.html" class="media" title="tragesym:ooo_attributes.png"><img src="http://geda.seul.org/wiki/_media/tragesym:ooo_attributes.png?w=&h=&cache=cache"; class="media" alt="" /></a>
</p>
</div>
<!-- SECTION [4588-6061] -->
<h2><a name="etape_5exporter_la_feuille_de_calcul_dans_un_fichier_texte_avec_separation_par_tabulation" id="etape_5exporter_la_feuille_de_calcul_dans_un_fichier_texte_avec_separation_par_tabulation">�tape 5: Exporter la feuille de calcul dans un fichier texte avec séparation par tabulation</a></h2>
<div class="level2">
<p>
Vous pouvez soit utiliser le fonction export de votre tableur pour créer un fichier texte délimité par des tabulations ou simplement sélectionner le tableau et copier son contenu dans votre éditeur de texte et sauvegarder le fichier.
</p>
</div>
<!-- SECTION [6062-6409] -->
<h2><a name="etape_6lancer_tragesym_et_creer_le_symbole" id="etape_6lancer_tragesym_et_creer_le_symbole">�tape 6: Lancer tragesym et créer le symbole</a></h2>
<div class="level2">
<p>
Utilisez un shell et exécutez tragesym:
</p>
<p>
<code>werner@werner-amd64:~/Desktop/tragesym_tutorial> tragesym pca555.src pca555.sch</code>
</p>
<p>
Si tragesym indique qu’il y a une erreur, faites quelques changements dans la feuille de calcul et exportez à nouveau le fichier ou éditez simplement le fichier exporté.
</p>
</div>
<!-- SECTION [6410-6771] -->
<h2><a name="etape_7controler_le_resultat_avec_gschem_et_peaufiner_le_symbole" id="etape_7controler_le_resultat_avec_gschem_et_peaufiner_le_symbole">�tape 7: Contrôler le résultat avec gschem et peaufiner le symbole</a></h2>
<div class="level2">
<p>
Ouvrez maintenant le symbole généré avec et contrôlez le résultat
</p>
<p>
<code>werner@werner-amd64:~/Desktop/tragesym_tutorial> gschem pca555.sch</code>
</p>
<p>
En validant le texte caché («·en·», Edit→Show/Hide Inv Text), vous pouvez voir le symbole généré en entier. Il n’est pas réellement nécessaire de changer quoi que ce soit mais cela peut améliorer l’aspect du symbole si vous réarrangez un peu les broches.
</p>
<p>
<a href="_detail/001tragesym_gschem_showhidden.html" class="media" title="tragesym:gschem_showhidden.png"><img src="http://geda.seul.org/wiki/_media/tragesym:gschem_showhidden.png?w=&h=&cache=cache"; class="media" alt="" /></a> <a href="_detail/001tragesym_gschem_finished.html" class="media" title="tragesym:gschem_finished.png"><img src="http://geda.seul.org/wiki/_media/tragesym:gschem_finished.png?w=&h=&cache=cache"; class="media" alt="" /></a>
</p>
<p>
Nous avons maintenant un symbole complet. Vous pouvez le copier dans votre bibliothèque locale de symboles, e.g. /usr/local/share/gEDA/sym/local/ et l’utiliser.
</p>
</div>
<!-- SECTION [6772-7503] -->
<h2><a name="conclusion" id="conclusion">Conclusion</a></h2>
<div class="level2">
<p>
C’était un exemple simple avec peu de broches mais cela est d’autant plus rentable lorsque vous en avez beaucoup (ie, bga-272, tfqp-100, etc.).
</p>
</div>
<!-- SECTION [7504-7673] -->
<h2><a name="credits" id="credits">Crédits</a></h2>
<div class="level2">
<p>
De grands remerciements à <Russ.Dill(AT)asu.edu>, qui a écrti la première version de ce tutoriel. Vous pouvez trouver ce tutoriel sur <a href="http://www.geda.seul.org/docs/current/tutorials/tragesym/tragesym.html"; class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/tragesym/tragesym.html"; rel="nofollow">http://www.geda.seul.org/docs/current/tutorials/tragesym/tragesym.html</a> (version anglaise)
</p>
<p>
NdT·: si vous voulez la version française: <a href="http://www.iznogood-factory.org/pub/gEDA/symboles.html"; class="urlextern" title="http://www.iznogood-factory.org/pub/gEDA/symboles.html"; rel="nofollow">http://www.iznogood-factory.org/pub/gEDA/symboles.html</a>
</p>
</div>
<!-- SECTION [7674-] --></div>
</body>
</html>
1.1 eda/geda/gaf/docs/wiki/geda_devel-tips.html
Index: geda_devel-tips.html
===================================================================
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en"
lang="en" dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>geda:devel-tips</title>
<meta name="generator" content="DokuWiki Release 2006-03-09" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
<link rel="contents" href="http://geda.seul.org/wiki/geda:devel-tips?do=index"; title="" />
<link rel="alternate" type="application/rss+xml" title="Recent Changes" href="http://geda.seul.org/wiki/feed.php"; />
<link rel="alternate" type="application/rss+xml" title="Current Namespace" href="http://geda.seul.org/wiki/feed.php?mode=list&ns=geda"; />
<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/geda:devel-tips?do=export_xhtml"; />
<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/geda:devel-tips?do=export_raw"; />
<meta name="date" content="2007-02-11T05:48:13-0500" />
<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>
<body>
<div class="dokuwiki export">
<div class="toc">
<div class="tocheader toctoggle" id="toc__header">Table of Contents</div>
<div id="toc__inside">
<ul class="toc">
<li class="level1"><div class="li"><span class="li"><a href="#geda_developer_tips_tricks_and_hints" class="toc">gEDA Developer Tips, tricks and hints</a></span></div>
<ul class="toc">
<li class="level2"><div class="li"><span class="li"><a href="#how_to_branch_correctly_using_cvs" class="toc">How to branch correctly using CVS</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#doxygen_comments_and_styles" class="toc">Doxygen Comments and styles</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#dialogsdesign_and_behaviour" class="toc">Dialogs: Design and Behaviour</a></span></div>
<ul class="toc">
<li class="level3"><div class="li"><span class="li"><a href="#dialog_design" class="toc">Dialog Design</a></span></div></li>
<li class="level3"><div class="li"><span class="li"><a href="#modal_or_nonmodal_dialogs" class="toc">Modal or Nonmodal dialogs</a></span></div></li>
<li class="level3"><div class="li"><span class="li"><a href="#where_to_place_the_dialog" class="toc">Where to place the dialog</a></span></div></li>
<li class="level3"><div class="li"><span class="li"><a href="#placing_dialogs_in_front_of_their_parent_window" class="toc">Placing dialogs in front of their parent window</a></span></div></li>
<li class="level3"><div class="li"><span class="li"><a href="#dialog_design_of_the_current_dialogs" class="toc">Dialog design of the current dialogs</a></span></div></li>
<li class="level3"><div class="li"><span class="li"><a href="#source_template_for_simple_dialogs" class="toc">Source template for simple dialogs</a></span></div></li>
<li class="level3"><div class="li"><span class="li"><a href="#current_dialog_issues_in_gschem" class="toc">Current Dialog Issues in Gschem</a></span></div></li></ul>
</li></ul>
</li></ul>
</div>
</div>
<h1><a name="geda_developer_tips_tricks_and_hints" id="geda_developer_tips_tricks_and_hints">gEDA Developer Tips, tricks and hints</a></h1>
<div class="level1">
</div>
<!-- SECTION [1-53] -->
<h2><a name="how_to_branch_correctly_using_cvs" id="how_to_branch_correctly_using_cvs">How to branch correctly using CVS</a></h2>
<div class="level2">
<p>
Here’s a summary of what should happen with development on a branch that is intended to later be merged to the trunk. Suppose the branch is called “mine”.
</p>
<p>
1) tag the repository (trunk) to create a branch point tag:
</p>
<pre class="code"> cvs tag mine-base </pre>
<p>
2) branch
</p>
<pre class="code"> cvs tag -b -r mine-base mine</pre>
<p>
What step #1 does is to keep track of where the “mine” branch started <br/>
from. The “-r mine-base” in step #2 says to create the branch starting <br/>
from the tag “mine-base”. It is important to do this because you need<br/>
to be able to know where each file is rooted (i.e., what version in the <br/>
trunk it is derived from).
</p>
<p>
Usually, it is a good idea to periodically merge changes which have taken <br/>
place on the trunk to the branch. This will reduce the amount of work when <br/>
the work on the branch is ready to go back to the trunk.
</p>
<p>
# go to where the trunk is checked out and update it
</p>
<pre class="code"> cd /to/my/trunk/sources
cvs update -PdA</pre>
<p>
# create a temporary tag in case someone commits stuff while you’re<br/>
# in the middle of this procedure. This keeps you from losing anything.
</p>
<pre class="code"> cvs tag merge-mine</pre>
<p>
# go to your branch source tree
</p>
<pre class="code">
cd /to/my/branch/sources
cvs update -Pd</pre>
<p>
# the following says to apply the changes that have taken place on<br/>
# the trunk between the version tagged with “mine-base” and “merge-mine”<br/>
# to your branch source tree
</p>
<pre class="code"> cvs update -j mine-base -j merge-mine -dP</pre>
<p>
# if all goes well, you’ll have no conflicts. It is not uncommon <br/>
# for there to be some cases where you have to resolve conflicts by<br/>
# hand. In this case the affected files will have a special comment<br/>
# showing what your file on the branch had and what the file tagged as<br/>
# merge-mine had. You, as the programmer, have to figure out what is<br/>
# correct. Once this is all done, proceed.<br/>
</p>
<p>
# checkin with a message like “sync with trunk” or<br/>
# “pull up revs #### from the trunk” (if you were pulling up<br/>
# a specific change).
</p>
<pre class="code"> cvs ci</pre>
<p>
# Now we move the branch point tag to the temporary merge tag<br/>
# This is because we have changed what rev each file in the branch<br/>
# is based on in the trunk. This is known as re-rooting.
</p>
<pre class="code"> cvs tag -F -r merge-mine mine-base</pre>
<p>
# now we don’t need the temporary merge tag anymore so remove it
</p>
<pre class="code"> cvs tag -d merge-mine</pre>
<p>
When it is time to merge changes that have taken place on a branch back<br/>
to the trunk (usually marking the end of that branch), first do a final <br/>
trunk → branch merge as mentioned above. Then do a branch → trunk merge.
</p>
<p>
Now for a branch to trunk merge you’d do
</p>
<pre class="code"> cd /to/my/trunk/sources
cvs update -PdA
cvs update -j mine-base -j mine -dP</pre>
<p>
# resolve conflicts
</p>
<pre class="code"> cvs ci
cvs tag -F mine-base</pre>
<p>
This takes any changes between “mine-base” and “mine” and tries to apply <br/>
it to the trunk. If it all goes cleanly, you just check it in otherwise you <br/>
have to resolve conflicts. Then you move the branch point tag because the trunk<br/>
now reflects the lastest in the branch.
</p>
<p>
The above was contributed by Dan McMahill
</p>
</div>
<!-- SECTION [54-3116] -->
<h2><a name="doxygen_comments_and_styles" id="doxygen_comments_and_styles">Doxygen Comments and styles</a></h2>
<div class="level2">
<p>
Any volunteer for writing some notes?
</p>
<ul>
<li class="level1"><div class="li"> which keywords to use</div>
</li>
<li class="level1"><div class="li"> a template for a function</div>
</li>
<li class="level1"><div class="li"> a template for structs?</div>
</li>
<li class="level1"><div class="li"> bug, todo and fixme tags</div>
</li>
</ul>
</div>
<!-- SECTION [3117-3310] -->
<h2><a name="dialogsdesign_and_behaviour" id="dialogsdesign_and_behaviour">Dialogs: Design and Behaviour</a></h2>
<div class="level2">
</div>
<!-- SECTION [3311-3353] -->
<h3><a name="dialog_design" id="dialog_design">Dialog Design</a></h3>
<div class="level3">
<p>
There’s a nice document from the gnome guys called <a href="http://developer.gnome.org/projects/gup/hig/2.0/"; class="urlextern" title="http://developer.gnome.org/projects/gup/hig/2.0/"; rel="nofollow"> Gnome HIG</a>. There are several suggestions on how to design dialogs and how they should behave.
</p>
<p>
<strong> The dialog design is mostly a matter of taste:</strong>
</p>
<ul>
<li class="level1"><div class="li"> alignment of elements. See <a href="http://developer.gnome.org/projects/gup/hig/2.0/design-window.html"; class="urlextern" title="http://developer.gnome.org/projects/gup/hig/2.0/design-window.html"; rel="nofollow"> Window Layout</a></div>
</li>
<li class="level1"><div class="li"> right alignment of dialog buttons</div>
</li>
<li class="level1"><div class="li"> some spacing around the dialog (but how much?)</div>
</li>
<li class="level1"><div class="li"> some spacing between the elements (vertical and horizontal)</div>
</li>
<li class="level1"><div class="li"> option groups with frames or indentation?</div>
</li>
<li class="level1"><div class="li"> frame labels or bold headlines?</div>
</li>
</ul>
<p>
<strong>Misc:</strong>
</p>
<ul>
<li class="level1"><div class="li"> with a <a href="http://www.chipx86.com/wiki/Libsexy#SexyIconEntry"; class="urlextern" title="http://www.chipx86.com/wiki/Libsexy#SexyIconEntry"; rel="nofollow"> libsexy widget</a> it would be possible to place an icon inside the text entry this would be usefull for some dialogs: </div>
<ul>
<li class="level3"><div class="li"> the filter entry in the component select dialog</div>
</li>
<li class="level3"><div class="li"> the file select in the print dialog</div>
</li>
<li class="level3"><div class="li"> the file select in the export png dialog</div>
</li>
</ul>
</li>
</ul>
</div>
<!-- SECTION [3354-4328] -->
<h3><a name="modal_or_nonmodal_dialogs" id="modal_or_nonmodal_dialogs">Modal or Nonmodal dialogs</a></h3>
<div class="level3">
<p>
A modal dialog is required whenever the main application provides data for the dialog.
</p>
<pre class="code">Example:
The dialog is called with a selection list and the dialog only should operate on this selection.</pre>
<p>
A modal dialog is OK too, if the dialog is only called very seldom. The file open dialog could be nonmodal because it does not require any input from the application.
</p>
<p>
A modal dialog is not OK if there is a lot of user interaction with the dialog. The component selection is a good example.
</p>
</div>
<!-- SECTION [4329-4859] -->
<h3><a name="where_to_place_the_dialog" id="where_to_place_the_dialog">Where to place the dialog</a></h3>
<div class="level3">
<p>
A dialog can be put on different places in on the screen. A list of possible places can be found in the <a href="http://developer.gnome.org/doc/API/2.0/gtk/gtk-Standard-Enumerations.html#GtkWindowPosition"; class="urlextern" title="http://developer.gnome.org/doc/API/2.0/gtk/gtk-Standard-Enumerations.html#GtkWindowPosition"; rel="nofollow"> GtkReference</a>
</p>
<p>
The current dialogs are placed either on the mouse position (GTK_WIN_POS_MOUSE) or at no preset position (GTK_WIN_POS_NONE). The Gnome HID does not say anything about that topic.
</p>
<p>
The default setting is GTK_WIN_POS_NONE for GtkWindow see <a href="http://developer.gnome.org/doc/API/2.0/gtk/GtkWindow.html#GtkWindow--window-position"; class="urlextern" title="http://developer.gnome.org/doc/API/2.0/gtk/GtkWindow.html#GtkWindow--window-position"; rel="nofollow"> GtkWindow</a>. The default for GtkDialog is GTK_WIN_POS_CENTER_ON_PARENT (<a href="http://cvs.gnome.org/viewcvs/gtk%2B/gtk/gtkdialog.c"; class="urlextern" title="http://cvs.gnome.org/viewcvs/gtk%2B/gtk/gtkdialog.c"; rel="nofollow"> taken from the GtkDialog source</a>).
</p>
</div>
<!-- SECTION [4860-5604] -->
<h3><a name="placing_dialogs_in_front_of_their_parent_window" id="placing_dialogs_in_front_of_their_parent_window">Placing dialogs in front of their parent window</a></h3>
<div class="level3">
<p>
Most of the dialogs are placed in front of their parent window using the transient_for property (see. <a href="http://developer.gnome.org/doc/API/2.0/gtk/GtkWindow.html#gtk-window-set-transient-for"; class="urlextern" title="http://developer.gnome.org/doc/API/2.0/gtk/GtkWindow.html#gtk-window-set-transient-for"; rel="nofollow"> GtkReference</a>). This property should be set for all modal dialogs.
</p>
<p>
For nonmodal dialogs the setting of transient_for property is not obvious. While in gschem for example the coord dialog should stay above the parent window, the log window does not need to stay in front of it.
</p>
<p>
<strong>Note:</strong> There is an older mechanism that keeps the the dialogs in front of gschem. If the <em>raise-dialog-boxes-on-expose</em> variable is set to <em>enable</em> in one of gschem’s configuration files, it may cause problems with some window managers. If dialogs are flickering at 100% CPU load, then disable that setting.
</p>
<pre class="code lisp"><span class="co1">; raise-dialog-boxes-on-expose string</span>
<span class="co1">;</span>
<span class="co1">; Controls if dialog boxes are raised whenever an expose event happens</span>
<span class="co1">; Default is enabled</span>
<span class="co1">;</span>
<span class="co1">;(raise-dialog-boxes-on-expose "enabled")</span>
<span class="br0">(</span>raise-dialog-boxes-on-expose <span class="st0">"disabled"</span><span class="br0">)</span></pre>
</div>
<!-- SECTION [5605-6690] -->
<h3><a name="dialog_design_of_the_current_dialogs" id="dialog_design_of_the_current_dialogs">Dialog design of the current dialogs</a></h3>
<div class="level3">
<p>
<a href="_detail/devel_tips_dialog_picture.html" class="media" title="devel_tips:dialog_picture.png"><img src="_media/devel_tips_dialog_picture.png" class="media" alt="" /></a>
</p>
<ul>
<li class="level1"><div class="li"> There is some space around the whole dialog (<em>DIALOG_BORDER_SPACING</em>). </div>
</li>
<li class="level1"><div class="li"> Some indentation to show the topic group (<em>DIALOG_INDENTATION</em>) below it’s bold headline.</div>
</li>
<li class="level1"><div class="li"> The vertikal and the horizontal separation is done with <em>DIALOG_H_SPACING</em> and <em>DIALOG_V_SPACING</em>.</div>
</li>
</ul>
</div>
<!-- SECTION [6691-7055] -->
<h3><a name="source_template_for_simple_dialogs" id="source_template_for_simple_dialogs">Source template for simple dialogs</a></h3>
<div class="level3">
<p>
This template is not intented to compile, but you can easily copy the code block that you need.
</p>
<pre class="code c"><span class="kw4">void</span> dialog <span class="br0">(</span>TOPLEVEL *w_current<span class="br0">)</span>
<span class="br0">{</span>
GtkWidget *vbox, *label, *alignment, *table;
GtkWidget *dialog;
<span class="coMULTI">/* only create the dialog if it is not there yet. This usually is a
widget pointer in the w_current structure:
dialog = w_current->tewindow */</span>
<span class="kw1">if</span> <span class="br0">(</span>!dialog<span class="br0">)</span> <span class="br0">{</span>
dialog = gtk_dialog_new_with_buttons<span class="br0">(</span>_<span class="br0">(</span><span class="st0">"Dialog title"</span><span class="br0">)</span>,
<span class="coMULTI">/* the parent window or NULL */</span>
GTK_WINDOW<span class="br0">(</span>w_current->main_window<span class="br0">)</span>,
<span class="coMULTI">/* dialog properties */</span>
GTK_DIALOG_MODAL, <span class="coMULTI">/* 0 for nonmodal dialogs */</span>
<span class="coMULTI">/* dialog buttons and response signals */</span>
GTK_STOCK_CANCEL,
GTK_RESPONSE_REJECT,
GTK_STOCK_OK,
GTK_RESPONSE_ACCEPT,
<span class="kw2">NULL</span><span class="br0">)</span>;
<span class="coMULTI">/* set default response signal. This is usually triggered by the
"Return" key */</span>
gtk_dialog_set_default_response<span class="br0">(</span>GTK_DIALOG<span class="br0">(</span>dialog<span class="br0">)</span>,
GTK_RESPONSE_ACCEPT<span class="br0">)</span>;
<span class="coMULTI">/* set the function for handling the button responses and dialog close
for nonmodal dialogs you can use dialog_run() too.*/</span>
gtk_signal_connect<span class="br0">(</span>GTK_OBJECT<span class="br0">(</span>dialog<span class="br0">)</span>, <span class="st0">"response"</span>,
GTK_SIGNAL_FUNC<span class="br0">(</span>dialog_response<span class="br0">)</span>, w_current<span class="br0">)</span>;
<span class="coMULTI">/* where to place the dialog: GTK_WIN_POS_MOUSE or GTK_WIN_POS_NONE */</span>
gtk_window_position<span class="br0">(</span>GTK_WINDOW <span class="br0">(</span>dialog<span class="br0">)</span>, GTK_WIN_POS_MOUSE<span class="br0">)</span>;
<span class="coMULTI">/* set the border spacing and the vbox spacing of the dialog */</span>
vbox = GTK_DIALOG<span class="br0">(</span>dialog<span class="br0">)</span>->vbox;
gtk_container_set_border_width<span class="br0">(</span>GTK_CONTAINER<span class="br0">(</span>dialog<span class="br0">)</span>,DIALOG_BORDER_SPACING<span class="br0">)</span>;
gtk_box_set_spacing<span class="br0">(</span>GTK_BOX<span class="br0">(</span>vbox<span class="br0">)</span>, DIALOG_V_SPACING<span class="br0">)</span>;
<span class="coMULTI">/* create a label (with markup) and pack it into the dialog box */</span>
label = gtk_label_new<span class="br0">(</span>_<span class="br0">(</span><span class="st0">"<b>Section label</b>"</span><span class="br0">)</span><span class="br0">)</span>;
gtk_label_set_use_markup<span class="br0">(</span>GTK_LABEL<span class="br0">(</span>label<span class="br0">)</span>, <span class="kw2">TRUE</span><span class="br0">)</span>;
gtk_misc_set_alignment<span class="br0">(</span>GTK_MISC<span class="br0">(</span>label<span class="br0">)</span>,<span class="nu0">0</span>,<span class="nu0">0</span><span class="br0">)</span>;
gtk_box_pack_start<span class="br0">(</span>GTK_BOX<span class="br0">(</span>vbox<span class="br0">)</span>, label, <span class="kw2">FALSE</span>, <span class="kw2">FALSE</span>, <span class="nu0">0</span><span class="br0">)</span>;
<span class="coMULTI">/* create a alignment container with the DIALOG_INDENTATION on the left */</span>
alignment = gtk_alignment_new<span class="br0">(</span><span class="nu0">0</span>,<span class="nu0">0</span>,<span class="nu0">1</span>,<span class="nu0">1</span><span class="br0">)</span>;
gtk_alignment_set_padding<span class="br0">(</span>GTK_ALIGNMENT<span class="br0">(</span>alignment<span class="br0">)</span>, <span class="nu0">0</span>, <span class="nu0">0</span>,
DIALOG_INDENTATION, <span class="nu0">0</span><span class="br0">)</span>;
gtk_box_pack_start<span class="br0">(</span>GTK_BOX<span class="br0">(</span>vbox<span class="br0">)</span>, alignment, <span class="kw2">FALSE</span>, <span class="kw2">FALSE</span>, <span class="nu0">0</span><span class="br0">)</span>;
<span class="coMULTI">/* a table can store several entries. It is stored in the aligment container.
Note: the vertical and horizontal cell spacings */</span>
table = gtk_table_new <span class="br0">(</span><span class="nu0">3</span>, <span class="nu0">2</span>, <span class="kw2">FALSE</span><span class="br0">)</span>;
gtk_table_set_row_spacings<span class="br0">(</span>GTK_TABLE<span class="br0">(</span>table<span class="br0">)</span>, DIALOG_V_SPACING<span class="br0">)</span>;
gtk_table_set_col_spacings<span class="br0">(</span>GTK_TABLE<span class="br0">(</span>table<span class="br0">)</span>, DIALOG_H_SPACING<span class="br0">)</span>;
gtk_container_add<span class="br0">(</span>GTK_CONTAINER<span class="br0">(</span>alignment<span class="br0">)</span>, table<span class="br0">)</span>;
<span class="coMULTI">/* a simple text label in one table cell with left alignment.
Note: the GTK_FILL in the third line is required */</span>
label = gtk_label_new<span class="br0">(</span>_<span class="br0">(</span><span class="st0">"Text:"</span><span class="br0">)</span><span class="br0">)</span>;
gtk_misc_set_alignment<span class="br0">(</span>GTK_MISC<span class="br0">(</span>label<span class="br0">)</span>,<span class="nu0">0</span>,<span class="nu0">0</span><span class="br0">)</span>;
gtk_table_attach<span class="br0">(</span>GTK_TABLE<span class="br0">(</span>table<span class="br0">)</span>, label, <span class="nu0">0</span>,<span class="nu0">1</span>,<span class="nu0">0</span>,<span class="nu0">1</span>, GTK_FILL,<span class="nu0">0</span>,<span class="nu0">0</span>,<span class="nu0">0</span><span class="br0">)</span>;
<span class="coMULTI">/* a simple text entry completes the option row */</span>
textentry = gtk_entry_new_with_max_length <span class="br0">(</span><span class="nu0">10</span><span class="br0">)</span>;
gtk_table_attach_defaults<span class="br0">(</span>GTK_TABLE<span class="br0">(</span>table<span class="br0">)</span>, textentry, <span class="nu0">1</span>,<span class="nu0">2</span>,<span class="nu0">0</span>,<span class="nu0">1</span><span class="br0">)</span>;
gtk_entry_set_activates_default<span class="br0">(</span>GTK_ENTRY<span class="br0">(</span>textentry<span class="br0">)</span>, <span class="kw2">TRUE</span><span class="br0">)</span>;
<span class="coMULTI">/* ..... more table rows with options, or new sections */</span>
<span class="coMULTI">/* create references to all widgets that you need later */</span>
GLADE_HOOKUP_OBJECT<span class="br0">(</span>dialog, sizeentry,<span class="st0">"textentry"</span><span class="br0">)</span>;
<span class="coMULTI">/* show all widgets recursivly */</span>
gtk_widget_show_all<span class="br0">(</span>dialog<span class="br0">)</span>;
<span class="br0">}</span>
<span class="kw1">else</span> <span class="br0">{</span>
<span class="coMULTI">/* Dialog is already there. Present it to the user.
This is only required if you have a nonmodal dialog */</span>
gtk_window_present<span class="br0">(</span>GTK_WINDOW<span class="br0">(</span>dialog<span class="br0">)</span><span class="br0">)</span>;
<span class="br0">}</span>
<span class="coMULTI">/* always set the current values to the dialog
If you're placing that part at the end of the dialog function you can
easily create dialogs that can be called, even if they are already open */</span>
textentry = g_object_get_data<span class="br0">(</span>G_OBJECT<span class="br0">(</span>dialog<span class="br0">)</span>, <span class="st0">"textentry"</span><span class="br0">)</span>;
gtk_entry_set_text<span class="br0">(</span>GTK_ENTRY<span class="br0">(</span>textentry<span class="br0">)</span>, <span class="kw4">string</span><span class="br0">)</span>;
<span class="coMULTI">/* select the text region that the user usually likes to overwrite */</span>
gtk_entry_select_region<span class="br0">(</span>GTK_ENTRY<span class="br0">(</span>textentry<span class="br0">)</span>, <span class="nu0">0</span>, strlen<span class="br0">(</span><span class="kw4">string</span><span class="br0">)</span><span class="br0">)</span>;
<span class="br0">}</span></pre>
<p>
The response function for such a dialog may look like this:
</p>
<pre class="code c"><span class="kw4">void</span> dialog_response<span class="br0">(</span>GtkWidget *widget, gint response, TOPLEVEL *w_current<span class="br0">)</span>
<span class="br0">{</span>
<span class="kw1">switch</span> <span class="br0">(</span>response<span class="br0">)</span> <span class="br0">{</span>
<span class="kw1">case</span> GTK_RESPONSE_ACCEPT:
<span class="coMULTI">/* apply the dialog settings:
just insert your code here if it is short
call an extra apply function if the required code is long */</span>
<span class="kw2">break</span>;
<span class="kw1">case</span> GTK_RESPONSE_REJECT:
<span class="kw1">case</span> GTK_RESPONSE_DELETE_EVENT:
<span class="coMULTI">/* for modal dialogs just do nothing,
for nonmodal dialogs, destroy the dialog and clean up */</span>
<span class="kw2">break</span>;
<span class="kw1">default</span>:
<span class="coMULTI">/* catch wrong signals signals (paranoid error checking ;-)) */</span>
<a href="http://www.opengroup.org/onlinepubs/009695399/functions/printf.html";><span class="kw3">printf</span></a><span class="br0">(</span><span class="st0">"dialog_response(): strange signal %d<span class="es0">\n</span>"</span>, response<span class="br0">)</span>;
<span class="br0">}</span>
<span class="coMULTI">/* for nonmodal dialogs just do nothing,
for modal dialogs, always destroy the dialog and clean up */</span>
<span class="br0">}</span></pre>
</div>
<!-- SECTION [7056-11883] -->
<h3><a name="current_dialog_issues_in_gschem" id="current_dialog_issues_in_gschem">Current Dialog Issues in Gschem</a></h3>
<div class="level3">
<ul>
<li class="level1"><div class="li"> every dialog has it’s own design</div>
</li>
<li class="level1"><div class="li"> dialog placement: mouse position or no predefined position?</div>
</li>
<li class="level1"><div class="li"> dialogs do not remember their last size, position and contents.</div>
</li>
<li class="level1"><div class="li"> missing keyboard shortcuts</div>
</li>
</ul>
<p>
<strong>Here’s a list of things that could be improved:</strong>
</p>
</div>
<h5><a name="print_dialog" id="print_dialog">Print Dialog</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> change design?</div>
</li>
</ul>
</div>
<h5><a name="write_image" id="write_image">Write Image</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> In the fileselect dialog the default filename is missing if the file does not exist</div>
</li>
<li class="level1"><div class="li"> Return key does not work in the filename entry</div>
</li>
</ul>
</div>
<h5><a name="execute_script" id="execute_script">Execute Script</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> </div>
</li>
</ul>
</div>
<h5><a name="edit_text" id="edit_text">Edit Text</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> some missing keyboard shortcuts</div>
</li>
<li class="level1"><div class="li"> add *unmodified* tags if there are multiple selections</div>
</li>
<li class="level1"><div class="li"> maybe add some color pixbufs for the color</div>
</li>
<li class="level1"><div class="li"> maybe replace the text alignment with nine ratio buttons, toggle buttons with icons or ...</div>
</li>
</ul>
</div>
<h5><a name="color_dialog" id="color_dialog">Color Dialog</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> maybe add some color pixbufs for the color</div>
</li>
</ul>
</div>
<h5><a name="line_width_and_type" id="line_width_and_type">Line Width and Type</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> keyboard shortcuts missing</div>
</li>
<li class="level1"><div class="li"> icons for the line type</div>
</li>
</ul>
</div>
<h5><a name="fill_type" id="fill_type">Fill Type</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> keyboard shortcuts missing</div>
</li>
<li class="level1"><div class="li"> icons in the fill type</div>
</li>
</ul>
</div>
<h5><a name="translate_symbol" id="translate_symbol">Translate Symbol</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> </div>
</li>
</ul>
</div>
<h5><a name="page_manager" id="page_manager">Page Manager</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> wrong button order? Depends on whether you think the refresh button is the main action button or just an extra button.</div>
</li>
<li class="level1"><div class="li"> Maybe the “Return” key should trigger Refresh</div>
</li>
</ul>
</div>
<h5><a name="component_selector" id="component_selector">Component Selector</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> strange edit widget when typing and the tree is selected (It’s a search helper widget, disable it?!)</div>
</li>
</ul>
</div>
<h5><a name="single_attribut_editor" id="single_attribut_editor">Single Attribut Editor</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> when multiple elements are selected and you call edit (ee) there are a few problems:</div>
<ul>
<li class="level3"><div class="li"> if the first object is text, then this dialog is opened (but with the wrong list parameter</div>
</li>
<li class="level3"><div class="li"> if the first object is complex then the multiple attribute editor is called</div>
</li>
</ul>
</li>
</ul>
</div>
<h5><a name="multi_attribute_editor" id="multi_attribute_editor">Multi Attribute Editor</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> </div>
</li>
</ul>
</div>
<h5><a name="add_text" id="add_text">Add Text</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> </div>
</li>
</ul>
</div>
<h5><a name="arc_params" id="arc_params">Arc Params</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> add the diameter to the dialog, but select the start angle entry (increment = grid)</div>
</li>
<li class="level1"><div class="li"> let “ee” call that dialog if only a single arc is selected</div>
</li>
<li class="level1"><div class="li"> maybe add a section label</div>
</li>
</ul>
</div>
<h5><a name="insert_picture" id="insert_picture">Insert Picture</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> </div>
</li>
</ul>
</div>
<h5><a name="picture_replace" id="picture_replace">Picture Replace</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> the new picture uses the aspect ratio of the old picture</div>
</li>
<li class="level1"><div class="li"> the dialog has lots in common with the Insert Picture dialog. They could use some code together</div>
</li>
</ul>
</div>
<h5><a name="find_text" id="find_text">Find Text</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> manipulates the mouse pointer (maybe the zooming code is the culprit). Just press “Return” to trigger a FindNext</div>
</li>
<li class="level1"><div class="li"> if you select hierarchy and the found text is in a different schematic, then the filename in the title is not updated</div>
</li>
<li class="level1"><div class="li"> maybe add an option: “Select all matching text objects”, disable hierarchy for that feature!</div>
</li>
<li class="level1"><div class="li"> <img src="lib/images/smileys/fixme.gif" class="middle" alt="FIXME" /> gschem hangs if you use that dialog with hierarchical schematics that have dependancy loops (e.g. the autonumber test schematics)</div>
</li>
<li class="level1"><div class="li"> add an option “search for visible text only”</div>
</li>
<li class="level1"><div class="li"> maybe use regular expressions instead of the substring for the searchtext</div>
</li>
</ul>
</div>
<h5><a name="hide_text" id="hide_text">Hide Text</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> use regular expressions instead of starting substring</div>
</li>
</ul>
</div>
<h5><a name="show_text" id="show_text">Show Text</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> use regular expressions instead of starting substring</div>
</li>
<li class="level1"><div class="li"> Maybe merge that dialog together with the “Hide Text” dialog</div>
</li>
</ul>
</div>
<h5><a name="autonumber_text" id="autonumber_text">Autonumber Text</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> Maybe disable the skip option if the renumber scope is “selection”. The other skip options (Page and Hierarchy) are really stupid.</div>
</li>
</ul>
</div>
<h5><a name="text_size" id="text_size">Text Size</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> </div>
</li>
</ul>
</div>
<h5><a name="snap_grid_spacing" id="snap_grid_spacing">Snap Grid Spacing</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> </div>
</li>
</ul>
</div>
<h5><a name="coord_dialog" id="coord_dialog">Coord Dialog</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> maybe move the world coordinates to the main window status bar</div>
</li>
</ul>
</div>
<h5><a name="about_dialog" id="about_dialog">About Dialog</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> </div>
</li>
</ul>
</div>
<h5><a name="hotkeys" id="hotkeys">Hotkeys</a></h5>
<div class="level5">
<ul>
<li class="level1"><div class="li"> </div>
</li>
</ul>
</div>
<!-- SECTION [11884-] --></div>
</body>
</html>
1.1 eda/geda/gaf/docs/wiki/geda_fedora_rpm_installation.html
Index: geda_fedora_rpm_installation.html
===================================================================
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en"
lang="en" dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>geda:fedora_rpm_installation</title>
<meta name="generator" content="DokuWiki Release 2006-03-09" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
<link rel="contents" href="http://geda.seul.org/wiki/geda:fedora_rpm_installation?do=index"; title="" />
<link rel="alternate" type="application/rss+xml" title="Recent Changes" href="http://geda.seul.org/wiki/feed.php"; />
<link rel="alternate" type="application/rss+xml" title="Current Namespace" href="http://geda.seul.org/wiki/feed.php?mode=list&ns=geda"; />
<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/geda:fedora_rpm_installation?do=export_xhtml"; />
<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/geda:fedora_rpm_installation?do=export_raw"; />
<meta name="date" content="2007-01-05T12:02:06-0500" />
<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>
<body>
<div class="dokuwiki export">
<div class="toc">
<div class="tocheader toctoggle" id="toc__header">Table of Contents</div>
<div id="toc__inside">
<ul class="toc">
<li class="level1"><div class="li"><span class="li"><a href="#installing_geda_rpm_packages_on_fedora_and_redhat" class="toc">Installing gEDA rpm packages on Fedora and RedHat</a></span></div>
<ul class="toc">
<li class="level2"><div class="li"><span class="li"><a href="#installing_rpm_packages_from_fedora_core_extra" class="toc">Installing rpm packages from Fedora Core Extra</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#distribution_specific_notes" class="toc">Distribution specific notes</a></span></div>
<ul class="toc">
<li class="level3"><div class="li"><span class="li"><a href="#fedora_core_4" class="toc">Fedora Core 4</a></span></div></li>
<li class="level3"><div class="li"><span class="li"><a href="#fedora_core_5" class="toc">Fedora Core 5</a></span></div></li>
<li class="level3"><div class="li"><span class="li"><a href="#fedora_core_6" class="toc">Fedora Core 6</a></span></div></li></ul>
</li></ul>
</li></ul>
</div>
</div>
<h1><a name="installing_geda_rpm_packages_on_fedora_and_redhat" id="installing_geda_rpm_packages_on_fedora_and_redhat">Installing gEDA rpm packages on Fedora and RedHat</a></h1>
<div class="level1">
</div>
<!-- SECTION [1-65] -->
<h2><a name="installing_rpm_packages_from_fedora_core_extra" id="installing_rpm_packages_from_fedora_core_extra">Installing rpm packages from Fedora Core Extra</a></h2>
<div class="level2">
<p>
TBD
</p>
</div>
<!-- SECTION [66-129] -->
<h2><a name="distribution_specific_notes" id="distribution_specific_notes">Distribution specific notes</a></h2>
<div class="level2">
<p>
Each distribution version has itâ??s own issues. Please read and enhance the notes below.
</p>
</div>
<!-- SECTION [130-260] -->
<h3><a name="fedora_core_4" id="fedora_core_4">Fedora Core 4</a></h3>
<div class="level3">
</div>
<!-- SECTION [261-285] -->
<h3><a name="fedora_core_5" id="fedora_core_5">Fedora Core 5</a></h3>
<div class="level3">
</div>
<!-- SECTION [286-310] -->
<h3><a name="fedora_core_6" id="fedora_core_6">Fedora Core 6</a></h3>
<div class="level3">
<ul>
<li class="level1"><div class="li"> <strong>guile 1.8.x problems:</strong> Fedora Core 6 has a guile version 1.8.x. This causes errors when placing pins or using gnetlist. Try to install guile version 1.6.7 instead.</div>
</li>
</ul>
</div>
<!-- SECTION [311-] --></div>
</body>
</html>
1.1 eda/geda/gaf/docs/wiki/geda_gedasuite_installation.html
Index: geda_gedasuite_installation.html
===================================================================
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en"
lang="en" dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>geda:gedasuite_installation</title>
<meta name="generator" content="DokuWiki Release 2006-03-09" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
<link rel="contents" href="http://geda.seul.org/wiki/geda:gedasuite_installation?do=index"; title="" />
<link rel="alternate" type="application/rss+xml" title="Recent Changes" href="http://geda.seul.org/wiki/feed.php"; />
<link rel="alternate" type="application/rss+xml" title="Current Namespace" href="http://geda.seul.org/wiki/feed.php?mode=list&ns=geda"; />
<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/geda:gedasuite_installation?do=export_xhtml"; />
<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/geda:gedasuite_installation?do=export_raw"; />
<meta name="date" content="2007-01-06T05:05:27-0500" />
<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>
<body>
<div class="dokuwiki export">
<div class="toc">
<div class="tocheader toctoggle" id="toc__header">Table of Contents</div>
<div id="toc__inside">
<ul class="toc">
<li class="clear">
<ul class="toc">
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_install_the_geda_suite" class="toc">How do I install the gEDA Suite?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_uninstall_the_geda_suite" class="toc">How do I uninstall the gEDA Suite?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#why_would_i_want_to_uninstall_the_geda_suite" class="toc">Why would I want to uninstall the gEDA Suite?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#aaaargh_i_put_the_cd_into_my_reader_and_mounted_the_cd_but_nothing_happened" class="toc">Aaaargh! I put the CD into my reader, and mounted the CD, but nothing happened!</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#help_me_i_m_trying_to_install_using_the_cd_rom_but_the_install_wizard_says_i_have_an_error" class="toc">Help me! I'm trying to install using the CD ROM, but the install wizard says I have an error!</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#waaaa_the_installation_ran_to_completion_but_i_get_a_segfault_or_other_problem_when_i_run_gschem_or_gattrib_or_gnetlist_or" class="toc">Waaaa! The installation ran to completion, but I get a segfault (or other problem) when I run gschem (or gattrib, or gnetlist, or. . . )!</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#fedora_core_4_install_notes" class="toc">Fedora Core 4 install notes</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#fedora_core_3_install_notes" class="toc">Fedora Core 3 install notes</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#fedora_core_2_install_notes" class="toc">Fedora Core 2 install notes</a></span></div></li>
<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="#ubuntu_install_notes" class="toc">Ubuntu 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>
</div>
<h2><a name="how_do_i_install_the_geda_suite" id="how_do_i_install_the_geda_suite">How do I install the gEDA Suite?</a></h2>
<div class="level2">
<p>
The easiest way to install the gEDA Suite is to grab the gEDA Suite CD ROM and use it. The instructions are contained in the README available on the <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">downloads page</a>. <strong><em>Note that the CD ROM installer assumes that you are running the Gnome desktop! The same is true of the gEDA tools: They use the GTK widget set which underlies Gnome. If you are running KDE, you need to at least get the Gnome libraries installed on your machine before trying to run the installer.</em></strong>
</p>
<p>
The gEDA Suite CD holds the tarballs of more than one dozen popular gEDA applications. It also incorporates a <acronym title="Graphical User Interface">GUI</acronym>-based install wizard which checks your system configuration, asks you a few questions, and then oversees the compilation and installation of the different gEDA applications. The install wizard just automates the normal â??./configure && make && make installâ?? process used to build GNU software from source. Therefore, it is more or less platform independent (as long as you are running Linux).
</p>
<p>
In the event that the install wizard canâ??t automatically install the gEDA Suite, you can still get the source tarballs off the CD and build them manually. The instructions are available from the download web page, as well as in the INSTALL file on the CD.
</p>
<p>
Also, people have created RedHat RPMs, Debian Debs, and Mac OSX Fink packages if you prefer to install that way. These binary distributions are available on the <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">downloads page</a>. Finally, source tarballs for all programs are also available on the <a href="http://geda.seul.org/download.html"; class="urlextern" title="http://geda.seul.org/download.html"; rel="nofollow">downloads page</a>.
</p>
<p>
By the way, itâ??s always a good idea to install gEDA into its own directory. That way, when you want to upgrade the package you just need to delete the directory and re-install. (This advice is true for any large suite of applications in unix.) More on this below.
</p>
<p>
Finally, if the instructions here arenâ??t enough, David Hart has placed a useful and detailed <a href="http://www.offramp.com/Lab-Install/doku.php?id=fc4#create_user_geda_account_and_install_geda_tool_suite"; class="urlextern" title="http://www.offramp.com/Lab-Install/doku.php?id=fc4#create_user_geda_account_and_install_geda_tool_suite"; rel="nofollow">guide for configuring and installing gEDA</a> (for Fedora Core 4, but probably helpful with other distros too), as well as a <a href="http://www.offramp.com/Lab-Install/doku.php?id=fc4#geda_tutorial"; class="urlextern" title="http://www.offramp.com/Lab-Install/doku.php?id=fc4#geda_tutorial"; rel="nofollow">gEDA Tutorial</a> for new users.
</p>
</div>
<!-- SECTION [1-2359] -->
<h2><a name="how_do_i_uninstall_the_geda_suite" id="how_do_i_uninstall_the_geda_suite">How do I uninstall the gEDA Suite?</a></h2>
<div class="level2">
<p>
As of this writing, no advanced method to uninstall the gEDA Suite exists. Unlike a certain commercial operating system, Linux (and unix) were not designed with the goal of easy package management in mind, and we all suffer with this legacy.
</p>
<p>
Therefore, we recommend that you install the gEDA Suite into its own special directory. For example, the CD Installer will place the Suiteâ??s executables into <strong><code>${HOME}/geda-install</code></strong> by default. Then, if you need to uninistall the gEDA Suite, you can just delete the entire directory.
</p>
<p>
<span class="hilited">(More advanced methods to install/uninstall packages on Linux/unix also exist. Could somebody please write about them here?)</span>
</p>
</div>
<!-- SECTION [2360-3071] -->
<h2><a name="why_would_i_want_to_uninstall_the_geda_suite" id="why_would_i_want_to_uninstall_the_geda_suite">Why would I want to uninstall the gEDA Suite?</a></h2>
<div class="level2">
<p>
Different applications belonging to gEDA/gaf all use the same shared library, libgeda.so. Things in the library change from one gEDA release to another. Therefore, applications are prevented from linking to libgeda.so if their release codes donâ??t match.
</p>
<p>
If you need to upgrade one application in gEDA/gaf, you will need to first uninstall your old version, and then install an entirely new set of applications, including the library and all components of gEDA/gaf.
</p>
<p>
Alternately, you can install the new gEDA/gaf into a new directory, and then edit your <strong><code>${PATH}</code></strong>, <strong><code>${PKG_CONFIG_PATH}</code></strong>, and <strong><code>${LD_LIBRARY_PATH}</code></strong> environment variables to remove the old directory, and point to the new one. Make sure you do this <strong>before</strong> you try installing the new gEDA/gaf.
</p>
</div>
<!-- SECTION [3072-3909] -->
<h2><a name="aaaargh_i_put_the_cd_into_my_reader_and_mounted_the_cd_but_nothing_happened" id="aaaargh_i_put_the_cd_into_my_reader_and_mounted_the_cd_but_nothing_happened">Aaaargh! I put the CD into my reader, and mounted the CD, but nothing happened!</a></h2>
<div class="level2">
<p>
Amazingly enough, some people simply copy the installer .iso file using â??cpâ?? onto a blank CD, and then try to use it. This wonâ??t work. You need to â??burnâ?? a CD with the .iso in a way which writes the whole filesystem directly onto the CDROM. The linux/unix command to do this is usually â??cdrecordâ??, or perhaps a <acronym title="Graphical User Interface">GUI</acronym> derivative of this utility. Donâ??t just â??cpâ?? the .iso file onto a blank CD!
</p>
<p>
Many modern Linux distributions will not automatically run executables on installed media. This is a security precaution. To overcome this, you need to mount the CD in a way which grants permission for executables to run. For example, in Gentoo and Debian you should mount the CD ROM this way:
</p>
<pre class="code">mount -o exec -t iso9660 /dev/cdrom /mnt/cdrom</pre>
<p>
The detailed flag or mount point relevant to your distribution might be a little different; read the manual for mount (â??man mountâ??) if you have any questions about how to do this.
</p>
<p>
After you have mounted the CD with execute permission, you can then run the installer from the command line like this:
</p>
<pre class="code">/mnt/cdrom/installer</pre>
<p>
At this point, the install wizardâ??s <acronym title="Graphical User Interface">GUI</acronym> should pop up, and you can get to installing. If you canâ??t install, please try doing an â??lsâ?? of the CD to see if it is readable. That is, do this:
</p>
<pre class="code">ls -l /mnt/cdrom/</pre>
<p>
And verify that you get a directory listing instead of an error message (or nothing at all).
</p>
</div>
<!-- SECTION [3910-5428] -->
<h2><a name="help_me_i_m_trying_to_install_using_the_cd_rom_but_the_install_wizard_says_i_have_an_error" id="help_me_i_m_trying_to_install_using_the_cd_rom_but_the_install_wizard_says_i_have_an_error">Help me! I'm trying to install using the CD ROM, but the install wizard says I have an error!</a></h2>
<div class="level2">
<p>
First off, please keep in mind that the CD ROMâ??s installer only works on Linux. The CD ROM installer will not work on Sun, BSD, or Mac OSX, and it certainly wonâ??t work on Windows.
</p>
<p>
As a general rule, if you are having problems installing gEDA from the CD, here are the things you can try:
</p>
<ol>
<li class="level1"><div class="li"> If you run the installer with the <strong><code>â??log</code></strong> flag set, it will place a file called Install.log into your local directory (where you are running the installer). This file is a log of all commands issued and all responses generated during the install process. It allows you to save the data displayed on the log window displayed during the install process. Running the installer with <strong><code>â??log</code></strong> set is a good idea if you are experiencing problems; you can send your Install.log file to an expert who might be able to diagnose your problem. More on this later.</div>
</li>
<li class="level1"><div class="li"> After experiencing a problem, the first thing you should do is look through the gEDA Wiki. Itâ??s quite likely that somebody has already experienced your problem, reported it, and a work around has been found and posted. Different Linux distributions have displayed different problems in the past. Depending upon your distribution, consult the help sections below.</div>
</li>
<li class="level1"><div class="li"> If no mention of your specific problem has been posted on the Wiki, try a Google search. GEDA tips and tricks show up in many different places on the web, and Google can find them for you. Also, the geda-user list is continually indexed by Google. Since people frequently post bugs and bug workarounds there, Google will help you find these reports.</div>
</li>
<li class="level1"><div class="li"> Next, try posting a question on the geda-user e-mail list. Note that you must first subscribe to the geda-user e-mail list before posting any e-mail to the list. Others may have already developed a work-around for your problem. Some of the experts hang out on that list, and might offer a few helpful suggestions.</div>
</li>
</ol>
</div>
<!-- SECTION [5429-7440] -->
<h2><a name="waaaa_the_installation_ran_to_completion_but_i_get_a_segfault_or_other_problem_when_i_run_gschem_or_gattrib_or_gnetlist_or" id="waaaa_the_installation_ran_to_completion_but_i_get_a_segfault_or_other_problem_when_i_run_gschem_or_gattrib_or_gnetlist_or">Waaaa! The installation ran to completion, but I get a segfault (or other problem) when I run gschem (or gattrib, or gnetlist, or. . . )!</a></h2>
<div class="level2">
<p>
After you install the gEDA Suite off the CD ROM, make sure you do the following:
</p>
<ol>
<li class="level1"><div class="li"> Set your <strong><code>${PATH}</code></strong> to point to the location where your new gEDA executables live (for example, <strong><code>/home/your-name/geda-install/bin</code></strong>). Make sure that you remove pointers to old gEDA editions, if they exist. You should not only set the <strong><code>${PATH}</code></strong> in your current shell, but you should also set it in your shell config scripts (i.e. .bashrc or .cshrc)</div>
</li>
<li class="level1"><div class="li"> Type â??rehashâ?? to update your executable search path.</div>
</li>
<li class="level1"><div class="li"> Set your <strong><code>${LD_LIBRARY_PATH}</code></strong> to point to the location where your new gEDA executables live (for example, <strong><code>/home/your-name/geda-install/lib</code></strong>). Make sure to remove pointers to old gEDA editions, if they exist. You should not only set the <strong><code>${LD_LIBRARY_PATH}</code></strong> in your current shell, but you should also set it in your shell config scripts (i.e. .bashrc or .cshrc)</div>
</li>
<li class="level1"><div class="li"> Run â??su -c ldconfigâ?? to tell the kernel where to find your new libgeda.so.</div>
</li>
</ol>
</div>
<!-- SECTION [7441-8568] -->
<h2><a name="fedora_core_4_install_notes" id="fedora_core_4_install_notes">Fedora Core 4 install notes</a></h2>
<div class="level2">
<p>
<a href="geda_fc4.html" class="wikilink1" title="geda:fc4">FC4 notes available here</a>
</p>
</div>
<!-- SECTION [8569-8647] -->
<h2><a name="fedora_core_3_install_notes" id="fedora_core_3_install_notes">Fedora Core 3 install notes</a></h2>
<div class="level2">
<p>
<a href="geda_fc3.html" class="wikilink1" title="geda:fc3">FC3 notes available here</a>
</p>
</div>
<!-- SECTION [8648-8726] -->
<h2><a name="fedora_core_2_install_notes" id="fedora_core_2_install_notes">Fedora Core 2 install notes</a></h2>
<div class="level2">
<p>
<a href="geda_fc2.html" class="wikilink1" title="geda:fc2">FC2 notes available here</a>
</p>
</div>
<!-- SECTION [8727-8805] -->
<h2><a name="fedora_core_1_install_notes" id="fedora_core_1_install_notes">Fedora Core 1 install notes</a></h2>
<div class="level2">
<p>
<a href="geda_fc1.html" class="wikilink1" title="geda:fc1">FC1 notes available here</a>
</p>
</div>
<!-- SECTION [8806-8884] -->
<h2><a name="suse_9.3_install_notes" id="suse_9.3_install_notes">Suse 9.3 install notes</a></h2>
<div class="level2">
<p>
<a href="geda_suse_9.html" class="wikilink1" title="geda:suse_9.3">SuSE 9.3 notes available here</a>
</p>
</div>
<!-- SECTION [8885-8968] -->
<h2><a name="suse_10.0_install_notes" id="suse_10.0_install_notes">Suse 10.0 install notes</a></h2>
<div class="level2">
<p>
<a href="geda_suse_10.html" class="wikilink1" title="geda:suse_10.0">SuSE 10.0 notes available here</a>
</p>
</div>
<!-- SECTION [8969-9055] -->
<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 [9056-9142] -->
<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 [9143-9220] -->
<h2><a name="ubuntu_install_notes" id="ubuntu_install_notes">Ubuntu install notes</a></h2>
<div class="level2">
<p>
<a href="geda_ubuntu.html" class="wikilink1" title="geda:ubuntu">Ubuntu notes available here</a>
</p>
</div>
<!-- SECTION [9221-9299] -->
<h2><a name="windows_install_notes" id="windows_install_notes">Windows install notes</a></h2>
<div class="level2">
<p>
<a href="geda_cygwin.html" class="wikilink1" title="geda:cygwin">Cygwin notes available here</a>
</p>
</div>
<!-- SECTION [9300-] --></div>
</body>
</html>
1.1 eda/geda/gaf/docs/wiki/geda_glossaire.html
Index: geda_glossaire.html
===================================================================
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en"
lang="en" dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>geda:glossaire.fr</title>
<meta name="generator" content="DokuWiki Release 2006-03-09" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
<link rel="contents" href="http://geda.seul.org/wiki/geda:glossaire.fr?do=index"; title="" />
<link rel="alternate" type="application/rss+xml" title="Recent Changes" href="http://geda.seul.org/wiki/feed.php"; />
<link rel="alternate" type="application/rss+xml" title="Current Namespace" href="http://geda.seul.org/wiki/feed.php?mode=list&ns=geda"; />
<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/geda:glossaire.fr?do=export_xhtml"; />
<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/geda:glossaire.fr?do=export_raw"; />
<meta name="date" content="2006-12-05T15:59:17-0500" />
<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>
<body>
<div class="dokuwiki export">
<h1><a name="glossaire_des_termes_de_geda_et_des_eda" id="glossaire_des_termes_de_geda_et_des_eda">Glossaire des termes de gEDA (et des EDA)</a></h1>
<div class="level1">
<p>
La conception en électronique implique beaucoup de termes spécifiques. Quelques termes ont une signification qui ne ressemble que vaguement à leur utilisation dans la vie de tous les jours. Ce glossaire est destiné à devenir un dictionaire de termes spécifiques à la suite gEDA, de même que monde plus grand des CAO pour l’électronique. Malheureusement, il n’existe pas de méthode universelle de nommage des concepts dans le champ de la conception électronique. Le glossaire donnera des éléments sur la manière dont les choses sont appelées dans les autres suites de conception.
</p>
<p>
<span class="hilited">(Aux auteurs du Wiki:Veuillez insérer les nouveaux termes dans l’ordre de l’alphabet)</span>
</p>
<ul>
<li class="level1"><div class="li"> <strong>anneau annulaire (annular ring)</strong>: L’anneau annulaire, quelque fois aussi appelé <strong>annulus</strong>, est un diamètre de cuivre qui doit être placé autour des trous métallisés comme les pastilles et les vias. La taille minimum de l’anneau annulaire est spécifié par les fabricants de pcb. Une spécification habituelle est de 16 mil plus large que le trou.</div>
</li>
<li class="level1"><div class="li"> <strong>empreinte (footprint)</strong>: Le dessin de métal et de silkscreen qui définit où vous placez un composant sur un circuit. Les empreintes sont disposées par l’utilisateur sur le circuit imprimé lors de la phase de « placement » (en utilisant i.e. l’outil open-source PCB). Une empreinte est aussi quelque fois appelée un « decal » (PADS) ou un « land-pattern ».</div>
</li>
<li class="level1"><div class="li"> <strong>flux de conception (design flow)</strong>: L’ordre des étapes dans lequel vous faites progresser votre étude depuis le concept initial, par la saisie de schéma, l’ajout d’attribut, le netlisting et le circuit imprimé. On utilisera typiquement plusieurs outils pour accomplir différentes tâches pendant la réalisation. La Suite gEDA utilise des programmes entièrement séparés pour les différents étapes du cheminement; chaque outil de la suite lit le fichier de sortie produit par l’outil précédent et écrit un fichier pouvant être lu par l’outil suivant dans la chaîne. Le flux de conception de gEDA pour réaliser un PCB est illustré <a href="http://geda.seul.org/dokuwiki/doku.php?id=geda:usage#what_does_the_design_flow_in_geda_look_like"; class="urlextern" title="http://geda.seul.org/dokuwiki/doku.php?id=geda:usage#what_does_the_design_flow_in_geda_look_like"; rel="nofollow">ici</a>. Notez que le flux du cheminement pour des tâches différentes peut varier. Par exemple, si votre but est de simuler votre circuit, vous utiliserez un flux différent de celui montré dans le lien ci-dessus. Finalement, les autres outils de conception de PCB â?? habituellement plus simples â?? utilisent une approche monolithique dans laquelle un seul programme (albeit avec différents modes d’édition) est utilisé pour réaliser le montage complet. Déterminer la meilleure approche est plus une affaire de croyance personnelle.</div>
</li>
<li class="level1"><div class="li"> <strong>net</strong>: Un net est la représentation d’un fil ou d’une connexion électrique dans un schéma. C’est, basiquement, une ligne connectant deux broches de symbole. Le terme « net » est aussi quelque fois utilisé pour parler d’une connexion électrique (via une fil ou une piste de PCB) dans un circuit réel. Quelques outils de saisie de schéma appellent un net un « fil ».</div>
</li>
<li class="level1"><div class="li"> <strong>netlist</strong>: Une netlist est une représentation en fichier texte de votre circuit qui souligne les connexions entre les différents éléments du circuit, peut être indépendants des boîtiers physiques constituants les composants réels du circuit.</div>
</li>
<li class="level1"><div class="li"> <strong>pad</strong>: Une pastille est une zone de cuivre sur lequel un SMD sera soudé. Bien que les pastilles soient habituellement carrées, elles peuvent aussi être rondes.</div>
</li>
<li class="level1"><div class="li"> <strong>pin</strong>: Une patte/broche est un trou dans un circuit imprimé qui permet de connecter un composant câblé. Dans plusieurs cas, le trou est rempli de cuivre par le fabricant.</div>
</li>
<li class="level1"><div class="li"> <strong>pcb</strong>: Dans le contexte de gEDA, cet acronyme a deux significations distinctes:</div>
<ol>
<li class="level2"><div class="li"> Un abbréviation de « printed circuit board ». C’est la partie qui est utilisée pour connecter les composants électroniques. Elle est aussi quelque fois appelée une « carte de câblage imprimée » (PWB), bien que cette utilisation ait été abandonné.</div>
</li>
<li class="level2"><div class="li"> Un puissant outil open-source, utilisé pour concevoir la disposition d’un circuit imprimé. La sortie des outils de gaf peut être utilisée comme entrée à pcb. (<a href="http://pcb.sourceforge.net/index.html"; class="urlextern" title="http://pcb.sourceforge.net/index.html"; rel="nofollow">page d'accueil de pcb</a>)</div>
</li>
</ol>
</li>
<li class="level1"><div class="li"> <strong>rats nest</strong>: Les lignes dessinées sur la zone de travail du circuit, qui relient les pastilles devant encore être connectées avec des pistes. Contrairement aux pistes réelles, les rats nest sont des lignes droites. Si plusieurs pastilles sont impliquées dans un net, pcb tente de dessiner les rats nests avec les longueurs les plus courtes possibles.</div>
</li>
<li class="level1"><div class="li"> <strong>refdes</strong>: Raccourci pour « reference designator » (numéro de référence). Le numéro de référence (ou nom) d’un composant. Les outils gEDA se réfèrent aux refdes pour organiser les composants en internes. C’est la raison pour laquelle, pour une création réussie de circuit imprimé, chaque composant doit être lié avec un refdes. Habituellement, le refdes consiste quelques majuscules et un chiffre. Exemples: R1, R2, U115, CONN3. (Protel: « Designator »)</div>
</li>
<li class="level1"><div class="li"> <strong>slot</strong>: Quelques composants contiennent de multiples parties identiques à l’intérieur d’un boîtier. Les IO (Input/output, entrées/sorties) pour chaque partie sont disposées pour différents jeux de broches sur le boîtier. Un exemple classique est la quadruple porte NAND TTL 7400. Gschem (comme d’autres paquets de saisie de schéma) traite ce type de composant en vous permettant de dessiner quatre symboles NAND séparés et de sélectionner ensuite quel « slot » devrait avoir chaque symbole en attachant un attribut de slot au symbole. Dans l’exemple du quadruple NAND 7400, vous sélectionneriez « <code>slot=1</code> » pour la première apparition du symbole, slot=2 pour la seconde et ainsi de suite. Notez que dans gschem, vous n’avez besoin d’attacher les liaisons d’alimentation à un composant en slot qu’une seule fois. (Les autres programme de saisie de schéma comme Orcad vous demandent d’attacher les liaisons communes â?? comme l’alimentation â?? sur chaque instantiation du symbole en slot.)</div>
</li>
<li class="level1"><div class="li"> <strong>symbole</strong>: Un symbole est la représentation d’un composant particulier dans votre schéma. Les exemples classiques sont les lignes en zig-zag pour les résistances (dans l’utilisation US néanmoins) ou un triangle pour un ampli opérationnel. En utilisant un programme de saisie de schémas (i.e. gschem), vous placez les symboles sur votre carte et alors les câbler pour créer une représentation de votre circuit.</div>
</li>
<li class="level1"><div class="li"> <strong>via</strong>: Un via est un trou métallisé qui qui est destiné à connecter électriquement des différentes couches du circuit imprimé. Habituellement, les vias sont aussi petits que possible pour sauvegarder de la place sur le le pcb.</div>
</li>
</ul>
</div>
</div>
</body>
</html>
1.1 eda/geda/gaf/docs/wiki/geda_suse_rpm_installation.html
Index: geda_suse_rpm_installation.html
===================================================================
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en"
lang="en" dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>geda:suse_rpm_installation</title>
<meta name="generator" content="DokuWiki Release 2006-03-09" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
<link rel="contents" href="http://geda.seul.org/wiki/geda:suse_rpm_installation?do=index"; title="" />
<link rel="alternate" type="application/rss+xml" title="Recent Changes" href="http://geda.seul.org/wiki/feed.php"; />
<link rel="alternate" type="application/rss+xml" title="Current Namespace" href="http://geda.seul.org/wiki/feed.php?mode=list&ns=geda"; />
<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/geda:suse_rpm_installation?do=export_xhtml"; />
<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/geda:suse_rpm_installation?do=export_raw"; />
<meta name="date" content="2007-01-04T09:43:03-0500" />
<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>
<body>
<div class="dokuwiki export">
<div class="toc">
<div class="tocheader toctoggle" id="toc__header">Table of Contents</div>
<div id="toc__inside">
<ul class="toc">
<li class="level1"><div class="li"><span class="li"><a href="#installing_geda_rpm_packages_on_suse" class="toc">Installing gEDA rpm packages on SuSE</a></span></div>
<ul class="toc">
<li class="level2"><div class="li"><span class="li"><a href="#available_rpm_packages" class="toc">Available rpm packages</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#installing_packages_from_the_suse_build_service" class="toc">Installing Packages from the SuSE Build Service</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#distribution_specific_notes" class="toc">Distribution specific notes</a></span></div>
<ul class="toc">
<li class="level3"><div class="li"><span class="li"><a href="#suse_9.3" class="toc">SuSE 9.3</a></span></div></li>
<li class="level3"><div class="li"><span class="li"><a href="#suse_10.0" class="toc">SuSE 10.0</a></span></div></li>
<li class="level3"><div class="li"><span class="li"><a href="#suse_10.1" class="toc">SuSE 10.1</a></span></div></li>
<li class="level3"><div class="li"><span class="li"><a href="#suse_10.2" class="toc">SuSE 10.2</a></span></div></li></ul>
</li></ul>
</li></ul>
</div>
</div>
<h1><a name="installing_geda_rpm_packages_on_suse" id="installing_geda_rpm_packages_on_suse">Installing gEDA rpm packages on SuSE</a></h1>
<div class="level1">
</div>
<!-- SECTION [1-52] -->
<h2><a name="available_rpm_packages" id="available_rpm_packages">Available rpm packages</a></h2>
<div class="level2">
<ul>
<li class="level1"><div class="li"> libgeda (20061020)</div>
</li>
<li class="level1"><div class="li"> geda-docs (20061020)</div>
</li>
<li class="level1"><div class="li"> geda-examples (20061020)</div>
</li>
<li class="level1"><div class="li"> geda-gattrib (20061020)</div>
</li>
<li class="level1"><div class="li"> geda-gnetlist (20061020)</div>
</li>
<li class="level1"><div class="li"> geda-gschem (20061020)</div>
</li>
<li class="level1"><div class="li"> geda-gsymcheck (20061020)</div>
</li>
<li class="level1"><div class="li"> geda-symbols (20061020)</div>
</li>
<li class="level1"><div class="li"> geda-utils (20061020)</div>
</li>
<li class="level1"><div class="li"> gerbv (1.0.2)</div>
</li>
<li class="level1"><div class="li"> pcb (20060822)</div>
</li>
<li class="level1"><div class="li"> ng-spice-rework (17)</div>
</li>
<li class="level1"><div class="li"> gnucap (0.35)</div>
</li>
<li class="level1"><div class="li"> gspiceui (0.8.90)</div>
</li>
<li class="level1"><div class="li"> gwave (20051222)</div>
</li>
<li class="level1"><div class="li"> gtkwave (3.0.10)</div>
</li>
<li class="level1"><div class="li"> verilog (0.8.3)</div>
</li>
</ul>
</div>
<!-- SECTION [53-498] -->
<h2><a name="installing_packages_from_the_suse_build_service" id="installing_packages_from_the_suse_build_service">Installing Packages from the SuSE Build Service</a></h2>
<div class="level2">
<ol>
<li class="level1"><div class="li"> Start Yast and go to â??Change Installation Sourceâ??</div>
</li>
<li class="level1"><div class="li"> Add a <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> source with the following properties: </div>
<ul>
<li class="level3"><div class="li"> <strong>Servername:</strong> software.opensuse.org </div>
</li>
<li class="level3"><div class="li"> <strong>Directory:</strong> /download/repositories/home:/werner2101/openSUSE_10.2/ (Choose the directory for your distribution version) </div>
</li>
</ul>
</li>
<li class="level1"><div class="li"> Start â??Install Softwareâ?? in Yast, goto â??Searchâ?? and look for gEDA. All packages appear.</div>
</li>
<li class="level1"><div class="li"> Install the packages as usuall.</div>
</li>
</ol>
<p>
For more informations read the <a href="http://en.opensuse.org/Build_Service/User"; class="urlextern" title="http://en.opensuse.org/Build_Service/User"; rel="nofollow"> generic installation notes</a> of the <a href="http://en.opensuse.org/Build_Service"; class="urlextern" title="http://en.opensuse.org/Build_Service"; rel="nofollow"> OpenSuSE Build Service</a>
</p>
</div>
<!-- SECTION [499-1169] -->
<h2><a name="distribution_specific_notes" id="distribution_specific_notes">Distribution specific notes</a></h2>
<div class="level2">
<p>
Each distribution version has it’s own issues. Please read the notes below.
</p>
</div>
<!-- SECTION [1170-1287] -->
<h3><a name="suse_9.3" id="suse_9.3">SuSE 9.3</a></h3>
<div class="level3">
<ul>
<li class="level1"><div class="li"> <strong>YaST</strong> of SuSE 9.3 does not support yum repositories. Please use another installation utility like yum or smart instead.</div>
</li>
<li class="level1"><div class="li"> <strong>gSpiceUI</strong> not build for SuSE9.3. wxwidget package is missing.</div>
</li>
</ul>
</div>
<!-- SECTION [1288-1504] -->
<h3><a name="suse_10.0" id="suse_10.0">SuSE 10.0</a></h3>
<div class="level3">
</div>
<!-- SECTION [1505-1525] -->
<h3><a name="suse_10.1" id="suse_10.1">SuSE 10.1</a></h3>
<div class="level3">
</div>
<!-- SECTION [1526-1546] -->
<h3><a name="suse_10.2" id="suse_10.2">SuSE 10.2</a></h3>
<div class="level3">
<ul>
<li class="level1"><div class="li"> <strong>guile 1.8.1 problems</strong> SuSE 10.2 has a guile version 1.8.1. There are some problems with the netlist programms. Try to install guile version 1.6.7 instead.</div>
</li>
<li class="level1"><div class="li"> <strong>gwave cannot be build</strong>, it requires guile-gtk which requires libglade and gtk12. libglade is no longer part of the SuSE distribution.</div>
</li>
</ul>
</div>
<!-- SECTION [1547-] --></div>
</body>
</html>
_______________________________________________
geda-cvs mailing list
geda-cvs@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-cvs