From: "Warp" <warplayer@free.fr>
To: "OCaml" <caml-list@inria.fr>
Subject: [Caml-list] OCaml IDE for Win32
Date: Tue, 25 Dec 2001 22:39:55 +0100 [thread overview]
Message-ID: <001c01c18d8c$b4cc72c0$65b00d50@warp> (raw)
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
Hello
I am starting now to think about building an IDE for OCaml under Win32. The Linux port will be done after.
Goals are :
- easy typing ( multiple-undo, syntax highlight, [auto indent], modes, search/replace tools, etc... )
- highly customizable ( custom keys and menus, configurations scripts written in ocaml )
- extensible ( modes in ocaml )
- written in ocaml ( with some C/C++ dll for Win32 User Interface - no GTK )
Targeted audience are windows developers.
This is a round-table, i would like to collect as much ideas / opinions before starting the project.
I have already seen EFuncs and Cameleon in the Hump, Efuncs is a little too much "emacs-like" and Cameleon seems to be far more than an editor. Does anyone have heard about other projects ?
Warp
http://warplayer.free.fr
[-- Attachment #2: Type: text/html, Size: 1765 bytes --]
reply other threads:[~2001-12-25 21:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='001c01c18d8c$b4cc72c0$65b00d50@warp' \
--to=warplayer@free.fr \
--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;
as well as URLs for NNTP newsgroup(s).