| ... | ... | @@ -120,7 +120,7 @@ The snippet shows the implementation of the UI element, let us elaborate it a bi |
|
|
|
public class CorefViewComposite extends Composite {
|
|
|
|
```
|
|
|
|
|
|
|
|
Then we got the fields that are stored in this view. As you can see, there is a reference to the controller object. The next three variables present new Composites (aka UI parts) themselfes. Separating them in this way keeps the code clean, as well as it helps you to have an easy understanding of the layout in which those elements are arranged (it is very easy to order three elements, managing all at once is extremely difficult sometimes)
|
|
|
|
Then we got the fields that are stored in this view. As you can see, there is a reference to the controller object. The next three variables present new Composites (aka UI parts) themselfes. Separating them in this way keeps the code clean, as well as it helps you to have an easy understanding of the layout in which those elements are arranged (it is very easy to order three elements, managing all at once is extremely difficult sometimes). In this view we got three sub-composites. If you go back to the image of the result, the first is the block with all the buttons. The second one contains just two checkboxes. And the last one contains the table and its header.
|
|
|
|
|
|
|
|
```java
|
|
|
|
private CorefView part;
|
| ... | ... | |
