for me there are two cool aspects to wicket-bench: 1) refactor support - if you rename a class that extends Component it will find any matching .html and .properties file and rename those also
2) editor - wicketbench replaces java editor with a tabbed editor that lets you quickly switch between java/html/properties files when you open a class that extends Component. very handy. however, it does have its problems. eclipse' java editor is not built with embedding in mind, so once you start using (2) you will miss out on such useful things as "mark occurences", double clicking the left border to set a breakpoint ( right clicking still works ), ctrl clicking into a class wont always work, etc. i think the idea is awesome, too bad eclipse makes it so hard to implement :( -igor On Fri, May 2, 2008 at 12:15 PM, Frank Silbermann <[EMAIL PROTECTED]> wrote: > > When I was developing in Wicket 1.2 I used Jbuilder 2006; it was what > the employer provided. Other developers, however, use Eclipse for their > (non-Wicket) projects, and Jbuilder 2007/8 are Eclipse-based, so I > figured might might as well start my Wicket 1.3 experiments using > Eclipse. > > What are the pros and (if any) cons of using the Wicket Bench plug-in? > Is it worth setting up if all I'm really going to be doing is (perhaps) > to upgrade a Wicket 1.2 application to Wicket 1.3? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
