-
Task
-
Resolution: Fixed
-
P2: Important
-
None
-
None
-
4ccc2b4ff (18.0)
Currently, the main entry point into extending Qt Creator is (https://doc.qt.io/qtcreator-extending/index.html) which is fine in principle as covers also "less intrusive" means likeĀ external tools and new file type.
It's also ok to have extensions as the most complex case last, but it only has only "Lua extensions" as an item, the more general C++ based extensions" are handled from via "Creating Plugins", which is linked several times from sub-items on the page and the "All topic", but not directly.
This "Creating Plugins" ranks high in search engines but /only/ covers for C++ based "extensions", therefore misleading people to the assumption that this is the only way.
I therefore suggest to
- add a paragraph on the "Creating Plugins" stating that plugins can currently be created with either Lua or C++, maybe with the pros and cons of the approaches
- rename the "Creating Your First Plugin" link to "Creating a C++-based Plugin",
- add above that link a link "Creating a Lua-based Plugins" pointing to https://doc.qt.io/qtcreator-extending/lua-extensions.html
Similiarly, "Distributing Plugins" is currently also restricted to C++ plugins and "manual" distributions.
This could be improved by pre-pending the the "new" extension store publishing procededure and noting that the currently described procedure there as a secondary way of distribution when publication in the extension store is not wanted or otherwise impossible.