Where’s the Designer? #AskPolymer -- Polycasts #31
Skills:
HTML & CSS60%
Key Takeaways
Covers the latest updates on Designer 2.0, Web Components, and best practices for HTML Imports
Full Transcript
hey there poters Rob here welcome back to ask polymer the show where you send in your hashtag questions and we answer them our first question today comes from Frank who asks will the designer tool be back in polymer 1.0 that's a great question a lot of people have asked me about it you might remember the designer from some of our older talks uh it was originally built as kind of a proof of concept of what you could possibly do with web components and the original designer was never really a production ready thing I'm happy to say though that in 1.0 we are working on Designer 2 if you will uh but when I've asked the team for the the ETA all they said was it'll be a long time so we're working on it we're going to make it an actual production ready thing but it might take a while for it to come out so thank you Frank for sending in that question all right our next question comes from Dominic who asks can you talk a little bit about the Safari support for polymer so that's a really great question uh what's recently happened is the webkit folks have announced that they've just landed support for shadow Dom in webkit nightly so you can check out this blog post over here to read more about that uh what that means is polymer should in the very near future start running a lot faster in Safari when that finally ships in their stable version so uh hopefully things are going to be improving there really soon thanks for that really awesome question Dominic all right our next question comes from robz who asks can I create a dat data binding imperatively so that's a really interesting question it's one that a few people have sent me on Twitter I asked the team about this and they said that even though this is kind of a often requested feature it's not something that's currently supported in polymer and when I asked why they said mainly because they want to focus on polishing the core features before adding any sort of like additional fanciness like that so for the moment that's not supported not saying it won't be supported someday uh but at the moment no you have to do everything declaratively all all right our next question comes from Dany who asks should an element import all of its dependencies or can you just take those Imports and put it in an elements HTML file so that's a really cool question and you know a lot of people are confused about this because you can put stuff in an elements HTML file and it'll seem like the app continues to work but generally as a best practice we recommend that any element have all of its dependencies imported at the top of its definition and mainly because this ensures that those other elements have loaded before your element tries to register and and use them um people also wonder you know does that possibly impact performance but the way HTML Imports are written all of those additional Imports even if there are duplicates they will actually be duplicated so there's no performance penalty there and if you're using vulcanize it's only going to add those Imports once and it'll do it in the right order so the best practice is always have your elements import their dependencies and you should be good to go okay our last question comes from Jose who asks can you declare Styles in an iron media query and if not like what's the point of the iron media query element so that's a really good question I know when you first see that element it's a little confusing you're not quite sure how to use it but the idea with iron media query is that it's mainly meant for data bindings so if you need to change an attribute or a property on some other element when your page is at a smaller screen size you can do that using that element you know this is the kind of work that you actually can't do with CSS you would probably have to write custom JavaScript to do that the iron media query element is just going to let you do that in a nice declarative fashion so thank you Jose for sending in that really great question so that's it for today thank you everyone who sent in those excellent questions if you yourself have a question you can leave it down in the comments or you can ping us on a social network of you're choosing at # askpolymer as always thank you so much for watching and I'll see you next time our next question comes from Jose who asks can I declare Styles this totally impressive ISM on the D FL [Music]
Original Description
Many folks have wondered, what ever happened to the Designer tool we used to demo in our talks. Today on Polycasts we’ll talk Designer 2.0, big announcements around Web Components, and best practices for your HTML Imports.
Polymer Slack: http://bit.ly/polymerslack
Subscribe to the Chrome Developers channel at: https://goo.gl/OUF4e2
Check out music from the show at: http://terramonk.com/
Playlist
Uploads from Chrome for Developers · Chrome for Developers · 20 of 60
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
▶
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Polymer Performance Patterns (The Polymer Summit 2015)
Chrome for Developers
Polymer Power Tools (The Polymer Summit 2015)
Chrome for Developers
Chrome Dev Summit 2014 – Chrome Case Studies
Chrome for Developers
Web Directions Code 2015 round up
Chrome for Developers
Maintainable Code - HTTP203
Chrome for Developers
iron-ajax… wat?! -- Polycasts #26
Chrome for Developers
The Guardian - Supercharged
Chrome for Developers
ES2015 (next version of JavaScript), Totally Tooling Tips (S2 Ep1)
Chrome for Developers
#AskPolymer: Rob answers all the questions ever -- Polycasts #27
Chrome for Developers
The Future of JavaScript - HTTP203
Chrome for Developers
Data Binding 101 -- Polycasts #28
Chrome for Developers
The Guardian part 2 - Supercharged
Chrome for Developers
The Future of Web Audio: with Chris Wilson and Chris Lowis
Chrome for Developers
Chrome 46: New motion-path animations, client hints and service worker improvements
Chrome for Developers
Sublime Snippets, Totally Tooling Tips (S2 Ep2)
Chrome for Developers
#AskPolymer: How do you make the show? -- Polycasts #29
Chrome for Developers
Critical Path CSS, Totally Tooling Tips (S2 Mini Tip #1)
Chrome for Developers
Binding to Objects -- Polycasts #30
Chrome for Developers
Player FM - Supercharged
Chrome for Developers
Where’s the Designer? #AskPolymer -- Polycasts #31
Chrome for Developers
Jake Beats Wikipedia - HTTP203
Chrome for Developers
Supercharged Observers! -- Polycasts #32
Chrome for Developers
Jai's Web blog - Supercharged
Chrome for Developers
Windows Command-line Tooling, Totally Tooling Tips (S2, Ep4)
Chrome for Developers
What about internationalization? #AskPolymer -- Polycasts #33
Chrome for Developers
Developing for Billions (Chrome Dev Summit 2015)
Chrome for Developers
Google+ Performance Improvement Comparison
Chrome for Developers
Deploying HTTPS: The Green Lock and Beyond (Chrome Dev Summit 2015)
Chrome for Developers
Progressive Web Apps (Chrome Dev Summit 2015)
Chrome for Developers
Instant Loading with Service Workers (Chrome Dev Summit 2015)
Chrome for Developers
Increase Engagement with Web Push Notifications (Chrome Dev Summit 2015)
Chrome for Developers
Engaging with the Real World: Web Bluetooth and Physical Web (Chrome Dev Summit 2015)
Chrome for Developers
Asking for Permission: respectful, opinionated UI (Chrome Dev Summit 2015)
Chrome for Developers
Polymer - State of the Union (Chrome Dev Summit 2015)
Chrome for Developers
Building Progressive Web Apps with Polymer (Chrome Dev Summit 2015)
Chrome for Developers
Introduction to RAIL (Chrome Dev Summit 2015)
Chrome for Developers
DevTools in 2015: Authoring to the max (Chrome Dev Summit 2015)
Chrome for Developers
RAIL in the real world (Chrome Dev Summit 2015)
Chrome for Developers
#ChromeDevSummit talks are up - W00T! -- Polycast #34
Chrome for Developers
V8 Performance from the Driver's Seat (Chrome Dev Summit 2015)
Chrome for Developers
Quantify and improve real-world RAIL (Chrome Dev Summit 2015)
Chrome for Developers
Owning your performance: RAIL (Chrome Dev Summit 2015)
Chrome for Developers
HTTP/2 101 (Chrome Dev Summit 2015)
Chrome for Developers
Leadership Panel (Chrome Dev Summit 2015)
Chrome for Developers
Build Processes, Totally Tooling Tips (S2, Ep 5)
Chrome for Developers
Accessibility (Chrome Dev Summit 2015)
Chrome for Developers
Binding to Arrays -- Polycasts #35
Chrome for Developers
HTTP2 - HTTP203
Chrome for Developers
Chrome 47: Splash Screens, requestIdleCallback and better desktop notifications (New in Chrome)
Chrome for Developers
Call For Submissions - Supercharged
Chrome for Developers
Cross Device Testing, Totally Tooling Tips (S2 Ep6)
Chrome for Developers
Testing AJAX with Web Component Tester -- Polycasts #37
Chrome for Developers
Slack: Extended Xmas Special - Supercharged
Chrome for Developers
Browser testing with Travis & Sauce Labs -- Polycasts #38
Chrome for Developers
Optimize for production with Vulcanize -- Polycasts #39
Chrome for Developers
Highlights from Chrome Dev Summit 2015
Chrome for Developers
Chrome 48: Custom buttons in notifications, DevTools Security panel, and Presentation mode
Chrome for Developers
Crisper: Protecting your Polymer app with CSP -- Polycasts #40
Chrome for Developers
How do I use Sass with Polymer? #AskPolymer -- Polycasts #41
Chrome for Developers
Colors – DevTools Tonight #0 (Pilot)
Chrome for Developers
More on: HTML & CSS
View skill →
🎓
Tutor Explanation
DeepCamp AI