| | 1 | Adding a wxWidgets contribution |
| | 2 | =============================== |
| | 3 | |
| | 4 | Here are some different kinds of contribution: |
| | 5 | |
| | 6 | 1. Bug fixes. You can send these to the wx-dev list. |
| | 7 | |
| | 8 | 2. New classes. They should go somewhere in the wxWidgets |
| | 9 | hierarchy if they are deemed to be 'core', otherwise they |
| | 10 | could be placed in external repositories of wxWidgets |
| | 11 | utilities, like wxCode (see http://wxcode.sf.net). |
| | 12 | |
| | 13 | 3. A utility application, such as a new dialog editor or |
| | 14 | file format conversion utility. If adding to the SVN |
| | 15 | archive, you may put it under the utils hierarchy, |
| | 16 | preferably with further src and docs directories. |
| | 17 | |
| | 18 | You may or may not wish to add your code to the main wxWidgets SVN |
| | 19 | archive. Whether your code is appropriate for this archive |
| | 20 | should first be ascertained by discussing it on wx-dev@wxwidgets.org. |
| | 21 | |
| | 22 | Also, in order to be included in wxWidgets, your code should |
| | 23 | follow the wxWidgets coding conventions |
| | 24 | (see http://www.wxwidgets.org/develop/standard.htm) and fit in the |
| | 25 | wxWidgets src, include, docs directories hierarchy. |
| | 26 | |
| | 27 | |
| | 28 | Author: Julian Smart |
| | 29 | |
projects / wxWidgets.git / blame_incremental