This has been stated previously ( I believe ), but we should move to make javadoc error highlighting, separably configurable from code error highlighting. I would prefer to use a color other than red, and possibly disable some of it.
Mike On 17 Feb 2002 at 16:25, Denis Krizanovic wrote: > > I've been thinking about the new javadoc features for a couple of weeks > now, and I've some suggestions. > > 1. I think highlighting javadoc errors in red is confusing. In my mind, > I've got red associated with "doesn't compile", so I often click on the > red bar to go to the non-compiling code only to find that it's a javadoc > error. I think the javadoc errors should be highlighted in blue or some > other non-critical colour. > > 2. It would be good to be able to do some analysis of the javadoc, at a > package level, so that you could fix all the problems in one hit. This > is especially useful for legacy code whose javadoc is -allways- out of > sync. > > 3. I notice that the javadoc error's never highlight things that aren't > there. It would be good if this could happen in some way. Because not > writing javadoc is a great way of not seeing any javadoc errors. : ) > > regards, > dk- > > _______________________________________________ > Eap-list mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-list > --- [EMAIL PROTECTED] To obtain my PGP public key, mail "SEND PUB KEY" in the subject to "[EMAIL PROTECTED]" _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
