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,4b27f494a96e0530 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news1.google.com!newshub.sdsu.edu!elnk-nf2-pas!newsfeed.earthlink.net!stamper.news.pas.earthlink.net!newsread1.news.pas.earthlink.net.POSTED!a6202946!not-for-mail From: Jeffrey Carter Organization: jrcarter commercial-at acm [period | full stop] org User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: A community Windows binding References: <2004100600261150073%david@bottoncom> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Message-ID: Date: Thu, 07 Oct 2004 17:37:41 GMT NNTP-Posting-Host: 63.184.104.233 X-Complaints-To: abuse@earthlink.net X-Trace: newsread1.news.pas.earthlink.net 1097170661 63.184.104.233 (Thu, 07 Oct 2004 10:37:41 PDT) NNTP-Posting-Date: Thu, 07 Oct 2004 10:37:41 PDT Xref: g2news1.google.com comp.lang.ada:4885 Date: 2004-10-07T17:37:41+00:00 List-Id: Warren W. Gay VE3WWG wrote: > JEWL when I looked at it last (>= yr) was nice and simple. As a > GUI training vehicle, I don't think you can beat it (unless you > insist on training on callbacks). I don't believe that JEWL's > design goals were such that it ever should be a General Purpose > interface for GUI. Problems such as the inability to redirect a > focus to a specific widget limits its wider use. JEWL is very nice for its purpose, which is instruction and fairly simple windowing on Windows. It was never intended to be complete, and is pure GPL. > There was a thread on the GUIs & callbacks sometime ago, where I > believe MDC was quite vocal. Callbacks are a pain, but there aren't > too many practical alternatives. The big main loop that JEWL uses, is > one such alternative, but I am not convinced this scales well to > larger projects. Between callbacks and the single queue of events for all windows of JEWL is an approach more suited to concurrent languages: multiple queues, one per top-level window, with the assumption of one task per queue/window. There should be the ability to select what events will be put in the queue, and the possibility to combine queues when a window doesn't merit its own task. Such an approach should scale better than JEWL's single queue, and be more readable than callbacks. What would be ideal would be an Ada-centric windowing library, with implementations based on Win32, X, and the like. -- Jeff Carter "Run away! Run away!" Monty Python and the Holy Grail 58