Awesome indeed! @Minas: how hard is to integrate this in WicketForge (IDEA users) ? :-)
On Wed, Feb 1, 2012 at 3:21 AM, Jenny Brown <jennybro...@gmail.com> wrote: > Working on someone else's complex wicket pages can result in a lot of time > spent hunting for components in the source. What if you could click on an > item in the web page and jump straight to the line of Java source that > created it? > > The net.ftlines.wicket-source module, plus a couple of plugins, lets you do > just that. There are three parts - a module for your WicketApplication, a > Firefox plugin, and an Eclipse plugin. > > 1. Wicket module records where in the source code each component is > constructed and saves it in an HTML attribute. > 2. Firebug extension displays the html attribute in Firebug's sidebar and > lets you click to open it in Eclipse. (Chrome extension pending.) > 3. Eclipse plugin listens for clicks from Firefox and opens the file to > that line of the Java source. > > These three pieces together close the circle from wicket components and > html rendering, to the browser, and back to the wicket component source, > speeding work on existing but unfamiliar pages, and making minor wording > tweaks quick and easy. > > For more information and installation, check out > https://www.42lines.net/2012/01/31/announcing-wicket-source/ > > Release 1.5.0_06 is available in maven central. 1.5.0.7-SNAPSHOT contains > a bug fix for ajax components. > > > Jenny Brown -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
