Hi John,
On 2/24/2015 18:43, john wrote:
I'm sorry about that - but I decided along with Neil that it was best
to get wxPython 3.x working since it was stable and fixes were being
posted. As a result of the decision much of your code was
reversed/removed.
That is what I still don't understand. Was it done so code would stay
compatible with existing Dabo applications or was it done because my
change caused a problem?
That said, I believe it is possible in the future to bring Phoenix in
when it becomes stable. Or we could have three versions Dabo .9,
Dabo2, Dabo3 where two = wxPython3 and three = Phoneix (I'm sure
wxPython .X will be the name).
I was and am still hoping that the code in 'phoenix-2ndtry' would work
with wxPython 3 classic and wxPython 3 phoenix and should really still
work with wxPython 2.8 classic. BUT it requires that applications using
it change from the dFrame.py to the frame.py etc.
Have you been able to test the commit - like your report writing stuff?
Yes, did a bit of testing and it seems to work. So, wanted to see why
it does and the 'phoenix-2ndtry' does not work, but to try to see the
changes just in dGrid.py in your code and grid.py in 'phoenix-2ndtry' is
not easy and some changes I don't know where they come from.
Will see if I find more time over the next few days
Werner
Johnf
On 02/24/2015 01:37 AM, Werner wrote:
That rename makes it also difficult to see what changes John and Neil
have done when doing a diff of the folders:-( to see what could be
reused from their work on the 'phoenix-2ndtry' branch.
[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]
