]> git.saurik.com Git - wxWidgets.git/blame_incremental - docs/html/roadmap.htm
clean up of memory debugging macros and chanegs to compile with CW7 (patch 548408)
[wxWidgets.git] / docs / html / roadmap.htm
... / ...
CommitLineData
1<HTML>
2<HEAD>
3 <TITLE>wxWindows Roadmap</TITLE>
4</HEAD>
5
6<BODY>
7
8<a name="top"></a>
9
10<font face="Arial, Lucida Sans, Helvetica">
11
12<table width=100% border=0 cellpadding=3 cellspacing=0>
13<tr>
14<td bgcolor="#004080" align=left height=24 background="images/bluetitlegradient.gif">
15<font size=+1 face="Arial, Lucida Sans, Helvetica" color="#FFFFFF">
16<b>wxWindows Roadmap</b>
17</font>
18</td>
19</tr>
20</table>
21
22<P>
23
24<CENTER>
25<a href="#schedule">Schedule</a> | <a href="#todo">To-Do List</a>
26</CENTER>
27
28<P>
29
30This page represents current thinking about where wxWindows is going in the near,
31medium and long-term. It also serves as a schedule for new releases so
32that both developers and users can know what to expect when, at least approximately.<P>
33
34We are adopting the Linux kernel style of numbering system where odd minor version numbers are development
35versions, and even numbers are stable versions. For example, 2.1.x are development releases,
36and the next 'stable' or final release of it would be 2.2.<P>
37
38Bug-fix patches to the stable release (if made) then become point
39releases of 2.2 (2.2.x) while development continues with wild abandon
40on 2.3.x until the end of the next development cycle when it is
41released as 2.4.<P>
42
43Development versions that end up on the FTP site or CD-ROM, as opposed to remaining
44in the CVS archive, are semi-stable -- i.e. they are checked for compilation and
45run-time problems, but not as thoroughly as the stable versions.<P>
46
47Note that since the wxWindows effort is voluntary, these are not hard-and-fast deadlines:
48but we will endeavour to follow them as closely as possible.<P>
49
50Note also that the releases described are for wxGTK, wxMSW and wxMotif ports. wxMac currently follows
51its own development path but is due to merge with the main code base in November/December.
52Also, minor snapshot releases for specific platforms may be
53available at dates convenient to the developers.
54
55Finally, this page only shows the things which are still left to do, please
56look elsewhere to see the complete list of changes between the releases,
57including the things which are already done.
58<P>
59
60<CENTER>
61<HR> <FONT SIZE=+2><I><B><a name="schedule">Schedule</a></B></I></FONT> <HR>
62</CENTER>
63<P>
64
65<H4>Release 2.4.0 (stable)</H4>
66
67Release date: Summer 2002?
68
69<p>
70
71Stable version of 2.3.
72
73<ol>
74 <li>Very important
75 <ul>
76 <li>wxMac: make the release together with the other ports
77 <li>Fix wxStream::Eof() problems
78 <li>wxGTK: GTK+ 2.0 support
79 </ul>
80
81 <li>Important
82 <ul>
83 <li>(Unix) implement <tt>wx-config</tt> as a version and build
84 parameters independent script which would just read the
85 configuration files
86 <li>Finish wxFileName
87 <li>Make it possible to process the key strokes portably
88 <li>Add wxSemaphor, fix wxCondition
89 </ul>
90
91 <li>Nice to have
92 <ul>
93 <li>support for text in the wxToolBar buttons
94 <li>radio buttons in wxToolBar
95 <li>possibility to use individual wxUniv controls from the native
96 ports
97 </ul>
98</ol>
99
100<P>
101
102<H4>Release 3.0.0 (stable)</H4>
103
104This release should finally mark the end of support for the antiquated
105compilers without decent support of the modern C++ features such as templates,
106exceptions and namespaces. wxWindows containers should be replaced with the
107corresponding standard library classes and <tt>std::basic_string&lt;&gt;</tt>
108should be used instead of <tt>wxString</tt>.
109
110<p>
111
112<CENTER>
113<HR> <FONT SIZE=+2><I><B><a name="todo">To-Do List</a></B></I></FONT> <HR>
114</CENTER>
115
116<P>
117
118This is just a collection of the various things which it would be nice to
119include in wxWindows but which are not actively worked on right now and for
120which no schedule is fixed yet. If you're interested in helping with wxWindows
121development, one of the small projects below could be a great way to join the
122team!
123
124<p>
125Developers: please feel free to add to these, and delete them when they are done.
126
127<P>
128
129<B><I>General</I></B><P>
130
131<ul>
132<li>A rich text editor similar to GTK+ 2.0 GtkTextView but cross-platform
133<li>Extend and unify drag and drop handling (e.g. we need to specify multiple drop targets
134that can handle multiple formats).
135<li>Support for 'skins', perhaps using a set of alternative control and window classes
136written generically in wxWindows.
137<li>Serial and parallel port support.
138<li>Modem and telephony support.
139<li>Book, tutorial.
140<li>More examples.
141</ul>
142
143<P>
144
145<B><I>wxMSW</I></B><P>
146
147<ul>
148<li>Windows CE port.
149</ul>
150
151<P>
152
153<B><I>wxGTK</I></B><P>
154
155<ul>
156<li>Full Unicode support using GTK+ 2.0
157<li>Wrap the new GTK+ 2.0 GtkTextView powerful widget
158<li>GNOME/KDE integration libraries.
159</ul>
160
161<P>
162
163</BODY>
164</HTML>
165