Not sure what you mean exactly. If I write some custom code that uses the @BXML annotation, the generated Javadocs would include the @BXML annotation if the access level allowed for that field to be documented at all. If all of my @BXML annotated fields are private I can still use the '-private' option to show those uses if I wish.
I'm not saying that it would help to enhance the Pivot API Javadocs in any way. Just that it would be there for Pivot consumers when they generate Javadocs for their own code that uses @BXML. On 8 August 2011 20:48, Greg Brown <gk_br...@verizon.net> wrote: >> I agree, but I suppose it might still be useful to see what custom >> code uses the BXML annotation and therefore would require signing to >> run in an applet. > > How would you see it though, if the field isn't documented? > >
