Build out the initial components. At this level of the library, components correspond to UI components. Will also need:
layout combinators
some notion of forms, probably
A form indicates that a bunch of elements submit values together, has a title, and a submit button. I feel this is optional but probably useful. Maybe it should be delayed?
The focus for this library is getting UIs developed quickly, not on providing every component or customization imaginable. So there is no need to support every possible component; just a reasonable subset.
Will need to think about how reactivity is handled, as there are components that have this nature (e.g. buttons). Look at the Websharper papers, and AirStream (which I think is Scala.js only). I don't think fs2 is suitable for UIs. Glitches, for example, are a problem in UIs.
Build out the initial components. At this level of the library, components correspond to UI components. Will also need:
A form indicates that a bunch of elements submit values together, has a title, and a submit button. I feel this is optional but probably useful. Maybe it should be delayed?
The focus for this library is getting UIs developed quickly, not on providing every component or customization imaginable. So there is no need to support every possible component; just a reasonable subset.
Will need to think about how reactivity is handled, as there are components that have this nature (e.g. buttons). Look at the Websharper papers, and AirStream (which I think is Scala.js only). I don't think fs2 is suitable for UIs. Glitches, for example, are a problem in UIs.
Relevant resources: