On Fri, May 2, 2008 at 10:05 PM, Igor Vaynberg [EMAIL PROTECTED]
wrote:
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
the problem is i dont know eclipse internals that well. i think if
johan, or anyone else was interested in spending time on it all he
would have to do to check this out is to create a new eclipse plugin
from the tabbed editor plugin wizard and then try to embed the java
editor as one of the panes.
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
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
