Re: Phoenix: what happened to the wx.aui classes?
Werner <[email protected]>
| Newsgroups | gmane.comp.python.wxpython.devel |
|---|---|
| Message-ID | <[email protected]> |
On 4/27/2015 14:28, Const wrote: > > On Sunday, April 26, 2015 at 11:58:11 PM UTC-2:30, DevPlayer wrote: > > Just curious. Need a refresher. > . Const, why are you interested in the wx.Aui* over the > wx.agw.lib.aui? > > It's not a huge deal. I just feel more comfortable using the wrapped > wxWidgets (C++) core classes over the third-party "lib" classes. I > have no evidence to back this up, but my thinking is they might be > more robust, or more likely to be maintained, given they are a part of > the core wxWidgets classes. Will they perform better? I don't know, > but I like to think so, given they are implemented in C++. I also I > have wxPython 2.9 software that uses these classes which I want to > port to Phoenix. I know the API is probably the same between wx.Aui > and wx.agw.lib.aui, but I don't want to spend the time finding out > during a port. I haven't used wx.aui for a long time, but there was definitely a time where it had more bugs then the agw.aui version. Speed of C++ classes might be better, don't know if there is enough of a difference that you can notice it. The API should be the same so you should just have to change 'import wx.aui as aui' to 'import wx.lib.agw.aui as aui'. Werner -- You received this message because you are subscribed to the Google Groups "wxPython-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.