> 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?
> * composite is deprecated, just use (make-instance 'widget :children
(...))
Ah didnt know that.
> * what do you mean by "in composite definition"?
I meant check for duplicate children in the code for the composite widget,
but it was a dump suggestion anyway. Should be handled in lowest possile
level.
> * not taking your answer to the above into account: it should probably
go into (setf widget-children)
Absolutely.
> Hope that helps. :) Thanks for your interest in Weblocks!
No, thank you and the other contributors for the framework :)
>
--
You received this message because you are subscribed to the Google Groups
"weblocks" group.
To post to this group, send email to weblocks@googlegroups.com.
To unsubscribe from this group, send email to
weblocks+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/weblocks?hl=en.
