From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,b6df8f8501cf7275 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,UTF8 X-Received: by 10.180.96.231 with SMTP id dv7mr8107748wib.6.1356786595588; Sat, 29 Dec 2012 05:09:55 -0800 (PST) Path: l12ni263057wiv.1!nntp.google.com!proxad.net!feeder1-2.proxad.net!usenet-fr.net!gegeweb.org!aioe.org!.POSTED!not-for-mail From: =?utf-8?Q?Yannick_Duch=C3=AAne_=28Hibou57?= =?utf-8?Q?=29?= Newsgroups: comp.lang.ada Subject: Re: Easiest way to build Qt/Gtk interfaces for Ada programs Date: Sat, 29 Dec 2012 14:09:50 +0100 Organization: Ada @ Home Message-ID: References: <1gda5kzj50h3l.jzmq13s0hw74.dlg@40tude.net> <1uzqolxxpmz0v.jea876uzf4tc$.dlg@40tude.net> NNTP-Posting-Host: aWaWeUaBdaj2Zzc04J1v5A.user.speranza.aioe.org Mime-Version: 1.0 X-Complaints-To: abuse@aioe.org User-Agent: Opera Mail/12.12 (Linux) X-Notice: Filtered by postfilter v. 0.8.2 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-Transfer-Encoding: Quoted-Printable Date: 2012-12-29T14:09:50+01:00 List-Id: Le Sat, 29 Dec 2012 13:27:56 +0100, Dmitry A. Kazakov = a =C3=A9crit: >>> You have to design all >>> vital data structures as models compatible to the GUI framework at >>> hand. >> You may do this way, while you are as much free to adapt the UI to an= UI >> specification, a specification which specify a human interface to a >> computation or service interface. > > No way. If you have, say, a DB and want to show its contents in a list= > control, the DB client must be a list store (the model deployed by the= = > list > control). If the DB client was designed in a way that does not support= > delivery of the result set incrementally, in portions, the UI will blo= ck > when rendering large result sets. If the DB client delivers each row > separately, that will choke the UI with a flood of events etc. You can= do > nothing about it. You have to change the client [or write new list = > widget]. The presenter can handle this. Or else, a specific widget is an option = too, indeed. >>> You have to place inspection/rollback/abort check points in all >>> lengthy operations to be able to add progress bars, cancel buttons e= tc. >> You may, if you designed the application. But you may as much have to= = >> add >> an interface to an already existing application which does not provid= e >> these facilities. > > It is very simple to [dis]prove your theory. Take (RM G.3.1) > > function Solve (A : Real_Matrix; X : Real_Vector) return Real_Vector; > > The objective is to start it on a button click, show a modeless dialog= = > with > a progress bar and a cancel button inside. That is going too far. >> Also, may be there's some confusions between application interface an= d >> user interface in this topic (some comments make me feel that; see = >> above). > > Oh, yes. Fancy papers about GUI design consider UI the problem space. = = > They > already took for granted that applications are built around the GUI. A= nd > all GUI frameworks I know require no less. These are two problem spaces, and none of both is at the centre (that's = = why it may suggest mediation). Have an happy day -- = =E2=80=9CSyntactic sugar causes cancer of the semi-colons.=E2=80=9D [1] =E2=80=9CStructured Programming supports the law of the excluded muddle.= =E2=80=9D [1] [1]: Epigrams on Programming =E2=80=94 Alan J. =E2=80=94 P. Yale Univers= ity