Skip to content

Update platform.js to webcomponents.js #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Nevraeka wants to merge 6 commits into
base: master
Choose a base branch
from
Open

Update platform.js to webcomponents.js #32

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
58b2ff4
[platform] Updated platform dependency to 0.5.1
Nevraeka Nov 14, 2014
f351ff0
[platform] Updated platform references across the app
Nevraeka Nov 14, 2014
8f5f841
[NO_STORY] Remove .idea files
Nevraeka Nov 14, 2014
4754a98
[NO_STORY] Remove generated files
Nevraeka Nov 14, 2014
a4b0bc9
[NO_STORY] Remove misspelled references
Nevraeka Nov 14, 2014
9006f3e
[NO_STORY] Fixed broken find/replace items
Nevraeka Nov 14, 2014
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion about.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, user-scalable=no, initial-scale=1, maximum-scale=1">
<title>Brick</title>
<script src="/bower_components/platform/platform.js"></script>
<script src="/bower_components/webcomponentsjs/webcomponents.js"></script>
<link rel="import" href="/bower_components/brick/dist/brick.html">
<link rel="stylesheet" href="//code.cdn.mozilla.net/fonts/fira.css">
<link href="//maxcdn.bootstrapcdn.com/font-awesome/4.1.0/css/font-awesome.min.css" rel="stylesheet">
Expand Down
14 changes: 7 additions & 7 deletions blog/2014-07-11-Brick-2-point-0.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, user-scalable=no, initial-scale=1, maximum-scale=1">
<title>Brick</title>
<script src="/bower_components/platform/platform.js"></script>
<script src="/bower_components/webcomponentsjs/webcomponents.js"></script>
<link rel="import" href="/bower_components/brick/dist/brick.html">
<link rel="stylesheet" href="//code.cdn.mozilla.net/fonts/fira.css">
<link href="//maxcdn.bootstrapcdn.com/font-awesome/4.1.0/css/font-awesome.min.css" rel="stylesheet">
Expand Down Expand Up @@ -65,7 +65,7 @@
<section><h1 id="brick-2-0">Brick 2.0</h1>
<h2 id="tl-dr">TL;DR</h2>
<ul>
<li><a href="#what-is-brick-">Brick is a constistent and curated collection of components (UI and functional) used to ease the webapp development process.</a></li>
<li><a href="#what-is-brick-">Brick is a consistent and curated collection of components (UI and functional) used to ease the webapp development process.</a></li>
<li><a href="#what-is-brick-not-">Brick is <strong>not</strong> a framework</a>.</li>
<li><a href="#custom-elements">Brick is a participant in the open Custom Elements ecosystem.</a></li>
<li><a href="#on-x-tag">Brick will no longer rely on the x-tag library.</a></li>
Expand All @@ -86,14 +86,14 @@ <h2 id="custom-elements">Custom Elements</h2>
<p>These new APIs have gotten developers excited about the Web in a whole new way, and people have begun building and sharing their own Custom Elements. Brick, Polymer, and many other third-party Custom Elements are being distributed and indexed as part of an awesome burgeoning <a href="//customelements.io">Custom Elements</a> ecosystem.</p>
<p>People have asked how their component can become part of Brick. We love contributions, but not every component may match the coding and API style of Brick, or meet its goals. Just as many programming languages have a standard library as well as a rich ecosystem of third-party modules, Brick aims to be a &#39;standard library&#39; of webapp-specific Custom Elements, but will support and interoperate with the larger community of components.</p>
<h2 id="on-x-tag">On X-Tag</h2>
<p>In the early(er) days of Web Components, the Custom Elements standard was very much so in flux. It was hard to build to the standard or even a polyfill because the APIs kept changing. <a href="https://github.com/csuwildcat/">Daniel Buchner</a> and <a href="https://github.com/pennyfx/">Arron Schaar</a> concieved of <a href="http://x-tags.org/">x-tag</a>, which provided useful helper functions around events and the component definition process. The library was a godsend, and using it Brick was able to get off the ground. Over time, however, the APIs have settled, and the project found itself in need of the other features of the Web Components standards. These features are all part of the <a href="https://github.com/Polymer/platform/">platform.js</a> polyfill that is part of Polymer and available externally as well. Additionally, the rising popularity of Google&#39;s Polymer and its syntax for describing Custom Elements grew, and when users came to contribute to Brick and x-tag, they found themselves facing an unfamiliar syntax and an underlying library that was frequently not well documented. The decision was made that if users encounter Custom Element registration syntax, it should be the standards-based syntax. Brick components are now written in a &#39;vanilla&#39; style, using the standards-based APIs directly.</p>
<p>In the early(er) days of Web Components, the Custom Elements standard was very much so in flux. It was hard to build to the standard or even a polyfill because the APIs kept changing. <a href="https://github.com/csuwildcat/">Daniel Buchner</a> and <a href="https://github.com/pennyfx/">Arron Schaar</a> concieved of <a href="http://x-tags.org/">x-tag</a>, which provided useful helper functions around events and the component definition process. The library was a godsend, and using it Brick was able to get off the ground. Over time, however, the APIs have settled, and the project found itself in need of the other features of the Web Components standards. These features are all part of the <a href="https://github.com/Polymer/webcomponentsjs/">webcomponents.js</a> polyfill that is part of Polymer and available externally as well. Additionally, the rising popularity of Google&#39;s Polymer and its syntax for describing Custom Elements grew, and when users came to contribute to Brick and x-tag, they found themselves facing an unfamiliar syntax and an underlying library that was frequently not well documented. The decision was made that if users encounter Custom Element registration syntax, it should be the standards-based syntax. Brick components are now written in a &#39;vanilla&#39; style, using the standards-based APIs directly.</p>
<p>Here&#39;s a diagram of how things looked with Brick 1.0:</p>
<div class="diagram">
<div class="layer">
<div class="label platform">Platform (standards)</div>
<div class="children">
<div class="layer">
<div class="label poly">Polyfill (platform.js)</div>
<div class="label poly">Polyfill (webcomponents.js)</div>
<div class="children">
<div class="layer">
<div class="label library">Polymer</div>
Expand All @@ -118,13 +118,13 @@ <h2 id="on-x-tag">On X-Tag</h2>
</div>
</div>

<p>Going forward, Brick will ship using the same <a href="https://github.com/Polymer/platform/">platform.js polyfill</a> used by Polymer. This gives us access to the full range of Web Components features, as well as ensures interoperability with Polymer and other standards-based Custom Elements:</p>
<p>Going forward, Brick will ship using the same <a href="https://github.com/Polymer/webcomponentsjs/">webcomponents.js polyfill</a> used by Polymer. This gives us access to the full range of Web Components features, as well as ensures interoperability with Polymer and other standards-based Custom Elements:</p>
<div class="diagram">
<div class="layer">
<div class="label platform">Platform (standards)</div>
<div class="children">
<div class="layer">
<div class="label poly">Polyfill (platform.js)</div>
<div class="label poly">Polyfill (webcomponents.js)</div>
<div class="children">
<div class="layer">
<div class="label library">Polymer</div>
Expand All @@ -145,7 +145,7 @@ <h2 id="on-x-tag">On X-Tag</h2>
</div>

<h2 id="so-what-s-next-">So What&#39;s Next?</h2>
<p>After deciding to use the platform.js polyfills and remove the x-tag library, Brick is being built from the ground-up to be lighter, more modular, and easier to contribute to. It&#39;s a big undertaking, so we&#39;re moving from 1.0 to 2.0 to reflect the scale of the work. It&#39;s a more-or-less reboot of the entire project, and I as well as the rest of the team are very excited about it. We haven&#39;t been vocal enough about updates, but I&#39;m committing to posting regularly here as well as on Twitter at <a href="https://twitter.com/mozbrick/">@mozbrick</a>. Stay tuned!</p>
<p>After deciding to use the webcomponents.js polyfills and remove the x-tag library, Brick is being built from the ground-up to be lighter, more modular, and easier to contribute to. It&#39;s a big undertaking, so we&#39;re moving from 1.0 to 2.0 to reflect the scale of the work. It&#39;s a more-or-less reboot of the entire project, and I as well as the rest of the team are very excited about it. We haven&#39;t been vocal enough about updates, but I&#39;m committing to posting regularly here as well as on Twitter at <a href="https://twitter.com/mozbrick/">@mozbrick</a>. Stay tuned!</p>
<p>~potch</p>
<p><small>written 15 July 2014 &middot; <a href="/blog/2014-07-11-Brick-2-point-0.html">permalink</a></small></p>
</section>
Expand Down
10 changes: 5 additions & 5 deletions blog/2014-07-11-Brick-2-point-0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ People have asked how their component can become part of Brick. We love contribu

## On X-Tag

In the early(er) days of Web Components, the Custom Elements standard was very much so in flux. It was hard to build to the standard or even a polyfill because the APIs kept changing. [Daniel Buchner](https://github.com/csuwildcat/) and [Arron Schaar](https://github.com/pennyfx/) concieved of [x-tag](http://x-tags.org/), which provided useful helper functions around events and the component definition process. The library was a godsend, and using it Brick was able to get off the ground. Over time, however, the APIs have settled, and the project found itself in need of the other features of the Web Components standards. These features are all part of the [platform.js](https://github.com/Polymer/platform/) polyfill that is part of Polymer and available externally as well. Additionally, the rising popularity of Google's Polymer and its syntax for describing Custom Elements grew, and when users came to contribute to Brick and x-tag, they found themselves facing an unfamiliar syntax and an underlying library that was frequently not well documented. The decision was made that if users encounter Custom Element registration syntax, it should be the standards-based syntax. Brick components are now written in a 'vanilla' style, using the standards-based APIs directly.
In the early(er) days of Web Components, the Custom Elements standard was very much so in flux. It was hard to build to the standard or even a polyfill because the APIs kept changing. [Daniel Buchner](https://github.com/csuwildcat/) and [Arron Schaar](https://github.com/pennyfx/) concieved of [x-tag](http://x-tags.org/), which provided useful helper functions around events and the component definition process. The library was a godsend, and using it Brick was able to get off the ground. Over time, however, the APIs have settled, and the project found itself in need of the other features of the Web Components standards. These features are all part of the [webcomponents.js](https://github.com/Polymer/webcomponentsjs/) polyfill that is part of Polymer and available externally as well. Additionally, the rising popularity of Google's Polymer and its syntax for describing Custom Elements grew, and when users came to contribute to Brick and x-tag, they found themselves facing an unfamiliar syntax and an underlying library that was frequently not well documented. The decision was made that if users encounter Custom Element registration syntax, it should be the standards-based syntax. Brick components are now written in a 'vanilla' style, using the standards-based APIs directly.

Here's a diagram of how things looked with Brick 1.0:

Expand All @@ -40,7 +40,7 @@ Here's a diagram of how things looked with Brick 1.0:
<div class="label platform">Platform (standards)</div>
<div class="children">
<div class="layer">
<div class="label poly">Polyfill (platform.js)</div>
<div class="label poly">Polyfill (webcomponents.js)</div>
<div class="children">
<div class="layer">
<div class="label library">Polymer</div>
Expand All @@ -65,14 +65,14 @@ Here's a diagram of how things looked with Brick 1.0:
</div>
</div>

Going forward, Brick will ship using the same [platform.js polyfill](https://github.com/Polymer/platform/) used by Polymer. This gives us access to the full range of Web Components features, as well as ensures interoperability with Polymer and other standards-based Custom Elements:
Going forward, Brick will ship using the same [webcomponents.js polyfill](https://github.com/Polymer/webcomponentsjs/) used by Polymer. This gives us access to the full range of Web Components features, as well as ensures interoperability with Polymer and other standards-based Custom Elements:

<div class="diagram">
<div class="layer">
<div class="label platform">Platform (standards)</div>
<div class="children">
<div class="layer">
<div class="label poly">Polyfill (platform.js)</div>
<div class="label poly">Polyfill (webcomponents.js)</div>
<div class="children">
<div class="layer">
<div class="label library">Polymer</div>
Expand All @@ -94,7 +94,7 @@ Going forward, Brick will ship using the same [platform.js polyfill](https://git

## So What's Next?

After deciding to use the platform.js polyfills and remove the x-tag library, Brick is being built from the ground-up to be lighter, more modular, and easier to contribute to. It's a big undertaking, so we're moving from 1.0 to 2.0 to reflect the scale of the work. It's a more-or-less reboot of the entire project, and I as well as the rest of the team are very excited about it. We haven't been vocal enough about updates, but I'm committing to posting regularly here as well as on Twitter at [@mozbrick](https://twitter.com/mozbrick/). Stay tuned!
After deciding to use the webcomponents.js polyfills and remove the x-tag library, Brick is being built from the ground-up to be lighter, more modular, and easier to contribute to. It's a big undertaking, so we're moving from 1.0 to 2.0 to reflect the scale of the work. It's a more-or-less reboot of the entire project, and I as well as the rest of the team are very excited about it. We haven't been vocal enough about updates, but I'm committing to posting regularly here as well as on Twitter at [@mozbrick](https://twitter.com/mozbrick/). Stay tuned!

~potch

Expand Down
Loading