Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "5 Display"
(→Naming Your Application.) |
|||
| Line 1: | Line 1: | ||
[[Comparison SWT / RWT|back to table of content]] | [[Comparison SWT / RWT|back to table of content]] | ||
| − | ===Naming Your Application | + | ===Naming Your Application=== |
Not yet implemented. The HTML title could be used to mimic a minimal application naming. | Not yet implemented. The HTML title could be used to mimic a minimal application naming. | ||
| − | ===Display Life Cycle | + | ===Display Life Cycle=== |
| + | Similar, but the display lives as long as the browser session is active. | ||
| − | ===Events and Listeners | + | ===Events and Listeners=== |
| + | Will be implemented. | ||
===Event Filters.=== | ===Event Filters.=== | ||
| + | Not yet implemented. Quote SWT book: "Filters are Powerful and Dangerous". | ||
| + | One of the standard use cases for event filtering - large numbers of events - are not a good idea for RWT because of the distributed nature of RAP (and associated network latency). | ||
===Runnable "Execs".=== | ===Runnable "Execs".=== | ||
| + | Not yet implemented. Async exec requires some effort on the RWT side, as the client needs to be informed of UI changes. As http is a stateless protocol with request/response pushing of data is not intended by the creators of the protocol. There are two workarounds: | ||
| + | * Polling (the client polls the server regulary while an async exec is running) | ||
| + | * so called Comet - a http response is kept open / alive and can be used to push data to the browser. Latest developments in java servers promise to implement Comet with minimal overhead (Jetty, Glassfish). | ||
===The Event Loop.=== | ===The Event Loop.=== | ||
Revision as of 15:11, 8 January 2007
Contents
- 1 Naming Your Application
- 2 Display Life Cycle
- 3 Events and Listeners
- 4 Event Filters.
- 5 Runnable "Execs".
- 6 The Event Loop.
- 7 Multithreaded Programming.
- 8 Timers.
- 9 Putting It All Together: Multithreading, Timers, Events, and the Event Loop.
- 10 Monitors, Bounds, and Client Area.
- 11 The Active Shell, All Shells, and Focus Control.
- 12 Cursor Control and Location.
- 13 Display Depth and DPI.
- 14 Updating the Display.
- 15 Application Data.
- 16 Coordinate Mapping and Mirroring.
- 17 Miscellaneous.
Naming Your Application
Not yet implemented. The HTML title could be used to mimic a minimal application naming.
Display Life Cycle
Similar, but the display lives as long as the browser session is active.
Events and Listeners
Will be implemented.
Event Filters.
Not yet implemented. Quote SWT book: "Filters are Powerful and Dangerous". One of the standard use cases for event filtering - large numbers of events - are not a good idea for RWT because of the distributed nature of RAP (and associated network latency).
Runnable "Execs".
Not yet implemented. Async exec requires some effort on the RWT side, as the client needs to be informed of UI changes. As http is a stateless protocol with request/response pushing of data is not intended by the creators of the protocol. There are two workarounds:
- Polling (the client polls the server regulary while an async exec is running)
- so called Comet - a http response is kept open / alive and can be used to push data to the browser. Latest developments in java servers promise to implement Comet with minimal overhead (Jetty, Glassfish).