Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

README: Describe how Hoodie & Polymer provide an awesome sync experience #23

Open
timblack1 opened this issue Aug 15, 2015 · 0 comments
Milestone

Comments

@timblack1
Copy link
Owner

Make this element's main selling point crystal clear, and provide example code to demonstrate.

Selling point

Hoodie syncs data between the server and JavaScript.

Polymer syncs data between JavaScript and the DOM.

(Illustrate with a graphic here.)

It's a match made in heaven.

It's two-way data binding all the way to the server, to other browsers, even to other users.

My data is your data, live.

Let the awesome begin.

Example code

(Make a model object which listens to a Polymer property's changes and syncs them to the server, and back again when changes are detected on the server. Make it easy to connect the two, maybe with something like this:

var model = new hoodie.PolymerModel(polymer_property, hoodie_id);

Or, consider making a plugin to Polymer's data-binding functionality to also automatically bind all properties to Hoodie there, if they are given a hoodie-type in their declaration.

Consider how to handle collections, or Polymer properties which contain more than one Hoodie doc. The firebase elements might be a good place to start: https://elements.polymer-project.org/elements/firebase-element.)

@timblack1 timblack1 added this to the 1.0 milestone Aug 15, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant