WD My Book Duo comes as a RAID 0 formatted with NTFS. For the Homeserver, it is prepared as a RAID 1 with ext4. To… Read More »Prepareing WD My Book Duo for Linux Usage
Route offers the possibility to put the content of a View into a parent layout. By default, the content of the View is just appended… Read More »Vaadin 14: Using a Placeholder in RouterLayouts
While Vaadin makes it easy to develop UIs in one language and allows extremely simple programming stlye like clunching everything into one class, the narrow way of setting up “the best way” for a clear separation of Model, View and Control is tricky to find.
At least for me, I define this path as follows:
- Model: usage of POJOs and Vaadin Data Model ( see here)
- View: Declarative Design (see here)
- Control: CustomComponent
To be able to follow this path, I would like to extract as much of the “Design” into the Declarative Design as possible. Unfortunately, at point of writing, the Vaadin documentation lacks on deepth about how to use each of their Component declaratively.
This Note is about using a Grid inside a Declarative Design and attaching a List of Pojos via a ListDataProvider.