|
How to specialize a dialog |
Specializing a dialog is much like specializing a page, see how to specialize a page.
Most dialogs do not contain an information part. Therefore you can not see the class inclusion information from the verbose debugging mode. Instead you can look at the dialogs HTML source for the first part inclusion comment. It should show the name of the dialogs class after 'in'. Then try to locate the dialogs class file in the application classFolder. If it is not there it must be in the root classFolder.
If you need to pass more information to the page that opened the dialog, you may override the [method:pnt.web.dialogs.PntDialog::getReplyScriptPiece|getReplyScriptPiece] method and answer a function definition string with extra parameters. The existing pages will include the function definition, but ignore the extra parameters in the function body. If you change the name of the function, you should also override printReturnFuncName to print the actual function call.
You may override the getMinWindowSize method to get a different size popup window.
You may also write you own custom dialog from scratch. See example 9 for a global filter dialog. |
|
