[wx-discuss] wxTNG: compatibility with wx2 API

[Stefan Csomor]

> JS> How about both approaches simultaneously? Basically it's 
> the 3-step 
> JS> plan with all steps being interleaved.
> JS> 
> JS> So, we all agree on the API and build this as a library 
> in CVS HEAD 
> JS> with several back-ends:
> JS> 
> JS> (a) Native back-ends:
> JS>      - MSW
> JS>      - Mac
> JS>      - GTK2
> JS>      - etc.
> JS> 
> JS> (b) wx2 back-end
> JS> 
> JS> Plus we start a new wx2 port, wxTNG2 or similar name.
> 
>  This looks like a pretty good idea in its own right and also 
> the best one we can agree on, apparently. At least I'd be 
> motivated to work on (b) and I guess Stefan wouldn't object 
> to (a), would you?

no doubt on that one ;-) that's why I proposed that we could start
discussing about the APIs whatever their implementation will be, I don't
think your idea about several backends will put less constraints on
these thoughts than native implementations. Unless we declare native
platform pecularities to be features ...

>  And like this we can, at least temporarily, put a stop to 
> this discussion and hopefully can start working together on 
> devising the new API.
> 
>  So do we all agree to follow Julian's suggestion?

In this plan there would be no migration path to new features for wx2
code but a full rewrite, which IMHO still is a BIG disadvantage, as
there would only be the wx2 backend and no bridges. But I'd probably
have to mix these in anyways to get my desired testbed, unless I'm the
only one interested in the part (a) of above plan, in which case I'd
have to scale plans to my own priorities. But let's see whether we can
find common grounds on the API ideas.

Best,

Stefan


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