caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: John Max Skaller <skaller@ozemail.com.au>
To: frouaix@liquidmarket.com
Cc: caml-list@inria.fr
Subject: Re: OCaml's long range graphical direction?
Date: Sat, 10 Feb 2001 04:50:03 +1100	[thread overview]
Message-ID: <3A842DCB.1A32D8DF@ozemail.com.au> (raw)
In-Reply-To: <200102082001.f18K1VH08374@nez-perce.inria.fr>

Francois Rouaix wrote:

> I actually think that none of CamlTk/LablTK/LabelGTK fit the most common need
> in GUI development. In many cases, it still strikes me as utterly boring and
> time consuming to write *code* to put up menus, buttons, dialogs and such. Of
> course, from time to time, when you need some form of widget that is a bit
> original, programming will be useful. But that doesn't happen a lot, unless
> you write something that needs complex rendering or interaction.
> Back in 1985, Apple started using resources to define interfaces. More
> recently, Palm used resources again to define interfaces. More recently,
> Mozilla folks used XML based representation (XUL) to define interfaces, with a
> GUI level scripting language (JavaScript/ECMAScript).

	Ah, but the specification of the resources is nothing more
than yet another programming language, and a seriously deficient one
usually (for example, not Turing complete).

	Furthermore, it is evident that this second programming language
must be _bound_ to the algorithmic one, and that binding is invariably
fragile and a serious problem.  That is, I think there is a downside
to separating functionality and appearance. As any serious game player
knows, the two are intimately connected.

-- 
John (Max) Skaller, mailto:skaller@maxtal.com.au
10/1 Toxteth Rd Glebe NSW 2037 Australia voice: 61-2-9660-0850
checkout Vyper http://Vyper.sourceforge.net
download Interscript http://Interscript.sourceforge.net



  parent reply	other threads:[~2001-02-10 21:15 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-05 17:48 Daniel Ortmann
2001-02-06  9:28 ` Xavier Leroy
2001-02-06 18:19   ` Sven LUTHER
2001-02-07 21:30     ` Pierre Weis
2001-02-08  7:32       ` Sven
2001-02-08  1:59     ` Jacques Garrigue
2001-02-08  7:55       ` Sven
2001-02-09  8:47         ` Claudio Sacerdoti Coen
2001-02-09 10:00           ` Sven LUTHER
2001-02-08 20:35       ` Brian Rogoff
2001-02-09  1:28         ` Jacques Garrigue
2001-02-09 18:11           ` Brian Rogoff
2001-02-10 13:01             ` Jacques Garrigue
2001-02-09 20:01           ` Marcin 'Qrczak' Kowalczyk
2001-02-12 14:52             ` Nicolas barnier
2001-02-12 23:47               ` Jacques Garrigue
2001-02-15 12:21                 ` [Caml-list] " Sven LUTHER
2001-02-08 10:28     ` Alan Schmitt
2001-02-09  1:24       ` bcpierce
2001-02-06 20:30   ` Dale Arntson
2001-02-07  0:39   ` John Max Skaller
2001-02-08 20:01   ` Francois Rouaix
2001-02-09  9:41     ` Sven LUTHER
2001-02-09  9:49     ` Jacques Garrigue
2001-02-09 19:58       ` Jerome Vouillon
2001-02-10 12:36         ` Jacques Garrigue
2001-02-10 21:25         ` Pierre Weis
2001-02-09 17:50     ` John Max Skaller [this message]
2001-02-06 19:33 Maxence
2001-02-09 23:31 Arturo Borquez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3A842DCB.1A32D8DF@ozemail.com.au \
    --to=skaller@ozemail.com.au \
    --cc=caml-list@inria.fr \
    --cc=frouaix@liquidmarket.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).