Article suggestion: MDV examples and best practices

[coding2012]

I'm interested in the "best practices" features around Polymer specific MDV features:
Passing in Javascript objects, responding to change in custom elements, making changes to data inside the element, and automatic update of the original object.

Another way to describe this is to offer some guidance on two custom elements interacting (not directly with each other) but through using shared data and/or events.

One silly example would be two custom elements, one providing a slider bar (or three for RGB), another displaying a color. The color is updated live by using a shared JS object for both custom elements.

[ebidel]

Love the idea.

The slider example is probably best suited for data binding within a <polymer-element>, but there are many "best practices" docs we could write for MDV (like #79).

In the meantime, there's some good info on communicating between elements @ https://docs.google.com/presentation/d/1VbhT4fU-xicGiRzfq2oXUdGawD9nzwhAFfpij5kklzU/pub?start=false&loop=false&delayms=3000

[jkomoros]

I wholeheartedly agree with this suggestion. :-)

On Fri, Jul 12, 2013 at 9:26 AM, Ravi L. notifications@github.com wrote:

I'm interested in the "best practices" features around Polymer specific
MDV features:
Passing in Javascript objects, responding to change in custom elements,
making changes to data inside the element, and automatic update of the
original object.

Another way to describe this is to offer some guidance on two custom
elements interacting (not directly with each other) but through using
shared data and/or events.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/98
.

[ebidel]

Here are better examples:http://jsbin.com/orumol/4/edit

[robdodson]

Rolling this into #339