Title: RE: [Eap-list] Defining Javadoc templates for getters and setters

Another suggestion for handling javadocs:
There's some beautifier (jindent I think) which will automatically generate javadocs for methods and fields which don't already have them.  I think it set certain javadoc fields like author, exception, param, etc.  It might also generate some simple text just describe the type and roughly where it's used.  This is pretty darn useful, and might be a good alternative to template-based alt-insert (though that obviously has some other benefits).

Anyway, in the post-Pandora version you might consider adding generated javadocs to the Code menu functions.

> -----Original Message-----
> From: Timothy Dean [mailto:[EMAIL PROTECTED]]
> Sent: 02 November 2001 15:42
> To: [EMAIL PROTECTED]
> Subject: [Eap-list] Defining Javadoc templates for getters and setters
>
>
> I just discovered the wonderful "encapsulate fields"
> refactoring... What a
> great way to automatically create getters and setters for my field
> definitions! I love this product more and more every time I
> figure out how to
> use a new refactoring!!
>
> One suggestion I would make for future enhancements: When I
> use this feature
> to generate getters and/or setters, it would be nice if I could have a
> Javadoc template that is used to generate my Javadoc for my
> new setters and
> getters.. Something like the class templates you already have
> under Tools/IDE
> Options/Class Templates would be wonderful!
>
> Thanks for the fabulous product - I used to be a Jbuilder
> zealot but I have
> been converted!
>
> - Tim
>
> _______________________________________________
> Eap-list mailing list
> [EMAIL PROTECTED]
> http://www.intellij.com/mailman/listinfo/eap-list
>


The information contained in this e-mail including any attachments may constitute Corvis Corporation Proprietary Information that is subject to Non-Disclosure Agreement and cannot be disclosed to any other party without the express consent of Corporation.

If you are neither the intended recipient of this e-mail nor responsible for delivering this e-mail to the intended recipient, note that any dissemination, distribution, copying, or retention of this e-mail is prohibited.

If you believe you have received this e-mail in error, we request that you notify the sender by return e-mail and then delete this mailand any return e-mail immediately.

Reply via email to