vndb/mithril-vndb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

build fix and doc fixes

Browse source
This commit is contained in:
Leo Horie 2014-11-17 21:33:16 -05:00
parent 5afefb30b8
commit 304c5a289b
3 changed files with 4 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/layout/index.html
View file

@ -251,7 +251,7 @@ m.module(document.getElementById("example"), app);
<blockquote class="twitter-tweet" lang="en"><p>Mithril: The newest JavaScript MVC library 3Kb. <a href="http://twitter.com/LeoHorie">@LeoHorie</a> got it right: It's all about good guides/docs: <a href="http://lhorie.github.io/mithril/comparison.html">lhorie.github.io/mithril/comparison.html</a></p> &mdash; David Corbacho (@dcorbacho) <a href="https://twitter.com/dcorbacho/status/446926407843991552">March 21, 2014</a></blockquote>
<script async src="http://platform.twitter.com/widgets.js"></script>
<script async src="https://platform.twitter.com/widgets.js"></script>
</div>
</div>
</section>

2
docs/practices.md
View file

@ -100,7 +100,7 @@ In the unlikely case that you have another global variable called `m` in your pa
Calling this method while using `m.module` or `m.route` should only be done if you have recurring asynchronous view updates (i.e. something that uses setInterval).
If you're integrating other non-recurring services (e.g. calling setTimeout), you should use [`m.startComputation` / `m.emdComputation`](mithril.computation.md) instead.
If you're integrating other non-recurring services (e.g. calling setTimeout), you should use [`m.startComputation` / `m.endComputation`](mithril.computation.md) instead.
This is the most potentially expensive method in Mithril and should not be used at a rate faster than the rate at which the native `requestAnimationFrame` method fires (i.e. the rate at which browsers are comfortable calling recurring rendering-intensive code). Typically, this rate is around 60 calls per second.