Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
4 Control Fundamentals
Contents
Bounds
Bounds work the same as in SWT.
Client Area
The client area will work the same as in SWT.
The method getClientArea() exists, but currently uses a very limited algorithm. This will change in the future.
Moving and Resizing
All the location and dimension methods work the same as in SWT.
Currently, the only control that can be moved or resized by the user is Shell. Resize events are already sent, sending move events is not yet implemented but will be done in the future.
Visibility
Though it is not yet fully implemented, visibility will work the same as in SWT.
Z-Order
planned
Enabling and Disabling
planned
Preferred Size
The preferred size calculation is used in many layouts to use the available space effectively. When layouting text the preferred size calculation calls the underlying operating system to determine the size of text strings. Calling the operating system is not possible with RAP, but we can use JavaScript to determine the text size. To avoid multiple request / response cycles during the layout process (which is taking place on the server side with RAP) we plan to implement a sophisticated system of text probing and application wide text / size storage.
See also WidgetToolkit#Challenges
Painting
Not yet available. Painting is based on the Graphics Context, see 16._Graphics_Fundamentals.
Repainting and Resizing
not planned
Filling the Background
not applicable