This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
The auto-generated code from formeditor and auto-comment disregard the settings from options/editor-settings. An example is the text limit count (i.e 80 chars). the generated code often is longer than this limit count. printing with more than 80 chars per line is difficult... another nice feature would be the placement of the attribute definitions of form editor. many programmers (like me) place attribute definitions on top in the source (uml-like)
The text limit count is used only to display a vertical delimiter line, AFAIK. Only thing I know about is that form editor does not reflect indentation engine set in editor (or just several properties only). We should probably implement some additional formatter that would adjust generated code (e.g. wrap lines, replace FQN with imported short names - see issue 7781) to reflect all relevant settings. As for placement of the generated variables definitions, you mean it should be configurable?
Yes, I meant the configurability. But this would be an (nice) enhancement. First of all, the "Java Indentation Engine" settings and the "Java Editor" settings (like text limit count) from Options should be kept. For example, the "Auto-Comment" tool notice the text limit count setting but not the "Add leading star in comment" setting, and so the comment lines are longer than text limit count. If you try to print the source code, many lines are to long. Modules like Jalopy can't change the protected code areas.
Sorry, but this is not a defect. Why do you think it is, or what thing exactly?
I think it's a defect because the "Java Indentation Engine" settings and the "Java Editor" settings (like text limit count) from Options is disregared by the gui and/or the editor component. When an user select 80 as text limit count (or such Identation engine stuff), then it should be noticed by these components. I also mean protected blocks created by gui editor. Why there is the ability to change formating rules and other editor setting, if they are disregarded?
Code generated by tools within the IDE (e.g. Matisse) should conform to the editor settings for formatting, line lengths, variable names, etc. In our shop we run coding standards tools (e.g. Checkstyle) against our entire code base. That results in a significant number of coding standard violations in the reports generated by Maven. While it's possible to exclude sections of code from coding standards in Checkstyle, it's painful to say the least since it involves line numbers that change. Lines longer than 80 columns also cause problems when we have occasion to print source code files. Joshua Smith