在聚合物入门页面，我们看到了一个聚合物的例子:
<html>
<head>
<!-- 1. Shim missing platform features -->
<script src="polymer-all/platform/platform.js"></script>
<!-- 2. Load a component -->
<link rel="import" href="x-foo.html">
</head>
<body>
<!-- 3. Declare the component by its tag. -->
<x-foo></x-foo>
</body>
</html>
你会注意到<x-foo></x-foo>是由platform.js和x-foo.html定义的。
看起来这相当于AngularJS中的指令模块:
angular.module('xfoo', [])
.controller('X-Foo', ['$scope',function($scope) {
$scope.text = 'hey hey!';
})
.directive('x-foo', function() {
return {
restrict: 'EA',
replace: true,
controller: 'X-Foo',
templateUrl: '/views/x-foo.html',
link: function(scope, controller) {
}
};
});
这两者之间有什么区别?
有哪些问题是聚合物解决了，而AngularJS还没有或不会解决的?
将来有计划把Polymer和AngularJS绑定在一起吗?
你不是第一个问这个问题的人:)在回答你的问题之前，让我澄清一些事情。
Polymer's webcomponents.js is a library that contains several polyfills for various W3C APIs that fall under the Web Components umbrella. These are:
Custom Elements
HTML Imports
<template>
Shadow DOM
Pointer Events
others
The left-nav in the documentation (polymer-project.org) has a page for all of these "Platform technologies". Each of those pages also has a pointer to the individual polyfill.
<link rel="import" href="x-foo.html"> is an HTML Import. Imports are a useful tool for including HTML in other HTML. You can include <script>, <link>, markup, or whatever else in an import.
Nothing "links" <x-foo> to x-foo.html. In your example, it's assumed the Custom Element definition of <x-foo> (e.g. <element name="x-foo">) is defined in x-foo.html. When the browser sees that definition, it's registered as a new element.
回答问题吧!
Angular和Polymer的区别是什么?
我们在问答视频中提到了一些。一般来说，Polymer是一个旨在使用(并展示如何使用)Web组件的库。它的基础是自定义元素(例如，你构建的所有东西都是一个web组件)，它随着web的发展而发展。为此，我们只支持最新版本的现代浏览器。
我将用这张图来描述Polymer的整个架构堆栈:
红色层:我们通过一组填充物得到明天的网。请记住，随着浏览器采用新的api，这些库会随着时间的推移而消失。
黄色层:在聚合物.js中撒一些糖。这一层是我们对如何一起使用指定api的意见。它还添加了数据绑定、语法糖、更改监视器、发布属性……我们认为这些东西有助于构建基于web组件的应用程序。
绿色:UI组件的综合集(绿色层)仍在进行中。这些web组件将使用所有的红色+黄色图层。
Angular指令与自定义元素?
请看Alex Russell的回答。基本上，Shadow DOM允许组合HTML片段，但也是封装HTML的工具。这基本上是web上的一个新概念，其他框架也会加以利用。
有哪些问题是聚合物解决了，而AngularJS还没有或不会解决的?
相似之处:声明式模板、数据绑定。
区别:Angular有用于服务、过滤器、动画等的高级api，支持IE8，在这一点上，它是一个构建生产应用的更健壮的框架。聚合物刚刚起步。
将来有计划把Polymer和AngularJS绑定在一起吗?
它们是独立的项目。也就是说，Angular和Ember团队都宣布，他们最终将在自己的框架中使用底层平台api。
在我看来，这是一个巨大的胜利。在web开发人员拥有强大工具(Shadow DOM, Custom Elements)的世界中，框架作者也可以利用这些原语来创建更好的框架。他们中的大多数人目前都经历了重重困难才能“完成工作”。
更新:
有一篇关于这个主题的很棒的文章:“这里是聚合物和Angular的区别”
I think from a practical perspective, in the end the template feature of angular directives, and the web component methodology leveraged by polymer both accomplish the same task. The major differences as I can see it are that polymer leverages web APIs to include bits of HTML, a more syntactically correct, and simplistic way of achieving what Angular does programatically as it renders templates. Polymer is however as has been stated, a small framework for building declarative and interactive templates using components. It is made available for UI design purposes only, and is only supported in the most modern browsers. AngularJS is a complete MVC framework designed to make web applications declarative by use of data bindings, dependencies, and directives. They're two completely different animals. To your question, it seems to me at this point you'll get no major benefit from using polymer over angular, except having dozens of pre built components, however that would still require you to port those over to angular directives. In the future however, as the web APIs become more advanced, web components will completely remove the need to programatically define and build templates as the browser will be able to simply include them in a similar way to how it handles javascript or css files.
1 & 2) Polymer components are scoped because of their hidden tree in the shadow dom. That means that their style and behaviour cannot bleed out. Angular is not scoped to that particular directive you create like a polymer web component. An angular directive could possibly conflict with something in your global scope. IMO the benefit you will get from polymer is what I explained.. modular components that have scoped css & JavaScript to that particular component that nothing can touch. Untouchable DOM!
Angular directives can be created so that you can annotate an element with several pieces of functionality. In Polymer web components that is not the case. If you want to combine functionality of components you include two components into another component (or wrap them in another component) or you can extend an existing component. Remember the main difference still is that each component is scoped in polymer web components. You can share css & js files across several components or you can inline them.
3)是的，根据Rob Dodson和Eric Bidelman的说法，Angular计划在版本2+中加入聚合物
有趣的是，这里没有人提到scope这个词。我认为这是主要的区别之一。
它们有很多不同之处，但当涉及到为应用程序创建像积木一样的功能块时，它们也有很多相似之处。我认为可以肯定地说，Angular将是应用程序框架，而聚合物有一天可能会与指令一起出现在同一个应用程序中，主要的区别是作用域，但聚合物可能会取代你当前的许多指令。但我看不出为什么Angular不能按原样工作，同时也要包含聚合物组件。
在我写这篇文章的时候，我又读了一遍答案，我注意到埃里克·比德尔曼(Eric Bidelman)在他的回答中提到了这一点:
Shadow DOM允许组合HTML片段，同时也是封装HTML的工具。”
我的答案来自于对Rob Dodson和Eric Bidelman的多次采访。但我觉得这个答案的措辞并没有让这个人的问题得到他想要的理解。话虽如此，我认为我已经触及了他正在寻找的答案，但在这个问题上，我所掌握的信息绝不比Rob Dodson和Eric Bidelman更多
以下是我收集到的信息的主要来源。
JavaScript Jabber -聚合物与Rob Dodson和Eric Bidelman
商店谈话节目-网络组件与罗伯多德森
聚合物是一种Web Components垫片
"Web Components" is a new set of standards that is enveloped by HTML 5 designed to provide reusable building blocks for web applications.
Browsers are at various states of implementing the "Web Components" specification, and therefore it's too early to write HTML using Web Components.
But alas! Polymer to the rescue! Polymer is a library that provides an abstraction layer to your HTML code, allowing it to make use of the Web Components API as if it were fully implemented in all browsers. This is called poly-filling, and the Polymer team distributes this library as webcomponents.js. This used to be called platform.js btw.
但是Polymer不仅仅是一个web组件的填充库…
Polymer还通过Elements提供开放和可重用的Web组件构建块
所有元素都可以定制和扩展。它们被用作从社交小部件到动画到web API客户端的任何东西的构建块。
Polymer不是一个web应用程序框架
Polymer is more of a library than a framework.
Polymer does not have support for things like routes, application scope, controllers, etc.
But it does have two-way binding, and using components "feels" just like using Angular directives.
Although there are some overlaps between Polymer and AngularJS, they are not the same. In fact, the AngularJS team has mentioned utilizing Polymer libraries in upcoming releases.
Also note that Polymer is still considered "bleeding edge" while AngularJS is stabilizing.
It will be interesting to watch both of these Google projects evolve!
这两者之间有什么区别?
对用户来说:没什么。你可以用这两种方法来构建出色的应用程序。
对于开发者来说:他们使用不同的语法，所以任何一种解决方案都有相当陡峭的学习曲线。Angular已经存在了很长时间，而且有一个庞大的社区，所以你很难找到还没有解决的问题。
To an architect: Very different. Angular is an application framework responsible for all aspects of your life. It even has directives vertically integrated in case you want component like features. Polymer on the other hand is more like pay-as-you-go. You want a modal, sure thing, you want an interactive widget, no problem, you want route handling, we can do that to. Polymer is also more portable in that Angular requires an Angular app to reuse directives. The idea with Polymer is be more moduler and will work in other apps, even Angular apps.
有哪些问题是聚合物解决了，而AngularJS还没有或不会解决的?
聚合物是一种朝向利用新的网络组件标准的方法。如果本地支持自定义元素、Shadow DOM和HTML导入等特性，那么不利用它们将是愚蠢的。目前，大多数web组件的功能还没有得到广泛的支持(目前的状态)，所以聚合物充当垫片或桥梁。有点像一个填充(事实上它确实使用填充)。
将来有计划把Polymer和AngularJS绑定在一起吗?
我们一起使用Angular和Polymer已经有一年多了。这样做的部分决定是基于聚合物团队直接向我们承诺的互操作性。我们已经放弃了那个想法。我们现在正朝着只使用聚合物的方向发展。
如果再做一遍，我们可能根本就不会使用聚合物，而是等待它成熟。话虽如此，聚合物有优点(有些很好)和缺点(有些很令人沮丧)，但我认为这是另一个话题的讨论。
Angular指令在概念上类似于自定义元素，但它们的实现不使用Web组件api。Angular指令是构建自定义元素的一种方式，但Polymer和Web Components规范是基于标准的方式。
polymer-element:
<polymer-element name="user-preferences" attributes="email">
<template>
<img src="https://secure.user-preferences.com/path/{{userID}}" />
</template>
<script>
Polymer('user-preferences', {
ready: function() {
this.userID= md5(this.email);
}
});
</script>
</polymer>
角指令:
app.directive('user-preferences', ['md5', function() {
return {
restrict: 'E',
link: function(scope, element, attrs) {
scope.userID= md5(attrs.email);
},
template: '<img src="https://secure.user-preferences.com/path/{{userID}}" />'
};
}]);
