caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "François-Xavier HOUARD" <IdeFX@Iname.com>
To: Daan Leijen <daan@cs.uu.nl>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] WxWidgets?
Date: Sun, 19 Sep 2004 23:46:55 +0200	[thread overview]
Message-ID: <1095621195.5727.42.camel@Bess> (raw)
In-Reply-To: <414A0CED.5070502@cs.uu.nl>

> Hi all,
> 
> I have created a binding from Haskell to wxWidgets, called wxHaskell.
> You can find more information (and nice screenshots) at 
> <wxhaskell.sourceforge.net>
> There is also a paper about it at <www.cs.uu.nl/~daan/pubs.html>
> 
> I also know that there is a student in France that has made a lot of 
> progress
> on an O'Caml binding to wxWidgets (as he contacted me a few times
> about technical issues). He also used the wxEiffel C wrapper (that wxHaskell
> uses)

I'm the french student having worked on it. The reason why I haven't
made any official release is that it doesn't work at all; I couldn't
solve memory issues. 
I'm working on a little "developper documentation" on my spare time, but
I have got fewer and fewer spare time, so... And what i've done for the
moment is in french... 

Whatever, what I can say you is that i've made a caml tool equivalent to
"wxDirect", which parses C header, and generate a typed Caml binding to
wxWidget. Even if the source of this tool is very awful (i couldn't find
time to clean it), it works quiet well, as the binding works -at least
on the few examples inspired from wxhaskell's one that i've tried-, and
as the typing scheme seems fine. I also tried to find solution to make a
nice integration of this binding to Ocaml, including garbage collection,
which doesn't work at all.

I think i will release something -a developper release- when the
developper documentation is ready, but i can't say you when: as I said
upper, i have very very few time to spend on it.

Whatever, feel free to ask me for more information, i will try to help
anybody asking...

Good night...


François-Xavier Houard
IdeFX@Iname.com

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  parent reply	other threads:[~2004-09-19 21:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 20:08 chris.danx
2004-09-16 20:25 ` Richard Jones
2004-09-16 21:29   ` chris.danx
2004-09-16 21:39     ` Richard Jones
2004-09-16 22:00       ` Daan Leijen
2004-09-17  0:06         ` SooHyoung Oh
2004-09-17  4:39           ` skaller
2004-09-17  7:13           ` Daan Leijen
2004-09-17  8:04             ` Jean-Marc EBER
2004-09-19 21:46         ` François-Xavier HOUARD [this message]
2004-09-16 23:58       ` chris.danx
2004-09-17  8:10         ` Richard Jones
2004-09-17 12:38     ` Olivier Andrieu
2004-09-17 13:11       ` chris.danx
2004-09-17 13:51         ` skaller
2004-09-17 18:31           ` Brian Hurt
2004-09-17  7:53   ` Benedikt Grundmann
2004-09-16 20:44 ` Micha
2004-09-16 20:56 ` Basile STARYNKEVITCH
2004-09-20  1:02 ` [Caml-list] WxWidgets? - wxcaml SooHyoung Oh
2004-09-21 23:21   ` Zeno

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=1095621195.5727.42.camel@Bess \
    --to=idefx@iname.com \
    --cc=caml-list@inria.fr \
    --cc=daan@cs.uu.nl \
    /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).