Re: What Coding Conventions Should We Follow Now? What should the IDE default to?

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

Re: What Coding Conventions Should We Follow Now? What should the IDE default to?

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 : > > > On Mar 16, 2018,

Re: What Coding Conventions Should We Follow Now? What should the IDE default to?

> On Mar 16, 2018, at 6:46 AM, Emilian Bold 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

Re: What Coding Conventions Should We Follow Now? What should the IDE default to?

Oooo ... nice. Thank you, Emilian -- Johnny Muczynski 734-262-2045 On Fri, Mar 16, 2018 at 7:21 AM Emilian Bold wrote: > > A format-on-save setting would be helpful. > > Tools -> Options -> Editor -> On Save > > ​--emi​ > > ‐‐‐ Original Message ‐‐‐ > > On

Re: What Coding Conventions Should We Follow Now? What should the IDE default to?

> A format-on-save setting would be helpful. Tools -> Options -> Editor -> On Save ​--emi​ ‐‐‐ Original Message ‐‐‐ On 16 March 2018 1:02 PM, John Muczynski wrote: > The product I'm working on at work is using NetBeans as the coding standard.  > > Last year, I

Re: What Coding Conventions Should We Follow Now? What should the IDE default to?

The product I'm working on at work is using NetBeans as the coding standard. Last year, I was able to apply the formatter on all the files in the project, and then commit. That helped make diffs readable. A format-on-save setting would be helpful. On Mar 16, 2018 6:47 AM, "Emilian Bold"

Re: What Coding Conventions Should We Follow Now? What should the IDE default to?

> 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

Re: What Coding Conventions Should We Follow Now? What should the IDE default to?

Here is my user comment. My colleagues at OracleLabs integrated Eclipse formatter into our continuous build. As far as I know it is the only formatter that works in headless mode and is sort of standardized and a bit stable. As it is annoying to always reformat from command line, I integrated

Re: What Coding Conventions Should We Follow Now? What should the IDE default to?

The coding conventions NetBeans follows and provides are "as-is". People that what to customize it have some options to toggle or could use 3rd party plugins. Particularly since there is no global Java standard I don't believe we should be looking for extra work for nothing. For reference, the

What Coding Conventions Should We Follow Now? What should the IDE default to?

I noticed that Oracle has not maintained a convention for the Java language like other groups have for their ecosystems. This also has not materialized from OpenJDK: http://www.oracle.com/technetwork/java/codeconvtoc-136057.html