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 "1 Widget Fundamentals"
Line 28: | Line 28: | ||
'''Querying the Display.''' | '''Querying the Display.''' | ||
− | Though RWT provides a class | + | Though RWT provides a class Display as well and Widget provides the <code>getDisplay()</code> method, the meaning of Display in RWT is |
− | + | somewhat different. | |
− | method, the meaning of Display in RWT is somewhat different. | + | Display is described in more detail in the chapter [[5. Display.|Display]] |
− | Display is described in more detail in the chapter | + | |
− | [[5. Display.|Display]] | + |
Revision as of 11:14, 8 January 2007
What Is a Widget?
TBD
Widget Hierarchy.
RWT uses the same widget hierarchy as SWT. In addition the class
Widget
implements Adaptable.
Events and Listeners.
RWT implements the SWT events as close as possible. Through the distributed nature of RWT e.g. key-stroke events with server-side turnarounds for event processing won't be available since the network latency is too big to make such events usefully applicable.
Currently RWT does not implement untyped Listeners as SWT does. Therefore all related methods (like Widget.notifyListeners(int,Event)) are missing.
Application Data.
Works the same as in SWT. All methods for both, named and unnamed application data, are implemented.
Querying the Display.
Though RWT provides a class Display as well and Widget provides the getDisplay()
method, the meaning of Display in RWT is
somewhat different.
Display is described in more detail in the chapter Display