[wx-discuss] wxTNG: using external libraries
Ryan Norton
wxprojects at comcast.net
Fri Feb 17 11:30:12 PST 2006
> IMO we shouldn't be writing container/string
> classes, socket and thread classes and probably database classes
> neither.
This really gets to the core question of whether one wants wx to be
just a gui framework which happens to use other libraries[1] or a
general purpose framework much like java and/or MFC that either
implements their own stuff or wraps around it with wrapper classes etc..
[1] and then why are we even eager to use external libs besides the
STL. I think maybe a comprimise would be maybe the dictum
Ryan 23.22:
"If you happen to touch on something [like threads] then make a wrapper
API for it for the users, and if it is something you do not touch
[databases] and does not have anything to do with your core goal [a GUI
library] then do not make an API for it."
(Not that I neccesarily agree with that as I would like a general
purpose lib) Then I think whether or not to use external libraries is
simply intuitive as in if there is one available and it is halfway
decent then you use it etc..
> wxSocket. Should I say more?
Actually, that is probably a bad example simply because even though it
isn't the greatest and the implementation by 90% of accounts is a mess
there really isn't too many (yes, there are a couple) other
alternatives for real cross-platform socket programming with event
integration.
The actual wxProtocols/wxURL are probably a good example, however.
Thanks,
Ryan
---------------------------------------------------------------------
To unsubscribe, e-mail: wx-discuss-unsubscribe at lists.wxwidgets.org
For additional commands, e-mail: wx-discuss-help at lists.wxwidgets.org
More information about the wx-discuss
mailing list