From: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
To: khamenya@mail.ru
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] OCaML, GUI, rapid prototyping
Date: Fri, 12 Sep 2003 15:26:33 +0900 [thread overview]
Message-ID: <20030912152633O.garrigue@kurims.kyoto-u.ac.jp> (raw)
In-Reply-To: <1081587883.20030911181547@mail.ru>
From: "Valery A.Khamenya" <khamenya@mail.ru>
I might be biased, but
> Q1. How advanced might be the GUI in OCaml applications?
As advanced as you wish.
GUI is a lot of dirty work to get ill-conceived toolkits to do what
you really want...
> Q2. What are the GUI engines (gtk/fltk/qt/.../?) supported today for
> OCaml?
GTK+ (both 1 and 2), and Tcl/Tk.
Tcl/Tk is included in the distribution.
> Q3. What kind of development framework are available in spirit of
> Delphi/Kylix/Glade?
I suppose you mean GUI-builders?
You can use glade in combination with LablGTK, and there are also a
few other options (all for LablGTK).
However, you must realize that Caml programming being much
higher-level in flavour compared to C, once you have a reasonnable
level of proficiency with the toolkit, you work faster by writing the
GUI code yourself.
You can have a look at the following link for LablGTK related software
http://wwwfun.kurims.kyoto-u.ac.jp/soft/olabl/lablgtk.html
> Q4. And what are the near plans concerning the issues above?
Hopefully LablGTK2 should become the main platform.
My only concern is that there is no good native Gtk for MacOSX yet.
(This just means that you have to install Apple's X11 first)
Cheers,
Jacques Garrigue
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2003-09-12 6:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 16:15 Valery A.Khamenya
2003-09-11 16:36 ` Richard Jones
2003-09-12 6:26 ` Jacques Garrigue [this message]
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=20030912152633O.garrigue@kurims.kyoto-u.ac.jp \
--to=garrigue@kurims.kyoto-u.ac.jp \
--cc=caml-list@inria.fr \
--cc=khamenya@mail.ru \
/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).