[Development] Qt Coding Guidelines

Hausmann Simon Simon.Hausmann at theqtcompany.com
Thu Mar 17 08:19:11 CET 2016

I agree with Rich.

This isn't documentation our users are facing. We don't need to extract from cpp files or use a particular style sheet.

+1 for Kai's initiative.


From: Richard Moore
Sent: Wednesday, March 16, 2016 22:55
To: Knoll Lars
Cc: development at qt-project.org
Subject: Re: [Development] Qt Coding Guidelines

On 16 March 2016 at 21:43, Knoll Lars <Lars.Knoll at theqtcompany.com<mailto:Lars.Knoll at theqtcompany.com>> wrote:
Good initiative. I think this is the right idea. Let's put the coding guidelines into .qdoc files after having a decision on the ML.

We should actually consider having a section about contributing to Qt in our documentation. Coding guidelines would fit nicely into that. But I think the .qdoc files should rather live in qtdoc instead of qtbase as most of the overview documentation is there.

?Personally I think markdown as Kai's used is better since we can link to that in git and have it rendered sensibly.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160317/a4563a81/attachment.html>

More information about the Development mailing list