Re: Phoenix: what happened to the wx.aui classes?
Const <[email protected]>
| Newsgroups | gmane.comp.python.wxpython.devel |
|---|---|
| Message-ID | <[email protected]> |
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. > . Werner (or anyone) Would the wx.Aui* not make it into Phoenix then if > Robin doesn't wrap them? > . Wasn't wx.Aui a 3rd party add on and if so would it become one again? > . Werner (or anyone) Are there issues wrapping wx.Aui? Perhaps just not > enough time or Mac compatibility? > -- 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.