Alex schrieb:
Hi,
we've been using wicket for about a month now, so far so good.
The only complain is about code lisibility, sometimes our constructors
are filled with a lot of code, particurally with all the :
add(new Link(myLink)
{
public void onClick(RequestCycle
Personally i use the Netbeans way of GUI code generation done in JFrame GUI builder
//constructor
public MyPage(){
printPageHeader();
createPageLinks();
createPagePanels();
createPageForms();
printPageFooters();
}infact i have made it a template in NB and i seem to enjoy this approach. even if
yeah, but how many times are your onclick handles that simple? usually they are more complex, they might have a few try/catch blocks, etc. this is just syntactic sugar.-Igor
On 4/3/06, Timo Stamm [EMAIL PROTECTED] wrote:
Alex schrieb: Hi, we've been using wicket for about a month now, so far so
Igor Vaynberg schrieb:
yeah, but how many times are your onclick handles that simple?
Quite often, actually. And if they are more complex, I would really like
to loose some of the superflous brackets and indentation which anonymous
classes add.
usually they
are more complex, they might
Hi,
we've been using wicket for about a month now, so far so good.
The only complain is about code lisibility, sometimes our constructors
are filled with a lot of code, particurally with all the :
add(new Link(myLink)
{
public void onClick(RequestCycle cycle)
{
imho, this is very soft. it doesnt stand up well to refactorings and only gives you runtime errors instead of compile time.a better solution, and what i often do is to forward to a method directly
ie:class MyPage extends WebPage { public MyPage() { add(new Link(mylink) { public void
I have been thinking about this for some time, but never got around to discussing it.Basically this is what makes the RoR lines of code metric so great. The only drawback I see is that you have a loose coupling between the method you want to instantiate: it is based on a string.
I do like the
Yeah, that could be a code saver. Personally I like just private
classes better. I use that when annonymous classes get too big/ messy.
The big advantage over not using introspection is that you can easily
track down how it is called from your IDE, you won't mess up with
refactoring and stepping
