Hi guys,
Hope there is room for some ideas in a few vesion's time...
1) Key shortcut which collapses a method's code block into only one visible
line and back again, to save space on screen.
2) Like the 'Go to Declaration'; Holding (eg) Ctrl down and placing the
mouse over a keyword opens a list of other possible keywords for use in that
location. A keyboard shortcut could also provide the same function without
the mouse.
3) Option (probably only from a menu) to have displayed all the inheritted
attributes of the class being viewed. eg: Everything 'my.package.A'
inherits from 'my.package.B' is displayed, but they are not editable without
going to 'B's class. (This could have a display option somewhere so that
all attributes inheritted from 'java.lang.*' and above (for example) are not
displayed.)
Obviously, inheritted fields are simply displayed 'as is', methods could be
initially collapsed, but expandable, and anything which has been overridden
could be labelled as such (eg; completely coloured red) or simply not
displayed (set by a tick-box in the options panel).
Display options for where the inheritted attributes are could be:
- grouped in their class/interfaces at the start/end of the file
listing
- alongside their overriding attributes (eg: overrider for equals(
Object ) would be beneath/above inheritted version) (any which are not
overridden could simply follow the last overridden attribute or (if none) be
placed at the end of the listing).
- not display the overridden attributes, but highlight overriding
fields/methods in a different colour, with a key combination or mouse
operation to display (perhaps in window's style floating box) the overridden
field/method.
4) It would also be really nice (excuse me if you have heard this before) to
be able to see a class diagram for classes from selected packages - options
could be controlled from the same display options panel which controls (3).
5) Perhaps a spelling checker for JavaDoc commments which ignores words not
in the dictionary but which do appear as class/field/keyword names.
6) An option for the programmer to enter default elements for their
class/method/field javadoc blocks for auto-generated code.
eg: We have a tendancy to use CVS tags, as well as our own style tags; it
would be useful to have them put in automatically when a new class is
generated, even if they are not standard.
7) As an aside: Maybe being able to repeat a simple operation would be
useful. eg: If a quick key-combo produces a drop-down to change 'private'
to 'public'/'protected'/etc for methods/classes/etc., it would be good for
the IDE to offer the same change throughout the current file. ie: After
changing one method's 'private' to 'public' it would perform the same
operation on all methods beginning with 'private'.
Hope this isn't all old news,
My congratulations on a great product - can't wait for the latest full
release!
Matt.
Matthew Webster
ext: 4740
mob: +44 7931 22 64 64
http://www.eudoxus.freeuk.com/
Disclaimer
This communication together with any attachments transmitted with it ('this E-mail')
is intended only for the use of the addressee and may contain information which is
privileged and confidential. If the reader of this E-mail is not the intended
recipient or the employee or agent responsible for delivering it to the intended
recipient you are notified that any use of this E-mail is prohibited. Addressees
should check this E-mail for viruses. The Carphone Warehouse Group PLC makes no
representations as regards the absence of viruses in this E-mail. If you have received
this E-mail in error please notify our ISe Response Team immediately by telephone on +
44 (0)20 8896 5828 or via E-mail at [EMAIL PROTECTED] Please then immediately
destroy this E-mail and any copies of it.
Please feel free to visit our website: http://www.phonehouse.com
_______________________________________________
Eap-features mailing list
[EMAIL PROTECTED]
http://www.intellij.com/mailman/listinfo/eap-features
