text / x-handlebars永远不会出现

时间:2013-03-07 17:49:10

标签: javascript html ember.js handlebars.js

我正在尝试开发我的第一个应用程序,而我无法让浏览器显示我的把手脚本

这是我的HTML:

<!doctype html>
<html>
<head>
        <title>Random Presents</title>
        <meta name="viewport" content="width=device-width, initial-scale=1.0">
        <link rel="stylesheet" href="style.css">
        <script src="lib/jquery.min.js"></script>
        <script src="lib/handlebars.js"> </script>
        <script src="lib/ember.js"></script>
        <script src ="js/app.js"></script>
</head>

<body>
    <script type="text/x-handlebars">
    {{#view App.AView}}{{firstName}}{{/view}}
</script>
<script type="text/x-handlebars">
    {{#view App.AView}}{{surname}}{{/view}}
</script>
</body>
</html>

和我的app.js文件:

App = Ember.Application.create();

App.AView = Ember.View.extend({
    tagName: 'span',
    firstName: 'Joe',
    surname: 'Bloggs'
});

加载文件时;该页面为空,即使源对应于我的html文件。 我没有在chrome javascript控制台中看到任何错误。

我怀念的东西真的很明显吗? 我测试了这些库,它们直接来自网站,并且是最新版本。

更糟糕的是,我实际上甚至尝试过只包含html的脚本,他也不会加载。

2 个答案:

答案 0 :(得分:3)

因为您在View类中创建了属性,所以应该使用view属性,在某些情况下,它有点像this关键字一样的指针。

将模板更改为:

<script type="text/x-handlebars">
    {{#view App.AView}}
        {{view.firstName}}
        {{view.surname}}
    {{/view}}
</script>

由于Ember惯例,代码中的两个把手模板代表相同的东西。当没有名称时,Ember假定模板名称为“application”。这意味着即使您在两个模板上将属性修复为{{view.propertyName}},后者也将覆盖第一个(或所有具有相同名称的前驱),因为Ember会将模板(使用Handlebars)编译为模板函数并且该名称将用作模板集合的键(路径Ember.TEMPLATES),因此您可以将这些表达式移动到单个模板中,就像上面的代码一样。

但你应该避免使用这样的观点。

视图应显示数据,但不应保留数据。您的数据应该存在于模型中(在商店中),并且视图应该向控制器询问数据,并且应该从疼痛中获取数据。控制器应该通过路由器填充来自商店的数据(它知道该做什么以及何时做)。

我根本就不是这么说的。因为你从Ember开始,只是想让你免于在街道的错误一边开车。

众所周知,有很多过时的教程,这有时会引起很多混乱(有repo过时的教程/文章应该接收更新或添加免责声明的通知。但总的来说,我建议您关注guides,观看一些videos about Ember,在互联网上查看other resources available

这是一个非常基本的sample application注释代码,只是为了展示您可以和应该使用的一些功能:

<强>车把

<!-- 
    when a template doesn't have a data-template-name, Ember assumes this is the 
    application main template. This is usually where you'd render the layout structure
    and also where you'd put the main outlet
-->
<script type="text/x-handlebars">
    <h1>Example</h1>
    {{outlet}}
</script>

<!-- 
    As per convention, a named template should match with its route name
    There are ways around using "partial", "render", or even defining 
    a View class and setting the templateName property to a different name, or
    using the route's renderTemplate hook

    Another thing. You can have nested views when using nested routes
    This view template has another outlet to display a person from the collection
-->
<script type="text/x-handlebars" data-template-name="people">
    {{#each person in controller}}
        {{#linkTo people.person person}}
            {{person.fullName}}
        {{/linkTo}}<br />
    {{/each}}
    <hr />
    {{outlet}}
</script>

<!-- 
    Unlike the very first code piece in this answer, when you have a view or 
    template connected to a controller, you can access the data from the controller
    using handlebars expressions.
-->
<script type="text/x-handlebars" data-template-name="people/person">
    First name: {{view Ember.TextField valueBinding="firstName"}}<br />
    Last name: {{view Ember.TextField valueBinding="lastName"}}<br />
    Full Name: {{fullName}}    
</script>

<强>的JavaScript

window.App = Ember.Application.create();

// defining routes which are somewhat like states (think of a state machine)
// they also provide the ability to have hash urls
// the router is a very important piece of ember due to conventions
App.Router.map(function() {
    // sample url ~/#/people
    this.resource('people', function() {
        // sample url ~/#/people/1
        this.route('person', { path: ':person_id' });
    });    
});

// In this route we provide the data to the list view in "people" template
// the data will actually go to the controller 'content' property which can 
// be a type of array for arraycontroller or a single object for object controller
// this should allow the view to call data from the controller 
App.PeopleRoute = Em.Route.extend({
    model: function() {
        return App.Person.find()
    }
});

// in this route we provide data for the "people/person" template
// In this case we are using the person id from the parameters to query our
// application store.
App.PeoplePersonRoute = Em.Route.extend({
    model: function(params) {
        return App.Person.find(params.person_id)
    }
});

// This is the very first route of the application
// Most of the time, you'll simply redirect from your index to a resource
// in this example, from ~/#/ to ~/#/people
App.IndexRoute = Em.Route.extend({
    redirect: function() {
        this.transitionTo('people');
    }
});

// The store manages your application data. Normally you only have to define
// the revision since it's not 1.0 yet (https://github.com/emberjs/data/blob/master/BREAKING_CHANGES.md)
// for this sample, I'm using the Fixture Adapter so I can add mock up data to the 
// app while testing/coding front end
App.Store = DS.Store.extend({
    revision: 11,
    adapter: 'DS.FixtureAdapter'
});

// Using Ember-Data, you can define a Model object which uses application
// semantics to describe your data, and does many operations which you'd 
// normally expect to see in a ORM. Ember-Data is no ORM, but it gets pretty close
// and in certain scenarios it goes beyond
App.Person = DS.Model.extend({
    firstName: DS.attr('string'),
    lastName: DS.attr('string'),
    fullName: function() {
        return '%@ %@'.fmt(
            this.get('firstName'),
            this.get('lastName')
        );
    }.property('firstName', 'lastName')
});

// Using the FixtureAdapter you can add mockup data to your data store
App.Person.FIXTURES = [
    {id: 1, firstName: 'Joe', lastName: 'Bloggs'},
    {id: 2, firstName: 'Other', lastName: 'Dude'}
];

// when your controller wants to handle a collection, use ArrayController
App.PeopleController = Em.ArrayController.extend();
// when it handles a single object, use ObjectController
App.PeoplePersonController = Em.ObjectController.extend();

答案 1 :(得分:2)

在模板中,默认上下文是控制器,因此您需要显式引用视图以访问其属性:{{view.property}}

在你的例子中:

{{#view App.AView}}{{view.surname}}{{/view}}

Working example JSBin