[wx-discuss] wxTNG: compatibility with wx2 API

[Stefan Csomor]

Hi Kevin 

> Well, even if we fix things using wx3, if we do indeed change 
> the class substantially in wx3 then I don't think we could 
> just "hide it under the hood" for the wx2 backend anyways, or 
> in some cases we'd be doing a disservice to our wx2 users by 
> doing so. e.g. assigning an encoding to strings, or moving to 
> floating point coordinates for wx3 DCs. So I think, 
> realistically, we have to understand that no matter what we 
> do, some degree of wx2 backwards compatibility is going to be broken.

this would perhaps mean, that unicode builds are required, but eg
CoreGraphics is using floating values for colours and coordinates now,
and we didn't have to change the API.

> Right, I'm just hoping for a compromise on the bridge issue 
> because API discussions will go a lot smoother if all sides 
> have the same basic goals. As I said earlier, if wx2 
> compatibility isn't a big deal in the API design, you could 
> radically change things in ways that may be very hard to 
> backport into the wx2 API.

I realize that I'm unable to make my point convincingly clear, yet I see
to many things that wouldn't change - and that are very important to me
- when using the wx3on2 approach. So I'm afraid I don't see that we can
reach a consensus there. But if it is just me it doesn't really matter,
because the wx3onwx2 approach most probably would not need too much work
in wxMac, so it is not necessary to have me on the implementation board,
it is rather just a personal question for me on where to invest my
'free' (I don't think I have ever any ;-) time.

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