[wx-discuss] wxTNG: compatibility with wx2 API

[Vadim Zeitlin]

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 
SC> > and the easiest one to implement, I agree with the first part 
SC> > but strongly 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 wx3
SC> upon wx2, apart from the High-Level APIs I mentioned before, where we
SC> could gain something already then, but at the lower level it would still
SC> 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:

SC> the wx2 on wx3 approach would eg be to implement
SC> some of the wx2 classes directly using some of the external libraries,
SC> this could be done piece by piece, libcurl or boost or whatever.

 E.g. instead of wrapping wxSocket in wx3 we could directly use libcurl (or
whatever) -- I'd actually be in favour of this. But this is only possible
for the classes which are not used elsewhere in wx2. E.g. it wouldn't work
for wxString or wxDateTime.

SC> We could eg also start implementing a new DC architecture using paths,
SC> colours etc. and have a wx2 wxDC that is more or less the same on all
SC> 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?

 Regards,
VZ


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