Scott I definitely see what you're saying. I guess I'm a little impatient/ADD when it comes to wanting to modify component internals. If there's something simple missing from a component, I want to just stick a property on the consumer and 'bam' there it is, instead of having to potentially clone, update, pull request, etc. But on a philosophical note, it seems like theres potentially a lot of boilerplate that could develop, as often times we're just exposing properties and mapping them right back onto the inner element in question. The inner element then becomes full of bindings. By having some kind of external addressing mechanism, we could eliminate that boilerplate and keep the inner implementation cleaner.
On Friday, July 18, 2014 3:30:16 PM UTC-4, Scott Miles wrote: > > Where to draw the line on encapsulation is a contentious issue, we tend > to the line away from isolation, but there are inevitable costs. > > IMO, this idea goes too far toward exposing element internals. The notion > today is that the element author should expose those configuration points > as properties and map them to the shadow-dom internals as appropriate. > > > On Fri, Jul 18, 2014 at 11:00 AM, Chris Gallo <[email protected] > <javascript:>> wrote: > >> For example, it would be useful to be able to say things like: >> <paper-menu-button $.icon.size="48> >> or >> <.... $-icon-size=".."> etc. >> Where the core-icon in paper-menu-button would have an id of 'icon'. >> >> One could use the same pattern for adjusting the shadow dom: >> <shadow $.myelem.vertical ....> >> >> There's a thread about composing the shadow dom that this relates >> to...but that was getting long already so I'm posting here. >> Any takers? :) >> >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/polymer-dev/2d4977b9-6576-4838-a0ea-41378b8a3e2c%40googlegroups.com >> >> <https://groups.google.com/d/msgid/polymer-dev/2d4977b9-6576-4838-a0ea-41378b8a3e2c%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > 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/976aab51-8916-43d1-84a4-adf5292d7f6f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
