docs/wiki/gtkwave-projects.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   2  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   3 <html>
   4 <head>
   5   <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
   6   <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
   7   <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
   8
   9   <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
  10 </head>
  11 <body>
  12
  13 <h3 class="sectionedit1" id="gtkwave_projects">GTKWave projects</h3>
  14 <div class="level3">
  15 <ul>
  16 <li class="level1"><div class="li"> System Verilog and/or VHDL support for RTLBrowse.  Currently it&#039;s only plain-vanilla verilog from the 1995 <abbr title="specification">spec</abbr>.</div>
  17 </li>
  18 </ul>
  19 <ul>
  20 <li class="level1"><div class="li"> More “interesting” integrations with other tools.  The new Tcl interface adds a bunch of possibilities.  I know one guy is using it to allow remote control from emacs through a bridge server.</div>
  21 </li>
  22 </ul>
  23 <ul>
  24 <li class="level1"><div class="li"> Improved analog support.  This would also mean being able to read various spice rawfiles, etc.</div>
  25 </li>
  26 </ul>
  27 <ul>
  28 <li class="level1"><div class="li"> An open source equivalent to FSDB in terms of speed, file size, and capabilities of the different types of data it can store.  This wouldn&#039;t necessarily be a gtkwave-only project given that I&#039;d expect a reader/writer <abbr title="Application Programming Interface">API</abbr> that for example, icarus/ghdl and gtkwave can interface to.  This is the most challenging of the bunch and would require not only coding, but lots of experimentation + throwing away code + restarting over when it&#039;s realized a better way can be used to do something.</div>
  29 </li>
  30 </ul>
  31
  32 </div>
  33 </body>
  34 </html>