Buhahaha.
I disagree (I believe that "smart" tabs is far superior to space-based
indentation), but I don't care enough to debate it on this mailing list.
We all know this point has been beaten to death for decades now.
On a side-note, in my experience checkstyle is a net loss on most
projects. The cost/benefit of using it relatively high, with users
having to suppress rules (usually due to bugs in checkstyle itself)
quite often. Javascript frameworks (e.g. ESLint) are way ahead of Java
on this point (I guess they have to be due to lack of strong typing).
Gili
On 2018-04-26 11:02 AM, Victor Williams Stafusa da Silva wrote:
Whatever is the convention adopted, I only implore one thing: Do not allow
tabs be the default setting!
By the way, a better integration with checkstyle would be welcome.
Victor Williams Stafusa da Silva
2018-04-26 11:32 GMT-03:00 Wade Chandler <[email protected]>:
On Mar 16, 2018, at 6:46 AM, Emilian Bold <[email protected]>
wrote:
Rather than discussing the actual conventions, make sure the IDE can
read and apply settings from Eclipse easily and exactly.
Not sure what this means. Just make sure plugins are able to format the
code?
Still, NetBeans does provide formatting and coding hints. Both should
follow /something/ and I assume Wade was wondering what standard to follow.
Exactly, and too, what makes the most sense.
My angle is that NetBeans, just like Eclipse, *is* a de-facto standard.
I don’t necessarily agree this makes the most sense, but I understand your
point. I guess for me this comes up as a source of friction when working on
projects. Intellij is by far the most used with Eclipse next, and then us.
I think either choosing some agnostic, and well written standard, or using
a real de-facto, sort of like how Spring became one over JEE, being used
more, makes for less friction.
Perhaps the answer is to provide NBs historical one as it is our code
base, and use that one with our project (NetBeans itself). Then provide
some others which are largely popular such as IntelliJ, Eclipse, Google,
and “Old Sun Java” for users of the IDE to use out of the box. It doesn’t
seem likely teams are going to go, oh, yeah, the few NB IDE users
formatting options win out over everybody else, and too, other projects are
not likely to provide a format which is easy to just import without some
upfront setup on behalf of the NB users. Too, most places in my experience
don’t come up with their own formatting. They generally pick one which
exists and is published. Us providing common ones makes that even easier
for IDE users.
Thanks for the replies and feedback all. I think I’ll look at this area
soon to see what can be done.
Wade
=======================
Wade Chandler
e: [email protected]
t: @wadechandler
https://www.linkedin.com/in/wade-chandler
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
