Informal Protocol declaration for WFPage delegates.
Function in this informal protocol are used to respond to different points in the page life cycle.
Common activities include setting up dynamic widgets, responding to actions, etc.
Located in /framework/WFPage.php (line 27)
Called by PHOCOA just before after page is rendered.
This callback can be used to munge the final output of the page rendering before it is returned to the caller.
UNTESTED!
Called by PHOCOA when an "action" (form submission) has taken place on the page.
If the action name is "search" then the delegate method is searchAction().
NOTE: This is the modern version of <pageName>_<actionName>_Action()
Called by PHOCOA when NO action is run for the page.
This is used to set up data default data that is needed should no action be taken. For instance, exeucting a default search query if no SEARCH field and "Search" action was run. This is common when loading a page for the first time (thus there is no way an action could have been run).
Called when the page instances have been loaded and configured.
You can be certain at this point that all instances in the .yaml files have been loaded and connected.
Of course, dynamically created instances may not exist yet.
Get the list of named parameters for the page.
Called when the page has finished loading.
State is not guaranteed to be totally restored.
The most common use for this callback is to load data objects with which the UI elements will be bound.
NOTE: This is the modern version of _PageDidLoad()
Called just befored rendering, but after the skin has been initalized.
This is a good callback to use to add head strings, meta tags, set the HTML title, set the skin to use, etc.
NOTE: This is the modern version of _SetupSkin()
Called just before the batched binding updates are pushed from the UI state back on to the model objects.
Remember, in PHOCOA, we are approximating a stateful environment on top of a stateless one. Thus unlike in Cocoa, we have to "batch" apply the changes made via the client. In Cocoa, all bindings are done one-at-a-time because the model is stateful and there is no penalty for dealing with one change at a time. On the web, to deal with each change at a time would REQUIRE a "doPostback" kind of mentality on every UI click, which leads to very painful applications for users.
NOTE: only gets called for the request page, since if you are the response page, there is no client state in existence to which might require application of changes made with bindings.
Called by PHOCOA just before the page is rendered.
NOTE: Not sure what this would ever be useful for... but I am putting it in here. Please let the PHOCOA communitiy know if you're using this. NOTE: This is called AFTER pullBindings() although no one should have to worry about this fact...
UNTESTED!
Documentation generated on Thu, 17 Apr 2008 13:51:59 -0400 by phpDocumentor 1.4.1