[wx-discuss] wxTNG: compatibility with wx2 API

[Stefan Csomor]

> -----Original Message-----
> From: Vadim Zeitlin [mailto:vadim at wxwindows.org] 
> Sent: Donnerstag, 16. Februar 2006 19:28
> To: wx-discuss at lists.wxwidgets.org
> Subject: Re[6]: [wx-discuss] wxTNG: compatibility with wx2 API
> 
> On Thu, 16 Feb 2006 18:43:48 +0100 Stefan Csomor 
> <csomor at advancedconcepts.ch> wrote:
> 
> SC> >  When Julian says that wx2-on-wx3 approach is the 
> cleanest and the 
> SC> > easiest one to implement, I agree with the first part 
> but strongly 
> SC> > disagree with the second one. I'm afraid
> SC> > wx3-on-wx2 is the only possibility in practice.
> SC> 
> SC> that's where I disagree, for me it would be a waste of 
> time to build 
> SC> wx3 upon wx2, apart from the High-Level APIs I mentioned before, 
> SC> where we could gain something already then, but at the 
> lower level 
> SC> it would still be the same problems.
> 
>  It's true that I mostly concentrate on new and better API 
> than on new and better features. And from the point of view 
> of new features wx2-on-wx3 does make more sense. But I think 
> we can find a compromise: work on wx3-on-wx2 but provide new 
> implementations of just some classes:

the clean API can be done in wx3 whether it is above or below wx2. wx2
on wx3 will allow to replace things step by step, have the new
implementation tested immediately, having the option to switch back if
we break things w/o having a good clue on how to solve them in short
time. whereas wx3 on wx2 will be plagued by all the problems wx2 has,
any effort to remedy them in wx2 will be either wasted or wx2 will never
be replaced at all. The latter is an option of course, but then it
should be stated upfront, because replacing wx2 completely when it is
sitting under wx3 is an even more herculean task, with the added
disadvantage of leaving all wx2 code users in the dust ...

> SC> We could eg also start implementing a new DC architecture using 
> SC> paths, colours etc. and have a wx2 wxDC that is more or less the 
> SC> same on all platforms that is implemented using wx3::dc
> 
>  This probably could be done in wx2 too, so why not add these 
> new features in wx2 DC class?

implementing this as wx3 and using wx2 to bridge upon will give the
chance for a cleaner API and new features at the same 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