From: Drup <drupyog+caml@zoho.com>
To: caml-list@inria.fr, ocsigen@inria.fr
Subject: [Caml-list] [ANN] TyXML 4.0
Date: Tue, 24 May 2016 00:27:11 +0200 [thread overview]
Message-ID: <1b0dfd55-54e6-e3af-498f-812e9c969693@zoho.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
It is with great pleasure that we are announcing the release of TyXML
4.0.0. The major features of this new release are a new PPX syntax
extension that allows to use the standard HTML syntax and an improved
user experience for both old and new TyXML users.
TyXML is a library for building statically correct HTML5 and SVG
documents. It provides a set of combinators which use the OCaml type
system to ensure the validity of the generated document. TyXML’s
combinators can be used to build textual HTML and SVG, but also DOM
trees or reactive interfaces, using Eliom and Js_of_ocaml.
A presentation of the new release is available on the ocsigen blog
<http://ocsigen.github.io/blog/2016/05/20/tyxml4/> and the changelog is
available on github <https://github.com/ocsigen/tyxml/releases/tag/4.0.0>.
Happy HTML and SVG hacking!
[-- Attachment #2: Type: text/html, Size: 1150 bytes --]
reply other threads:[~2016-05-23 22:27 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=1b0dfd55-54e6-e3af-498f-812e9c969693@zoho.com \
--to=drupyog+caml@zoho.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