<!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:todos</title> <meta name="generator" content="DokuWiki Release rc2007-05-24" /> <meta name="robots" content="index,follow" /> <meta name="date" content="2007-08-23T09:28:32-0400" /> <meta name="keywords" content="geda,todos" /> <link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php" title="geda Wiki" /> <link rel="start" href="http://geda.seul.org/wiki/" /> <link rel="contents" href="http://geda.seul.org/wiki/geda:todos?do=index" title="Index" /> <link rel="alternate" type="application/rss+xml" title="Recent Changes" href="http://geda.seul.org/wiki/feed.php" /> <link rel="alternate" type="application/rss+xml" title="Current Namespace" href="http://geda.seul.org/wiki/feed.php?mode=list&ns=geda" /> <link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:todos" /> <link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:todos" /> <link rel="stylesheet" media="all" type="text/css" href="lib/exe/css" /> <link rel="stylesheet" media="screen" type="text/css" href="lib/exe/001css" /> <link rel="stylesheet" media="print" type="text/css" href="lib/exe/002css" /> </head> <body> <div class="dokuwiki export"> <div class="toc"> <div class="tocheader toctoggle" id="toc__header">Table of Contents</div> <div id="toc__inside"> <ul class="toc"> <li class="level1"><div class="li"><span class="li"><a href="#todo" class="toc">ToDo</a></span></div> <ul class="toc"> <li class="level2"><div class="li"><span class="li"><a href="#things_to_be_done_before_the_next_release" class="toc">Things to be done before the next release</a></span></div></li> <li class="level2"><div class="li"><span class="li"><a href="#longer_term_upgrades_desired_for_specific_tools" class="toc">Longer term upgrades desired for specific tools</a></span></div></li> <li class="level2"><div class="li"><span class="li"><a href="#ideas_for_new_tools_or_geda_suite-wide_enhancements" class="toc">Ideas for new tools or gEDA Suite-wide enhancements</a></span></div></li> <li class="level2"><div class="li"><span class="li"><a href="#code_cleanup_and_refactoring" class="toc">Code cleanup and refactoring</a></span></div></li></ul> </li></ul> </div> </div> <h1><a name="todo" id="todo">ToDo</a></h1> <div class="level1"> <p> These lists are meant to provide developers a reminder of undone projects. It is also a wish list capturing user’s desires for new features. New developers can also look here for projects which they might be interested in working on. </p> <p> See <a href="http://geda.seul.org/wiki/geda:tasks" class="wikilink1" title="geda:tasks">tasks</a> for non-programmer tasks. </p> </div> <!-- SECTION "ToDo" [1-298] --> <h2><a name="things_to_be_done_before_the_next_release" id="things_to_be_done_before_the_next_release">Things to be done before the next release</a></h2> <div class="level2"> <ul> <li class="level1"><div class="li"> TBD</div> </li> </ul> </div> <!-- SECTION "Things to be done before the next release" [299-362] --> <h2><a name="longer_term_upgrades_desired_for_specific_tools" id="longer_term_upgrades_desired_for_specific_tools">Longer term upgrades desired for specific tools</a></h2> <div class="level2"> <ul> <li class="level1"><div class="li"> <strong>Libgeda</strong>:</div> <ul> <li class="level2"><div class="li"> Enable handling of .sch files with symbols having some (but not all) pins promoted onto the .sch file. This will enable pin-swapping via backannotation from PCB</div> </li> <li class="level2"><div class="li"> Merge per-page netlisting from gnetlist (or re-write if necessary).</div> </li> <li class="level2"><div class="li"> Make postscript output more friendly to the LaTeX package “pstricks”.</div> <ul> <li class="level3"><div class="li"> Use the “show” command to display a whole string at once instead of rendering character by character.</div> </li> <li class="level3"><div class="li"> Might not be possible / simple as the current approach is due to the overbar drawing postscript.</div> </li> </ul> </li> </ul> </li> <li class="level1"><div class="li"> <strong>Gschem</strong>:</div> <ul> <li class="level2"><div class="li"> Enable hierarchical bus support.</div> </li> <li class="level2"><div class="li"> Make gschemrc variables settable from within gschem using a “settings” pull-down menu item (new).</div> </li> <li class="level2"><div class="li"> Improve symbol library to handle very large symbol collections better</div> </li> <li class="level2"><div class="li"> Now the SELECTION is a GedaList and we can get “changed” signals, make more dialogs non-modal:</div> <ul> <li class="level3"><div class="li"> Single attribute editor</div> </li> <li class="level3"><div class="li"> Text properties</div> </li> <li class="level3"><div class="li"> Line width and type</div> </li> <li class="level3"><div class="li"> Fill type</div> </li> <li class="level3"><div class="li"> Edit slot</div> </li> <li class="level3"><div class="li"> Edit color</div> </li> <li class="level3"><div class="li"> Text size (Sets size for new text, so doesn’t rely on the selection anyway)</div> </li> </ul> </li> <li class="level2"><div class="li"> Enable <strong><code>-</code><code>-</code>help</strong> flag. (Currently supports -h only). Consider using GTK’s mechanism for this.</div> </li> <li class="level2"><div class="li"> Support for embedding LaTeX maths to be rendered in text.</div> <ul> <li class="level3"><div class="li"> This could be output only, or preview bitmaps could be generated and cached by calling LaTeX, dvips and ps2epsi.</div> </li> <li class="level3"><div class="li"> Would we add a new type of object for this, or allow attaching a “latex=1” attribute to the text object its self?</div> </li> </ul> </li> </ul> </li> <li class="level1"><div class="li"> <strong>Gnetlist</strong>:</div> <ul> <li class="level2"><div class="li"> Enable <strong><code>-</code><code>-</code>help</strong> flag. Do other gEDA/gaf programs recognize this flag?</div> </li> </ul> </li> <li class="level1"><div class="li"> <strong>Gattrib</strong>:</div> <ul> <li class="level2"><div class="li"> Make it export CSV to support BOM generation.</div> </li> <li class="level2"><div class="li"> Get printing working.</div> </li> <li class="level2"><div class="li"> Enable attachment of attributes to nets.</div> </li> <li class="level2"><div class="li"> Consider using GTK’s mechanism to display <strong><code>-</code><code>-</code>help</strong> flag text.</div> </li> </ul> </li> <li class="level1"><div class="li"> <strong>Garchive</strong>:</div> <ul> <li class="level2"><div class="li"> Incorporate guile so that it reads RC files using the same mechanism as the rest of gEDA/gaf.</div> </li> </ul> </li> <li class="level1"><div class="li"> <strong>CD Installer</strong>:</div> <ul> <li class="level2"><div class="li"> Change it so that the user is presented a pick-list at the beginning of the install, instead of blindly installing everything.</div> </li> </ul> </li> <li class="level1"><div class="li"> <strong>Refdes_renum</strong>:</div> <ul> <li class="level2"><div class="li"> Doesn’t currently work properly with slotted parts (it gives new refdes numbers to slotted parts). Fix it so it recognizes slotted parts and assigns refdes appropriately.</div> </li> <li class="level2"><div class="li"> Provide <strong><code>-</code><code>-</code>gentle</strong> option, which doesn’t clobber (overwrite) any refdeses which are already assigned.</div> </li> </ul> </li> </ul> </div> <!-- SECTION "Longer term upgrades desired for specific tools" [363-2872] --> <h2><a name="ideas_for_new_tools_or_geda_suite-wide_enhancements" id="ideas_for_new_tools_or_geda_suite-wide_enhancements">Ideas for new tools or gEDA Suite-wide enhancements</a></h2> <div class="level2"> <ul> <li class="level1"><div class="li"> Develop scheme for backward annotation of changes from PCB to gschem. Requires modifications to libgeda to support, e.g. pin promotion from .sym file to .sch file (enabling pin swapping).</div> </li> <li class="level1"><div class="li"> Create a Gerber → .pcb conversion tool. Result is metal layer or footprint editable by PCB. This might be a <acronym title="Practical Extraction and Report Language">Perl</acronym> script.</div> </li> <li class="level1"><div class="li"> Implement lockfiles between gattrib and gschem.</div> </li> </ul> </div> <!-- SECTION "Ideas for new tools or gEDA Suite-wide enhancements" [2873-3309] --> <h2><a name="code_cleanup_and_refactoring" id="code_cleanup_and_refactoring">Code cleanup and refactoring</a></h2> <div class="level2"> <ul> <li class="level1"><div class="li"> Remove use of non GList linked lists. This is very invasive work, but allows much code cleanup where mixtures of the old and GList methods were available.</div> </li> <li class="level1"><div class="li"> Remove unused variables and functions from various structures. Unused may also include “used”, but ineffective.</div> </li> <li class="level1"><div class="li"> Remove back-exports to libgeda of global function pointers from gschem and other libgeda “clients”. These aren’t portable.</div> </li> <li class="level1"><div class="li"> Clean up / produce generic <acronym title="Application Programming Interface">API</acronym> interfaces to act on an object of any type, or lists of objects.</div> </li> <li class="level1"><div class="li"> Convert functions used within one ".c” file, and not useful for public <acronym title="Application Programming Interface">API</acronym> into static functions, removing from prototype.h.</div> </li> </ul> </div> <!-- SECTION "Code cleanup and refactoring" [3310-] --></div> </body> </html>
distrib
>
Mandriva
>
2010.0
>
i586
>
media
>
contrib-release
>
by-pkgid
>
917b12189aa1c35ab526605d1d1ac12b
>
files
>
282
