trace.cpp:113: warning: Can't link to 'InputMethod.traceBegin()'
trace.cpp:113: warning: Can't link to 'InputMethod.traceEnd()'

Change-Id: I47377b78b7db41684cf92dc0f1f611acc589389a
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

AbstractInputMethod marked internal, so no links possible

Change-Id: Id41f013a0b8b46eb170b5aebf6e75c259809ff33
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

These classes are not public APIs.

Change-Id: I3778743a98d11ccf0374778879a40443716425fe
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
Reviewed-by: Topi Reiniö <topi.reinio@theqtcompany.com>

[ChangeLog] Renamed QML import from
"import QtQuick.Enterprise.VirtualKeyboard" to
"import QtQuick.VirtualKeyboard", as the module is now open-source.

Change-Id: I240a3c1b598ca4aa41d2aad02b6e548622308833
Reviewed-by: Lars Knoll <lars.knoll@theqtcompany.com>

Change-Id: I0dc6af72a3ae52a0b97b704df84fb1a8197aeeb8
Reviewed-by: Jani Heikkinen <jani.heikkinen@theqtcompany.com>
Reviewed-by: Rainer Keller <rainer.keller@theqtcompany.com>

Since the virtual keyboard C++ interface is wrapped inside a
namespace, it is possible to get rid of "Declarative" name
in the class names, that would otherwise conflict with the
QML namespace in the documentation.

- Rename DeclarativeSettings to VirtualKeyboardSettings
- Remove "Declarative" from class names

The rationale for this change is that the name Declarative
refers to now obsolete QtQuick1 module. Also, the class names
are now the same in C++ and QML name spaces.

Change-Id: Ide050d47110443d894d95d35dddf0df5891587be
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>

This change wraps the entire C++ API into namespace.

In practice, all the C++ interfaces inside the qtvirtualkeyboard plugin
are private, except the QPlatformInputContext plugin API. Even the
AbstractInputMethod and AbstractInputPanel are not really a public in
the sense that they could be used outside the plugin. At least it does
not make sense, since there is no way to extend the virtual keyboard
functionality without recompiling the plugin.

Task-number: QTRD-3628
Change-Id: I1037ee247abca3219efeaa4e4150baaff7c3d668
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>

Change-Id: Iba2bd21b95dde1aac5750ac77856716e0c61e577
Reviewed-by: Kalle Viironen <kalle.viironen@theqtcompany.com>

Using the commercial template found here:

https://wiki.it.local/display/QTCOM/Header+templates+to+be+used+in+Qt+Code



Change-Id: If401d8fa3ff4dab6ea1e74477d5c02b5dcd09eea
Task-number: QTRD-3693
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>

Handwriting support was originally added as 1.4, but has been
updated to 2.0 in this commit.

Since the major version number has changed, all the components
must be registered with the new major version number.

Change-Id: I34c74f5dd24684423d153ff85a4a24eed8d4ffd1
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>

This change adds generic support for pattern recognition
based input methods.

Added new API for the input engine and input method to
process trace data. The trace data can originate from
various input devices, e.g. from touch screen or from
a dedicated hardware touch panel.

Added new data model type for trace supporting both the C++
and QML interfaces. The new data model is DeclarativeTrace
and Trace respectively, and it stores the trace data captured
from the input device.

The trace object is owned by the input method and is accessible
to the UI layer, capture device and the input method.

First, when the trace event begins, the capture device invokes
the InputEngine.traceBegin(). The input engine forwards this
call to the input method, which creates the trace object in
response to successful call.

Then the capture device receives the trace object and starts
collecting the data. Also, in case of touch screen input, there
are also the UI layer which renders the data. For this purpose
there are new kinds of Style elements available in the Styles
plugin. TraceCanvas is a specialized Canvas for rendering the
trace object on screen. The TraceCanvas is a normal styling
component, and can be customized like any other style element.

Finally, the InputMethod.traceEnd() is called when the trace
interaction ends. The trace is removed from screen automatically
when the trace object is deleted. I.e., the input method has
full control on how many traces it wants to collect for single
recognition phase.

Change-Id: I80ed90032f715726280197d9e94e7f0bd8280ff3
Reviewed-by: Gatis Paeglis <gatis.paeglis@theqtcompany.com>