These are chat archives for ractivejs/ractive
from my point of view, most important improvement would be the ones that help adding new examples to the documentation.
#1: That would be great for both usage perspective and learning perspective (I'm looking for ways to implement such a feature in scada.js)
I'm just thinking out loud, Playground:
right now it does some global stuff with settings and window event listen...
is this a response to "async component" idea?
ractive component -id src -o distand it works fine!
<script>section as is, and just pops in the template and css in the code.
app.js, a 300MB minified js) with browserify. Then we develop a BlackMagic project which will use this
app.jsas a source database and serve little bundles on demand.
app.js.metafile that would hold the offsets of dependencies
app.jscan be splitted up in