>> With the new widget tree framework we could have a client-side >> MARK-DIRTY function that finds a widget for a given dom id, marks it >> dirty on the server side and updates it in the request response. > > Isn't that still making a server request though? I don't entirely > understand how this would be different from the normal mark-dirty > function (except that I am giving it a dom id instead of the widget > itself).
Yes, but it's more convenient. Without this you'd have to set up an action on the server side to mark the appropriate widget dirty and call that. Do you want a pure client-side solution? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
