DwtShell: Difference between revisions
No edit summary |
No edit summary |
||
(One intermediate revision by one other user not shown) | |||
Line 1: | Line 1: | ||
When instantiated, DwtShell will occupy the whole window of the current browser (in the next | {{Archive}}When instantiated, DwtShell will occupy the whole window of the current browser (in the next | ||
version of the toolkit DwtShell will be able to be instantiated in the context of an iframe or other | version of the toolkit DwtShell will be able to be instantiated in the context of an iframe or other | ||
HTML element). It essentially provides an application’s top level graphical context and handles | HTML element). It essentially provides an application’s top level graphical context and handles | ||
Line 6: | Line 6: | ||
component that does not require another DWT component as its parent, thus one must always be | component that does not require another DWT component as its parent, thus one must always be | ||
instantiated to provide the context under which other components may be instantiated. | instantiated to provide the context under which other components may be instantiated. | ||
{{Article Footer|unknown|4/4/2006}} | |||
[[Category:Zimbra AjaxTk]] |
Latest revision as of 12:27, 24 March 2015
When instantiated, DwtShell will occupy the whole window of the current browser (in the next version of the toolkit DwtShell will be able to be instantiated in the context of an iframe or other HTML element). It essentially provides an application’s top level graphical context and handles such tasks as browser window resizing, blocking the browser context menu as appropriate, providing overlays for blocking user input, and keyboard event dispatching. DwtShell is the only component that does not require another DWT component as its parent, thus one must always be instantiated to provide the context under which other components may be instantiated.