Community
Participate
Working Groups
Sort members treats all nested types the same, but interfaces and annotations are quite different from classes because they are essentially declarative. I tend to put all my annotations in one spot, and can't sort methods, etc. without mixing annotations and classes. So it would be nice to distinguish annotation, interface, and class kinds of Type in the sort order. A workaround is for me to create an enclosing class for the annotations that should be combined. Alternatively, you could permit the user to exclude kinds of members from the sort. re: UI, in the Members Sort Order preference dialog, below the "up" and "down" buttons would be "add" and "remove". The user could then remove "types" from member sorting. re: implementation, hints to where to investigate a patch appreciated.
I see what you mean. However, we have no plans here. Help is wanted.
Oh, now we did encourage you too much;-) See patch at bug 218542 for a start, if you want to provide a patch. The preference page is called MembersOrderPreferencePage. I would not allow to exclude elements form the sorting though.