Ａｌｅｘ
Ａｌｅｘ
This might be outside of the scope for this project, but the ability to have multiple `` elements on a page (where `toast()` calls could have a `ToasterID` passed in)...
Using ES5, bootstrap JSX-less React under the hood for Coco to utilize its masterful engineering initially. https://dev.to/vonheikemen/creating-react-components-using-only-es5-features-52a1 (Will deprecate/circumvent as time goes on.)
Patching of the DOM tree (at least on Safari) causes a flicker when performed fast. (It seems replaceChild might be to blame.) Example: [coco-dom-layout-flicker.gif](https://user-images.githubusercontent.com/6964069/54164082-96b72680-4418-11e9-8fc7-523dc85250df.gif)
Give developers the option to embed raw string literal HTML templates in their components as an alternative to having the markup separate in another file (e.g. App.html). This will improve...
This redesign will allow current users of Go to more intuitively engage with Coco for frontend web design. e.g. * Replace js-like callbacks with go channels. * Centralize event handling...
Allow users to embed a global store in their components, having them diff/recompile on mutation. This should be sprinkled intermittently throughout a component hierarchy and patch as needed.
Add [Go Modules](https://github.com/golang/go/wiki/Modules) to base project folder for modern packaging support.
DOM currently renders from top to bottom without efficiently patching the diff of the incoming VDOM structure. See [gooact](https://github.com/sweetpalma/gooact/blob/master/gooact.js) for an example of a minimal patching implementation.