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 "4 Control Fundamentals"
m (4. Control Fundamentals. moved to 4 Control Fundamentals) |
m |
||
| Line 1: | Line 1: | ||
[[Comparison SWT / RWT|back to table of content]] | [[Comparison SWT / RWT|back to table of content]] | ||
| − | ===Bounds | + | ===Bounds=== |
Bounds work the same as in SWT. | Bounds work the same as in SWT. | ||
| − | ===Client Area | + | ===Client Area=== |
The client area will work the same as in SWT. | The client area will work the same as in SWT. | ||
The method <code>getClientArea()</code> exists, but currently uses a very limited algorithm. This will change in the future. | The method <code>getClientArea()</code> exists, but currently uses a very limited algorithm. This will change in the future. | ||
| − | ===Moving and Resizing | + | ===Moving and Resizing=== |
All the location and dimension methods work the same as in SWT. | All the location and dimension methods work the same as in SWT. | ||
| Line 14: | Line 14: | ||
Resize events are already sent, sending move events is not yet implemented but will be done in the future. | Resize events are already sent, sending move events is not yet implemented but will be done in the future. | ||
| − | ===Visibility | + | ===Visibility=== |
Though it is not yet fully implemented, visibility will work the same as in SWT. | Though it is not yet fully implemented, visibility will work the same as in SWT. | ||
| − | ===Z-Order | + | ===Z-Order=== |
planned | planned | ||
| − | ===Enabling and Disabling | + | ===Enabling and Disabling=== |
planned | planned | ||
| − | ===Preferred Size | + | ===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. | 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. | ||
| − | ===Painting | + | ===Painting=== |
Not yet available. Painting is based on the Graphics Context, see [[16._Graphics_Fundamentals.]] | Not yet available. Painting is based on the Graphics Context, see [[16._Graphics_Fundamentals.]] | ||
| − | ===Repainting and Resizing | + | ===Repainting and Resizing=== |
not planned | not planned | ||
| − | ===Filling the Background | + | ===Filling the Background=== |
not applicable | not applicable | ||
Revision as of 19:04, 9 January 2007
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.
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