Hi
please do send your resumes to vrenikun...@goavancer.com
We have Data Modeler- Level III job opening for 3 Months Contract in
Washington DC
if your are seeking to apply please do send your resume in word format and
let me know best time to reach you to discuss for more about the job
iron-ajax id=get_file
handle-as=text
last-response={{fileContent}}
headers='{accept: application/vnd.github.VERSION.html}'
on-response=handleFile
on-error=handleFileErrorResponse
/iron-ajax
ready: function() {
this.$.get_file.url =
On Mon, May 18, 2015 at 5:46 PM, Eric Eslinger eric.eslin...@gmail.com
wrote:
One of the really rad things about Polymer (0.5) and webcomponents is that
everything is just DOM. You can pretty easily use core- and paper-
components libraries inside of an (say) angular app to render out content.
There are no official guidelines. I think for the most part it's a style
thing, and at the moment what you see in the docs may depend on who first
wrote the example. There are two basic schools of thought:
School #1) Curly braces are automatic -- in almost all cases, they just
do the right thing.
Just musing to myself I wondered if there exists currently or on the
roadmap the ability to specify a set of values a particular property may
accept. This would be similar to other languages' `enum` type where you
specify up-front all the possible values and the implementation refuses to
Ah. So, yes, if you do that, the content element won't work.
One of the main problems shadow DOM is designed to solve is composition.
Without shadow DOM (or the shady DOM shim in 0.9+), you don't have content
projection.
So I guess the question is: what are you trying to achieve by putting the
One of the really rad things about Polymer (0.5) and webcomponents is
that everything is just DOM. You can pretty easily use core- and paper-
components libraries inside of an (say) angular app to render out content.
This is truly the great promise of Web Components, and will be completely
true
