[wx-discuss] wxTNG: compatibility with wx2 API

Andreas Mohr andi at rhlx01.fht-esslingen.de
Thu Feb 16 07:08:50 PST 2006


Hi,

On Thu, Feb 16, 2006 at 02:51:32PM +0000, Julian Smart wrote:
> 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);

Count me in here. It's a large effort to work on a big program, this implies
that it's not easy to change things on the whim to account for the latest
ground-breaking changes in the new version of the toolkit it uses.
I'm all for modernization of a framework, but the rate of forced change would
better be measured in years at least (say, after at least 2 to 3 years
one would then HAVE to use the new infrastructure).
The downside of not being able to go with the newest toolkit version would be
having to work on an old "stable" (whatever that means) version that would
often get unsupported faster than you could say "ouch!", despite all good
intentions to the contrary. Not to mention that having to use the old version
would mean one customer less who's able to work on improving features/stability
of the current, modern version...

> (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.

Sounds very nice, but that's all just theory and nice words for now ;)

Andreas Mohr

---------------------------------------------------------------------
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