Source Code Formatting in kdev4
Megan Webb
mwebb at unwired.com.au
Fri May 4 13:29:16 UTC 2007
Hi Matt,
At the moment, still trying to understand all the interfaces in
kdevelop. I don't have a good
grip on them yet. Honestly didn't get all the 3.4 ones, just worked out
enough to get what
I was fixing/working on done within the exiting interfaces. Know even
less about kdev4 at
the moment.
If you have any ideas or suggestions for starting points for a source
formatting interface, as I'm
definitely interested.
Regards
Megan
Matt Rogers wrote:
> On Friday 04 May 2007 06:04, Megan Webb wrote:
>
>> Hi Everyone,
>>
>>
>
> Hi Megan!
>
>
>> I know I've been a bit silent (and absent from irc) lately, but now am
>> back:)
>>
>>
>
> Welcome back!
>
>
>> For source code formatting in Kdev 4, I've started a wiki page at:
>> http://kdevelop.org/mediawiki/index.php/Source_Code_Formatter
>> with some ideas I've had. Feel free to update, or comment here on
>> what is listed.
>>
>> Really open to any ideas and suggestions you have at the moment for
>> formatting.
>>
>> I can say that I'm keen to have uncrustify as well as astyle support. My
>> thought is
>> that if we (I) drop using the library interface of the formatter, and
>> use either that
>> the formatter supports command line switches, or a configuration file of
>> options,
>> then we can then more easily support having other code formatters.
>>
>> The alternative is to continue to support astyle as is, and add options
>> for uncrustify
>> and others.
>>
>>
>
> Perhaps the best way to go is to create an interface for the source code
> formatters that can be used so that we don't have to worry about how to call
> the code from the rest of kdevelop.
>
>
>> My reasoning for this is to (hopefully) be able to offer some support
>> for code formatters for
>> languages other than C/C++ and Java.
>>
>>
>
> Yes indeed, code formatters for other languages would be nice to have.
>
More information about the KDevelop-devel
mailing list