Backbone.Marionette VS骨干，样板 [英] Backbone.Marionette vs Backbone-Boilerplate

问题描述

我是新来的骨干，并试图决定如何处理发展。

I'm new to Backbone and trying to decide how to approach development.

目前，我不知道什么时候人会使用backbone.marionette在骨干网的样板？

At the moment I'm wondering when people would use backbone.marionette over backbone-boilerplate?

这是我可以告诉木偶是一个很大的prescriptive，但是这是大多数人在这里接近发展的方式吗？

From what I can tell Marionette is a lot more prescriptive, but is this the way that most people approach development here?

推荐答案

木偶很多关于家政工作的自动化来的意见，我认为应该骨干已经包含在首位。木偶积极维护和发现它是为我的项目是非常有用的，灵活的。

Marionette automates a lot of housekeeping work with respect to views that I believe Backbone should've included in the first place. Marionette is actively maintained and found it to be extremely useful and flexible for my project.

骨干-样板，从我所看到的，更多的是一种方式来组织你的code到模块，但不触及主干的意见。

backbone-boilerplate, from what I see, is more of a way to organize your code into modules but doesn't touch Backbone views.

您应该能够使用code组织的样板，并为木偶更易于管理的意见。我相信，他们解决问题的互补

You should be able to use boilerplate for code organization, and Marionette for more-easily-manageable views. I believe they address complementing issues.

最近木偶增加了一个AMD的版本，所以它现在RequireJS开箱即用的兼容。

Marionette recently added an AMD version so it is now compatible with RequireJS out of the box.

这篇关于Backbone.Marionette VS骨干，样板的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！