mirror of
https://github.com/wxWidgets/Phoenix.git
synced 2025-12-16 09:40:07 +01:00
Added notes about additional TODO's needed for the core modules, etc.
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxPython/Phoenix/trunk@69975 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
73
TODO.txt
73
TODO.txt
@@ -129,6 +129,11 @@ build.py
|
||||
unnecesary rebuilds.
|
||||
|
||||
|
||||
Deprecated C++ items
|
||||
---------------------
|
||||
* Does Doxygen have a standard way to mark items as deprecated
|
||||
that will also be tagged as such in the XML?
|
||||
|
||||
|
||||
wxProgressDialog
|
||||
----------------
|
||||
@@ -136,25 +141,6 @@ wxProgressDialog
|
||||
* and wxProgressDialog inherits from the generic version
|
||||
|
||||
|
||||
Generated Unitests
|
||||
------------------
|
||||
* Autogenerate a skeleton unittest module for each etg module.
|
||||
* It can traverse the items in the module object and use a test
|
||||
template based on what kind of item it is. Templates could
|
||||
include toplevel window tests, non-toplevel window, event
|
||||
binder, event class, etc.
|
||||
* If the file already exists then don't overwrite it. Or perhaps
|
||||
we could have a "# AUTOGENERATED" tag in the file that means that
|
||||
it can be overwritten. If a human wants to take over the file and
|
||||
add additional tests then they just need to remove that tag.
|
||||
|
||||
|
||||
|
||||
Deprecated C++ items
|
||||
---------------------
|
||||
* Does Doxygen have a standard way to mark items as deprecated
|
||||
that will also be tagged as such in the XML?
|
||||
|
||||
|
||||
other dev stuff
|
||||
---------------
|
||||
@@ -174,10 +160,51 @@ other dev stuff
|
||||
|
||||
* Word-wrap the briefDoc strings used for %Docstring directives
|
||||
|
||||
* It looks like the code that is flattening the element nodes to
|
||||
extract the briefDocs is not getting some spaces that should be in
|
||||
there, probably where some tags are being removed.
|
||||
|
||||
* For full coverage of what is in Classic core modules ETG files
|
||||
are needed for:
|
||||
* filesys, fs_mem, fs_inet, fs_arch (with wxZipFSHandler typedef)
|
||||
* versioninfo
|
||||
* popupwin
|
||||
* tipwin
|
||||
* vscroll
|
||||
* taskbar
|
||||
* all missing common dialogs
|
||||
* print (as in print framework classes)
|
||||
* mdi (die mdi! die!)
|
||||
* scrollbar
|
||||
* toolbar
|
||||
* listctrl
|
||||
* treectrl
|
||||
* dirctrl
|
||||
* cshelp
|
||||
* dragimag
|
||||
* datectrl
|
||||
* hyperlink
|
||||
* pickerbase, clrpicker, filepicker, fontpicker
|
||||
* filectrl
|
||||
* infobar
|
||||
* commandlinkbutton
|
||||
* axbase
|
||||
* settings
|
||||
* sysopt
|
||||
* tipdlg
|
||||
* check for items missing from _functions.i and _misc.i
|
||||
* joystick
|
||||
* sound
|
||||
* mimetype
|
||||
* artprov
|
||||
* datetime, or make it be a MappedType for Python date objects?
|
||||
* clipbrd, dnd, finish dataobj
|
||||
* power
|
||||
* about
|
||||
* uiaction
|
||||
|
||||
|
||||
|
||||
* Divide Phoenix core into multiple modules. Perhaps using the same
|
||||
divisions that a wx multi-lib build uses would be a good idea.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user