This repository has been archived by the owner on Mar 13, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 189
Will Topeka be rewritten in 1.0? #28
Comments
Vote! |
+1 |
10 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 for this |
+1 |
2 similar comments
+1 |
+1 |
After stepping into this thread for half a year, exactly, I think this wish will never come true without doing it ourselves. During the six months, I discovered that it shouldn't be that hard at all. Here is a good resource for developing responsive web ui, http://udacity.com/course/ud893 The animations... we can do it with the new components after studying them for an hour or two. After all, this may not be a perfect demo. See issue #32 ... Perhaps, Google is struggling with the browser compatibility themselves. This is what I know the best Polymer 1.0 demo so far (after io15 web), https://santatracker.google.com/ |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've recently begun studying Polymer 0.5, but now that 1.0 is released (yay!) and lots have changed, it would really help to see how code will change through its implementation in Topeka.
The text was updated successfully, but these errors were encountered: