On 02/27/2015 12:29 AM, Werner wrote:
It is my understanding that classic will die as soon or soon after
Phoenix is released, Phoenix will support Py2.7, Py3.3+.
I understand your reasoning. That said, history tells me that we are
talking about sometime far in the future. I'm of the opinion that
python 3 will be closer to python 4 (it's already at 3.5 rc) by the time
Phoenix is released and stable. This is not a put down of Robin or
anyone - because if it was I would be putting myself down too. Just
like Robin I have to make a living and have only so much time. And Neil
now has a full time job that does not use anything remotely like the
tech stack that Dabo uses. So his interest will soon be else where.
Truth be told all my itches are satisfied with this commit. All my
forms run well and are fast. All my reports work. I would hope further
work will be done to match wxPython 3 classic features and code. Then
we can get with the business of moving non-wx code from the ui/wx.
Moving the non-wx code will better prepare Dabo for Phoenix. When
Phoenix arrives we will have an easier time re-coding the ui/wx code.
And if what you believe comes true then we can deal with the code
changes (if any) required for Dabo. If ends up like I believe is going
to happen then we can just fork to the new Dabo 3.
P.S. I feel for Robin because the underlying wxWidgets code he is using
is in constant change. In fact it's also moving in different
directions. There is a port taking place that uses the Qt framework -
it's called the wxQt port. I'm sure this port will be a major change
for the Linux world - will Linux wxPython code move from GTK to Qt?
Then of interest is the Chrome port - will we be running Dabo inside a
browser?????
Johnf
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/[email protected]
