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 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,3ed4c57426e16006 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,UTF8 Path: g2news2.google.com!news4.google.com!feeder1-2.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail User-Agent: NewsTap/3.2 (iPad) From: Georg Bauhaus Newsgroups: comp.lang.ada Content-Type: text/plain; charset=UTF-8 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: <2071638942327568344.500599rm-host.bauhaus-maps.arcor.de@news.arcor.de> Subject: Re: GtkAda using Glade References: Date: 20 May 2011 08:01:29 GMT Organization: Arcor NNTP-Posting-Date: 20 May 2011 10:01:29 CEST NNTP-Posting-Host: 06b03a1d.newsspool1.arcor-online.net X-Trace: DXC=6SY52F::EejVHOVDjZiIWmaFR\;nG9ROM_E X-Complaints-To: usenet-abuse@arcor.de Xref: g2news2.google.com comp.lang.ada:20308 Date: 2011-05-20T10:01:29+02:00 List-Id: Yannick Duchêne (Hibou57 ) wrote: > Le Thu, 19 May 2011 09:36:07 +0200, Dmitry A. Kazakov > a Ècrit: >> Unfortunately the reality is that the GUI and the functional part of the >> program are tightly interwoven. > Real separation could be achieved if there was a standard protocol for the > communication between both. Because, to achieve a real separation, there > is the need for the program to communicate with the UI as if it was an > external entity, not an entity which is part of its own (as it is supposed > to be in this thread). > > In that matter, the paradigm of the web page (as already noticed in > another thread) could help to learn to do things this way. Indeed, a web page that does not control another application programmatically is an interesting comparison. But I imagine that the new world's operating system, HTML5, is perfect for obfuscation again: it is about at which end you keep status information and then, about how the ends of a web program use it later. For example, you can store status in both browser local storage and in server side storage. Then, distribute the whole program's status dependent control both across web pages and server side programs: Write source text, e.g. JavaScript functions, that has effects at the server side, knowing that a later JavaScript function will then work as intended. Written in such a way, studying the source of the client side will not reveal anything about the logic of why the first function controls the second, indirectly. And neither will studying the server side source reveal how the web end logic depends on the interaction. Reminiscent of the PHP case, isn't it? In fact, according to Douglas Crockford speaking on stage (URL was posted here recently), vendors are trying to push for a change to JavaScript that would make it a better object code language. They are selling tools that reuse their existing language offerings and will produce Javascript output.