[wx-discuss] wxTNG: using external libraries

[ABX]

Julian Smart <julian at anthemion.co.uk>:
> Here are some concerns about use of external libraries:

Taking strings as an example I would prefer something like consistent use of

  wx::string in the API

and if somebody want to use foo::string in user application then deliver

  #include "wx-boost.h"

which could allow us to write code with transparent conversions like 

  boost::string new_title;
  win.SetTitle(new_title); // SetTitle(wx::string title) was prototype

because wx-boost.h would contain all the conversions required (or nothing if
wx::string would be in fact boost::string internally). I admit I don't know if
that's possible with single header.

> 3. Will we have to drop support for any significant compilers?

I'm not a phanatic of outside-mainstream compilers but I would like to have
opportunity to inform their developers about features we started to use so
they could decide whether they want to implement missing features and keep
being supported. In other words to give them a chance to do minimal fixes
without any compromise in our code.

> 4. What about overhead?

My worries exactly. I would like to have static apps still downloadable in
reasonable time with not ideal bandwith.

> 6. What happens when the external libraries don't do
> things we need them to do? (If we want to change them
> we have to straddle several projects, and we might not
> get permission.)

Yes, just because wxW principles are important for us, from other toolkits
point of view we can be as important as trivial is changing wxWindows to
wxWidgets name in licence.

ABX


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