docs/html/roadmap.htm

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