From 8daf84c27f097d28f41ab382f8a500f2bf76a09d Mon Sep 17 00:00:00 2001 From: Zbynek Konecny Date: Sat, 13 Sep 2025 19:47:21 +0200 Subject: [PATCH] Fix a link --- src/main/markdown/doc/latest/DevGuideUiCellWidgets.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/main/markdown/doc/latest/DevGuideUiCellWidgets.md b/src/main/markdown/doc/latest/DevGuideUiCellWidgets.md index 38a5d3d32..e62d4907e 100644 --- a/src/main/markdown/doc/latest/DevGuideUiCellWidgets.md +++ b/src/main/markdown/doc/latest/DevGuideUiCellWidgets.md @@ -12,8 +12,8 @@ This design follows the flyweight pattern where data is accessed and cached only flyweight Cell objects. A cell widget can accept data from any type of data source. The data model handles asynchronous updates as well as push updates. When you change the data, the view is automatically updated. -Cells are the basic blocks of a user interface and come in a variety of [available cell types] -(#available). They render views of data, interpret browser events and can be selected. A Cell has +Cells are the basic blocks of a user interface and come in a variety of [available cell types](#available). +They render views of data, interpret browser events and can be selected. A Cell has a type based on the data that the cell represents; for example, DatePickerCell is a `Cell` that represents a Date and allows the user to select a new Date. Cells must implement a render method that renders the typed value as an HTML string. In addition, cells can override onBrowserEvent to act as a flyweight that handles events that are fired on elements that were rendered by the cell.