The text based QML editor provides all features expected from a modern code editor. Those features include syntax highlighting, code completion, context sensitive help and real time error detection which all depend on a well functioning and complete code model. To be able to build up the code model, the parser has to find all QML modules (partly defined in plugins) available to developers. And here is currently the problem. The plugin detection in Qt Creator and the QML engine itself is not flexible enough to load plugins and subsequently feed the information into the code model. This results in missing code completion or false positives for error highlighting. And without really knowing which objects, methods and properties developers have available, we unnecessarily complicate developers' lifes.

While code completion offers a good starting point for developers, documentation is even more important. Obviously, it's impossible to autogenerate a complete documentation set for a plugin but a high level overview listing of all the methods and properties as well as the module (installation) names can be generated. Offering a documentation skeleton and tools will certainly lower the bar for developers to write documentation in the first place.