caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@maxtal.com.au>
To: bcpierce@cis.upenn.edu
Cc: ohl@hep.tu-darmstadt.de, caml-list@inria.fr
Subject: Re: Preferred GUI Toolkit for O'Caml 3?
Date: Wed, 23 Feb 2000 00:41:24 +1100	[thread overview]
Message-ID: <38B29204.D4882C63@maxtal.com.au> (raw)
In-Reply-To: <6830.951153768@saul.cis.upenn.edu>

"Benjamin C. Pierce" wrote:
> 
> We in the Unison group are also about to embark on a major UI redesign
> and have been wondering which toolkit to use.  Besides Thorsten's
> points, there are two more that are critical concerns for us:
> 
>    * seamless portability (Unix and Win32)
>    * ability to build statically linked binaries (this is a pretty
>      big drawback to the Tk-based solutions)

	I do not understand the latter comment. Tk can be statically
linked, or dynamically linked, or even dynamically loaded as a tcl
package. GTK can also be statically or dynamically linked.

-- 
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:[~2000-02-22 14:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-18 13:54 Thorsten Ohl
2000-02-21 17:22 ` Benjamin C. Pierce
2000-02-22 11:41   ` William Chesters
2000-02-23  7:36     ` Alan Schmitt
2000-02-23  9:24     ` Sven LUTHER
2000-02-24 10:24       ` Fabrice Le Fessant
2000-02-25 16:22         ` skaller
2000-02-22 13:41   ` skaller [this message]
2000-02-22 14:22     ` Benjamin C. Pierce
2000-02-22  1:46 ` Jacques Garrigue
2000-02-22 13:39   ` skaller
2000-02-22 20:13     ` Gerd Stolpmann
2000-02-22  8:17 ` Sven LUTHER
2000-02-22 11:04 ` jean-marc alliot
2000-02-22 17:05 ` Pascal Cuoq

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=38B29204.D4882C63@maxtal.com.au \
    --to=skaller@maxtal.com.au \
    --cc=bcpierce@cis.upenn.edu \
    --cc=caml-list@inria.fr \
    --cc=ohl@hep.tu-darmstadt.de \
    /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).