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

doc tweaks

Browse source
This commit is contained in:
Leo Horie 2014-11-12 20:06:24 -05:00
parent 515ba7cf9c
commit 5ed8891db3
6 changed files with 94 additions and 25 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/practices.md
View file

@ -18,7 +18,7 @@ Because Mithril encourages all entity logic to be done in the model layer, it's
Models are also responsible for centralizing tasks such as filtering of entity lists and validation routines, so that access to these methods is available across the application.
DOM manipulation should be done in the view via [`m()` and `config`](mithril). Controllers may explicitly call [`m.redraw`](mithril.redraw.md), but, if possible, it's preferable to abstract this into a service which integrates with Mithril's auto-redrawing system (see [`m.startComputation` / `m.endComputation`](mithril.computation.md)).
DOM manipulation should be done in the view via [`m()` and `config`](mithril). Controllers may explicitly call [`m.redraw`](mithril.redraw.md), but, if possible, it's preferable to abstract this into a service which integrates with Mithril's auto-redrawing system (see [`m.startComputation` / `m.endComputation`](mithril.computation.md)). You should avoid instantiating controller classes from views.
---