Re: [Development] QHash for Qt 6

>However, instead of adding >template bool qIsEmpty(const T ) { return t.empty(); } >we keep discussing how ugly std is=) But that's kind of ugly too. I read it as qlsEmpty(), not qIsEmpty(). See what I mean? On of those is a lower case L. How about a new approach to adding free functions:

[Development] Stepping down as QDoc maintainer

fiction novel for those same 25 years, and now I won't have an excuse for not writing it. Thanks for an interesting job as both software engineer and technical writer. Martin Smith ___ Development mailing list Development@qt-project.org https://lists.qt

Re: [Development] The age-old T* foo vs. T *foo

>I for one, never liked >QObject* x, y; >because x is a pointer, and y is not. It seems like they should both be >QObject*s. But that argues for not allowing the comma. QObject* x; QObject* y; I've always done it that way. From: Development on behalf

Re: [Development] Gerrit update

"Not that there's anything wrong with that." :-) From: Development on behalf of Bogdan Vatra via Development Sent: Tuesday, October 1, 2019 7:53 AM To: development@qt-project.org Subject: Re: [Development] Gerrit update Hi, Since yesterday I can't

Re: [Development] HEADS-UP: QStringLiteral

PM To: Qt development mailing list Subject: Re: [Development] HEADS-UP: QStringLiteral On 2019-08-22 14:48, Martin Smith wrote: > Now that we use clang in Creator and QDoc, suppose we write a QString > source code analysis tool using clang. The tool would parse sources > looking for uses o

Re: [Development] HEADS-UP: QStringLiteral

Now that we use clang in Creator and QDoc, suppose we write a QString source code analysis tool using clang. The tool would parse sources looking for uses of QString and then analyzing the code patterns where QString is used to find possible optimizations using the other Qt string classes. The

Re: [Development] Nominating Kavindra Palaraja for approvership

+1 From: Development on behalf of Topi Reiniö Sent: Thursday, July 11, 2019 5:33 PM To: development@qt-project.org Subject: Re: [Development] Nominating Kavindra Palaraja for approvership +1 from me. \topi From:

Re: [Development] Assistant WebKit/WebEngine support

, you can install the Qt documentation add-on. The Qt documentation site/add-on then just needs an index of all the snippets Creator might need to load. From: Samuel Gaist Sent: Friday, June 28, 2019 8:25 AM To: Martin Smith Cc: Palaraja, Kavindra; devel

Re: [Development] Assistant WebKit/WebEngine support

>That's what I'm trying to explain. I can't use what Creator gives me right now >as it doesn't match what is published on Qt's very own documentation site >(https://doc.qt.io). Shouldn't Creator go directly to the documentation site to get what it needs?

Re: [Development] Nominating Mikhail Svetkin for Approver status

+1 from martin From: Development on behalf of Lorn Potter Sent: Friday, May 17, 2019 1:45 AM To: development@qt-project.org Subject: Re: [Development] Nominating Mikhail Svetkin for Approver status +1 On 17/5/19 12:45 AM, Volker Hilsheimer wrote: >

Re: [Development] Nominating Ryan Chu for Approvership

+1 from Martin From: Development on behalf of Topi Reiniö Sent: Wednesday, May 15, 2019 1:39 PM To: Paul Wicking; development@qt-project.org Subject: Re: [Development] Nominating Ryan Chu for Approvership A solid +1 from me. \topi

Re: [Development] On deprecating functions

When qdoc sees the function declaration, it must be able to mark the qdoc node for the declaration as deprecated in 5.13, for example, so that it can require that the deprecation be mentioned in the function documentation. martin From: Development on

Re: [Development] Proposal: New branch model

>That's laudable, but a non-professional developer who just submitted a >fix and doesn't follow all the other changes going on might have a >different opinion. Wouldn't we expect those external patchers to submit changes to dev only? Then the module maintainer, or an LTS version maintainer (is

Re: [Development] Proposal: New branch model

>It is the absolute exception that a change goes into qtbase on first attempt. But many rejections have nothing to do with any change at all. I often submit documentation-only changes to QtBase, and they often get tested alone, with no other changes. They still get rejected multiple times

Re: [Development] Proposal: New branch model

: [Development] Proposal: New branch model 23.01.2019, 21:38, "Alex Blasche" : >> ____ >> From: Martin Smith >> If you make all patches in dev and then cherrypick them back to earlier >> versions that need them, why would you ever do

Re: [Development] Missing documentation in Qt 5.12

Subject: Re: [Development] Missing documentation in Qt 5.12 On Tue, Dec 18, 2018 at 11:49:22AM +, Eike Ziller wrote: > > > > On Dec 18, 2018, at 11:25, Konstantin Shegunov > > wrote: > > > > On Tue, Dec 18, 2018 at 9:39 AM Martin Smith > > wrote: I'l

Re: [Development] Missing documentation in Qt 5.12

There are no technical limitations, and it will be kept. I expect the fix will be fairly simple. But it sounds like you're asking for a better search mechanism. From: André Hartmann Sent: Tuesday, December 18, 2018 9:19:07 AM To: Martin Smith

Re: [Development] Missing documentation in Qt 5.12

be removed. martin From: Konstantin Shegunov Sent: Monday, December 17, 2018 11:03:50 PM To: Martin Smith Cc: Sze Howe Koh; Qt development mailing list Subject: Re: [Development] Missing documentation in Qt 5.12 Not only are members missing, but links lead

Re: [Development] Missing documentation in Qt 5.12

Are the missing chunks always in the all-members list? In the case of QWidget, it inherits QObject and QPaintDevice. Those pages look correct to me, but the all-members pages are missing some inherited members. Are there other missing chunks? martin

Re: [Development] Nominating Paul Wicking for Approvership

+1 From: Development on behalf of Simon Hausmann Sent: Wednesday, December 12, 2018 11:58:47 AM To: development@qt-project.org Subject: [Development] Nominating Paul Wicking for Approvership Hi, I would like to nominate Paul for approvership. He

Re: [Development] Who is in charge of qt-project.org?

>You've just dropped Qbs, what's next? >I don't trust you anymore, nor the company-ies you represent - Nothing >personal. >I think that it is time for the qt-project.org domain to be handed >back to the Qt Project community. But "dropped Qbs" means The Qt Company won't be developing Qbs anymore,

Re: [Development] QUIP 12: Code of Conduct

text and premise. I'm defending the goal of establishing a CoC. >Not if they don't elevate to a criminal act. My turn to bite. What is a heinous act that is not a criminal act? From: Konstantin Shegunov Sent: Sunday, October 28, 2018 11:35:42 AM To:

Re: [Development] QUIP 12: Code of Conduct

ch acts will be referred to the appropriate legal authority. From: Konstantin Shegunov Sent: Saturday, October 27, 2018 9:04:12 PM To: Martin Smith Cc: development@qt-project.org Subject: Re: [Development] QUIP 12: Code of Conduct On Sat, Oct 27, 201

Re: [Development] QUIP 12: Code of Conduct

prevent abusive behavior.We need a formal procedure to enable that, and the CoC is that procedure. From: André Pönitz Sent: Saturday, October 27, 2018 8:37:12 PM To: Martin Smith Cc: Bernhard Lindner; development@qt-project.org Subject: Re: [Developmen

Re: [Development] QUIP 12: Code of Conduct

no laws, so the implication is we don't consider any behavior an offense. From: André Pönitz Sent: Saturday, October 27, 2018 7:25:39 PM To: Martin Smith Cc: Bernhard Lindner; development@qt-project.org Subject: Re: [Development] QUIP 12: Code of Conduct On Sat,

Re: [Development] QUIP 12: Code of Conduct

of abuse, would suddenly lose their ability to resolve abuse problems and would instead use the CoC to abuse alleged abusers. That's what it looks like to me. From: Alexey Andreyev Sent: Saturday, October 27, 2018 5:21:10 PM To: Martin Smith Cc: NIkolai

Re: [Development] QUIP 12: Code of Conduct

the benefit. I hope that's not what you mean. Being a super contributor doesn't buy one the privilege of being an asshole to others. From: NIkolai Marchenko Sent: Saturday, October 27, 2018 4:03:41 PM To: Martin Smith Cc: Konstantin Shegunov; Qt developme

Re: [Development] QUIP 12: Code of Conduct

, real or not, is not resolved. From: Konstantin Shegunov Sent: Saturday, October 27, 2018 3:48:49 PM To: Martin Smith Cc: development@qt-project.org Subject: Re: [Development] QUIP 12: Code of Conduct On Sat, Oct 27, 2018 at 4:09 PM Martin Smith mailto:martin.sm...@qt.io>> w

Re: [Development] QUIP 12: Code of Conduct

re doing now. From: NIkolai Marchenko Sent: Saturday, October 27, 2018 3:17:09 PM To: Martin Smith Cc: priv...@bernhard-lindner.de; Qt development mailing list Subject: Re: [Development] QUIP 12: Code of Conduct Note that installing a conflict resolution authority

Re: [Development] QUIP 12: Code of Conduct

>Well, then let me give you my simple minded opinion on this topic, an engineers >opinion: >Do not introduce a CoC. In that case, if a contributor is mistreated by another contributor, what recourse does the victim have? martin From: Development on

Re: [Development] QUIP 12: Code of Conduct

:19 PM To: Martin Smith Cc: jh...@gmx.com; Volker Hilsheimer; Qt development mailing list Subject: Re: [Development] QUIP 12: Code of Conduct > Don't define it because you already know what it is. Just explain the > complaint process and create the committee to deal with each complaint o

Re: [Development] QUIP 12: Code of Conduct

>There are two ways to resolve this: either >1) Do not consider it, or >2) Define in excruciating detail, as to remove the "slippery" from the slope. There is a 3rd way: 3) Don't define it because you already know what it is. Just explain the comp[laint process and create the committee to deal

Re: [Development] QUIP 12: Code of Conduct

f the bad behavior of Donald Trump, we all know what is bad behavior in this context. From: Alexey Andreyev Sent: Thursday, October 25, 2018 3:56:18 PM To: Martin Smith Cc: Ulf Hermann; Qt development mailing list Subject: Re: [Development] QUIP 12: Code of Con

Re: [Development] QUIP 12: Code of Conduct

I suspect that most if not all of the commenters here who object to the CoC object to the attempt to define unacceptable behavior. It really has to be decided on a case by case basis, so remove the examples of unacceptable behavior, and don't attempt to define it at all. No one can object to

Re: [Development] QUIP 12: Code of Conduct

>It seems very wrong to make such decisions at conventions where only a small >part of the contributors can participate. >Especially for something as big and divisive It isn't wrong if the adoption process allows everyone to vote on whether to adopt the eventual CoC. What seems wrong is to

Re: [Development] Nominating Mårten Nordheim as an approver

+1 From: Development on behalf of Oliver Wolff Sent: Thursday, April 26, 2018 7:12:17 AM To: development@qt-project.org Subject: Re: [Development] Nominating Mårten Nordheim as

Re: [Development] how to include further changes while previous commit is still under review?

martin From: Konstantin Tokarev <annu...@yandex.ru> Sent: Monday, January 22, 2018 1:30:10 PM To: Martin Smith; Daniel Savi; Samuel Gaist Cc: development@qt-project.org Subject: Re: [Development] how to include further changes while previous commit is still under review? 22.01.2018, 14

Re: [Development] how to include further changes while previous commit is still under review?

martin From: Konstantin Tokarev <annu...@yandex.ru> Sent: Monday, January 22, 2018 12:36:38 PM To: Martin Smith; Daniel Savi; Samuel Gaist Cc: development@qt-project.org Subject: Re: [Development] how to include further changes while previous commit is

Re: [Development] how to include further changes while previous commit is still under review?

When updating the documentation, I often do 2 or more different commits and pushes to a single branch. Then I wait for them to get approved. Often, a reviewer will require changes to the first pushed commit after I have pushed the second commit. Then I do: git rebase -i HEAD~2 ...and I

Re: [Development] Project ERROR: Could not find feature future.

When I get that error, I do: git clean -dxf and run configure again. From: Development on behalf of Igor Mironchik Sent: Wednesday, January 3, 2018 6:29:19 PM To:

Re: [Development] Speeding up the review process (was: PostgreSQL cross compile for Pi)

+1 I am a member of the Qt documentation team, and I am often included as a reviewer for code changes that also include changes to qdoc comments. I always assume I am meant to review only the documentation, so if the documentation is ok, I give the change a +1 and add a comment that I only

Re: [Development] [docs] changing the way overloads are documented and presented

>The text duplication is silly, and I have seen several places where >information was inadvertently added to only one of the overloads. We still need a way to tell qdoc how to provide information that applies to one overload, or to a subset of the \fn overloads in the list. martin

Re: [Development] [docs] changing the way overloads are documented and presented

>I am a bit worried about having a good way to describe the specifics of a >>specific overload or group thereof. Remember you will still have the option of giving an overload its own qdoc comment instead of including it in the common \fn comment. martin

Re: [Development] [docs] changing the way overloads are documented and presented

I haven't looked at all of it, but +1 on the general idea. martin From: Development on behalf of Sean Harmer Sent: Friday, April 28, 2017 10:07:46 AM To:

Re: [Development] qdoc for C++ and QML

Uwe Rathmann <uwe.rathm...@tigertal.de> Sent: Tuesday, April 25, 2017 8:12:44 AM To: development@qt-project.org Subject: Re: [Development] qdoc for C++ and QML On Tue, 25 Apr 2017 06:05:38 +, Martin Smith wrote: > Use \internal in their qdoc comments to tell qdoc not to incl

Re: [Development] qdoc for C++ and QML

>Not sure if qdoc is intended to be useful for 3rd party libraries as >well, but at least for my use case it would save me a lot of work. It is meant to be useful for 3rd party libraries, so we just need to agree on the right way to do this. From:

Re: [Development] qdoc for C++ and QML

__ From: Shawn Rutledge Sent: Monday, April 24, 2017 5:08:25 PM To: Martin Smith Cc: development@qt-project.org Subject: Re: [Development] qdoc for C++ and QML > On 24 Apr 2017, at 16:38, Martin Smith <martin.sm...@qt.io> wrote: > > The problem when combining C++ and QML

Re: [Development] qdoc for C++ and QML

=qt...@qt-project.org> on behalf of Sean Harmer <s...@theharmers.co.uk> Sent: Monday, April 24, 2017 4:17:58 PM To: development@qt-project.org Subject: Re: [Development] qdoc for C++ and QML Hi, On 24/04/2017 14:23, Martin Smith wrote: > Regarding documenting both C++ and QML at t

Re: [Development] qdoc for C++ and QML

Regarding documenting both C++ and QML at the same time, I will be happy to implement it if we can get a good idea for how to do it. Regarding the creator issue, I don't understand the problem so I can't comment. martin From: Development

Re: [Development] \until

>The changes from Qt4 to Qt5 are actually among the most interesting >ones. So, rather than comparing on a file-by-file base, wouldn't it be >better to first index the documentation by function signatures and then >compare on a function-by-function base? That would also handle cases of >functions

Re: [Development] \until (was: Re: QList)

__ From: Development <development-bounces+martin.smith=qt...@qt-project.org> on behalf of Marc Mutz <marc.m...@kdab.com> Sent: Monday, April 3, 2017 9:33:35 AM To: development@qt-project.org Subject: Re: [Development] \until (was: Re: QList) On Saturday 01 April 2017 18:26:34

Re: [Development] \until (was: Re: QList)

development-bounces+martin.smith=qt...@qt-project.org> on behalf of Marc Mutz <marc.m...@kdab.com> Sent: Saturday, April 1, 2017 5:58:06 PM To: development@qt-project.org Subject: [Development] \until (was: Re: QList) On 2017-04-01 08:32, Martin Smith wrote: > But about the indirect

Re: [Development] QList

>But no \until. I try to put this in the docs, and sometimes I succeeded, but >I've also been -1ed for trying already. I have never been asked to add \until to qdoc. martin From: Development on behalf of

Re: [Development] QList

> I'm not even counting the argument from authority when >CS/Math were brought to the table without an invitation I will keep bringing them to the table because, as a documentation guy following this and other similar discussions, it looks like you (plural) are willing to ignore the importance

Re: [Development] QList

t inherit QVector, but I'm saying that makes sense because a polygon is not a vector. From: giuseppe.dang...@kdab.com <giuseppe.dang...@kdab.com> on behalf of Giuseppe D'Angelo <giuseppe.dang...@kdab.com> Sent: Monday, March 27, 2017 11:25:39 AM To: Martin

Re: [Development] QList

development@qt-project.org Subject: Re: [Development] QList Il 27/03/2017 09:22, Martin Smith ha scritto: > vector is an ordered collection of points, but a QVector can > contain anything; QVector<void*> can even contain unlike things, which > is truly a tuple. So the problem here

Re: [Development] QList

t-project.org Subject: Re: [Development] QList On Sunday 26 March 2017 22:53:59 Martin Smith wrote: > >Yes, using vector for an array type was not Stepanov's best choice of > >terms (he says so himself), but what you're doing is like arguing that > >"debt" should be spel

Re: [Development] QList

> Il 25/03/2017 17:11, Martin Smith ha scritto: > >>Note that I think we should change QPolygon to stop inheriting from > >> > > QVector in > > > >>the first place. QPolygon is not a QVector. > >> > > But then a vector is not a coll

Re: [Development] QList

>Note that I think we should change QPolygon to stop inheriting from QVector in >the first place. QPolygon is not a QVector. But then a vector is not a collection. From: Development on behalf of Thiago

Re: [Development] QList

: Monday, March 20, 2017 2:13:30 PM To: development@qt-project.org Subject: Re: [Development] QList On Monday 20 March 2017 13:42:09 Martin Smith wrote: > >Qt must have acceptable performance for end user applications to be able > >to have acceptable performance at all - whether or no

Re: [Development] QList

>Qt must have acceptable performance for end user applications to be able to >have >acceptable performance at all - whether or not it is a priority to those >developers. I write an application that has two performance requirements: 1. It must complete execution in 1 minute. 2. It must not

Re: [Development] QDataStream: blackbox or document all versions?

Do we need a way to tie A specific qdoc comment to the result of a specific autotest? martin From: Development on behalf of Thiago Macieira Sent: Sunday, September 25, 2016

Re: [Development] dev doesnt builds

I did git checkout 5.8 at the qt5 level but kept my qtbase module on dev branch. That seems to work. martin From: Development on behalf of Vlad Stelmahovsky Sent: Friday,

Re: [Development] Qt API review with clazy

There is a flag that tells clang to keep going when it can't find something or encounters too many errors, but it is in clang 3.9. martin From: Development on behalf of Sergio Martins

Re: [Development] [FYI] commit/review policy refactored

Sometimes I am listed as a reviewer for a code change in Qt that also involves documentation changes. The code change is sometimes outside my expertise, but I assume I have been included to approve the documentation changes. I always give +1 in such cases. Is that correct? martin

Re: [Development] Use of Standard Library containers in Qt source code

How about a merger of options 3 & 4 for Qt 6.0? A QtSTL that combines the ease of use of the Qt collections with the efficiency of STL algorithms. martin From: Development on behalf of André Somers

Re: [Development] commas in ctor-init-lists

mma-first, never change it to comma-last, even when the conditional compilation is removed. martin From: Eike Ziller Sent: Friday, June 3, 2016 10:42:20 AM To: Martin Smith Cc: Edward Welbourne; André Somers; development@qt-project.org Subject: Re: [Developm

Re: [Development] commas in ctor-init-lists

rd Welbourne Sent: Friday, June 3, 2016 10:14:38 AM To: Martin Smith; André Somers; development@qt-project.org Subject: Re: [Development] commas in ctor-init-lists > I think it would be instructive to hear the reasoning of the first > engineer to add a ctor-init-list on separate lines with l

Re: [Development] commas in ctor-init-lists

ing Andre's, yet his reply to me was explicitly absolute, where mine was not. martin From: Edward Welbourne Sent: Friday, June 3, 2016 10:05:52 AM To: Martin Smith; André Somers; development@qt-project.org Subject: Re: [Development] commas in ctor-init-lists I wr

Re: [Development] commas in ctor-init-lists

devious thinking would cause one to do that in the first place? martin From: Development <development-bounces+martin.smith=qt...@qt-project.org> on behalf of Martin Smith <martin.sm...@qt.io> Sent: Friday, June 3, 2016 10:00:26 AM To: Edwa

Re: [Development] commas in ctor-init-lists

>Please allow that, I do, of course. Andre didn't. He wrote... >> if (blah || boo || foo) { //no line breaking allowed ...with the comment. From: Edward Welbourne Sent: Friday, June 3, 2016 9:54:43 AM To: Martin Smith; André Somers; devel

Re: [Development] commas in ctor-init-lists

equire each expression to be on a separate line? I thought they should be on separate lines when the list is too long to be on a single line. martin From: André Somers <an...@familiesomers.nl> Sent: Friday, June 3, 2016 9:25:18 AM To: Martin Smith; de

Re: [Development] commas in ctor-init-lists

rom: Development <development-bounces+martin.smith=qt...@qt-project.org> on behalf of André Somers <an...@familiesomers.nl> Sent: Friday, June 3, 2016 8:45:29 AM To: development@qt-project.org Subject: Re: [Development] commas in ctor-init-lists Hi, Op 03/06/2016 om 08:28 schre

Re: [Development] commas in ctor-init-lists

>but it is very structurally clean and in some circumstances I prefer it due to >that. The structure is a comma separated list. Historically, the comma has always been placed directly after the first of two list items. The comma tells the reader that another list item will follow. There is

Re: [Development] commas in ctor-init-lists

>The two space indented colon in the coding style is even more awkward, having >to >manually indent the colon instead of using the editor's tab feature, plus it >breaks the >"put things at the end rule". emacs has handled it correctly for me for at least two decades. I just hit return it goes

Re: [Development] Nominating Edward Welbourne for approver status

+1 martin From: Development on behalf of Simon Hausmann Sent: Monday, May 9, 2016 1:20:28 PM To: Lars Knoll; Qt development mailing list Subject: Re: [Development] Nominating

Re: [Development] Build errors with raspbian

On Nov 15, 2013, at 9:32 AM, Sorvig Morten morten.sor...@digia.com wrote: On 14 Nov 2013, at 09:39, Stephen Kelly stephen.ke...@kdab.com wrote: Hello, I get build errors when trying to build qtbase dev branch for raspbian.

[Development] Nominating Topi Reiniö (topi.rei...@digia.com) as approver

and for the qdoc tool. Seconds? Martin Smith ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Nominating Topi Reiniö (topi.rei...@digia.com) as approver

On Oct 22, 2013, at 1:06 PM, Sergio Ahumada sergio.ahum...@digia.com wrote: On 10/22/2013 01:00 PM, Mitch Curtis wrote: On 10/22/2013 11:53 AM, Martin Smith wrote: I nominate Topi as an approver. Topi has been the leader of the Qt documentation team in Oslo for a long time. A search

[Development] Is this QML parser behaviour correct?

The QML parser has callbacks for processing the Import list and for processing individual imports. In qdoc, I used the one that gets the entire import list: virtual bool visit(UiImportList *) { return true; } virtual bool visit(UiImport *) { return true; } I assumed it would bet called once,

[Development] qdoc and DITA XML

or Topi Reiniö. martin smith ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Qt-creator] gerrit-speak

On Dec 14, 2012, at 10:40 AM, Sune Vuorela wrote: On 2012-12-13, Jenssen Tim tim.jens...@digia.com wrote: I would prefer that you didn't submit this reads to my brain much like go f*k yourself without the raw words. I get all the idea of the automating thing and all, and that machines

[Development] If you are working on documentation...

If you have trouble creating a link to something (usually title or subtitle) because the title or subtitle you are trying to link to exists in more than one document and your link goes to the wrong one, consider using the \target command. It didn't work across modules until today. The relevant

Re: [Development] If you are working on documentation...

Oops! The link to the target example should be this: See the section called \l {a_unique_string} {Qt Script} for more details. martin On Dec 12, 2012, at 12:22 PM, Martin Smith wrote: If you have trouble creating a link to something (usually title or subtitle) because the title or subtitle

Re: [Development] If you are working on documentation...

On Dec 12, 2012, at 12:22 PM, Martin Smith wrote: If you have trouble creating a link to something (usually title or subtitle) because the title or subtitle you are trying to link to exists in more than one document and your link goes to the wrong one, consider using the \target command

Re: [Development] Example clean-up for Qt 5

You can use \quotefromfile, \skipto, \printuntil, etc http://doc-snapshot.qt-project.org/qdoc/07-0-qdoc-commands-includingexternalcode.html#quotefromfile-command martin On Oct 3, 2012, at 2:29 PM, Sorvig Morten wrote: Help by offering your opinion on: * Does the example have a meaningful

[Development] Documentation and Modularization

I'm not sure if we want to go down this route (doxygen), but it seems an option to me. We have discussed it many times. The management decision has always been to proceed with qdoc. I don't feel strongly either way, but if I'm asked I would say we should stay with qdoc and just move qdoc