From: hmf@inescporto.pt
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] New Ocaml Plug-in for NetBeans
Date: Sat, 26 Jul 2008 09:46:19 +0100 [thread overview]
Message-ID: <1217061979.488ae45b452b9@webmail.inescporto.pt> (raw)
Jon Harrop wrote:
> On Wednesday 23 July 2008 09:50:03 adonis28850 wrote:
>> thanks Hugo, i know there's a Eclipse plug-in, but i would like to get it
>> on NetBeans,so if someone could help i will thanks!
>
> 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?
>
Because writing one that is usable and complete requires a *lot* of
effort. Maybe the authors of cameleon (http://home.gna.org/cameleon/)
could also comment on the amount of work and commitment that is
required to build one of these things.
> This has long since seemed like an obvious idea to me but everyone continues
> to battle on with tools like Emacs and Eclipse that are (IMHO) horrendous.
>
Hmmm... if I recall correctly you mentioned one of the advantages of
using F# is its IDE (Visual Studio?). In fact code-completion seemed to
be one of the functionalities you pointed out as useful. Well, OcaIDE
has this. And much more. I figure if you believe a full blown IDE for
F# is advantageous, then it should also stand for Eclipse, Netbeans,
or any other IDE.
Mind you, I assume your "horrendous" may also have something to do with
the plug-ins quality. I believe OcalIDE is quite usable at this point in
time. So.. try it out. Join the forum and give you feedback.
BTW, I am harping on this issue because I truly believe that a good IDE
is an excellent medium for promoting the use of Ocaml.
Rgrds,
HF.
next reply other threads:[~2008-07-26 8:46 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 8:46 hmf [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2008-07-26 12:44 hmf
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 9:18 hmf
2008-07-26 9:22 ` Richard Jones
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-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
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
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=1217061979.488ae45b452b9@webmail.inescporto.pt \
--to=hmf@inescporto.pt \
--cc=caml-list@yquem.inria.fr \
--cc=jon@ffconsultancy.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