From d548ebb548d860dfb95ff9dbc69e4a45c25973df Mon Sep 17 00:00:00 2001 From: Artur Date: Fri, 3 Mar 2017 10:17:11 +0200 Subject: [PATCH] Fix documentation links (#8726) * Fix documentation links --- documentation/datamodel/datamodel-overview.asciidoc | 12 ++++++------ .../migration/migrating-to-vaadin8.asciidoc | 8 ++++---- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/documentation/datamodel/datamodel-overview.asciidoc b/documentation/datamodel/datamodel-overview.asciidoc index 42dd0a73d6..ea11d63f2f 100644 --- a/documentation/datamodel/datamodel-overview.asciidoc +++ b/documentation/datamodel/datamodel-overview.asciidoc @@ -11,7 +11,7 @@ The Vaadin Data Model is one of the core concepts of the library. There is a standard data interface that all UI components use to access and modify the application's data. The most basic UI component for handling data is a field component that lets the user define a single value, for instance a text field for writing the name of a product or a dropdown menu for selecting which department an employee belongs to. -See <> to learn how these components can be used on their own. +See <> to learn how these components can be used on their own. In most applications, there are business classes that represent real-world objects like a single employee or a product in an inventory. The user interface is structured as a form that lets the user edit all the different properties of a single business object instance. @@ -22,11 +22,11 @@ You have full control over how you configure and lay out the individual input fi There are UI components in the framework that lists multiple similar objects and lets the user view, select and in some cases even edit those objects. A listing component can get its data from an in-memory collection or lazily fetch it from some backend. In either case, there are options available for defining how the data is sorted and filtered before being displayed to the user. -Read more about how to provide lists of data to these components in <>. -Using a listing component as an input field to select one or many of the listed items is described in <>. +Read more about how to provide lists of data to these components in <>. +Using a listing component as an input field to select one or many of the listed items is described in <>. Vaadin Data Model topic references:: -* <> +* <> * <> -* <> -* <> +* <> +* <> diff --git a/documentation/migration/migrating-to-vaadin8.asciidoc b/documentation/migration/migrating-to-vaadin8.asciidoc index 0a351240ab..2aa14dfbb7 100644 --- a/documentation/migration/migrating-to-vaadin8.asciidoc +++ b/documentation/migration/migrating-to-vaadin8.asciidoc @@ -125,13 +125,13 @@ Framework 8 no longer uses `Item`, `Property` nor `Container`. These building blocks for the old data binding have been deprecated in favor of more Java 8 friendly APIs. The new data model can be roughly split into three main topics, namely binding data to field components, providing data to listing components and handling selections. -The revised <> chapter is the recommended resource to get started with learning these new concepts. +The revised <> chapter is the recommended resource to get started with learning these new concepts. For migration from Framework 7 the key references are the following sections: -* <> and <>, which cover the new data binding concepts that replace `Property` and `FieldGroup`. +* <> and <>, which cover the new data binding concepts that replace `Property` and `FieldGroup`. -* <>, which covers the new `Container` and `Item` replacement, the `DataProvider`, as well as the associated sorting and filtering APIs. +* <>, which covers the new `Container` and `Item` replacement, the `DataProvider`, as well as the associated sorting and filtering APIs. -* And for the new selection APIs, <>. +* And for the new selection APIs, <>. For a full list of incompatible changes between Framework 7 and 8, please refer to the _Incompatible or Behavior-altering Changes_ section of the release notes, available at link:https://vaadin.com/download/prerelease/8.0/8.0.0/8.0.0.beta1/release-notes.html#incompatible[]. -- 2.39.5