Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "1 Widget Fundamentals"

m (1. Widget Fundamentals. moved to 1 Widget Fundamentals)
(Replaced content with "This page was obsolete and has been deleted. Please see the history if you need to access the content.")
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Comparison SWT / RWT|back to table of content]]
+
This page was obsolete and has been deleted. Please see the history if you need to access the content.
 
+
===What Is a Widget?===
+
 
+
TBD
+
 
+
===Widget Hierarchy.===
+
 
+
RWT uses the same widget hierarchy as SWT. In addition the class
+
<code>Widget</code> 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 <code>getDisplay()</code> method, the meaning of Display in RWT is
+
somewhat different.
+
Display is described in more detail in the chapter [[5. Display.|Display]]
+

Latest revision as of 06:19, 7 January 2014

This page was obsolete and has been deleted. Please see the history if you need to access the content.

Back to the top