Add a reminder about the activation context

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxPython/Phoenix/trunk@69810 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Robin Dunn
2011-11-24 01:41:52 +00:00
parent 617698bcd3
commit c6351e0d1a

View File

@@ -121,6 +121,16 @@ SIP already have a solution for this?
Win32 Activation Context
-------------------------
Port the code from Classic that creates the activation context for the
process. This is what is needed to make the themed version of the native
controls be used instead of the old Win2k style controls. There are a
couple tickets in Trac releated to the activation context, so look at those
and see if those issues are solveable in the Phoenix verison of the code.
Exceptions
----------
* Can we convert C++ exceptions to Python exceptions?
@@ -175,6 +185,31 @@ Deprecated C++ items
that will also be tagged as such in the XML?
other dev stuff
---------------
* data buffer support for wxImage RGB and alpha data
* port all of the wx.Bitmap copy-to and copy-from buffer methods, and
raw bitmap access routines from Classic.
* Come up with some way to implement the MustHaveApp check that
Classic does. It should raise an exception when something is
created/used that should not be done before there is an application
object.
* Should the functions created for things like addCppMethod be
marked static? How about using inline?
* 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.
Daily builds and releases
-------------------------
@@ -219,6 +254,8 @@ able to do full builds themselves. Specifically, we should:
Namespace Diff Tool
-------------------
I think that this will be more than just a diff tool, but for now that
@@ -279,26 +316,3 @@ way:
other stuff
------------
* data buffer support for wxImage RGB and alpha data
* port all of the wx.Bitmap copy-to and copy-from buffer methods, and
raw bitmap access routines from Classic.
* Come up with some way to implement the MustHaveApp check that
Classic does. It should raise an exception when something is
created/used that should not be done before there is an application
object.
* Should the functions created for things like addCppMethod be
marked static? How about using inline?
* 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.