Where are the wx.aui classes on Phoenix? I know about wx.agw.lib.aui, but I’m looking for the wrapped versions of wxWidgets wx.Aui* classes that existed in wxPython classic.
Thanks.
They are not yet wrapped, and not sure if Robin plans to wrap them.
Werner
···
On 4/23/2015 19:46, Const wrote:
Where are the wx.aui classes on Phoenix? I know about wx.agw.lib.aui, but I'm looking for the wrapped versions of wxWidgets wx.Aui* classes that existed in wxPython classic.
Just curious. Need a refresher.
. Const, why are you interested in the wx.Aui* over the wx.agw.lib.aui?
. 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?
···
On Thu, Apr 23, 2015 at 4:22 PM, Werner wernerfbd@gmx.ch wrote:
Where are the wx.aui classes on Phoenix? I know about wx.agw.lib.aui, but I’m looking for the wrapped versions of wxWidgets wx.Aui* classes that existed in wxPython classic.
On 4/23/2015 19:46, Const wrote:They are not yet wrapped, and not sure if Robin plans to wrap them.
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 wxPython-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Just curious. Need a refresher.
. Const, why are you interested in the wx.Aui* over the wx.agw.lib.aui?
. Werner (or anyone) Would the wx.Aui* not make it into Phoenix then if Robin doesn't wrap them?
unless someone else is doing the wrapping work.
. Wasn't wx.Aui a 3rd party add on and if so would it become one again?
I think you are correct that it was created as an external/3rd party add on to wxWidgets. If I understand correctly as far as wxWidgets is concerned wx.AUI is now an integral part of it and will 'not go external'.
. Werner (or anyone) Are there issues wrapping wx.Aui? Perhaps just not enough time or Mac compatibility?
I think one of the issues was that wx.AUI had no maintainer/was badly maintained. This might have changed, there was a 2009 Google Summer of Code project for it and I think sometimes last year someone picked that up and there is an AUI branch which is planned for 3.2 (wxTrac has been migrated to GitHub Issues - wxWidgets).
Werner
···
On 4/27/2015 4:28, Dev Player 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.
···
On Sunday, April 26, 2015 at 11:58:11 PM UTC-2:30, DevPlayer wrote:
. 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?
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
···
On 4/27/2015 14:28, Const wrote:
On Sunday, April 26, 2015 at 11:58:11 PM UTC-2:30, DevPlayerwrote:
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 usingthe 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.
Appreciated