For anyone looking for client-side routing, I've made a collection of
Polymer elements called <app-router> <https://github.com/ahuth/app-router>.
To use it, you set up routes (the target attribute specifies where views
will get rendered into):
<app-router target="#main">
<app-route to="index">/</app-route>
<app-route to="contact">/contacts/:id</app-route>
</app-router>
And then you set up views that correspond to the to attributes on the
routes:
<app-views>
<template name="index">
<p>This is the main page</p>
</template>
<template name="contact">
<p>This is contact {{ id }}</p>
</template>
</app-views>
Url parameters (in this example 'id') get passed into the views.
What are your guy/gal's thoughts on this? I'm not a big fan of having the
view definitions on the page. Not sure how else to do it, though. This is
also my first Polymer element, so it may not be as Polymeric as it could
be. Any pointers on that are greatly appreciated.
Finally, how should this be packaged? It's really a collection of 3 Polymer
elements. Should they be separate, or combined into one package together?
<app-router>, <app-route>, and <app-views> are all available at
github.com/ahuth/app-router. Get it while supplies last!
P.S. This is a rewrite of an earlier post (now deleted) because I didn't
like how I worded it before.
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/988bc2b7-9015-4d5d-8db7-9ff550b9bd2d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
