caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Martin DeMello <martindemello@gmail.com>
To: Alain Frisch <alain.frisch@lexifi.com>
Cc: ocsigen@inria.fr, OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Announce: ocaml-vdom (pre-release)
Date: Wed, 30 Nov 2016 14:46:41 -0800	[thread overview]
Message-ID: <CAFrFfuETDbyHOUsQFFiobLLO11FFWZZHraWLjXk8fZRczu_f6w@mail.gmail.com> (raw)
In-Reply-To: <96757896-e79c-f940-fc3a-090fc1419df2@lexifi.com>

[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]

Looks very exciting, thanks for the release!

Any tips on setting up a project? For example, with elm I use
elm-webpack-starter [https://github.com/moarwick/elm-webpack-starter],
which sets up an asset pipeline and a dev environment with live reloading.

martin

On Wed, Nov 30, 2016 at 8:52 AM, Alain Frisch <alain.frisch@lexifi.com>
wrote:

> Dear all,
>
> You might be interested in the ocaml-vdom project which has been used by
> LexiFi for some time and open-sourced recently.  It contains two components
> which we use to create our browser-side UIs with js_of_ocaml and which
> might be useful to the community:
>
>    - Bindings to the DOM and other browser APIs, implemented with
> gen_js_api.  (Partial bindings, expanded on demand.)
>
>    - An implementation of a "virtual DOM" and the "Elm architecture", i.e.
> a programming model where the UI is specified by a state type, a view
> function (producing a functional version of the DOM), and an update
> function that modifies the state based on messages (generated by UI events
> or external interactions).
>
>
> Project page:
>
>      https://github.com/LexiFi/ocaml-vdom
>
>
> -- Alain
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>

[-- Attachment #2: Type: text/html, Size: 2309 bytes --]

  parent reply	other threads:[~2016-11-30 22:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 16:52 Alain Frisch
2016-11-30 19:22 ` Yaron Minsky
2016-12-01  9:32   ` Alain Frisch
2016-12-01 22:18     ` Yaron Minsky
2016-11-30 22:46 ` Martin DeMello [this message]
2016-12-01  9:56   ` Alain Frisch
     [not found] ` <CAG+nEjzO1qFfxHSMqueiKcTJyJYnREmvXhzGR7H+noBmV2oUKw@mail.gmail.com>
2016-12-02 13:41   ` Alain Frisch
2016-12-02 16:59     ` Vincent Balat
2016-12-02 18:18       ` Alain Frisch
2016-12-02 22:31     ` Yaron Minsky
2016-12-10 13:34       ` SP
     [not found]     ` <5db7c03d-bec8-8285-b458-82e681842dbb@zoho.com>
2016-12-05 15:55       ` Ashish Agarwal

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=CAFrFfuETDbyHOUsQFFiobLLO11FFWZZHraWLjXk8fZRczu_f6w@mail.gmail.com \
    --to=martindemello@gmail.com \
    --cc=alain.frisch@lexifi.com \
    --cc=caml-list@inria.fr \
    --cc=ocsigen@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).