4 ms·
I'm not sure I understand what you mean by additional mapping. Here's all that's needed in the template: <div class="city"><span class="name"></span> has
by daliwali 9y ago
I'm not sure I understand what you mean by additional mapping.
Here's all that's needed in the template:
<div class="city"><span class="name"></span> has <span class="population"></span> residents</div>
And the mapping would be:
[ 'city': [ '.city', { name: '.name', population: '.population' } ] ]
If you don't want to manually define a mapping, you could do it automatically by assuming that some attribute like `data-bind` corresponds to a binding, but Simulacra.js doesn't make assumptions like that.
- TekMol 9y agoyou could do it automatically by assuming that some attribute like `data-bind` corresponds to a binding Yes, that could be done. That would mean to extend Simulacra. Or do it outside of it. To me personally, <div>{{NAME}}</div> is easier to read and reason about. Also, it enables you to do stuff like <div>{{CITY}} has {{POPULATION}} residents</div> Which is much shorter then <div><span data-bind="city"></span> has <span data-bind="population"></span> residents</div> You can also do other useful stuff. For example: <div class="{{STATUS}}">{{MACHINE}}</div> And then style different statuses via CSS.
- daliwali 9y agoSorry, but avoiding templating syntax was really a hard design goal. It may not be a tool for everyone. The reason is that every templating language I've used either is or becomes a Turing-complete language by itself.
- TekMol 9y agoWhat would force you to make your own templating language turing complete?