> > But I don't know how to pass this "cyfox" as the parameter to the second > element (customer-detail). >
To do this with more-routing, you'll probably want to create a <more-route> element and bind to its params inside your <customer-detail>. There's a good example of this in the more-routing demo: https://github.com/PolymerLabs/more-routing/blob/v0.5.0/demo/polyfora-user.html#L8 Or you can pass the value in from outside your element, something like this: <more-route-selector selectedParams="{{params}}"> <core-pages> <customer-detail route="customer-detail" customerId="{{params.cuname}}"></customer-detail> <!-- ... --> </core-pages> </more-route-selector> > the one for more-routing. I am also referring to > https://www.polymer-project.org/0.5/articles/spa.html but no where I > could see how parameter could be passed across different elements (or I did > not understand!). > > Please help. Thanks in advance. > > Subrata > > > > On Saturday, 15 March 2014 02:53:26 UTC+5:30, Andrew Huth wrote: >> >> 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/78925055-cf2e-4296-bf18-fc5b8e002104%40googlegroups.com > <https://groups.google.com/d/msgid/polymer-dev/78925055-cf2e-4296-bf18-fc5b8e002104%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/CAKc-BFgizZfBXYxjdQF7hD%3DdtBLhhiAFY7k-VL2m_vu4Ee0b%2Bw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
