Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Jake Donham <jake@donham.org>
To: caml-list@inria.fr
Subject: ANN: ocamljs 0.2 + orpc 0.2 + froc 0.1
Date: Wed, 22 Apr 2009 09:37:56 -0700	[thread overview]
Message-ID: <c7e4e9f0904220937h3a9f1e7erf4375cee5f46cb1@mail.gmail.com> (raw)

Hi,

I am happy to announce the release of three related projects:

  ocamljs 0.2: Javascript backend for ocamlc + libraries for web programming
  orpc 0.2: generates RPC bindings from OCaml signatures (ONC RPC with
Ocamlnet or HTTP with ocamljs)
  froc 0.1: library for functional reactive programming, works with ocamljs

You can find the releases at:

  http://code.google.com/p/ocamljs/
  http://code.google.com/p/orpc2/
  http://code.google.com/p/froc/

Changes to ocamljs since version 0.1 include:

  new 'dom' library for browser programming
  new 'lwt-js' library for Lwt lightweight threads (useful with orpc)
  new 'jslib' library for parsing / pretty-printing Javascript with Camlp4
  fuller language support (including calling Javascript methods with
OCaml object syntax)
  support for Javascript inlined in OCaml code
  findlib support

Changes to orpc since version 0.1 include:

  support for RPC over HTTP from an ocamljs client to an ocaml server
  the 'lwt-equeue' library supports all of Lwt on top of Equeue, plus
extra concurrency stuff

Froc is a library for functional reactive programming in the style of
Flapjax and FrTime. It includes the 'froc-dom' library for browser
programming with ocamljs, but can also be used with regular OCaml.

I hope you find this work useful, and I am eager to hear your feedback.

Jake


                 reply	other threads:[~2009-04-22 16:38 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=c7e4e9f0904220937h3a9f1e7erf4375cee5f46cb1@mail.gmail.com \
    --to=jake@donham.org \
    --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