[jrawio-dev] Re: Re: Re: Re: Re: Re: Re: Re: Re: API CHANGES: *.raw packages renamed to *.craw

[Endre Stølsvik <java@stolsvik.com>]

On Sun, Sep 6, 2009 at 00:49, Fabrizio Giudici <fabrizio.giudici@tidalwave.it> wrote:

Endre Stølsvik wrote:

And third. Your choice for code formatting is [sorry] - terrible! Yep, I would accept it, consistent rules for the project is a must, and good or bad, they are always better than not having it, but my IDE (Eclipse) refuses to format your way, independent of my tries to configure it. It is only one thing that causing problem - but adding spaces by hand after every insert of any brace - it's madness! Why not take rules that Sun recommends for Java code? They are quite common it the community and when they are 'not as I would like it', I was quickly used to them an they are not so bad! Usually the only exception is added to them - using either tabs or spaces for indentation, not both mixed as Sun suggests (this is really terrible suggestion)...

I know, my formatting style is particular. But I'm really acquainted to it and it allows me very fast scanning. I contribute to other projects, where the common style is used, and I have some troubles - I can't scan so fast.

Suggestion: Make an Eclipse formatting file for it (it's an xml file). If that is not possible, you could consider abandoning the worst peculiarities of your format to be able to wedge it into a format that both NetBeans and Eclipse can support?

It's on my task list. When I used Eclipse, I used Jalopy as the formatter and I had a configuration file for it. Does still exist Jalopy for Eclipse?

I have no idea - Eclipse has a built-in formatter that is pretty good and very configurable. The save-function can be tailored (by checkboxes!) to do format and auto-import (amongst other things), which is pretty neat. I wouldn't suggest using anything else than that, as that is what .. well .. AFAIK .. 100% of Eclipse-users use! ;-)

Endre.