[wx-discuss] wxTNG: compatibility with wx2 API

Vadim Zeitlin vadim at wxwindows.org
Thu Feb 16 06:27:36 PST 2006


 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





More information about the wx-discuss mailing list