[wx-discuss] wxTNG: compatibility with wx2 API

[Julian Smart]

My view is that

(a) we absolutely must provide some kind of compatibility
or we will lose most of our customer base (and will need to maintain
2 code bases since many people won't migrate);

(b) the easiest and cleanest way to do that is basically a wxWidgets 2 port
wrapping wxWidgets 3. It should be relatively straightforward because it's
totally generic (1 size fits all platforms), and (hopefully) will be a
thinnish wrapper. So people who don't need backward compatibility won't have
the overhead of the wxWidgets 2 API, and those who do can gradually
migrate.

Regards,

Julian

At 14:27 16/02/2006, you wrote:
>  Hello again,
>
>  I'd like to start by one of the most fundamental questions about wxTNG:
>how much is it supposed to be compatible with wx2 public API and,
>relatedly, how much of existing wx2 implementation code can it reuse?
>
>  I think we all agree that we won't be aiming at keeping 100% compatibility
>with the existing API. However I also think that most of us would like to
>keep some degree of compatibility to make porting existing code to wxTNG
>easier and, at least as importantly, to allow reusing the existing
>implementation instead of having to rewrite everything.
>
>  So what degree of compatibility do we want to preserve? There is a whole
>range of options:
>
>0. No compatibility at all, while we might keep [almost] the same class
>    names (wx::Window) we wouldn't try to preserve their semantics (e.g. I
>    think wx::Window should be used as a value, not as a pointer) nor their
>    methods names and signatures
>
>1. Try to preserve some compatibility with wx2 API, e.g. provide wxWindow
>    as synonym for the new wx::Window, keep passing them by pointer, but
>    feel free to change other important things
>
>2. Keep as much compatibility as possible, by providing backwards-
>    compatible wrappers around the new constructs (or, OTOH, new wrappers
>    around the old API)
>
>and, of course, many intermediate variants.
>
>  So why are we/you (Stefan) aiming at for wxTNG?
>VZ
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: wx-discuss-unsubscribe at lists.wxwidgets.org
>For additional commands, e-mail: wx-discuss-help at lists.wxwidgets.org

==============================================================================
Julian Smart                           julian at anthemion.co.uk
28/5 Gillespie Crescent, Edinburgh,    http://www.anthemion.co.uk
Midlothian, U.K., EH10 4HU             +44 (0)131 229 5306
Writer's Cafe: power tools for writers http://www.writerscafe.co.uk
HelpBlocks:    HTML help authoring     http://www.helpblocks.com
DialogBlocks:  cross-platform dialogs  http://www.anthemion.co.uk/dialogblocks
============================================================================== 



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