different material implementation?

[sdebaun]

reconsidering the choice of snabbdom-material:

• syntax is subtly different from regular ol' snabbdom: for MaterialThing(foo, children) and snabbThing(foo, children), different properties on foo are used.
• some snabbdom-material functions infer appearance from behavioral hooks, e.g. Button() is shown as disabled if there is no onClick.

This inspired me to look for a mostly- or pure-css material library that we could use instead of snabbdom-material.

Options

• leaf - defunct?
• Material CSS - "mostly css" - needs zepto, velocity, and its own js library included
• MUI - "mostly CSS" - js helper claims to automatically detect new changes and augment interactive elements
• Surface - pure CSS. requires a scss mixin for tab controls with different tab counts. could be handled in component?
• MDL - "mostly css" - looks like you have to manually call upgradeElement on a dom node in order to enable some behavior?

currently leaning towards surface. thoughts?

[TylorS]

Surface looks really awesome! I don't have much to say about the others, except MDL.

I've personally tried to use MDL in one of my applicaitons, but it really just does not work. There are so many bugs and problems with it's layout/grid system, and even forcing upgradeElement() on every update didn't help with a most of the behaviors that it expects.