# Should discourse have so much logic in their modal views?

**URL:** <https://discuss.emberjs.com/t/should-discourse-have-so-much-logic-in-their-modal-views/344>\
**Category:** Uncategorized\
**Created:** [March 12, 2013, 1:07pm UTC](https://discuss.emberjs.com/t/should-discourse-have-so-much-logic-in-their-modal-views/344 "2013-03-12T13:07:32Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![teddyzeenny](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/teddyzeenny/32/14243_2.png) [@teddyzeenny](https://discuss.emberjs.com/u/teddyzeenny)\
**Post date:** [March 12, 2013, 1:47pm UTC](https://discuss.emberjs.com/t/should-discourse-have-so-much-logic-in-their-modal-views/344/2 "2013-03-12T13:47:43Z")

</div>

I prefer to move as much logic as possible out of the view, and into to the view’s controller; thus making my views as dumb as possible.

To ensure my views stay dumb, I create a controller for each view. Instead of using `{{view Ember.View}}` I use view/controller pairs by utilizing `route.render()` or `{{render}}` or `{{control}}`. That way every view has a corresponding controller. (Unless I don’t need any logic such as `Ember.TextField` which only does value binding).

I also try to make my controllers as thin as possible by moving events into the route. Unfortunately if a view does not represent a higher state (and thus no route exists for it), and might be re-used in any route, I either use `App.ApplicationRoute` to handle its events, or handle its events in its controller.

I am interested to know if that is considered good practice.

---

_[View the full topic](https://discuss.emberjs.com/t/should-discourse-have-so-much-logic-in-their-modal-views/344)._