From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] New Ocaml Plug-in for NetBeans
Date: Sat, 26 Jul 2008 03:57:40 +0100 [thread overview]
Message-ID: <200807260357.40358.jon@ffconsultancy.com> (raw)
In-Reply-To: <20080726102402.b0bcbd3c.mle+ocaml@mega-nerd.com>
On Saturday 26 July 2008 01:24:02 Erik de Castro Lopo wrote:
> Jon Harrop wrote:
> > If I might stick my oar in: why don't the OCaml community write an IDE
> > for OCaml in OCaml using Camlp4 for parsing with throwback and LablGTK
> > for the GUI?
>
> Most people who actually code in Ocaml do so using the best IDE on
> the planet, Unix. For those people an IDE is a step backwards and
> hence they have no interest in writing one.
Graphical throwback of documentation is invaluable for interactive API
exploration, particularly in the context of GUI programming (I currently
trawl through ocamlbrowser's useful but very basic interface). A GUI to
browse and visualize performance profiles is useful (I currently browse
gprof's output as plain text files using KWrite). A GUI to visualize
dependencies is useful (I currently lookup the use of "dot" every time I need
it and the PostScript output is typically mangled by GhostScript).
> So I have an idea; why don't *you* write a cross platform IDE and if
> it really is better than Unix then people would use it.
I shall see if it is feasible to develop such an application within an OCaml
Journal article or two. I think it would be both very useful and a very
instructive educational exercise combining several of OCaml's strengths.
However, the resulting program would most likely be difficult to distribute
due to licensing issues (e.g. if you want to reuse OCaml's typechecker or
top-level) and could not be a viable commercial product due to the
limitations of OCaml itself.
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/products/?e
next prev parent reply other threads:[~2008-07-26 2:57 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 11:14 adonis28850
2008-07-23 8:42 ` hmf
2008-07-23 8:50 ` adonis28850
2008-07-25 23:56 ` Jon Harrop
2008-07-26 0:24 ` Erik de Castro Lopo
2008-07-26 2:57 ` Jon Harrop [this message]
2008-07-26 12:25 ` Romain Beauxis
2008-07-26 9:09 ` Richard Jones
2008-07-28 17:25 ` Pal-Kristian Engstad
2008-07-28 19:25 ` Jon Harrop
2008-07-26 18:12 ` adonis28850
2008-07-26 8:46 hmf
2008-08-20 6:29 ` Maxence Guesdon
2008-08-20 14:38 ` Richard Jones
2008-08-22 6:34 ` Maxence Guesdon
2008-08-20 16:32 ` Jon Harrop
2008-08-22 6:41 ` Maxence Guesdon
2008-09-07 23:31 ` Nathaniel Gray
2008-09-08 1:10 ` Jon Harrop
2008-09-09 5:31 ` Nathaniel Gray
2008-09-09 7:43 ` Jon Harrop
2008-09-09 7:50 ` Nathaniel Gray
2008-08-27 20:24 ` kirillkh
2008-09-02 6:49 ` Maxence Guesdon
2008-07-26 9:02 hmf
2008-07-26 9:19 ` Richard Jones
2008-07-28 9:58 ` Florian Hars
2008-07-26 10:03 ` Erik de Castro Lopo
2008-07-26 11:40 ` Jon Harrop
2008-07-26 12:07 ` Erik de Castro Lopo
2008-07-26 15:22 ` Jon Harrop
2008-07-29 14:16 ` Damien Doligez
2008-07-29 14:30 ` Lukasz Stafiniak
2008-07-29 18:01 ` Jean-Christophe Filliâtre
2008-09-07 21:39 ` Nathaniel Gray
2008-07-26 11:42 ` Jon Harrop
2008-07-26 9:18 hmf
2008-07-26 9:22 ` Richard Jones
2008-07-26 12:01 hmf
2008-07-26 12:25 ` Erik de Castro Lopo
2008-07-26 15:37 ` Jon Harrop
2008-07-26 12:44 hmf
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=200807260357.40358.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--cc=caml-list@inria.fr \
/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