> One more thought on this -- I don't really understand how your solution > (Stephen) determines ordering.
Order is irrelevant for subwidgets. Once again I turn to my favorite example, the available-contract-browser on http://www.hfsbo.com/services-and-pricing . There is *no* notion of order of the interval browsers (the gridedits) that could possibly be useful to any general-purpose renderer. In fact, I cannot allow anything like composite's render method to touch them, because what it would do would be to just render them one after another, which is completely wrong. (I render them in an after method on render-object-view-impl.) However, I still need tree walking to touch them. Why? Because when an admin logs out, those interval browsers respond by hiding the editing buttons, select boxes, etc. Auth-based transitions happen all over the place, so they are implemented with a tree walk. My dataforms tend to respond by rechecking the editing-allowed? GF I defined and switching back to data mode (and rerendering) if there was a true->false transition. The property listings respond by showing or hiding the view stats widget. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
<<inline: hfsbo-s+p-admin.png>>
Furthermore, anyone who uses navigations and calls render-widget in any render-widget-body method she's defined may potentially rely on this. With nav2, simply rendering a widget is enough to "touch" it for nav purposes; moving nav touching outside the render phase means we need a way for that touching to be ported. -- Sorry but you say Nibiru is a Hoax? Doesnt Exist? So maybe The Sumerian people doesnt exist also! --Anonymous by way of SkI
