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,ASCII
X-Received: by 10.180.74.74 with SMTP id r10mr9541531wiv.3.1356776479959;
Sat, 29 Dec 2012 02:21:19 -0800 (PST)
Path:
i11ni329919wiw.0!nntp.google.com!proxad.net!feeder1-2.proxad.net!193.252.117.184.MISMATCH!feeder.news.orange.fr!not-for-mail
Date: Sat, 29 Dec 2012 11:23:30 +0100
From: Blady
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: Easiest way to build Qt/Gtk interfaces for Ada programs
References:
<87072854-0f81-41fd-8cb0-ede78fccf6e7@googlegroups.com>
<52aed30c-1fd3-407e-be52-2c366b9002d6@googlegroups.com>
<49ad97eb-fac1-49f0-a4ea-2dd79fa803d0@googlegroups.com>
In-Reply-To:
Message-ID: <50dec41f$0$8991$ba4acef3@reader.news.orange.fr>
Organization: les newsgroups par Orange
NNTP-Posting-Date: 29 Dec 2012 11:21:19 CET
NNTP-Posting-Host: 2.9.206.243
X-Trace: 1356776479 reader.news.orange.fr 8991 2.9.206.243:11279
X-Complaints-To: abuse@orange.fr
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Date: 2012-12-29T11:21:19+01:00
List-Id:
Le 29/12/12 01:48, Randy Brukardt a �crit :
> wrote in message
> news:49ad97eb-fac1-49f0-a4ea-2dd79fa803d0@googlegroups.com...
> ....
>> Thanks. That is what I was looking for!! So, the workflow seems to be:
>> creating the widjets with Glade, then using Gate3 to generate Ada code,
>> then using the generated code in Ada programs.
>
> I suspect that this workflow is the problem that Dmitry is referring to. It
> doesn't mesh well with incremental, agile development, where you are
> constantly tweaking both the GUI and the code that supports it.
>
> I realize that this makes it possible for one "front-end" to support many
> different code generation schemes (and that code generation is the "easy"
> part of a GUI builder), but it is just too far from the sort of control
> needed to make real, living applications. The Claw Builder (for instance),
> supports specifying how the package specification corresponding to a dialog
> box will look, whether it is just a single subprogram call (for a dialog
> that does all of its work in call-backs), a subprogram call that returns a
> visible record (of the data specified by the box), or whether the dialog
> type is also visible (so that multiple instances can be created). These
> sorts of decisions can't be productively made by the software alone, and
> only generating a single template is never going to have the flexibility
> needed for these things.
>
> Of course, the other approach is a heck of a lot of work, one reason why the
> Claw Builder's development has stalled...
>
> Randy.
>
>
Hello, I don't know about Claw, I use GtkAda for the same reason as Dmitry.
The question is why not Qt or else... Claw.
I aim building GUI native apps for Mac in Ada, maybe Cocoa without
success up to now.
Well, the link http://en.wikipedia.org/wiki/Glade_Interface_Designer
given by Justin show a very interesting chart at the end : Ada is not
present. It's really amazing ;-)
Ada programmers should'nt any more ask themselves the question : which
GUI Ada API for my program?
What about of standardized graphic Ada specification packages?
Compiler providers could then map the specifications to any underlying
graphic toolkit or native system API.
In this way GUI Ada program will be source code portable as the aim of Ada.
Ada 2012 is born this month, an idea for future Ada 202x?
Happy New Year 2013, Pascal.