This brings a question: what is the proper strategy to initialize property values when using ajax submits? Does finishLoad() does the trick? I am still a bit confused about when all those methods/listeners are invoked and in which order
I've got a question about this as well, although I am Tap 4.0 centric. Why do we not have an interface which gives a consistent initialization point for a page. pageBeginRender runs before both rewind and render, so isn't terribly useful for init code without extra logic checking which cycle I am in. pageAttached() would be great, except that it occurs before activateExternalPage(), so if the params received by activateExternalPage would cause a model to change, then I have to generate the model twice, once during pageBeginRender and again in activateExternalPage. I can't do it only in activateExternalPage, because that method doesn't get executed during form posting. Currently, I've got a base class which finalizes pageBeginRender but which calls two methods, one for initializing only before rewind and one which executes before both rewind and render, effectively splitting pageBeginRender where I need to. But this seems like an awkward kludge which would be better served by something more similar to a 'constructor' method, which we don't currently seem to have. The same need exists for a 'destructor,' although pageDetached does pretty well for that. --sam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
