Re: Re: wxPython (Phoenix) fork for wxWidgets trunk version.
Svyatoslav Bulbakha <[email protected]>
| Newsgroups | gmane.comp.python.wxpython.devel |
|---|---|
| Message-ID | <[email protected]> |
Good news, thanks! Better HiDPI support and new wxNativeWindow is a really cool things and second one will allow to use all native components (hopes via pyobjc). Classic and Phoenix using different major versions of wxWidgets and I think there is no best way to do it. I will be really happy to help with Phoenix but still can't do more than just fix bugs. Maybe we must have some "Contributing" page with styleguides, etc. combined with issue tracker? вторник, 1 марта 2016 г., 3:32:12 UTC+7 пользователь Robin Dunn написал: > > Svyatoslav Bulbakha wrote: > > Really no one is not interested in porting python port to 3.1? :( > > суббота, 13 февраля 2016 г., 23:16:58 UTC+3 пользователь Svyatoslav > Bulbakha написал: >> >> Hi! >> >> I just forked Phoenix repo and adapted it for wxWidgets trunk version: >> https://github.com/ssbb/Phoenix >> >> I know that Robin don't want to start working 3.1 right now since Phoenix >> is not finished yet (there is a pull request from Aug 2014 with same >> purpose but for older wx version). >> >> But maybe someone will be interested and we can create a pull request >> later. >> >> I compiled it on OS X but Travis build passing too: >> https://travis-ci.org/ssbb/Phoenix >> >> For now I just added wxActivityIndicator since I am an interested in >> native NSProgressIndicator on OS X and need it for my current project. But >> also I am very interested in wxNativeWindow ( >> http://docs.wxwidgets.org/trunk/classwx_native_window.html) and >> hopefully will migrate it soon. >> >> >> > I've been considering switching over to wxWidgets trunk, especially since > the 3.1 release just happened. My only concern is having an easy migration > path for users from Classic. It seems to me that moving from Classic 3.0.x > to Phoenix 3.0.x would be easier than moving straight to Phoenix 3.1, or > maybe even being forced to wait until 3.2 for the "stable" version due to > policies set in their projects. And in order to provide that path I think > we need to have more of the remaining parts of Phoenix done, at least up to > a solid beta level. > > I'm wiling to hear and think about other opinions if anybody has strong > feelings about it and wants to try to persuade me. > > Another key factor for me is continuing build up my wxWidgets involvement > level again so I can get caught up and keep up with discussions and issues > in wx-dev, get some of my recent changes merged, etc. > > -- > Robin Dunn > Software Craftsman > http://wxPython.org > -- 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.