1 - templating: I took core-component-page and extended because I wanted to
modify the template. I did not use <shadow></shadow>. So I got the logic
but not the template.
If you look at the core-component-page source code (
https://github.com/Polymer/core-component-page-dev/blob/master/core-component-page.html)
you will see the logic its inherited - properties and events.
<link rel="import" href="../polymer/polymer.html">
<link rel="import" href="../core-component-page/core-component-page.html">
<polymer-element name="my-component-page" extends="core-component-page">
<template>
<link rel="stylesheet" href="my-component-page.css">
<core-toolbar class="appbar">
<span>{{moduleName}}</span>
<a class="choiceC" target="_blank"
href="../{{moduleName}}/demo.html">demo</a>
<a class="choiceC" target="_blank"
href="../{{moduleName}}/test/index.html">tests</a>
</core-toolbar>
<core-doc-viewer flex url="{{url}}"
sources="{{sources}}"></core-doc-viewer>
</template>
<script>
(function(){
Polymer({});
})();
</script>
</polymer-element>
2- I did copy over the css into my own css file.
Hope this helps.
On Monday, October 27, 2014 6:03:00 AM UTC-5, Claudius Nicolae wrote:
>
> Let's say element B extends A.
>
> <polymer-element name="A">
> <template>
> The property: {{property}}
> </template>
> <script>
> Polymer({ property: 'Property defined in A' });
> </script>
> </polymer-element>
>
> <polymer-element name="B" extends="A">
> <template>
> <!--shadow></shadow--> <!-- NO shadow! I want my own completely
> different template! -->
> My own template, with binding: {{property}}
> </template>
> <script>
> Polymer(); // no overrides here
> </script>
> </polymer-element>
>
> 1. (templating)
> Can B have it's own template without calling "<shadow></shadow>" ?
> If yes, will properties and events defined in A be bound the B's new
> template ?
>
> 2. (styling)
> Will styles defined for A apply to B, now that the tag name has changed ?
> If yes, how much of them? Only those defined on :host, or also those
> involving the "A" tag name ?
>
> Thanks.
>
On Monday, October 27, 2014 6:03:00 AM UTC-5, Claudius Nicolae wrote:
>
> Let's say element B extends A.
>
> <polymer-element name="A">
> <template>
> The property: {{property}}
> </template>
> <script>
> Polymer({ property: 'Property defined in A' });
> </script>
> </polymer-element>
>
> <polymer-element name="B" extends="A">
> <template>
> <!--shadow></shadow--> <!-- NO shadow! I want my own completely
> different template! -->
> My own template, with binding: {{property}}
> </template>
> <script>
> Polymer(); // no overrides here
> </script>
> </polymer-element>
>
> 1. (templating)
> Can B have it's own template without calling "<shadow></shadow>" ?
> If yes, will properties and events defined in A be bound the B's new
> template ?
>
> 2. (styling)
> Will styles defined for A apply to B, now that the tag name has changed ?
> If yes, how much of them? Only those defined on :host, or also those
> involving the "A" tag name ?
>
> Thanks.
>
Follow Polymer on Google+: plus.google.com/107187849809354688692
---
You received this message because you are subscribed to the Google Groups
"Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/polymer-dev/2b7d4231-9b7b-4f50-bc98-5940ac1733e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
