[wx-discuss] wxTNG: compatibility with wx2 API

[Stefan Csomor]

Hi

> SC> I was referring to the step by step in the following sense :
> SC> 
> SC> - when I implement a new wx3-dc on mac, I have to write a wx2-wx3 
> SC> bridge in order to test it, but if I have bridged colour, 
> brush, dc 
> SC> then I can test it already, I can now add an 
> implementation for msw, 
> SC> use the same bridge test that again etc ..
> 
>  So you'd write a new wx::DC implementation but the only way 
> to use it, for foreseeable future, would be via existing wx2 
> wxDC. I don't find this very interesting because, again, I'm 
> mostly interested in using new API directly and this is not 
> going to be possible before wx3 is finished.

you'd have to wait until the dc implementation is finished, for a
certain platform before you can use it from a wx3 api, but not for more.
The wx2-wxDC would have it's peer wx3-dc and you can retrieve it and use
the wx3 API on it directly.

> SC> >  As I said, I do expect wx2 to stay alive for quite 
> some time (I'm 
> SC> > speaking about years here, maybe 5, more likely 10). But this 
> SC> > doesn't mean wx3 will still be using it in a couple of years -- 
> SC> > e.g. I fully expect/hope to have a native .NET 
> implementation of 
> SC> > wx3 relatively soon.
> SC> 
> SC> who will be able to benefit ? IIUC only people writing 
> against the 
> SC> wx3 API - or also wx2 users ?
> 
>  I hope both. But for this it should be possible to use both 
> wx2 and wx3 in the same program, which is why I put it as one 
> of important goals in the wiki page.
> 
> SC> of course having a clean API with pluggable implementations for 
> SC> .NET, wx2, qt etc. could help acceptance by boost, but 
> this would be 
> SC> an entirely new framework and wx2 users would never be able to 
> SC> benefit from it
> 
>  wx2 would be interoperable with wx3 version using wx2 
> backend. Of course, the existing wx2 code would need to be 
> ported to wx3 to profit from the new features and new 
> backends, but this is not only unavoidable IMO but also good 
> as this will motivate people to move to wx3. But without 
> forcing them to do it all at once.

I don't see yet, how I could mix wx2 and wx3 code when eg I want a .NET
backend, let's say a WPF window, would this be implemented in wx2, I
thought you said you wanted one as a wx3 backend ?
 
> SC> I don't think making everyone happy is key,
> 
>  Well, IMNSHO it is. We speak a lot about wx users but we, wx 
> developers, should also be motivated to develop wx3. If we're 
> not, I don't believe this project can succeed.
> 
>  E.g., personally, I don't want to embark on a project which 
> is not going to bring any fruits at all before several 
> years... 

Motivation is very important, I agree on that of course. You are
supporting your view with your assumptions on wx2on3, on which I
disagree, especially as you keep saying 'any' so we apparently cannot
advance there, and I cannot motivate you ;-). I myself don't see too
many advantages on a wx3 on wx2 effort, apart from a few prototyping
things which could be done more easily like this, so I lack motivation
there ...

> For me it is important to have something working 
> relatively soon is important. If we can achieve this -- in 
> whatever way -- I'll be happy. I.e. if you can propose a 
> development plan which would allow us to write applications 
> using wx3 API soon, I'd be glad to accept it. Do you have such plan?

My idea -  I wouldn't call it a plan yet - is to replace module by
module or layer by layer of wx2 code that is implemented directly on
several platforms with 

a) an wx3 implementation that is native on the several platforms
b) a wx2 on wx3 bridge

of course such an approach thing takes up more time than a wx3on2
implementation, but as soon as you think about replacing different
backends I don't think this approach takes more time than a the overall
wx3on2 solution, as you are thinking about adding / replacing different
backends.

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