From f9bd6d9b9304a4eb73fc404009e0a973818c6d1a Mon Sep 17 00:00:00 2001
From: Erik Lumme <erik@vaadin.com>
Date: Wed, 13 Sep 2017 10:27:22 +0300
Subject: Migrate UseTooltipsToClarifyFunctions

---
 .../UseTooltipsToClarifyFunctions.asciidoc         | 32 ++++++++++++++++++++++
 1 file changed, 32 insertions(+)
 create mode 100644 documentation/articles/UseTooltipsToClarifyFunctions.asciidoc

(limited to 'documentation/articles/UseTooltipsToClarifyFunctions.asciidoc')

diff --git a/documentation/articles/UseTooltipsToClarifyFunctions.asciidoc b/documentation/articles/UseTooltipsToClarifyFunctions.asciidoc
new file mode 100644
index 0000000000..af871a6332
--- /dev/null
+++ b/documentation/articles/UseTooltipsToClarifyFunctions.asciidoc
@@ -0,0 +1,32 @@
+[[use-tooltips-to-clarify-functions]]
+Use tooltips to clarify functions
+---------------------------------
+
+Even when clearly labelled, the action performed by a button might not
+be clear enough to the user. This is especially common when space or
+design constraints force you to keep the label very short, or use an
+icon instead of a label. This is where tooltips come in handy.
+
+image:img/tooltip.png[A tooltip]
+
+Tooltips are very easy to add to Vaadin components, although the method
+used to set them is the somewhat misleadingly named *setDescription()*:
+
+[source,java]
+....
+Button btnAttach = new Button();
+btnAttach.setIcon(new ThemeResource("icons/attach.png"));
+btnAttach.setDescription("Attach a file");
+....
+
+Of course, tooltips can be used for all kinds of UI components, not just
+buttons. An input field or even a read-only indicator can benefit from a
+tooltip. While the entire point of tooltips is to convey more
+information that would fit in the component’s caption or label, it’s
+still a good idea of try to keep the tooltip’s text as short as
+possible. Big tooltip balloons get in the way of using the UI and become
+annoying distractions instead of helpful aids.
+
+Keep in mind, however, that tooltips cannot be seen on a touch screen,
+since there is no mouse pointer to hover over the component. For input
+fields, consider using an *input prompt* instead.
-- 
cgit v1.2.3

