There was an really fine request from Marc Strapetz last week about grouping fields and methods. Each group could have an comment (header) and an arbitrary set of options (e.g. private/protected/public, static/non-static, ...).
I'm sure, this could solve those problems very elegant. Tom At 09:27 18.03.02 +0000, you wrote: >More generally, the ability to sort fields and methods by access and >modifier would be really usefull. I'd love to have the ability to tell >IDEA to sort my fields and methods, first by access: public --> protected >--> package --> private, and alphabetically within each access level. Even >better would be the ability to specify the sort order priority (eg. sort by >name, then by access, then by modifier, OR sort by modifier then by name >then by access level etc). > >-Darren > >PS +1 > > > > >Thomas Singer <[EMAIL PROTECTED]>@intellij.com on 16/03/2002 07:09:24 > >To: [EMAIL PROTECTED] >cc: >bcc: >From: [EMAIL PROTECTED], 16 March 2002, 7:09 a.m. >Contact: > >Re: [Eap-features] Request: Placement of generated fields > > >+1 > >At 10:27 16.03.2002 +1100, you wrote: > >+1! > > > >At 06:46 AM 16/03/2002, you wrote: > >>Using the Introduce Field refactoring, when I generate a private final > >>static field, I would like for it to be organized with other private >final > >>static fields directly underneath the class declaration and before my > >>instance variables. > >> > >>b > > >_______________________________________________ >Eap-features mailing list >[EMAIL PROTECTED] >http://www.intellij.com/mailman/listinfo/eap-features > > > > >_______________________________________________ >Eap-features mailing list >[EMAIL PROTECTED] >http://www.intellij.com/mailman/listinfo/eap-features _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-features
