Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Ashish Agarwal <agarwal1975@gmail.com>
To: Drup <drupyog@zoho.com>
Cc: Alain Frisch <alain.frisch@lexifi.com>,
	Vincent Balat <vincent.balat@ocsigen.org>,
	 ocsigen <ocsigen@inria.fr>,
	OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Announce: ocaml-vdom (pre-release)
Date: Mon, 5 Dec 2016 08:55:57 -0700	[thread overview]
Message-ID: <CAMu2m2KQgR7EBaT6gjVhg=y=qbj8qQOE6BR8wEGVeS_HEdMCBg@mail.gmail.com> (raw)
In-Reply-To: <5db7c03d-bec8-8285-b458-82e681842dbb@zoho.com>

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

I don't have a strong opinion either way, but one point not mentioned about
Tyxml is that you get nice auto-completion when combined with merlin. I've
been pleased to learn the possible values for some attributes while coding
without having to reference any documentation.

On Sat, Dec 3, 2016 at 10:27 AM, Drup <drupyog@zoho.com> wrote:

>
> About Tyxml itself: I think that it addresses a rather different set of
>> issues (ensuring that the DOM is "statically correct" w.r.t. definition of
>> HTML5/SVG).  We haven't identified those issues as being relevant for us,
>> i.e. we have never hit a bug related to breaking such validity constraints,
>> and the lack of static typing does not seem to make refactoring UI code
>> more difficult or fragile; so it's not clear to us that adding more static
>> typing here would help.  If we tried to combine it with our vdom approach,
>> it would probably add some noise, since the vdom type would receive extra
>> type parameters, which would be visible in the interface of all components
>> exposing "view" functions.
>>
>
> Tyxml is not only about type-safety. It's about providing an exhaustive,
> consistent and convenient HTML5 API for your users.
>
> Tyxml also gives you combinators covering the complete HTML5 surface API.
> This API will be exactly the same as the various other implementation of
> Tyxml (textual (Tyxml.Html), dom/react (Tyxml_js), incremental (JST's
> library), react/shared (in eliom)).
> Any user that is familiar with one of those API will be able to pick up
> the others extremely easily.
>
> Currently, in your API, you implemented 3 elements: div, input, span.
> You'll have to build all of the others by hand. You don't even have
> attributes, only the underlying primitives. Tyxml provides a nice API with
> sum types and correct types for all HTML5 attributes.
>
> Finally, you get a syntax extension that takes the usual HTML syntax and
> generates the appropriate combinator calls. You don't have to use it, but
> some users want to. :)
>
> Of course, there is a price to pay, you need to implement Tyxml's
> Xml_sigs.T. I believe it's not a high price, although your extra type
> parameter makes this kind of things more delicate...
>
>

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

      parent reply	other threads:[~2016-12-05 15:56 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
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 [this message]

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='CAMu2m2KQgR7EBaT6gjVhg=y=qbj8qQOE6BR8wEGVeS_HEdMCBg@mail.gmail.com' \
    --to=agarwal1975@gmail.com \
    --cc=alain.frisch@lexifi.com \
    --cc=caml-list@inria.fr \
    --cc=drupyog@zoho.com \
    --cc=ocsigen@inria.fr \
    --cc=vincent.balat@ocsigen.org \
    /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