I don't understand your point, but I think Robin need to said something at this point.
AFAIR, Robin has been hired to work on QtSomething
and voiced his general willingness to look at
wxPython issues as time allows.
Time doesn't allow, apparently (which is fine). I
think we need to also strongly investigate non-Robin
solutions.
Karsten
I’d like to add this tip since this thread is read by many people. Please, if you can, change your default notification settings so that you can receive all postings in this group. This way, we can help each other by seeing all emails and issues.
Click on My groups
Change the email setting to All email
See picture below.
On Thu, Apr 28, 2016 at 3:49 AM, Karsten Hilbert Karsten.Hilbert@gmx.net wrote:
I don’t understand your point, but I think Robin need to said something at this point.
AFAIR, Robin has been hired to work on QtSomething
and voiced his general willingness to look at
wxPython issues as time allows.
Time doesn’t allow, apparently (which is fine). I
think we need to also strongly investigate non-Robin
solutions.
Karsten
–
You received this message because you are subscribed to the Google Groups “wxPython-users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
no, not really -- but it does need maintenance. Every software project does
-- we WILL need to go to py3 at some point, and at the wxWidgets level,
bugs will crop up with each new version of the OSs.
It is too bad that wxPython has been a one-person project for so long (Not
completely, there have been a few folks that have contributed core code or
core bug fixes, but close)
But it's a pretty complicated piece of software -- not many folks are
capable of really driving it forward.
But there seems to be a fair bit of interest here, so maybe someone else
can take on the administrative job, and we can find folks to actually go an
and do bug fixes.
-Chris
On Tue, Apr 26, 2016 at 2:33 PM, Tim Roberts <timr@probo.com> wrote:
When one starts an open source project, one envisions that it will solve
some problem. Once that problem has been solved, the project is finished.
The open source world seems to have a SERIOUS problem with any project
being declared "finished". Why do we feel the need to churn features
endlessly? If wxPython provides a Python interface to wxWidgets, and that
works, then why should we expect there to be a continuous stream of
pointless features?Now, it's true that there are known, unsolved bugs in wxPython, so in that
sense there is still work to be done, but I'm not sure there's anything
wrong with a "dead open source project". After all, the entire user
interface universe upon which wxWidgets is based is itself dead. Microsoft
isn't doing anything new with GDI, and hasn't for years. We've already
missed two revolutions (Windows Forms and WPF), and the world is moving
into a third (descriptive HTML UIs with Javascript). Should wxPython
really need to be changing?
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker@noaa.gov
Hello all,
I didn’t notice this thread because I was only subscribed to wxpython-dev not users.
I am certainly willing to help out with Phoenix (and I have been doing what I can, see the list of open pull requests waiting to be merged).
I am working on packaging Phoenix for Fedora (and am planning to do so for Debian also afterwards).
Probably what would be really helpful for the project is for more people to start using Phoenix and report the issues that they find.
It would be helpful though if Robin could comment and maybe pass on/share the torch. 
Scott
On Monday, April 25, 2016 at 11:51:32 AM UTC-4, johnf wrote:
Hi Everyone,
It’s been almost 16 months since we had an update. I don’t see Robin answering question any longer - at least none I noticed. The Phoenix project just has nightly builds but I don’t see new code (not exactly true there is something supporting python 3.5). The messages and questions have slowed to a crawl.
So I think it is fair to say “we are very close to one more dead open source project”.
I do not want to see this die. I’m willing to help with some money (I don’t have the skills to write C or C ++ code). I have limited resources but I can help with some cash.
But first we need to find someone willing to take over with the skills (even if we have the money). I know many believe the desktop program is dead. But it’s not - with the web being hacked daily and mobile apps not suited to data entry - the desktop is NOT dead. GitHub just came out with Electron - because they believe the desktop is not dead.
We could just move to other tech and say bye to wxPython but what about the investment we all made. If wxPython would just moved to Python 3 we all could get many more years just using wxPython.
Please guys don’t let this die. Let’s do something - organize a way to fund a programmer and move forward. Let’s not lose our investment in wxPython.
Johnf
That’s a packaging bug inherited from Debian. Ubuntu doesn’t modify the package so in those cases you may get faster response if you create a Debian bug upstream.
In any event, the Debian bug will be fixed soon.
Scott
On Tuesday, April 26, 2016 at 3:59:37 PM UTC-4, Mario Lacunza wrote:
Meanwhile I can contribute with testing …for example I reported this bug in Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/wxwidgets3.0/+bug/1388847
more than 1 year ago and still is not fixed
looks like distros dont want to help with wxpython …
Hi folks,
I'm still here and am not dead yet! 
Seriously, as you've all probably guessed, there have been changes and complications that have affected the time I have for wxPython and Phoenix, but I do still have the desire to move it forward. I have been working on reorganizing things so I can spend more time on the projects, but once the momentum was gone it's been hard to get caught up and get things rolling at a steady pace again even as more time became available.
Although the desire to complete Phoenix is still present, maybe it is time for more motivation to help get me over the first mountain, although I really hate asking for donations. There really isn't any hardware or other tools that I need to do the work, and payments along the way are not really motivating for me these days, but perhaps a larger bounty upon completion of the first official Phoenix release would be the right carrot to help get me moving forward and to keep moving at a steady pace.
What do you guys think about pledging to some fund that only pays out when the release is finished? Is there some online service that would be appropriate for managing this? At first glance it doesn't seem like it would fit in with kickstarter or indegogo, but maybe they have an option for a bounty system or maybe there is something else. It probably wouldn't be appropriate for me to administrate this since I would likely be the primary beneficiary, so is somebody willing to take the lead?
One non-dev, non-$$$ way that people can help out is to continue doing what you have been doing on this mail list, helping each other out and taking care of newbies too. I'm unable to keep up with wx email so if I'm able to just focus on wxPython-dev instead of both of them then that will help greatly. If there is something that absolutely needs my attention but isn't appropriate for wxPython-dev then feel free to point it out to me, but if you guys can take care of it please do.
Any other suggestions?
--
Robin Dunn
Software Craftsman
http://wxPython.org
I’m so glad you’re back, Robin!!!
Guys, please let’s have all of us contribute by evetythjng we can to move forward. As I promised before, I’m happy to ask my company for finical help. But let’s have some official way to collect funding as Robin suggested. I will check on my side of ways how to do that.
On Monday, May 2, 2016, Robin Dunn robin@alldunn.com wrote:
Hi folks,
I’m still here and am not dead yet!
Seriously, as you’ve all probably guessed, there have been changes and complications that have affected the time I have for wxPython and Phoenix, but I do still have the desire to move it forward. I have been working on reorganizing things so I can spend more time on the projects, but once the momentum was gone it’s been hard to get caught up and get things rolling at a steady pace again even as more time became available.
Although the desire to complete Phoenix is still present, maybe it is time for more motivation to help get me over the first mountain, although I really hate asking for donations. There really isn’t any hardware or other tools that I need to do the work, and payments along the way are not really motivating for me these days, but perhaps a larger bounty upon completion of the first official Phoenix release would be the right carrot to help get me moving forward and to keep moving at a steady pace.
What do you guys think about pledging to some fund that only pays out when the release is finished? Is there some online service that would be appropriate for managing this? At first glance it doesn’t seem like it would fit in with kickstarter or indegogo, but maybe they have an option for a bounty system or maybe there is something else. It probably wouldn’t be appropriate for me to administrate this since I would likely be the primary beneficiary, so is somebody willing to take the lead?
One non-dev, non-$$$ way that people can help out is to continue doing what you have been doing on this mail list, helping each other out and taking care of newbies too. I’m unable to keep up with wx email so if I’m able to just focus on wxPython-dev instead of both of them then that will help greatly. If there is something that absolutely needs my attention but isn’t appropriate for wxPython-dev then feel free to point it out to me, but if you guys can take care of it please do.
Any other suggestions?
–
Robin Dunn
Software Craftsman
–
You received this message because you are subscribed to the Google Groups “wxPython-users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
One suggestion for a funding mechanism might be bountysource
Bountysource - Wikipedia &
https://www.bountysource.com/- I haven't used them myself but the github
integration looks promising.
On 03/05/2016 02:44, Robin Dunn wrote:
Hi folks,
I'm still here and am not dead yet!
Seriously, as you've all probably guessed, there have been changes and
complications that have affected the time I have for wxPython and
Phoenix, but I do still have the desire to move it forward. I have been
working on reorganizing things so I can spend more time on the projects,
but once the momentum was gone it's been hard to get caught up and get
things rolling at a steady pace again even as more time became available.Although the desire to complete Phoenix is still present, maybe it is
time for more motivation to help get me over the first mountain,
although I really hate asking for donations. There really isn't any
hardware or other tools that I need to do the work, and payments along
the way are not really motivating for me these days, but perhaps a
larger bounty upon completion of the first official Phoenix release
would be the right carrot to help get me moving forward and to keep
moving at a steady pace.What do you guys think about pledging to some fund that only pays out
when the release is finished? Is there some online service that would
be appropriate for managing this? At first glance it doesn't seem like
it would fit in with kickstarter or indegogo, but maybe they have an
option for a bounty system or maybe there is something else. It
probably wouldn't be appropriate for me to administrate this since I
would likely be the primary beneficiary, so is somebody willing to take
the lead?One non-dev, non-$$$ way that people can help out is to continue doing
what you have been doing on this mail list, helping each other out and
taking care of newbies too. I'm unable to keep up with wx email so if
I'm able to just focus on wxPython-dev instead of both of them then that
will help greatly. If there is something that absolutely needs my
attention but isn't appropriate for wxPython-dev then feel free to point
it out to me, but if you guys can take care of it please do.Any other suggestions?
--
Steve (Gadget) Barnes
Any opinions in this message are my personal opinions and do not reflect
those of my employer.
I am working on packaging Phoenix for Fedora (and am planning to do so for
Debian also afterwards).
Yay !! :-))
I can offer testing non-official packages if need be.
At which point I can start:
Probably what would be really helpful for the project is for more people to
start using Phoenix and report the issues that they find.
Best,
Karsten
On Mon, May 02, 2016 at 06:11:33PM -0700, stalbert@gmail.com wrote:
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
Today, there are no more working GUI toolkits for Python.
Probably, the single remaining options are:
Jython or IronPython.
See: https://groups.google.com/forum/#!topic/comp.lang.python/2NJfjVcwqQ8
Regards.
Hi Robin,
I'm really glad to hear you're not dead yet. I hope life is treating you well.
Put me down for contributing to the completion bounty. For me, wxMediaCtrl is absolutely essential, though, if you want my cash. ;)>
David
On 05/02/2016 08:44 PM, Robin Dunn wrote:
Hi folks,
I'm still here and am not dead yet!
Seriously, as you've all probably guessed, there have been changes and complications that have affected the time I have for wxPython and Phoenix, but I do still have the desire to move it forward. I have been working on reorganizing things so I can spend more time on the projects, but once the momentum was gone it's been hard to get caught up and get things rolling at a steady pace again even as more time became available.
Although the desire to complete Phoenix is still present, maybe it is time for more motivation to help get me over the first mountain, although I really hate asking for donations. There really isn't any hardware or other tools that I need to do the work, and payments along the way are not really motivating for me these days, but perhaps a larger bounty upon completion of the first official Phoenix release would be the right carrot to help get me moving forward and to keep moving at a steady pace.
What do you guys think about pledging to some fund that only pays out when the release is finished? Is there some online service that would be appropriate for managing this? At first glance it doesn't seem like it would fit in with kickstarter or indegogo, but maybe they have an option for a bounty system or maybe there is something else. It probably wouldn't be appropriate for me to administrate this since I would likely be the primary beneficiary, so is somebody willing to take the lead?
One non-dev, non-$$$ way that people can help out is to continue doing what you have been doing on this mail list, helping each other out and taking care of newbies too. I'm unable to keep up with wx email so if I'm able to just focus on wxPython-dev instead of both of them then that will help greatly. If there is something that absolutely needs my attention but isn't appropriate for wxPython-dev then feel free to point it out to me, but if you guys can take care of it please do.
Any other suggestions?
Hi Robin,
On Mon, May 2, 2016 at 8:44 PM, Robin Dunn robin@alldunn.com wrote:
Hi folks,
I’m still here and am not dead yet!
Seriously, as you’ve all probably guessed, there have been changes and complications that have affected the time I have for wxPython and Phoenix, but I do still have the desire to move it forward. I have been working on reorganizing things so I can spend more time on the projects, but once the momentum was gone it’s been hard to get caught up and get things rolling at a steady pace again even as more time became available.
Although the desire to complete Phoenix is still present, maybe it is time for more motivation to help get me over the first mountain, although I really hate asking for donations. There really isn’t any hardware or other tools that I need to do the work, and payments along the way are not really motivating for me these days, but perhaps a larger bounty upon completion of the first official Phoenix release would be the right carrot to help get me moving forward and to keep moving at a steady pace.
What do you guys think about pledging to some fund that only pays out when the release is finished? Is there some online service that would be appropriate for managing this? At first glance it doesn’t seem like it would fit in with kickstarter or indegogo, but maybe they have an option for a bounty system or maybe there is something else. It probably wouldn’t be appropriate for me to administrate this since I would likely be the primary beneficiary, so is somebody willing to take the lead?
One non-dev, non-$$$ way that people can help out is to continue doing what you have been doing on this mail list, helping each other out and taking care of newbies too. I’m unable to keep up with wx email so if I’m able to just focus on wxPython-dev instead of both of them then that will help greatly. If there is something that absolutely needs my attention but isn’t appropriate for wxPython-dev then feel free to point it out to me, but if you guys can take care of it please do.
Any other suggestions?
–
Robin Dunn
Software Craftsman
–
You received this message because you are subscribed to the Google Groups “wxPython-users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Thanks very much for the post, Robin. I’d be willing to pitch in, in both respects as well. I’m not great at C++, but if there is a concerted effort developing and maintaining wxPython, I’d be happy to help with testing and trying to fix problems on all three platforms.
Phoenix is working pretty well for me (testing mostly on Mac OSX and Windows7 64bit with Python2.7 and 3.5). I’ve had some trouble with initial attempts at translating code from Classic that use DC contexts for fast image display, but I haven’t tracked these down to know whether this is an issue with Phoenix or my code. I should say admit that I don’t use MediaCtrl.
I agree with the sentiment that it would be better to release Phoenix for both Python 2 and 3 soon, even if there are known missing or crippled features compared to Classic. With only snapshot builds available, I think that Phoenix is used much less than it could be.
I do see several Issues and PRs on the github site, but I assume these aren’t the main problems standing in the way of release. It would be nice to see a more strategic and complete to-do list for release, if only to understand what needs the most work. Does such a list exist?
–Matt
It’s good to hear from you Robin. I think we all appreciate how busy you are. Like you, I’ve been involved in other things and have not had much time to follow the different wxPython-xxxx groups very closely recently, but in the last few weeks I have been converting my own (commercial) wxPython software to Python 3.4 & Phoenix. It has all gone pretty well and I have only a handful of issues to raise - some fairly trivial but one or two show stoppers - like the classes based on wx.lib.activex.ActiveXCtrl.
I don’t know the best place to report these. Maybe there should be a new group called wxPython-phoenix specifically for raising, discussing and generally keeping in touch - perhaps at the expense of wxPython-mac which has only received about six messages this year.
I don’t have the C++ skills to contribute anything to the central core but if anything in Python or cross-platform testing needs doing, someone please say. I’m also more than happy to contribute to a completion bonus/bounty if that will help.
They are actually working on a new PyQt (and PySide2) for the latest versions of Qt. Of course, there’s also Tkinter. And there’s also Kivy, although it’s quite a bit different from the others.
Mike
On Tuesday, May 3, 2016 at 3:05:37 AM UTC-5, jmfauth wrote:
Today, there are no more working GUI toolkits for Python.
Probably, the single remaining options are:
Jython or IronPython.See: https://groups.google.com/forum/#!topic/comp.lang.python/2NJfjVcwqQ8
Regards.
I don’t know what you were trying to say here, but as you have
stated it that statement is just silly. WxPython, Qt, and TkInter
are all alive and well, as well as a plethora of smaller and more
specialized toolkits.
jmfauth wrote:
Today, there are no more working GUI toolkits forPython.
Probably, the single remaining options are: Jython or IronPython.
-- Tim Roberts, Providenza & Boekelheide, Inc.
I agree with the sentiment that it would be better to release Phoenix for
both Python 2 and 3 soon, even if there are known missing or crippled
features compared to Classic. With only snapshot builds available, I think
that Phoenix is used much less than it could be.
I'm not sure why people are so scared of the snapshot builds. They are generally working pretty well, from my experience.
I do see several Issues and PRs on the github site, but I assume these
aren't the main problems standing in the way of release. It would be nice
to see a more strategic and complete to-do list for release, if only to
understand what needs the most work. Does such a list exist?
Well there is this:
https://github.com/wxWidgets/Phoenix/blob/master/TODO.txt
Scott
On Tue, 3 May 2016, Matt Newville wrote:
Which would you be interested in, Fedora or Debian?
Scott
On Tue, 3 May 2016, Karsten Hilbert wrote:
I am working on packaging Phoenix for Fedora (and am planning to do so for
Debian also afterwards).Yay !! :-))
I can offer testing non-official packages if need be.
Distributions want Known Good Points (IOW, releases) and end
users / IT firms want Official Packages. It's all about
maintainability and common ground.
If I tell my users (medical practices) to "grab a snapshot
build and cross your fingers, they work pretty well", they'll
go "uh, no".
If snapshots work pretty well it "should" be a no-brainer to
spin a release from one of them.
Regards,
Karsten
On Wed, May 04, 2016 at 12:07:54AM -0400, Scott Talbert wrote:
> I agree with the sentiment that it would be better to release Phoenix for
> both Python 2 and 3 soon, even if there are known missing or crippled
> features compared to Classic. With only snapshot builds available, I think
> that Phoenix is used much less than it could be.I'm not sure why people are so scared of the snapshot builds.
generally working pretty well, from my experience.
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
Debian
Thanks for asking !
Karsten
On Wed, May 04, 2016 at 12:14:47AM -0400, Scott Talbert wrote:
> > I am working on packaging Phoenix for Fedora (and am planning to do so for
> > Debian also afterwards).
>
> Yay !! :-))
>
> I can offer testing non-official packages if need be.Which would you be interested in, Fedora or Debian?
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
Note that I am neither saying that *packages* should be a
no-brainer nor complaining in general
Karsten
On Wed, May 04, 2016 at 11:21:38AM +0200, Karsten Hilbert wrote:
If snapshots work pretty well it "should" be a no-brainer to
spin a release from one of them.
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346