caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: Louis Gesbert <louis.gesbert@ocamlpro.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] geany as an ocaml ide
Date: Mon, 11 Feb 2013 13:14:12 +0100	[thread overview]
Message-ID: <CAPFanBGW50D_dGXR-UQcz2wGYKd4wf4YEp5fdzxwGDQxtwS=_A@mail.gmail.com> (raw)
In-Reply-To: <201302111240.35711.louis.gesbert@ocamlpro.com>

I must say I'm a bit dubious of dedicated editors: people prefer to
use the tools they're familiar with from other languages, and I'm not
really sure what the added value of a different tool would be. There
have been attempts to write editors for OCaml (Cameleon{,2}, zed (
https://github.com/diml/zed )...), so far none of them really gained
traction.

Volunteers work on whatever they fancy and I prefer not to interfere
negatively -- though it's unclear in this case whether this is a
personal side-project or an OCamlPro project. Moreover, all these
efforts have led to interesting byproducts: various libraries from
Cameleon (eg. ocaml-rss http://zoggy.github.com/ocamlrss/ ) and zed (
and in particular the nice toplevel utop https://github.com/diml/utop
).

That said, I would still feel more enthusiastic about a project that
can be used with other tools people use ( this is a good property of
ocp-indent for example ), or directly improving OCaml support about
tools that already have a user base : syntax highlighting libraries
for various editors, etc. For example, Online Client-side
Javascript-implemented In-the-cloud programming editors are all the
rage now, they use a relatively small number of popular Javascript
edition engines under the hood, is there work to do to make sure OCaml
a first-class citizen there?

On Mon, Feb 11, 2013 at 12:40 PM, Louis Gesbert
<louis.gesbert@ocamlpro.com> wrote:
> OCaml is definitely lacking in this area; I am at the moment working precisely
> on solving this issue, with a dedicated Gtk editor that runs on Linux, OSX and
> Windows. It is pretty basic at the moment but already has code edition and
> working toplevel interaction (no compilation or project yet).
>
> Release is intended in a few months from now, with sufficient features for
> beginners and students. If successful, it will then be extended to handle
> bigger projects (multi-file, build system integration, etc.).
>
> Until then, you may see the project's github page at
> https://github.com/OCamlPro/ocp-edit-simple (name temporary)
>
> --
> Louis Gesbert, OCamlPro
>
> Le Monday 11 February 2013 01:49:41, Martin DeMello a écrit :
>> I spent some time last night going through all the "what is a good
>> (beginner's) ide for ocaml?" threads I could find online, and trying
>> out the various options suggested. I ruled out the following:
>>
>> * vim, emacs and eclipse (not beginner-friendly; people who want to
>> use them will know how to do it)
>> * anything that did not provide a binary install for Windows and OSX,
>> and wasn't a simple configure/make/make install on linux
>> * anything that needed fiddling with config files just to install it
>> * anything that needed the OCaml sources to be independently present
>> and configured (!)
>> * anything that was abandoned, or didn't seem to support OCaml 4
>>
>> I was left with Geany and Komodo Edit as possibilities, and Geany won
>> out by letting me open up a test.ml file and immediately being able to
>> find and run the OCaml compiler. At least on Linux, it was a perfect
>> beginner-friendly experience.
>>
>> So what do people think about ocaml.org officially promoting Geany as
>> the answer to "I'm learning OCaml; what is a good IDE?"? I'd be happy
>> to write up a page on it and contribute it.
>>
>> martin
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs

  reply	other threads:[~2013-02-11 12:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11  0:49 Martin DeMello
2013-02-11  1:37 ` Ashish Agarwal
2013-02-11 11:40 ` Louis Gesbert
2013-02-11 12:14   ` Gabriel Scherer [this message]
2013-02-11 12:47     ` Fabrice Le Fessant
2013-02-11 12:58       ` Gabriel Scherer
2013-02-11 13:34         ` Fabrice Le Fessant
2013-02-11 13:12     ` Daniel Bünzli
2013-02-11 23:24   ` Martin DeMello
2013-02-12 11:29     ` Louis Gesbert
2013-02-13 14:12       ` AW: " Gerd Stolpmann
2013-02-13 15:41         ` Wojciech Meyer
2013-02-13 17:09           ` AW: " Gerd Stolpmann
2013-02-13 21:17             ` Wojciech Meyer
2013-02-13 22:06               ` Török Edwin
2013-02-13 23:30                 ` Wojciech Meyer
2013-02-13 23:44               ` Jon Harrop
2013-02-13 20:49           ` Martin DeMello
2013-02-13 16:30   ` Jon Harrop
     [not found] <fa.1FRjr8uAIOVSiUsks0LzN6W66uw@ifi.uio.no>
     [not found] ` <fa.gn5tDTJZJCRXzApZqR8w/J9DpfE@ifi.uio.no>
     [not found]   ` <fa.cGTdfVOLEIBfOV6bs56X7I0nLbo@ifi.uio.no>
     [not found]     ` <fa.7UNgdMcpsuTGVINo2cZWiHvr2Wg@ifi.uio.no>
2013-02-13  9:13       ` ftovagliari

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='CAPFanBGW50D_dGXR-UQcz2wGYKd4wf4YEp5fdzxwGDQxtwS=_A@mail.gmail.com' \
    --to=gabriel.scherer@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=louis.gesbert@ocamlpro.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).