<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- X-URL: http://bur-jud-118-039.rh.uchicago.edu/abiword/docs/roadmap -->
<!-- Date: Fri, 02 Jun 2000 20:45:21 GMT -->
<!-- Last-Modified: Tue, 13 Nov 2000 23:58:07 GMT -->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org" />
<base
href="http://bur-jud-118-039.rh.uchicago.edu/abiword/docs/roadmap" />
<title>AbiWord Roadmap</title>
</head>
<body>
<h2 align="Center">AbiWord Roadmap</h2>
<ul>
<li>Last updated: 13 Nov 2000, the current tarball is 0.7.12</li>
<li>Please see the explanatory <a href="#notes">notes</a> at the
bottom of this list.</li>
</ul>
<hr />
<table width="100%" border="1">
<tr align="CENTER">
<td width="25%"><b>0.9/1.0</b></td>
<td width="25%"><b>1.1/1.2</b></td>
<td width="25%"><b>Unknown</b></td>
<td width="25%"><b>Future</b></td>
</tr>
<tr>
<td>
<p>AbiWord will be at version 0.9 when it has [substantially] all
of the features we want in our "1.0" release. Accordingly, the list
below represents our current plan for the "1.0" feature set. This
list is still subject to a certain amount of change. However, most
of the features that we want for 1.0, have been done.</p>
<p>Note that our target feature set for version 1.0 is very basic.
<i>"Version 1.0 is the beginning, not the end."</i></p>
<p>After sufficient bug fixing on the 0.9 code base, we'll call it
1.0.0 and consider it to be a maintenance tree. When we're ready to
start adding post-1.0 features, we'll fork a new development tree
for the 1.1/1.2 series releases.</p>
</td>
<td>
<p>User feedback from the 1.0 release will be used to determine
priorities for the 1.2 release. The following list is extremely
tentative right now.</p>
</td>
<td>
<p>We're not quite sure where these features go yet.</p>
</td>
</tr>
<tr><!-- ********************** column 1 ********************** -->
<td valign="top">
<ul>
<li style="list-style: none">
<hr />
<b>Features</b><br />
</li>
<li>Finish headers and footers</li>
<li>DLOG: File/Page Setup (aka Format/Section) (with page margins,
size, orientation)</li>
<li>DLOG: Borders and Shading</li>
<li>DLOG: Styles</li>
<li>DLOG: Insert/Page Numbers</li>
<li>MacOS port (Hubert Figure)</li>
<li>Word 97 export (Dom Lachowicz)</li>
</ul>
</td>
<!-- ********************** column 2 ********************** -->
<td valign="top">
<ul>
<li>Context menu for images</li>
<li>Context cursors for image</li>
<li>switch to UTF-8 encoding for internal piece table storage</li>
<li>Cleanup mapping of Unicode encodings to font encodings,
focusing on: bullets, dashes, fancy quotation marks, symbols,
dingbats</li>
<li>tables</li>
<li>import/export WordPerfect</li>
<li>image resize. Involves the addition of "handles" on the corners
and edges of the image, when it's selected for resize. Requires
mouse interaction and drag code. This should be possible to do
entirely in XP code.</li>
<li>vertical keeps (partially done, in fb_ColumnBreaker.cpp)</li>
<li>horizontal keeps</li>
</ul>
</td>
<!-- ********************** column 3 ********************** -->
<td valign="top">
<ul>
<li>Qt port, anyone? <tt>:-)</tt></li>
<li>Inline marks for bookmarks, TOC, index, etc.</li>
<li>Calculation Editor</li>
<li>Database Integration</li>
<li>Gnome: Bonobo Integration</li>
<li>autosave</li>
<li>floats</li>
<li>improvements to RTF importer</li>
<li>Tip of the Day</li>
</ul>
</td>
<!-- ********************** column 4 ********************** -->
<td valign="top">
<ul>
<li>print preview (zoom works as a nice substitute)</li>
<li>normal view</li>
<li>drop caps</li>
<li>paragraph borders and shading</li>
<li>footnotes</li>
<li>outline mode</li>
<li>decimal-aligned tabs</li>
<li>Table of contents</li>
<li>macros and scripting</li>
<li>Multilingual document support for Hebrew, Arabic</li>
<li>Background color</li>
<li>Threads</li>
</ul>
</td>
</tr>
</table>
<hr />
<h3>Notes</h3>
<ul>
<li>This roadmap changes a lot. More specifically, the status and
plan for the project changes a lot, and this roadmap struggles to
keep up.</li>
<li>Version numbers use a scheme similar to the Linux kernel:
Major.Minor.Patch -- The Major version number indicates the overall
version of the app, with differences distinguishing very
substantial levels of features. The Minor version number indicates
an overall level of features within that Major version. Odd
numbered Minor versions are development releases which are not in
maintenance. A release with an even numbered Minor version
indicates a release which is believed to be stable and which will
be maintained even as development of the next version proceeds in a
separate source code tree.</li>
<li>There will not be a 0.8.0 release.</li>
<li>This is, in some sense, a To-Do list. However, since it does
not include a complete listing of bugs, it should not be regarded
as the only listing of work that needs to be done. The difference
between a bug and a missing feature can be subtle, at times. We
mention a specific bug here under certain circumstances, such as
when we know that we'll want it to be fixed for a certain release.
In general, you should check our <a
href="http://www.abisource.com/bugzilla/">bug database</a> for
additional information. The mention of specific bugs in association
with specific releases is not intended to imply that those are the
only bugs which will get fixed for that release.</li>
<li>In general, this list contains only work which is not yet done.
Once it's done, we remove it from this list. If it's partially
done, we'll remove it and replace it with a reminder of the part
that's not done yet. If you want a summary of what has already been
done, we'd suggest our <a href="http://www.abisource.com/bonsai">
Bonsai</a> or <a
href="http://www.abisource.com/mailinglists/abiword-dev/">archives
of the mailing list</a>.</li>
<li>If you see an email address specified in parenthesis after any
item, that's the person we believe is working on it, or who has
mentioned an intent to do so. If there's no email address there, we
probably don't know who's doing it. Contributors welcome, AbiWord
is a <a
href="http://www.tuxedo.org/~esr/writings/cathedral-bazaar/index.html">
Bazaar</a>.</li>
<li>Please notify the mailing list if you see anything on this list
which is inaccurate or out-of-date.</li>
<li>If you want to work on something, please mention your intent to
do so on the mailing list. This will allow us to avoid clashes and
keep this roadmap up to date. Also, most of the features mentioned
below have had at least some discussion, so there is a history of
assumptions about how each feature should work. We don't have a
full, written spec for the behavior of everything, so if you want
to uncover those assumptions, you'll have to ask. <tt>:-)</tt></li>
<li>The project mailing list is <a
href="mailto:abiword-dev@abisource.com">
abiword-dev@abisource.com</a>.</li>
</ul>
</body>
</html>
