Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Documentation Tool Recommendation Required
Forum Update on Monday, May 27th 2025

Documentation Tool Recommendation Required

Scheduled Pinned Locked Moved Unsolved General and Desktop
documentationtool
8 Posts 5 Posters 2.2k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • V Offline
    V Offline
    Vader
    wrote on 19 Apr 2016, 05:58 last edited by
    #1

    I am looking for a good tool for helping me in documentation (Class diagrams, Sequence Diagrams etc). My team is required to follow waterfall model and hence we are required to document everything; every function, every variable. Since we are required to do this for every stage, I wanted some tool to help me do the work [or rather do this boring work for me].

    I tried Enterprise Architect, but it doesn't recognize signals and slots, making the output not exactly ideal. I looked it up and I read that there is no support for integration of EA with Qt.

    Searching the net landed me stuff like NCReport C++/Qt Report Generator and Doxygen as the top results. I honestly don't have any experience with either of them.

    So, I wanted to know what tool is used/recommended by you guys and why you use/recommend it.

    K 1 Reply Last reply 19 Apr 2016, 07:55
    0
    • M Offline
      M Offline
      mrjj
      Lifetime Qt Champion
      wrote on 19 Apr 2016, 06:26 last edited by
      #2

      My vote goes to Doxygen
      Reason:

      • Easy to use
      • Easy to setup.
      • Easy to tweak
      • You can use only minimal tagging. ( non very intrusive)
      • Its free software and source is available ( no lock down)
      • So far it worked very well with Qt
      • It has many types of diagram
      • Huge User base. ( many to ask/questions solved)

      It also have a plugin for Creator
      https://wiki.qt.io/Doxygen_Plugin_for_QtCreator
      (I have not tested it as I use mingw and have no VS installed)

      If you want to spend as little time as possible, its a time saver to create the different comment styles (tag)
      as text snippets for fast insertion. :)

      1 Reply Last reply
      0
      • V Vader
        19 Apr 2016, 05:58

        I am looking for a good tool for helping me in documentation (Class diagrams, Sequence Diagrams etc). My team is required to follow waterfall model and hence we are required to document everything; every function, every variable. Since we are required to do this for every stage, I wanted some tool to help me do the work [or rather do this boring work for me].

        I tried Enterprise Architect, but it doesn't recognize signals and slots, making the output not exactly ideal. I looked it up and I read that there is no support for integration of EA with Qt.

        Searching the net landed me stuff like NCReport C++/Qt Report Generator and Doxygen as the top results. I honestly don't have any experience with either of them.

        So, I wanted to know what tool is used/recommended by you guys and why you use/recommend it.

        K Offline
        K Offline
        kshegunov
        Moderators
        wrote on 19 Apr 2016, 07:55 last edited by kshegunov
        #3

        @Vader
        This would really be a question of preference more than anything. However, Qt uses Doxygen qdoc (which is similar to Doxygen) for building its documentation, so I suppose that'd be "recommended" if such label can be applied at all. I'd used Doxygen in the past and I'm not very impressed by the easiness or the workflow, but it does work as one would expect and it does have the necessary capabilities.

        Read and abide by the Qt Code of Conduct

        P 1 Reply Last reply 19 Apr 2016, 08:02
        0
        • K kshegunov
          19 Apr 2016, 07:55

          @Vader
          This would really be a question of preference more than anything. However, Qt uses Doxygen qdoc (which is similar to Doxygen) for building its documentation, so I suppose that'd be "recommended" if such label can be applied at all. I'd used Doxygen in the past and I'm not very impressed by the easiness or the workflow, but it does work as one would expect and it does have the necessary capabilities.

          P Offline
          P Offline
          Paul Colby
          wrote on 19 Apr 2016, 08:02 last edited by Paul Colby
          #4

          @kshegunov said:

          Qt uses Doxygen for building its documentation

          Is that actually true? I've seen it implied and suggested a few times, discussed on the mailing lists etc, but I've never found a definitive reference for it being so. Just curious myself :)

          K 1 Reply Last reply 19 Apr 2016, 08:05
          1
          • P Paul Colby
            19 Apr 2016, 08:02

            @kshegunov said:

            Qt uses Doxygen for building its documentation

            Is that actually true? I've seen it implied and suggested a few times, discussed on the mailing lists etc, but I've never found a definitive reference for it being so. Just curious myself :)

            K Offline
            K Offline
            kshegunov
            Moderators
            wrote on 19 Apr 2016, 08:05 last edited by
            #5

            @Paul-Colby
            I have to check the build scripts to be completely sure that some magic is not employed, but these comments in the source sure look like Doxy syntax.

            Read and abide by the Qt Code of Conduct

            1 Reply Last reply
            0
            • P Offline
              P Offline
              Paul Colby
              wrote on 19 Apr 2016, 08:12 last edited by
              #6

              @kshegunov said:

              these comments in the source sure look like Doxy syntax.

              Yeah, but they also look like QDoc commands.

              My understanding (which is very limited), is that Qt began with QDoc years ago, which then inspired the creation of Doxygen. There's since been plenty of comments re Qt moving to Doxygen one day, but I have no idea if that has already happened, is currently in progress, or just planned for one day in the future?

              Doxygen is great either way (I use it a lot). I was just curious to know if Qt had officially moved to it yet :)

              Cheers.

              K 1 Reply Last reply 19 Apr 2016, 08:17
              1
              • P Paul Colby
                19 Apr 2016, 08:12

                @kshegunov said:

                these comments in the source sure look like Doxy syntax.

                Yeah, but they also look like QDoc commands.

                My understanding (which is very limited), is that Qt began with QDoc years ago, which then inspired the creation of Doxygen. There's since been plenty of comments re Qt moving to Doxygen one day, but I have no idea if that has already happened, is currently in progress, or just planned for one day in the future?

                Doxygen is great either way (I use it a lot). I was just curious to know if Qt had officially moved to it yet :)

                Cheers.

                K Offline
                K Offline
                kshegunov
                Moderators
                wrote on 19 Apr 2016, 08:17 last edited by
                #7

                @Paul-Colby

                Yeah, but they also look like QDoc commands.

                Fair enough. It's (quite) possible I'm just mistaken, especially as it seems qdoc provides its own parser, so I suppose qdoc is the tool used.

                Read and abide by the Qt Code of Conduct

                1 Reply Last reply
                0
                • S Offline
                  S Offline
                  SGaist
                  Lifetime Qt Champion
                  wrote on 19 Apr 2016, 08:59 last edited by
                  #8

                  Hi,

                  Yes, it's still qdoc that's used, it's also been updated for the QML documentation.

                  Interested in AI ? www.idiap.ch
                  Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                  1 Reply Last reply
                  1

                  2/8

                  19 Apr 2016, 06:26

                  topic:navigator.unread, 6
                  • Login

                  • Login or register to search.
                  2 out of 8
                  • First post
                    2/8
                    Last post
                  0
                  • Categories
                  • Recent
                  • Tags
                  • Popular
                  • Users
                  • Groups
                  • Search
                  • Get Qt Extensions
                  • Unsolved