From: Kuba Ober <ober.14@osu.edu>
To: caml-list@inria.fr
Subject: Camelia progress - it compiles ;)
Date: Thu, 30 Oct 2008 13:46:17 -0400 [thread overview]
Message-ID: <200810301346.18840.ober.14@osu.edu> (raw)
I've finished the initial part of translating Camelia
to Qt4. It now uses no Qt3 classes/methods, and compiles cleanly
with Qt3 support disabled. Some minor Qt3-isms were refactored,
but it's just a tip of the iceberg. I now have to get it into a running shape.
I commit to SVN every day or two, on the days that I have time to work
on it, but it's still perhaps too early for others to contribute.
It'd be better to wait till it actually runs and can do something useful.
Right now it won't even bring the main window up, just idles ;)
I don't mind anyone looking at the code obviously, that's why it's
pretty much up-to-date in SVN, and it's GPL too :)
As for bringing it to ocamlforge: my grander plan is for Camelia to become the
defacto "minimal IDE" for a variety of programming environments, thus it
won't be limited to OCaml. I'd like it to replace various, often
underdeveloped, proprietary tools supplied by microcontroller vendors,
and also to provide a common alternative IDE for common open source
environments (say gcc/gdb for embedded devices, picmicro tools, etc).
It will stay minimal in the sense that it's meant to be a portable,
single-executable on Windows, same on Unices, and it won't really support
any sort of a plugin interface; everything will be compiled-in. I also don't
plan to veer in the direction of big IDEs like Eclipse or Kdevelop: I find
that I simply do not use most of their potential, and many people can
be perfectly productive without a monster IDE (as some have indicated in
a previous thread).
Cheers, Kuba
reply other threads:[~2008-10-30 17:46 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=200810301346.18840.ober.14@osu.edu \
--to=ober.14@osu.edu \
--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