220 28831 <5644e922-d6c9-411c-9e06-4a5302e0de58@isocpp.org> article Path: news.gmane.org!.POSTED!not-for-mail From: FrankHB1989 Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Re: GUI Date: Fri, 14 Oct 2016 04:39:05 -0700 (PDT) Lines: 156 Approved: news@gmane.org Message-ID: <5644e922-d6c9-411c-9e06-4a5302e0de58@isocpp.org> References: <8e7ef2a9-cc07-41bf-b802-6e7ea795f880@isocpp.org> <45d02760-81b8-4039-b306-75266197b420@isocpp.org> <24eac99c-2d60-4c31-8815-0936674c9d1b@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_546_1244414449.1476445145266" X-Trace: blaine.gmane.org 1476445167 6368 195.159.176.226 (14 Oct 2016 11:39:27 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 14 Oct 2016 11:39:27 +0000 (UTC) To: ISO C++ Standard - Future Proposals Original-X-From: std-proposals+bncBCTJVBPG3QIBBWUHQPAAKGQEULQTWHY@isocpp.org Fri Oct 14 13:39:23 2016 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-oi0-f70.google.com ([209.85.218.70]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bv0pO-0007jL-UF for gclcip-std-proposals@m.gmane.org; Fri, 14 Oct 2016 13:39:07 +0200 Original-Received: by mail-oi0-f70.google.com with SMTP id a195sf220668526oib.0 for ; Fri, 14 Oct 2016 04:39:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isocpp-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=6QhtfGnyyv9npgV9X0zHvGloWwKJSrr4ACMna2BJF9Q=; b=s4mjl5iLwIePvx5CPi86Dko8bKbsbOW4Jch6L0S+k7shcVxcWut+6x/gek/6QmCSvy SJfVqOfHc2qFBgN4xuoiIuU7dW1vjTflT2Qrbtj/r8kMrVjFdK0xZHxioDP7OtOPnhqP stWL67GkvoRBMO2Yck3fplEdbRDuJt++scj+beavbwKZINSOQZZU3nrZp2vbu0WVUAmW MBalh1apzl87LsuhUHtG1qZOqCbFBKWwvpPv5DBf2uYllVz+27KA8dQqtZb9685zoo3b tgzP65daKBXzwpCDg3unx5neNaNRh2qKipTV+amNpc4xRX/UGRD1LGQIHgLz47nLY8Fj Do/g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=6QhtfGnyyv9npgV9X0zHvGloWwKJSrr4ACMna2BJF9Q=; b=eXEwpQ5SkrM7drhIPjiHm8jw17tDkUWUhdTceciRtEITIFvY4AlGT7a0+dRRS9Wuep f73xiU1bfgwowvL1va3+sHZDhGZP6b4myx2ZAL1+zn5LT3sQzYt1ThljLq0f0bKpZagy V+AY1WUwTrJqw/JctpZgBKN9lRZzbYA2A6NM+MZvHCosrXnWJIYuUejLeifBcSoiOk5A dHNZ3Whxb3mlUbtIDPmeINdTvP18VbgH3u1Px3cOY34aohDYUsbhb+6kUblHjlrWP1Y/ OsbcJ5zwGG8olpvzi0v27hKwKGBc7/aT1fX0DbJMYJ7FlxPbvYb7xvSe9yuC1WQvhbhy GPaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version:x-original-sender:reply-to:precedence :mailing-list:list-id:x-spam-checked-in-group:list-post:list-help :list-archive:list-subscribe:list-unsubscribe; bh=6QhtfGnyyv9npgV9X0zHvGloWwKJSrr4ACMna2BJF9Q=; b=DKEsQSWWGXZDpOWgm8H+86q6AJviOmtvyWoJfK3YNv8X/dLyMuNFTmEMRsc7YEkS6+ i7bXOCgSD+gPS8IFT5NSbcDpdr+2XF/7Q6Ey1uuFC63dRx5VdbcKPAJgNkXgh//r4e2W nF4fIiLmIv6th2sqchiGTph486DJRDfMoQClaIO93g80Raad5/bLZILtDylpOVK5pAWU xOqQEYhekakUZ74NOU9QAw9fBGtCed2nFFXenmThicFvZ/J9PeRbCjEyZ4BafZNs/6nB 6ou2/vphOuhREoZFnwhopqsSnaxGu2PBJg6Ls0wzFTr8l2ijbOLdWrJL9m+KJUJrPrsg NAzQ== X-Gm-Message-State: AA6/9RmvFAFadaBD5I142g0HGFBGlaarAhjdnH+kPedFs+q4oBfV5/nrcoUyVVUZz8H//g== X-Received: by 10.157.40.176 with SMTP id s45mr3141138ota.142.1476445148645; Fri, 14 Oct 2016 04:39:08 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.107.142.17 with SMTP id q17ls2972866iod.1.gmail; Fri, 14 Oct 2016 04:39:06 -0700 (PDT) X-Received: by 10.36.217.2 with SMTP id p2mr121130itg.5.1476445146094; Fri, 14 Oct 2016 04:39:06 -0700 (PDT) In-Reply-To: X-Original-Sender: frankhb1989@gmail.com Precedence: list Mailing-list: list std-proposals@isocpp.org; contact std-proposals+owners@isocpp.org List-ID: X-Google-Group-Id: 399137483710 List-Post: , List-Help: , List-Archive: List-Subscribe: , List-Unsubscribe: , Xref: news.gmane.org gmane.comp.lang.c++.isocpp.proposals:28831 Archived-At: ------=_Part_546_1244414449.1476445145266 Content-Type: multipart/alternative; boundary="----=_Part_547_1979040706.1476445145266" ------=_Part_547_1979040706.1476445145266 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable =E5=9C=A8 2016=E5=B9=B410=E6=9C=8812=E6=97=A5=E6=98=9F=E6=9C=9F=E4=B8=89 UT= C+8=E4=B8=8B=E5=8D=887:50:29=EF=BC=8CVille Voutilainen=E5=86=99=E9=81=93=EF= =BC=9A > > On 12 October 2016 at 14:05, Victor Dyachenko=20 > > wrote:=20 > >> I don't recall anyone suggesting putting Qt or wxWidgets into the=20 > >> standard.=20 > >=20 > > I just wanted to say that one can write portable GUI today using C++=20 > without=20 > > having "C++ standard library".=20 > > One can write a whole lot of things without using the standard library=20 > for that. The issue=20 > there is that such solutions are less portable than they would be as=20 > standard features,=20 > and the availability is another issue.=20 > > That's not true. I have written something containing reusable GUI code=20 portable between platforms with=20 freestanding implementation and hosted implementations of C++, but the=20 standard can't provide enough to cover it. Because the standard can't=20 guarantee the intended GUI APIs being able to be implemented on arbitrary= =20 freestanding implementations it already supported, so it simply can't=20 require it, before having some kinds of "client profiles". The latter will= =20 not likely come true in the near future. >> > Standard? To have big deprecated parts in the Standard in the future?= =20 > >> Why would such deprecation be necessary?=20 > > Why std::auto_ptr, std::strstream et al were deprecated? Because today= =20 > we=20 > > have better solutions. GUI and GUI libraries are evolving. Imagine MFC= =20 > > GUI libraries, and especially their APIs, don't seem to evolve nearly=20 > as fast as some=20 > people like to think. But if your view is that it's better to have=20 > nothing than to have something=20 > in the standard library, I doubt I'm going to agree with that view.=20 > > > mid-90's vintage being the part of Standard. GUI system is a very=20 > > sophisticated thing. Much more complex than vector class or sorting=20 > > algorithm.=20 > > Yeah, which is actually a fair reason to have a standardized GUI=20 > library or to have standardized=20 > facilities that help GUI programming.=20 > --=20 You received this message because you are subscribed to the Google Groups "= ISO C++ Standard - Future Proposals" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to std-proposals+unsubscribe@isocpp.org. To post to this group, send email to std-proposals@isocpp.org. To view this discussion on the web visit https://groups.google.com/a/isocpp= ..org/d/msgid/std-proposals/5644e922-d6c9-411c-9e06-4a5302e0de58%40isocpp.or= g. ------=_Part_547_1979040706.1476445145266 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


=E5=9C=A8 2016=E5=B9=B410=E6=9C=8812=E6=97=A5=E6= =98=9F=E6=9C=9F=E4=B8=89 UTC+8=E4=B8=8B=E5=8D=887:50:29=EF=BC=8CVille Vouti= lainen=E5=86=99=E9=81=93=EF=BC=9A
On 12 October 2016 at 14:05, Victor Dyachenko
<victor.d...@gmail.com> wrote:
>> I don't recall anyone suggesting putting Qt or wxWidgets i= nto the
>> standard.
>
> I just wanted to say that one can write portable GUI today using C= ++ without
> having "C++ standard library".

One can write a whole lot of things without using the standard library
for that. The issue
there is that such solutions are less portable than they would be as
standard features,
and the availability is another issue.

That's not true. I have written something containing reusable GUI code port= able between platforms with freestanding implementation and hosted implemen= tations of C++, but the standard can't provide enough to cover it. Beca= use the standard can't guarantee the intended GUI APIs being able to be= implemented on arbitrary freestanding implementations it already supported= , so it simply can't require it, before having some kinds of "clie= nt profiles". The latter will not likely come true in the near future.=

>> > St= andard? To have big deprecated parts in the Standard in the future?
>> Why would such deprecation be necessary?
> Why std::auto_ptr, std::strstream et al were deprecated? Because t= oday we
> have better solutions. GUI and GUI libraries are evolving. Imagine= MFC

GUI libraries, and especially their APIs, don't seem to evolve near= ly
as fast as some
people like to think. But if your view is that it's better to have
nothing than to have something
in the standard library, I doubt I'm going to agree with that view.

> mid-90's vintage being the part of Standard. GUI system is a v= ery
> sophisticated thing. Much more complex than vector class or sortin= g
> algorithm.

Yeah, which is actually a fair reason to have a standardized GUI
library or to have standardized
facilities that help GUI programming.

--
You received this message because you are subscribed to the Google Groups &= quot;ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to std-proposa= ls+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit https://groups.google.= com/a/isocpp.org/d/msgid/std-proposals/5644e922-d6c9-411c-9e06-4a5302e0de58= %40isocpp.org.
------=_Part_547_1979040706.1476445145266-- ------=_Part_546_1244414449.1476445145266-- .