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,37023471dc2e1934
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news4.google.com!news1.google.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: "Alex R. Mosteo" <devnull@mailinator.com>
Newsgroups: comp.lang.ada
Subject: Re: Custom model in gtkada?
Date: Fri, 30 Jun 2006 12:28:37 +0200
Message-ID: <4gkcj7F1nhau6U1@individual.net>
References: <3ndpd7br1nn9$.vkcrts8e898z.dlg@40tude.net>
 <20060614210028.GA18024@ws.max.zp.ua>
 <b6ehptggg0ol$.lebhfvkvarnm.dlg@40tude.net>
 <44917d39$0$4495$9b4e6d93@newsread2.arcor-online.net>
 <xw8jxgsp30w8$.1llfb1lh4mohz$.dlg@40tude.net>
 <44941be9$0$11065$9b4e6d93@newsread4.arcor-online.net>
 <14e2r2ftir9ok.i8u1axnplx11.dlg@40tude.net>
 <449a432e$0$15869$bb6a4dc3@news.uunet.fr>
 <mgfz59ck9hje.18zecgqt5ze9w$.dlg@40tude.net> <usllwjbma.fsf@acm.org>
 <Q5Vmg.795589$084.104972@attbi_s22> <ud5cryj2m.fsf@nasa.gov>
 <HqWog.1048852$xm3.717438@attbi_s21>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
X-Trace: individual.net p/pYir+Sel6WrCZSmq2uzAj7AIzzDD8sNxPwBMN/Zbq9FzfCg=
User-Agent: KNode/0.10.2
Xref: g2news2.google.com comp.lang.ada:5328
Date: 2006-06-30T12:28:37+02:00
List-Id: <comp.lang.ada>

Jeffrey R. Carter wrote:

> In the mid-1980s I considered how to implement a windowing system in
> Ada, and decided event queues were the simplest and clearest approach. I
> then used actual windowing systems, with callbacks, and saw nothing to
> change my mind. I've used CLAW, which uses type extension and
> overriding. When I used JEWL, which has an event queue, it was much
> easier to use. This is in part because JEWL is a simple windowing
> library, without the power and complexity of more complete systems. But
> it's also in part because, despite my familiarity with callback
> libraries, the event-queue model is simpler and more intuitive.

Event queues are such a wonderful thing. I had a period of fever in which
I'd program every multitasking program with event queues. It was going to
the extreme, but there are valuable lessons there.