[wx-discuss] wxTNG: compatibility with wx2 API

[Vadim Zeitlin]

On Thu, 16 Feb 2006 15:51:22 +0000 Julian Smart <julian at anthemion.co.uk> wrote:

JS> However I don't think that wx3-on-wx2 will necessarily be a panacea for
JS> backwards compatibility, because wx3 will need its own initialisation

 Sorry, I don't see what's the problem with this? If some class wx::Foo
needs to do more than wxFoo, it can always do it in its ctor/dtor
before/after creating wxFoo. And for global initialisation we could just
use a specific wxModule.

JS> and dealing with wx2 objects may not be tenable to make wx3 do the
JS> right thing. Whereas you know with a proper wx2-on-wx3 port that
JS> using wx2 objects is always allowed.

 Yes, I won't argue that wx2-on-wx3 port is possible and, even, desirable.
I just don't think it's going to happen in practice any time soon.

JS> But one could argue for the phased approach:
JS> 
JS> 1) Implement wx3-on-wx2 for speed of development.
JS> 2) Implement wx3-on-native-ports.
JS> 3) Implement wx2-on-wx3 for backwards compatibility.

 I do agree with this schedule but with a reservation that the step (3)
might in fact never happen.

 Regards,
VZ


---------------------------------------------------------------------
To unsubscribe, e-mail: wx-discuss-unsubscribe at lists.wxwidgets.org
For additional commands, e-mail: wx-discuss-help at lists.wxwidgets.org