On 02/25/2015 03:53 AM, Werner wrote:
On 2/24/2015 22:51, Neil Flowers wrote:
Agreed, I think that is the only way to proceed without hanging
yourself in the long run. As mentioned, though, it will probably be a
non-trivial amount of work to honor DRY. It will make the process of
combining the two branches straight forward, though, since they will
simply reside in different locations.
Not sure I understand what is suggested.
ui/wx will contain the 0.9x
ui/wxphoenix will contain a Phoenix compatible version, which might be
comp with 3.0 classic, at least to start with
- where does the Dabo2 branch fit into this, will it go into ui/wx as
it is compatible with existing Dabo based applications.
Werner
The way I see it - ui/wx2 will be the Dabo2 branch for the near future
for python 2.x. It will contain the code we have now (in beta) and in
the future will contain Phoenix (hopefully). And I see ui/wx as
supporting Dabo 0.9.
That said, Paul is also suggesting that ui/wxphoenix also be created
temporarily to allow development. He would like to see much of the
non-based wxPython code moved into Dabo 3. Then when wxPhoenix is ready
and working with python 3.x we create a ui/wx3. This will allow Dabo 3
to work with both ui/wx2 and ui/wx3.
At least that's how I understand it.
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]
