Hi John,
I am kind of in the same position with the 'phoenix2ndtry' branch, I
have ReportDesiger/Writer working for me in Py2 with classic and Phoenix
and it works with Py3 too.
BUT I don't like to use my custom code on a long term, so would like to
switch back to an official version - preferably sooner then later.
Currently it is not clear to me how Dabo will move forward and I don't
want to put more time into it without knowing a bit more.
With regards to Phoenix and its arrival. If progress goes as it did in
Jan/Feb this year (over 100 commits) then I think it is closer to
release then you guess, but that is only my guess:) and it depends
heavily on how much time Robin can keep spending on it and how much
other people put in to test things and get wx.lib up to speed and it
would be even better if some more C++ devs would step in.
With regards to QT, I don't think there will be a wxPython/QT for
Classic as currently the only work done by the wxQT port author with
regards to wxPython is against Phoenix - see: [wxPython-dev] GSoC 2014
wxQT + wxPython (Phoenix) wxWidgets 3.2
Werner
On 2/27/2015 14:03, john wrote:
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
[excessive quoting removed by server]
_______________________________________________
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]
