GitLab

This should look better when rendered in browsers.

Olaf Mandel authored Feb 02, 2021 and Carl Schwan committed Feb 02, 2021

This is not strictly necessary, but it makes the output look nicer if
the block comments are completely left-shifted. This makes all lines
line up with the first line.

Olaf Mandel authored Feb 02, 2021 and Carl Schwan committed Feb 02, 2021

Doxygen differentiates between adjacent C++ comments and C++ comments
separated by an empty line: the former form one block, the latter
multiple blocks. Preserve this from the input file to the output.

Note that there was a mistake in the endcond functional test: the
expected output did wrongly merge two comments into a block.

Olaf Mandel authored Feb 02, 2021 and Carl Schwan committed Feb 02, 2021

In preparation to get the comment-order functional test to pass, treat
adjacent C++ comments (starting with "//") as one token: this is how
Doxygen sees them as well.

To preserve the intentation in the functional tests, also implement a
left_shift_comment() method which is called from fixup_tokens().

Olaf Mandel authored Feb 02, 2021 and Carl Schwan committed Feb 02, 2021

Output class members in the order they were defined in, switching
between public and private access as needed. This is needed as a
preparation for getting the comment-order functional test to pass: it
free-standing comment blocks that must be kept in their original order.

As a side effect, the output no longer contains an obligatory "public:"
access-declaration at the start of the class. This requires changing
some of the existing test cases with empty classes or where the first
element is private.

Olaf Mandel authored Feb 01, 2021 and Carl Schwan committed Feb 02, 2021

Some doxygen comments are not associated with any element translatable
into C++, e.g. opening and closing groups: those are stand-alone.
Accordingly, comments (and the elements they may refer to) must not be
resorted when generating the output.

In addition, one-line comments must preserve empty lines between them:
putting them together causes the interpretation to change, e.g. a @{
followed by a @brief always opens a group, but the brief is part of the
group instead of the following element if there is no empty line between
the two comments.

This test case show-cases the problem without having an implementation,
yet.

Lasse Lopperi authored Jan 10, 2021 and Carl Schwan committed Jan 10, 2021

Add QML enums as "enum class" as both introduce a namespace.

Addresses: #4

Olaf Mandel authored Nov 11, 2020 and Carl Schwan committed Nov 11, 2020

Doxygen 1.8.20 apparently needs a READ property accessor in order to
detect a Q_PROPERTY() macro correctly. So add a dummy-accessor to our
output.

As suggested by Matthew Jones in #7.

Standalone comments (e.g. those trailing after an attribute) should be
put into the same visibility category (public / private) as the
preceeding element.

The old ci used travis but now doxyqml is on gitlab :D

add default parameter support

Add option to not generate "Since: [ver]" in docs

Use flake8 to enforce code style

Flake8 requires at least 3.4

Use flake8 to make the code mostly pep8 compliant. Only exception is line
length, which is set to 120.

Handling for attributes and nested components