5b95b795cc
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@3822 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
213 lines
5.2 KiB
HTML
213 lines
5.2 KiB
HTML
<HTML>
|
|
<HEAD>
|
|
<TITLE>wxWindows Roadmap</TITLE>
|
|
</HEAD>
|
|
|
|
<BODY>
|
|
|
|
<a name="top"></a>
|
|
|
|
<font face="Arial, Lucida Sans, Helvetica">
|
|
|
|
<table width=100% border=4 cellpadding=5 cellspacing=0>
|
|
<tr>
|
|
<td bgcolor="#660000">
|
|
<font size=+1 face="Arial, Lucida Sans, Helvetica" color="#FFFFFF">
|
|
wxWindows Roadmap
|
|
</font>
|
|
</td>
|
|
</tr>
|
|
</table>
|
|
|
|
<P>
|
|
|
|
<CENTER>
|
|
<a href="#schedule">Schedule</a> | <a href="#todo">To-Do List</a>
|
|
</CENTER>
|
|
|
|
<P>
|
|
|
|
This page represents current thinking about where wxWindows is going in the near,
|
|
medium and long-term. It also serves as a schedule for new releases so
|
|
that both developers and users can know what to expect when, at least approximately.<P>
|
|
|
|
Note (1): as the wxWindows effort is voluntary, these are not hard-and-fast deadlines:
|
|
but we will endeavour to follow them as closely as possible.<P>
|
|
|
|
Note (2): the releases described are for wxGTK, wxMSW and wxMotif ports. wxMac currently follows
|
|
its own development path but is due to merge with the main code base in November/December.
|
|
Also, minor snapshot releases for specific platforms may be
|
|
available at dates convenient to the developers.<P>
|
|
|
|
<CENTER>
|
|
<HR> <FONT SIZE=+2><I><B><a name="schedule">Schedule</a></B></I></FONT> <HR>
|
|
</CENTER>
|
|
<P>
|
|
|
|
<H4>Release 2.0.?</H4>
|
|
|
|
<ul>
|
|
<li>Release date: October 3rd, 1999
|
|
<li>This beta is intended to be the last stable snapshot before wxWindows
|
|
is split into base and GUI libraries.
|
|
<li>New wxGrid in beta.
|
|
<li>wxWizard (beta)
|
|
<li>wxDialUpManager and wxPhoneDialer (beta)
|
|
<li>wxFontEnumerator (beta)
|
|
<li>Preliminary support for different encodings
|
|
<li>wxPostEvent function
|
|
</ul>
|
|
|
|
<P>
|
|
|
|
<H2>Release 2.1</H2>
|
|
|
|
<ul>
|
|
<li>Release date: November 7th, 1999
|
|
<li>Splits wxWindows into base and GUI libraries. Most, but not all makefiles
|
|
are expected to support this: for the rest, the makefiles will build a valid
|
|
combined base/GUI library for GUI applications only.
|
|
<li>New wxGrid.
|
|
<li>wxSocket working.
|
|
<li>Full support for fonts in different encodings
|
|
<li>Tested multithreading support (wxThread)
|
|
<li>wxHTML printing (possibly).
|
|
<li>Better i18n support (i.e. more translations)
|
|
<li>Animation classes (possibly, low priority).
|
|
<li>PCX writing capability (possibly, low priority).
|
|
<li>wxImage handlers in separate .h and .cpp files.
|
|
<li>Rewritten timer.cpp, possible wxChrono class.
|
|
<li>Bug tracking system in place.
|
|
</ul>
|
|
|
|
<P>
|
|
|
|
<H4>Release 2.1.1</H4>
|
|
|
|
<ul>
|
|
<li>Release date: January 9th, 2000
|
|
<li>Miscellaneous fixes and small enhancements.
|
|
</ul>
|
|
|
|
<P>
|
|
|
|
<H4>Release 2.1.2</H4>
|
|
|
|
<ul>
|
|
<li>Release date: March 5th, 2000
|
|
<li>Miscellaneous fixes and small enhancements.
|
|
<li>wxDateTime class in beta.
|
|
</ul>
|
|
|
|
<P>
|
|
|
|
<H4>Release 2.1.3</H4>
|
|
|
|
<ul>
|
|
<li>Release date: May 7th, 2000
|
|
<li>Unicode compilation starting to work in wxGTK and wxMSW.
|
|
</ul>
|
|
|
|
<P>
|
|
|
|
<H2>Release 2.2</H2>
|
|
|
|
<ul>
|
|
<li>Release date: c. July 2nd, 2000
|
|
<li>Unicode compilation working in wxGTK and wxMSW.
|
|
<li>wxDateTime class.
|
|
</ul>
|
|
|
|
<P>
|
|
|
|
<H2>Release 2.3</H2>
|
|
|
|
<ul>
|
|
<li>Release date: unknown
|
|
<li>WinCE port available.
|
|
</ul>
|
|
|
|
<P>
|
|
|
|
<CENTER>
|
|
<HR> <FONT SIZE=+2><I><B><a name="todo">To-Do List</a></B></I></FONT> <HR>
|
|
</CENTER>
|
|
|
|
<P>
|
|
|
|
Developers: please feel free to add to these, and delete them when they are done.
|
|
|
|
<P>
|
|
|
|
<B><I>General</I></B><P>
|
|
|
|
<ul>
|
|
<li>wxHTML printing. When finished, this will allow an application to generate
|
|
printed reports with very little effort.
|
|
<li>wxSocket.
|
|
<li>Split library into several, for base (classes and functions usable by console and GUI
|
|
applications), console (classes and functions usable by console application only)
|
|
and GUI (classes and functions usable by GUI application only).
|
|
<li>Extend and unify drag and drop handling (e.g. we need to specify multiple drop targets
|
|
that can handle multiple formats).
|
|
<li>Expand the number of controls that can be specified in a WXR file;
|
|
add constraint specification to WXR syntax and Dialog Editor; add multilanguage support to WXR.
|
|
May be we'd better change the format completely and replace WXR with XML
|
|
(providing conversion utility for old files)?
|
|
<li>Rewrite Dialog Editor.
|
|
<li>Modem-oriented classes: wxDialUpManager for dialing up the ISP and
|
|
determining if there is a connection to Internet on the machine and
|
|
wxPhoneDialer for dialing arbitrary phone numbers and otherwise communicating
|
|
with the modem.
|
|
<li>PCX writing code.
|
|
<li>GIF animation code.
|
|
<li>Tidying of timer code, addition of wxChrono class.
|
|
<li>Debug wxPostScriptDC further.
|
|
<li>wxDateTime class.
|
|
<li>Expansion of wxHTML to support further tags, and frames.
|
|
<li>MGL port (see Backroom/Future Ports page).
|
|
<li>Rotated text support.
|
|
<li>FreeType support.
|
|
<li>Support for 'skins', perhaps using a set of alternative control and window classes
|
|
written generically in wxWindows.
|
|
<li>Serial and parallel port support.
|
|
<li>Modem and telephony support.
|
|
<li>Book, tutorial.
|
|
<li>More examples.
|
|
</ul>
|
|
|
|
<P>
|
|
|
|
<B><I>wxMSW</I></B><P>
|
|
|
|
<ul>
|
|
<li>Windows CE port.
|
|
<li>Cure bug whereby in a panel within another panel, all buttons become
|
|
default buttons (heavy black border).
|
|
<li>Write a RC->WXR converter.
|
|
</ul>
|
|
|
|
<P>
|
|
|
|
<B><I>wxGTK</I></B><P>
|
|
|
|
<ul>
|
|
<li>GNOME/KDE integration libraries.
|
|
</ul>
|
|
|
|
<P>
|
|
|
|
<B><I>wxMotif</I></B><P>
|
|
|
|
<ul>
|
|
<li>Fix menu accelerators
|
|
<li>Fix refresh problems
|
|
<li>Allow wxSystemSettings to be configurable, perhaps via a control
|
|
panel application.
|
|
</ul>
|
|
|
|
|
|
</BODY>
|
|
</HTML>
|
|
|