Sujet : Re: 'Graphics' of libwy
De : david.brown (at) *nospam* hesbynett.no (David Brown)
Groupes : comp.lang.c++Date : 17. Dec 2024, 08:49:46
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vjraeq$1l76m$1@dont-email.me>
References : 1 2 3
User-Agent : Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0
On 17/12/2024 01:47, Lynn McGuire wrote:
On 12/16/2024 3:29 AM, David Brown wrote:
On 15/12/2024 11:04, wij wrote:
I had headache whenevr I think about graphics in C++. Why C++ does not provide
a graphics library (lots complaint about this), not even a simplest one for
demonstrating its 'power' of C++ itself?
>
There are 101 C++ graphics libraries, all with their pros and cons and different use-cases. How could the C++ standard library pick just one of them?
Open Source and LGPL would be a good place to start.
https://en.wikipedia.org/wiki/List_of_widget_toolkits
So that leaves - what - 20-odd different libraries from that page that are open source, cross-platform and suitable for C or C++ ? And there's maybe an order of magnitude more that not on the Wikipedia page but are still established enough to be contenders.
Then you need to consider that the C++ world is not just *nix, MacOS and Windows - and that even for those, needs vary enormously (big, small, easy-to-use, wide selection of widgets, 2D, 3D, etc.). The things /I/ want from a gui library for an embedded system are hugely different from what you would want on a PC. And of course LGPL is useless for me.
No, that page is not really a good place to start - unless you are using it as a starting point for showing how meaningless it would be to try to pick a single gui library that is somehow "standard" for C++.
I don't know if that will stop the C++ committee from trying to pick or make a standard GUI library - after all, it's certainly an appealing idea. But if the "success" of C++'s threading support is any judge, they have a hard road in front of them.