Hi,
I will soon develop a new small application for a company, and I am considering to use wxPython. However, I don’t know if I should use the classic version, or the Phoenix one.
The classic version has not a lot of activity, and the development efforts seems to be focused on the Phoenix version. On the other side, the Phoenix version has still
no stable release.
So, is someone using wxPython Phoenix in production ? Is it really less stable than wxPython Classic ?
Hi,
Hi,
I will soon develop a new small application for a company, and I am considering to use wxPython. However, I don't know if I should use the classic version, or the Phoenix one.
The classic version has not a lot of activity, and the development efforts seems to be focused on the Phoenix version. On the other side, the Phoenix version has still no stable release.
So, is someone using wxPython Phoenix in production ? Is it really less stable than wxPython Classic ?
There are some controls/widgets still not wrapped and if you need the grid then it has some outstanding issues which might mean that it won't work for you (maybe look through the wxPython-dev list archive for threads having Phoenix in the subject).
I am in the process of converting my shareware to Phoenix, as far as wxPython is concerned I have no issues outstanding, but have some with others (XML tool I use and Dabo ReportWriter - although that one I think is mostly resolved). All changes I do in a why that the code still works with wxPython 2.9 and 3.0.2 Classic (i.e. just check for 'phoenix' in wx.PlatformInfo), so I can easily switch wxPython version and transition at my pace to Phoenix.
Werner
···
On 4/3/2015 12:12, Kévin Bernard-Allies wrote:
Thanks for your response.
Using Classic while preparing the transition is an interesting idea.
But it’s not a time consuming task ?
There seems to have not much differences between Classic and Phoenix.
Do you have a lot of if … else …, for supporting both versions ?
Or do you have automatized some parts ?
···
Le vendredi 3 avril 2015 15:29:47 UTC+2, werner a écrit :
Hi,
On 4/3/2015 12:12, Kévin Bernard-Allies wrote:
Hi,
I will soon develop a new small application for a company, and I am
considering to use wxPython. However, I don’t know if I should use the
classic version, or the Phoenix one.
The classic version has not a lot of activity, and the development
efforts seems to be focused on the Phoenix version. On the other side,
the Phoenix version has still no stable release.
So, is someone using wxPython Phoenix in production ? Is it really
less stable than wxPython Classic ?
There are some controls/widgets still not wrapped and if you need the
grid then it has some outstanding issues which might mean that it won’t
work for you (maybe look through the wxPython-dev list archive for
threads having Phoenix in the subject).
I am in the process of converting my shareware to Phoenix, as far as
wxPython is concerned I have no issues outstanding, but have some with
others (XML tool I use and Dabo ReportWriter - although that one I think
is mostly resolved). All changes I do in a why that the code still
works with wxPython 2.9 and 3.0.2 Classic (i.e. just check for ‘phoenix’
in wx.PlatformInfo), so I can easily switch wxPython version and
transition at my pace to Phoenix.
Werner
I had an existing shareware app based on classic 2.9.5. I didn’t
keep track on how much time I spent but I don’t think it was a lot.
I have about 50 if/else for this type of stuff:
if ‘phoenix’ in wx.PlatformInfo:
pyValidator = wx.Validator
else:
pyValidator = wx.PyValidator
if ‘phoenix’ in wx.PlatformInfo:
tctrl.SetToolTip(ctrl[‘toolt’])
else:
tctrl.SetToolTipString(ctrl[‘toolt’])
The line statistics for shareware are:
TOTAL: files: 175, classes: 303, defs: 1893, lines: 52167]
No automation at all.
Werner
···
Hi,
On 4/8/2015 10:38, Kévin Bernard-Allies wrote:
Thanks for your response.
Using Classic while preparing the transition is an interesting
idea.
But it's not a time consuming task ?
There seems to have not much differences between Classic and
Phoenix.
Do you have a lot of if … else … , for supporting
both versions ?
Or do you have automatized some parts ?