Fwd: Re: source formatting: what is supposed to be automatic now?

Milian Wolff mail at milianw.de
Mon Nov 28 14:11:47 UTC 2011

forwarding to kdevelop-devel

----------  Forwarded Message  ----------

Subject: Re: source formatting: what is supposed to be automatic now?
Date: Monday 28 November 2011, 13:55:20
From: David Nolden <david.nolden.kdevelop at art-master.de>
To: Milian Wolff <mail at milianw.de>

2011/11/28 Milian Wolff <mail at milianw.de>:
> Personally though, I find it not very usable yet though. It would be really
> cool if we could get a proper UI for configuring uncrustify. Otherwise our
> formatting settings dialog simply makes no sense, as the preview will not 
> at all. I bet that people using KDevelop will compare the script formatter
> with the astyle formatter, see that the latter is much easier to configure 
> use that. Most people won't know uncrustify or know that it is much more
> powerful than astyle...

There is a GUI to configure uncrustify, it's an application called
"universalindentgui". I don't like the idea of creating even more
hardly maintainable GUI code.

It's totally fine if people use astyle because it's easier to
configure. A consistent formatting using uncrustify is mainly
interesting for larger shared projects which want to enforce
consistency, like us, and for such projects, I don't see a problem in
configuring uncrustify _once_ (for example using universalindentgui)
and then distributing the configuration as part of the source code.

You have the option: Either you use the simple built-in astyle which
is easy to set-up but not shareable, or you use the powerful
custom-script based formatting which is more difficult to configure
initially, but then can be arbitrarily powerful and easily shared.
Milian Wolff
mail at milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20111128/059b71e5/attachment.sig>

More information about the KDevelop-devel mailing list