why not just attach the wicket source to your ide? for me all i have to do
is ctrl+click on a component class and i am taken to its source code.
-igor
On 2/19/07, Aaron Hiniker <[EMAIL PROTECTED]> wrote:
I am always running into problems where I need to replace a components
functionality somehow, which requires me to know the parent's component
hierarchy. I then need to go to the wicket SVN or look at my local copy
of the source code to view the component's source.
Do you guys think it would be helpful to modify the javadoc output for
all wicket components which adds a link to view the component's markup
from within the javadocs?
I've never really hacked the javadoc generation before, but I'm fairly
sure there might be hooks available to customize the output to
accomplish this.
Aaron
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
