marionettejs / blog

:memo: Blog for Marionettejs.com (hosted on the gh-pages branch)
http://blog.marionettejs.com
4 stars 8 forks source link

Documentation suggestion for views #13

Closed jasonmng closed 10 years ago

jasonmng commented 10 years ago

This is in reference to: Note: The Marionette.View class is not intended to be used directly.

I think this should be changed. I find that using views directly is a good way to provide an interface to existing elements, or an interface to other view types. In this case it acts as a "controller" of sorts. Say you have a group of tabs and each tab renders a different collection, a view can provide an interface to handle the transition.

samccone commented 10 years ago

Hmm @jasonmng that indeed is one way to do it.

Marionette is full of semi opinions but makes it easy to do whatever makes the most sense to you and your project.

Using the raw view class is a bit "tricky" and requires you to know what you are doing. By using the raw view class tho you are losing a bunch of the default power we put into place for models and collections.

This is why we say

The Marionette.View class is not intended to be used directly.

But if you know what you are doing it is not a bad thing it is just a more advanced use.

Thanks for the input!