They all need to be dynamic .. Im not concerned with a complicated solution ;p My current path was already pretty spaghetti .. Ive been digging through polymer-dev and node.bind trying to mimic the attribute publishing that happens when the element is registered .. Ive spent far too much time on it already .. I was hoping somebody knew how to accomplish this
One idea was to bind to calls to setAttribute on custom-pager, then put a path observer on the attribute name and just bind it all together myself with some messy ass glue :) But since poly is already doing this, I was hoping to leverage it On Friday, September 5, 2014 3:12:45 PM UTC-4, Scott Miles wrote: > > Do 'pageAttr1', etc. also need to be fully dynamic, or only the shared > data? > > >> And yes, I understand each page can have its own core-media-query to do > the same thing, but thats not the point here .. > > Sure, I'm not trying to tell you you want the wrong thing, I'm only trying > to understand what you want, to make sure the solution isn't more > complicated than it needs to be. > > Scott > > > On Fri, Sep 5, 2014 at 12:07 PM, Paul Hodges IV <[email protected] > <javascript:>> wrote: > >> Yes .. It is a requirement that the page gets the updated attribute >> immediately .. here is an example of one possibility: >> >> http://jsbin.com/yevezidiqalu/1/edit >> >> And yes, I understand each page can have its own core-media-query to do >> the same thing, but thats not the point here .. >> >> Thanks for taking the time to dig through this with me :) >> >> On Friday, September 5, 2014 2:58:09 PM UTC-4, Scott Miles wrote: >>> >>> I'm still not sure we are talking about the same thing. For sure you >>> intend that some time *after* a user has selected a page, you want to be >>> able to, e.g. change `example-pager-guy.sharedpageattr` and have the >>> page automatically update? >>> >>> >> Id like to keep the custom-pager generic and not have to extend it >>> every time i want to pass around bound attributes/properties >>> >>> Sure, but that doesn't have anything to do with the question of dynamics >>> that I'm getting at. >>> >>> >>> On Fri, Sep 5, 2014 at 11:54 AM, Paul Hodges IV <[email protected]> >>> wrote: >>> >>>> They need to be bound as they can change (I thought I had specified >>>> that in the OP.) Id like to keep the custom-pager generic and not have to >>>> extend it every time i want to pass around bound attributes/properties >>>> >>>> On Friday, September 5, 2014 2:49:27 PM UTC-4, Scott Miles wrote: >>>>> >>>>> We still haven't covered the key question, which is whether the values >>>>> you are sending in to the pager really need to be _bound_ (that is >>>>> dynamic) >>>>> or whether they just need to be sent in one time. If you don't need them >>>>> to >>>>> be fully dynamic, it's all pretty easy: >>>>> >>>>> http://jsbin.com/hoteba/2/edit >>>>> >>>>> Minor notes: >>>>> - this.textContent = '' is a simpler way of removing all the children >>>>> than your while loop, you certainly don't need both >>>>> - the bindings you have to custom-pager in your example don't do >>>>> anything, I removed them for clarity >>>>> >>>>>> 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/fb3c9645-9fcb-434a-9057-72ac68aca53b%40googl >>>>>> egroups.com >>>>>> <https://groups.google.com/d/msgid/polymer-dev/fb3c9645-9fcb-434a-9057-72ac68aca53b%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/8dfb2d6e-ec29-4a6a-a269-552b8b3bf8b0% >>>> 40googlegroups.com >>>> <https://groups.google.com/d/msgid/polymer-dev/8dfb2d6e-ec29-4a6a-a269-552b8b3bf8b0%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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/polymer-dev/18ea0636-588e-45be-b078-8948ad1aebcf%40googlegroups.com >> >> <https://groups.google.com/d/msgid/polymer-dev/18ea0636-588e-45be-b078-8948ad1aebcf%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/020d2022-b360-496e-a74f-276d8110f446%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
