Where would I find this now, I couldn't find any reference to it in the migration guide, have I missed something?
···
--
My fellow Pythonistas, ask not what our language can do for you, ask what you can do for our language.
Mark Lawrence
Mark Lawrence wrote:
Where would I find this now, I couldn't find any reference to it in the
migration guide, have I missed something?
No, it hasn't been wrapped yet. I'm debating doing it though since the C++ code still isn't being maintained, although it does seem to be getting a little more attention recently, and most Python people prefer the AGW version of AUI.
There are also a couple other extension modules still on the Phoenix TODO list. wx.richtext needs to be finished up (including unittests and demos), wx.media needs added, I think I'll add a wx.msw module for some Windows-only classes, and I need to decide if wx.propgrid will be included. (Again there is some stagnation on the C++ side of the house there, but there isn't a Python implementation to fall back on for this one.)
···
--
Robin Dunn
Software Craftsman
I love the property grid. Hope it finds it’s way in.
That is the biggest complaint I hear from other people.
Basically there is a ass-load of fixs submitted and whoever is in control on the C++ side doesn’t have much motivation or it just isn’t being “maintained” anymore.
Most of these complainer have since moved onto QT, which isn’t a good thing in regards to wx in general.
Now I hear them complain about what features QT doesn’t support that AUI had.
Geez… winers.
As far as AUI I believe it should stay on the list to port. I personally use AGW solely for the extra features and bug fixes “support”(maintained).
Otherwise I would use AUI for the speed/performance benefits.
As far as property grid… What ever happened to Cody’s GUI builder project he had some basic info/previews about.???
I have some code starting a similar to wxFormBuilder project written in wxPython for wxPython.
So yes, I see the PropertyGrid module necessary if you ever want to see someone make a GUI builder similar to what QT has right out of the box eventually.
Maybe someone will also make a python port similar to Andreas AGW AUI someday. Who knows.
Also, separating the Operating specific stuff into their own named modules is a good start.
I try to do a similar approach for my projects. Ex: MSWindowsModule, MacModule, LinuxModule.
···
On Saturday, January 4, 2014 4:21:36 AM UTC-6, Robin Dunn wrote:
Mark Lawrence wrote:
Where would I find this now, I couldn’t find any reference to it in the
migration guide, have I missed something?
No, it hasn’t been wrapped yet. I’m debating doing it though since the
C++ code still isn’t being maintained, although it does seem to be
getting a little more attention recently, and most Python people prefer
the AGW version of AUI.There are also a couple other extension modules still on the Phoenix
TODO list. wx.richtext needs to be finished up (including unittests and
demos), wx.media needs added, I think I’ll add a wx.msw module for some
Windows-only classes, and I need to decide if wx.propgrid will be
included. (Again there is some stagnation on the C++ side of the house
there, but there isn’t a Python implementation to fall back on for this
one.)–
Robin DunnSoftware Craftsman