OvermindDL1

Probably need a websocket subscription manager written overall. Should not be too hard, I can do it when I get time again (so mid-late November for me), but if you...

> As our intuition suggests -- the subscription aspect of TEA is not necessary in OCaml-Tea Precisely. :-) It is still usually good form, but absolutely not required. :-) You...

I'm going to leave this open until I do get a subscription manager set up for it though, to remind me. :-)

> I thought the previous attempt of using Tea.Cmd.call was a solution ... but alas update does not get called. You have to return the results of that in the...

> I sense a misconception of the ocaml module system here and recommend reading Chapter 4 of the book Real World Ocaml. Apart of allowing clean abstraction of complex implementation...

A few things I notice about it: > Each node in the VDOM tree has a "key" string field. By default, the key corresponds to the tag name for elements...

> I was talking more about the superficial aspects than the engine. The thing I really want is labels rather than positional arguments when constructing html elements, the rest is...

`pushMsg` is *very* low level stuff that should usually not be touched unless building other API's (like Cmd's and Sub's and Event's use it) first of all. ^.^; Second: ```ocaml...

> Embarrassed sigh, now fixed: We all experience that! ^.^ > I'd like to take your advice re using standard HTML events instead of pushMsg. Yeah the webstandard 'componantized' way...

> I will work on this this weekend! (and I hope you have a great one) Lol, you too, enjoy! ^.^