1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
|
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<html> <head>
<title>Epydoc: Future Directions</title>
<link rel="stylesheet" href="epydoc.css" type="text/css"/>
</head>
<!-- $Id: future.html 1211 2006-04-10 19:38:37Z edloper $ -->
<body>
<div class="body">
<h1> Epydoc: Future Directions </h1>
<h2> Short Term </h2>
<p> Epydoc version 3.0 is currently in alpha release. My current
plans for the near future include: </p>
<ul>
<li> Improve support for graph generation. </li>
<li> Work on plaintext output. </li>
<li> Profiling </li>
<li> More regression tests </li>
<li> Add support for generating indices of bugs, todo items,
etc. </li>
<li> Add an <code>@ingroup</code> tag.
<li> Release epydoc 3.0. </li>
</ul>
<h2> Long Term </h2>
<p> Things I'd eventually like to see in epydoc include: </p>
<ul>
<li> Change the epytext parser to use simple classes instead
of DOM. </li>
<li> Output to man (troff)? </li>
<li> Output to docbook or directly to pdf? </li>
</ul>
</div>
<table width="100%" class="navbox" cellpadding="1" cellspacing="0">
<tr>
<a class="nav" href="index.html">
<td align="center" width="20%" class="nav">
<a class="nav" href="index.html">
Home</a></td></a>
<a class="nav" href="installing.html">
<td align="center" width="20%" class="nav">
<a class="nav" href="installing.html">
Installing Epydoc</a></td></a>
<a class="nav" href="using.html">
<td align="center" width="20%" class="nav">
<a class="nav" href="using.html">
Using Epydoc</a></td></a>
<a class="nav" href="epytext.html">
<td align="center" width="20%" class="nav">
<a class="nav" href="epytext.html">
Epytext</a></td></a>
<td align="center" width="20%" class="nav">
<A href="http://sourceforge.net/projects/epydoc">
<IMG src="sflogo.png"
width="88" height="26" border="0" alt="SourceForge"
align="top"/></A></td>
</tr>
</table>
</body>
</html>
|
