wxWindows 2.5 Migration

This will be a page describing what will be involved in moving from wxWindows 2.4.2.4 to wxWindows 2.5.

Current plan

• See what changes we have made to wx
• Import wxWindow 2.5 to code (in different directory from current wxWindows code)
• Do a branch so that Jed (and others) can update Chandler to use 2.5 while allowing others to continue working on head
• Do a merge of 2.5 branch into head once it is stable

Issues

• Module Initialization
  • This should allow Morgen to more easily test files that import wxPython
  • This shouldn't require many (if any) changes, but I have to research more to be sure

• SWIG 1.3
  • All classes are now "new-style" classes
  • We may have to rework any overrides we do over getattr and setattr of wxPython classes
  • We will have to change any references to wxFooPtr classes
  • Difficulty: 4/10 with some uncertainty factor

• Binding Events
  • No changes required, but there are improvements we should take advantage of
  • We should move event bindings to the new style
  • Difficulty: 2/10

• wx Namespace
  • This should require relatively few changes as backward compatibility is provided.
  • That being said, compatibility is not perfect or guaranteed
  • We should probably migrate to the new style
  • Difficulty: 2/10 (required), 6/10 to get it right

• New wx.DC Methods
  • I don't know how much we are using dc methods, but the transition seems straightforward
  • How we adjust this depends on whether we move to the new wx namespace
  • Difficulty: 3/10

• Building, extending, and embedding wxPython
  • We will have to build additional libraries
  • We will have to add things to our path
  • Difficulty: 3/10

• Two (or Three) Phase Create
  • We barely take advantage of this feature and I think we can get away with not touching this for now
  • Difficulty: 0/10

• Sizers
  • Minor changes
  • I don't think we currently use the option keyword
  • Difficulty: 2/10

• Other Stuff
  • I believe we use wxPyDefaultPosition (has to be renamed)
  • We should remove references to NO_FULL_REPAINT_ON_RESIZE
  • Difficulty: 2/10

References

• 2.5 Migration

-- JedBurgess - 11 Mar 2004