Legacy modules are modules whose specification
qmldir file does not contain a module identifier directive. A legacy module may be either installed into the QML import path (as an installed legacy module) or
imported by clients with a relative import (as a located legacy module). Clients are advised to avoid using legacy modules if possible. Module developers should ensure they create identified modules and not legacy
An installed, non-identified module is automatically given an identifier by the QML engine. This implicitly defined identifier is equal to the install path of the module (relative to the QML import path) where directory-separator characters are replaced with period characters.
A non-identified module which is installed into the QML import path has the following semantics:
A non-identified module which is imported via a relative directory path import statement is loaded by the engine as a located legacy module. The following semantics apply to located legacy modules:
A located legacy module may reside on the local file system or on the network and can be referred to by a URL that specifies the file system path or network URL.
As part of the free Business evaluation, we offer a free welcome call for companies, to talk about your requirements, and how the Felgo SDK & Services can help you. Just sign up and schedule your call.
Sign up now to start your free Business evaluation: