ex);
>> }
>> }
>> }
>> NIFTY!! I hadn't written any IComponentResolver's before - but wanted to
>> try it. Wicket is AWESOME!! It makes it so easy to customize the
>> framework
>> to YOUR needs without imposing one person's ideas on another person.
>>
>
> --
> -Wicket f
COOL!!! :)
Jeremy Thomerson wrote:
You can do exactly what you asked in less than 40 lines of code - and not be
bound to the class name in the HTML (which you shouldn't do). Here's how:
IN YOUR APPLICATION CLASS:
@Override
protected void init() {
super.init();
register
t; > feedbackPanel, a feedbackpanel component is automatically added to that
> > page.
> > Another example is SubmitLink component. No special handling required,
> but
> > for wicket sake the developer must add it on the java the page.
> >
>
> --
> View this m
with id
> feedbackPanel, a feedbackpanel component is automatically added to that
> page.
> Another example is SubmitLink component. No special handling required, but
> for wicket sake the developer must add it on the java the page.
>
--
View this message in context:
http://www.nabbl
dd a markup with id
feedbackPanel, a feedbackpanel component is automatically added to
that
page.
Another example is SubmitLink component. No special handling required,
but
for wicket sake the developer must add it on the java the page.
--
View this message in contex
rstand that CoC means convention
>>>>>>> over
>>>>>>> configuration instead of the Dutch meaning "gay rights group".
>>>>>>>
>>>>
our own addon framework and publish it on 'stuff or
>>>>>> google code, but I won't be using it ever nor including it in core.
>>>>>>
>>>>>> The biggest plus point of wicket is that it doesn't perform magic. I
>>>>>&g
d the bigger part of the day wondering which
>>>>> incantation I did wrong.
>>>>>
>>>>> Martijn
>>>>> On 11/26/08, Ricardo Mayerhofer <[EMAIL PROTECTED]> wrote:
>>>>>>
>&
; On 11/26/08, Ricardo Mayerhofer <[EMAIL PROTECTED]> wrote:
>>>>>>
>>>>>> I started to use wicket some time ago, and I'm really enjoying it.
>>>>>> Best
>>>>>> framework ever.
>>>>>> But I've so
amework ever.
>>>>> But I've some suggestions.
>>>>> I think wicket could be better if it had less boiler plate code. This
>>>>> could
>>>>> be reduced by using CoC.
>>>>> Take the FeedBackPanel for example, you always
t.
>>>>> Best
>>>>> framework ever.
>>>>> But I've some suggestions.
>>>>> I think wicket could be better if it had less boiler plate code. This
>>>>> could
>>>>> be re
>> I think wicket could be better if it had less boiler plate code. This
>>>>> could
>>>>> be reduced by using CoC.
>>>>> Take the FeedBackPanel for example, you always have to add the
>>>>> component
>>>>> on
>>&g
Assunto: Re: Wicket and CoC
Perhaps the name could be userFeedBackPanel :)
"One Word per Concept" (Clean Code, Bob Martin, p. 26)
I'm just talking about code duplication, add( new SubmitLink( "submitLink" )
) and similars many times in a code doenst makes a programmer happ
this message in context:
>>>> http://www.nabble.com/Wicket-and-CoC-tp20706881p20706881.html
>>>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>>>
>>>>
>>>> --
gt;> Take the FeedBackPanel for example, you always have to add the component
>>> on
>>> the web page, even if no special handling is requires (which is almost
>>> the
>>> case).
>>> Wicket could have some reserved ids, so if I add a markup with id
>>
always have to add the component
> >> on
> >> the web page, even if no special handling is requires (which is almost
> >> the
> >> case).
> >> Wicket could have some reserved ids, so if I add a markup with id
> >> feedbackPanel, a feedbackpanel compon
he web page, even if no special handling is requires (which is almost
>> the
>> case).
>> Wicket could have some reserved ids, so if I add a markup with id
>> feedbackPanel, a feedbackpanel component is automatically added to that
>> page.
>> Another exam
is SubmitLink component. No special handling required,
>> but
>> for wicket sake the developer must add it on the java the page.
>>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands,
With IComponentResolver you can easily roll your own 'CoC' solution.
Sven
Ricardo Mayerhofer schrieb:
I started to use wicket some time ago, and I'm really enjoying it. Best
framework ever.
But I've some suggestions.
I think wicket could be better if it had less boiler plate code. This could
be
ket could have some reserved ids, so if I add a markup with id
> feedbackPanel, a feedbackpanel component is automatically added to that
> page.
> Another example is SubmitLink component. No special handling required, but
> for wicket sake the developer must add it on the java the page.
&g
d, but
for wicket sake the developer must add it on the java the page.
--
View this message in context:
http://www.nabble.com/Wicket-and-CoC-tp20706881p20706881.html
Sent from the Wicket - User mailing list archive at Nabble.com.
--
21 matches
Mail list logo