radisb wrote: >> I wonder how you would end up putting a duplicate object into a children >> list; never fell into that pit. > > I fell into that pit by trying the following: I wanted to present the one > widget twice on the client by "splitting-mirroring" its visual behaviour in > the same page but in two different locations (Start and end of the page). > For example I would like for all my pages to render a widget as header and > as footer. It should be the same widget because it is the same data I want > to present. I just want to present it in 2 locations. So why creating > another widget and having to synchronise its contents? > > Would that be a legit case?
It seems to be, but there are some issues you'll have to take care of. In this case we somehow need to ensure that DOM ids are unique, and be careful to sync the state of the other copies when one of them is updated (marked dirty). So I guess it could be done, but it will need a couple of hours to make it work correctly (and not break anything else). Leslie -- You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/weblocks?hl=en.
