3、Angular-Ui Router 多个命名视图

253人阅读 评论(0) 收藏 举报
分类:


You can name your views so that you can have more than one ui-view per template. Let's say you had an application state that needed to dynamically populate a graph, some table data and filters for the table like this:
您可以为您的视图命名,以便您可以在每个模板中拥有多个ui-view。假设您有一个需要动态填充图形的应用程序状态,其中一些表数据和过滤器如下所示:

When setting multiple views, you need to use the views property on the state object. views is an object.
在设置多个视图时,需要在state对象上使用views属性。views是一个对象。

Views override state's template properties
views属性会覆盖状态的template属性

If you define a views object, your state's templateUrltemplate and templateProvider will be ignored. So in the case that you need a parent layout of these views, you can define an abstract state that contains a template, and a child state under the layout state that contains the 'views' object.
如果您定义了一个views属性,那么您的状态的templateUrl、template和templateProvider将被忽略。因此,在需要这些views的父布局的情况下,您可以定义包含模板的抽象状态,以及包含“views”对象的布局状态下的子状态。

Example - Name Matching
例子 - 名称匹配

The property keys on views should match your view names, like so:
views中的属性应该与您的视图名称匹配,例如:

<!-- index.html -->		
<body>		
  <div ui-view="filters"></div>		
  <div ui-view="tabledata"></div>		
  <div ui-view="graph"></div>		
</body>		
$stateProvider		
  .state('report', {		
    views: {		
      'filters': { ... templates and/or controllers ... },		
      'tabledata': {},		
      'graph': {},		
    }		
  })		

Then each view in views can set up its own templates (templatetemplateUrltemplateProvider) and controllers (controllercontrollerProvider).
然后,views中的每个视图都可以设置自己的模板(template, templateUrl, templateProvider)和控制器(controller, controllerProvider)。

$stateProvider		
  .state('report',{		
    views: {		
      'filters': {		
        templateUrl: 'report-filters.html',		
        controller: function($scope){ ... controller stuff just for filters view ... }		
      },		
      'tabledata': {		
        templateUrl: 'report-table.html',		
        controller: function($scope){ ... controller stuff just for tabledata view ... }		
      },		
      'graph': {		
        templateUrl: 'report-graph.html',		
        controller: function($scope){ ... controller stuff just for graph view ... }		
      }		
    }		
  })		

View Names - Relative vs. Absolute Names
视图名称-相对与绝对名称

Behind the scenes, every view gets assigned an absolute name that follows a scheme of viewname@statename, where viewname is the name used in the view directive and state name is the state's absolute name, e.g. contact.item. You can also choose to write your view names in the absolute syntax.
在幕后,每个视图会被指定一个这样形式(viewname@statename)的绝对名,其中viewname是视图指令中使用的名称, statename是状态的绝对名称,,例如contact.item。您还可以选择在绝对语法中编写视图名称。

For example, the previous example could also be written as:
例如,前面的例子也可以写成:

  .state('report',{		
    views: {		
      'filters@': { },		
      'tabledata@': { },		
      'graph@': { }		
    }		
  })		

Notice that the view names are now specified as absolute names, as opposed to the relative name. It is targeting the 'filters', 'tabledata', and 'graph' views located in the root unnamed template. Since it's unnamed, there is nothing following the '@'. The root unnamed template is your index.html.
注意,视图名称现在被指定为绝对名称,而不是相对名称。它的目标是'filters', 'tabledata'和'graph' 视图,这些视图位于未命名的模板中。因为它是匿名的,所以“@”后面没有任何东西。未命名的模板是您的index.html。

Absolute naming lets us do some powerful view targeting. Remember! With power comes responsibility. Let's assume we had several templates set up like this (this example is not realistic, it's just to illustrate view targeting):
绝对命名让我们可以做一些强大的视图定位。记住!与权力相伴的是责任。让我们假设我们有几个这样的模板(这个例子没有实际意义,只是为了说明视图的目的):

<!-- index.html (root unnamed template) -->		
<body ng-app>		
<div ui-view></div> <!-- contacts.html plugs in here -->		
<div ui-view="status"></div>		
</body>		
<!-- contacts.html -->		
<h1>My Contacts</h1>		
<div ui-view></div>		
<div ui-view="detail"></div>		
<!-- contacts.detail.html -->		
<h1>Contacts Details</h1>		
<div ui-view="info"></div>		

Let's look at the various views you could target from within the contacts.detail state. Remember that if an @ is used then the view path is considered absolute:

$stateProvider		
  .state('contacts', {		
    // This will get automatically plugged into the unnamed ui-view 		
    // of the parent state template. Since this is a top level state, 		
    // its parent state template is index.html.		
    templateUrl: 'contacts.html'   		
  })		
  .state('contacts.detail', {		
    views: {		
        ////////////////////////////////////		
        // Relative Targeting             //		
        // Targets parent state ui-view's //		
        ////////////////////////////////////		
		
        // Relatively targets the 'detail' view in this state's parent state, 'contacts'.		
        // <div ui-view='detail'/> within contacts.html		
        "detail" : { },            		
		
        // Relatively targets the unnamed view in this state's parent state, 'contacts'.		
        // <div ui-view/> within contacts.html		
        "" : { }, 		
		
        ///////////////////////////////////////////////////////		
        // Absolute Targeting using '@'                      //		
        // Targets any view within this state or an ancestor //		
        ///////////////////////////////////////////////////////		
		
        // Absolutely targets the 'info' view in this state, 'contacts.detail'.		
        // <div ui-view='info'/> within contacts.detail.html		
        "info@contacts.detail" : { }		
		
        // Absolutely targets the 'detail' view in the 'contacts' state.		
        // <div ui-view='detail'/> within contacts.html		
        "detail@contacts" : { }		
		
        // Absolutely targets the unnamed view in parent 'contacts' state.		
        // <div ui-view/> within contacts.html		
        "@contacts" : { }		
		
        // absolutely targets the 'status' view in root unnamed state.		
        // <div ui-view='status'/> within index.html		
        "status@" : { }		
		
        // absolutely targets the unnamed view in root unnamed state.		
        // <div ui-view/> within index.html		
        "@" : { } 		
  });		

You can see how this ability to not only set multiple views within the same state but ancestor states could become a meritable playground for a developer :).
您可以看到,这种能力不仅可以在同一个状态下设置多个视图,而且可以成为开发人员的一个走迷宫的游乐场。

0
0

查看评论
* 以上用户言论只代表其个人观点,不代表CSDN网站的观点或立场
    个人资料
    • 访问:294787次
    • 积分:2992
    • 等级:
    • 排名:第12162名
    • 原创:85篇
    • 转载:10篇
    • 译文:5篇
    • 评论:154条
    最新评论