[Qt-creator] Qt Creator plugin API question

[Tino Pyssysalo]

Hi all,

This is in fact needed in https://bugreports.qt.io/browse/QTPM-1475 to improve prioritizing tutorials and examples in Qt Creator Welcome screen. Now, we have a long list of highlighted examples in alphabetical order, but new users have no idea which one to choose. Wed like to show 3-5 most relevant examples and hide others behind some More button. To set the priorities, we need to know, which ones are the most popular and that's exactly what telemetry could provide us.
--
Tino


On 11/10/2018, 5.05, "Aleksey Kontsevich" <tantrido at ya.ru> wrote:

    I see. However it is not clear to me: whether I can monitor now which help URL was opened, keywords searched, etc in QtC or can not?
    
    In src/plugins/coreplugin/helpmanager.h file you've removed
    
    void helpRequested(const QUrl &url, Core::HelpManager::HelpViewerLocation location);
    
    signal which allowed at least to track URLs of opened help documents.
    
    In Qt Help classes http://doc.qt.io/qt-5/qthelp-module.html I see the possibility and signals to track opened help documents or search keywords. Not sure how to get document titles from URLs, seems Qt Help does not provide this as well?
    
    So the only question: is it possible somehow to get  QHelpEngine instance for Qt Creator to connect to above signals? I do not see QtC help plugin provides such interface to public. Use QObject::findChild()? Thanks!
    
    -- 
    Best regards,
    Aleksey
    Linked in  https://www.linkedin.com/in/alekseykontsevich
    
    
    10.10.2018, 11:00, "Eike Ziller" <eike.ziller at qt.io>:
    >>  On 10. Oct 2018, at 00:57, Aleksey Kontsevich <tantrido at ya.ru> wrote:
    >>
    >>  Hi again,
    >>
    >>  Have question about QtC help system as well. I saw there was some class which emits signal when some document openned in help system with help page URI as argument: (Core::HelpManager) or something. Now can't find it. Whether it was removed or such functionality does not exist?
    >
    > That signal only existed to get the information from Core plugin to Help plugin. This has been changed to a direct call in https://codereview.qt-project.org/238543 when making Core plugin independent from QtHelp.
    >
    >>  --
    >>  Best regards,
    >>  Aleksey
    >>  Linked in https://www.linkedin.com/in/alekseykontsevich
    >>
    >>  08.10.2018, 00:53, "Aleksey Kontsevich" <tantrido at ya.ru>:
    >>>  Hi Eike,
    >>>
    >>>  I see there is no documentation about QtSupport namesapce or QtKitInformation?
    >>>
    >>>  Also it is not clear how to get other information like:
    >>>  - compiler
    >>>  - debugger
    >>>  - target platform
    >>>  - make system (qmake, qbs, cmake, etc)
    >>>
    >>>  Could You provide more info please? Thanks!
    >>>
    >>>  --
    >>>  Best regards,
    >>>  Aleksey
    >>>  Linked in https://www.linkedin.com/in/alekseykontsevich
    >>>
    >>>  12.09.2018, 14:20, "Eike Ziller" <eike.ziller at qt.io>:
    >>>>   If your question is about kits, generally the KitManager provides the list of defined Kits.
    >>>>   Kits are composed of data generated by KitInformation classes.
    >>>>   A specific KitInformation class can be used to provide specific info about a kit, e.g. QtKitInformation::qtVersion(kit) returns the Qt version specified in the kit.
    >>>>
    >>>>   Br, Eike
    >>>>
    >>>>>    On 11. Sep 2018, at 14:29, Aleksey Kontsevich <tantrido at ya.ru> wrote:
    >>>>>
    >>>>>    Hi all,
    >>>>>
    >>>>>    I need to implement KitDataSource for new ConnectedCreatorPlugin which will be officially shipped with QtC distribution. This data source gather information about compilers, platforms, target platforms, debuggers, etc used by a QtC user. I've found ProjectExplorer Namespace documentation (https://doc-snapshots.qt.io/qtcreator-extending/projectexplorer.html#namespaces) with classes which contains this information however documentation is still very poor and there are very many classes so it is not quite clear which one to use, how to use and how they are connected to each other. So question is:
    >>>>>    - how better organize these information gathering
    >>>>>    - which classes to use
    >>>>>    - which signals, methods
    >>>>>    - when to gather the information: on a project open, kit setup, etc?
    >>>>>
    >>>>>    Gould you guide me a little on this please? Thanks!
    >>>>>
    >>>>>    --
    >>>>>    Best regards,
    >>>>>    Aleksey
    >>>>>    Linked in https://www.linkedin.com/in/alekseykontsevich
    >>>>>    _______________________________________________
    >>>>>    Qt-creator mailing list
    >>>>>    Qt-creator at qt-project.org
    >>>>>    http://lists.qt-project.org/mailman/listinfo/qt-creator
    >>>>
    >>>>   --
    >>>>   Eike Ziller
    >>>>   Principal Software Engineer
    >>>>
    >>>>   The Qt Company GmbH
    >>>>   Rudower Chaussee 13
    >>>>   D-12489 Berlin
    >>>>   eike.ziller at qt.io
    >>>>   http://qt.io
    >>>>   Geschäftsführer: Mika Pälsi,
    >>>>   Juha Varelius, Mika Harjuaho
    >>>>   Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B
    >
    > --
    > Eike Ziller
    > Principal Software Engineer
    >
    > The Qt Company GmbH
    > Rudower Chaussee 13
    > D-12489 Berlin
    > eike.ziller at qt.io
    > http://qt.io
    > Geschäftsführer: Mika Pälsi,
    > Juha Varelius, Mika Harjuaho
    > Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B