> it will also break all existing implementations of the interface out there.
Well, the effort will nicely blend in with the chores of refactoring
to the changes in generics... :) Or should it be made an abstract
class?
Another possibility would be to just enable suitable hooks in the
rendering phase of xxChoices. I.e., a method "String
getOptionAttributes(T t)" or similar would be called during the render
phase of a DropDownChoice.
It would then be easier for anybody to 'sugarcoat' their DropDown and
it would not break the existing inplementations. There I could just
check if (renderer instanceof MyChoiceRenderer) { ... and sugarcoat my
option ... }
**
Martin
>
> On Sat, Aug 9, 2008 at 10:21 PM, Martin Makundi
> <[EMAIL PROTECTED]> wrote:
>> It would be pretty easy to just add a getDispayStyle method into the
>> IChoiceRenderer interface and refactor the various classes using it to
>> support it accordingly. Don't you think?
>>
>> **
>> Martin
>>
>> 2008/8/10 Igor Vaynberg <[EMAIL PROTECTED]>:
>>> so write a component that works the way you want.
>>>
>>> as core devs we have to maintain a hard balance between simplicity and
>>> flexibility. the more pluggable/customizable you make something, the
>>> more complicated it becomes.
>>>
>>> we do not make core components ultra pluggable because they serve as a
>>> basis and examples for users who want to see how they work and want to
>>> implement something similar. what we do concentrate on a lot is making
>>> writing your own components easy.
>>>
>>> if you look at the dropdownchoice class hiearchy you might find a base
>>> class that is a good starting point and will get you 80% of where you
>>> want to go. the other 20% are up to you.
>>>
>>> -igor
>>>
>>> On Sat, Aug 9, 2008 at 10:06 PM, Martin Makundi
>>> <[EMAIL PROTECTED]> wrote:
>>>>> Take a look http://jweekend.com/dev/ArticlesPage/ here , at the "Wicket
>>>>> Select And SelectOption" presentation (roughly about half way through).
>>>>
>>>> Yes, but with Select And SelectOption you loose the benefits of
>>>> dropdownchoice (automatic notnull and localization, for example).
>>>>
>>>> **
>>>> Martin
>>>>
>>>>>
>>>>> Regards - Cemal
>>>>> http://www.jWeekend.co.uk http://jWeekend.co.uk
>>>>>
>>>>>
>>>>> fulltoos wrote:
>>>>>>
>>>>>> hi
>>>>>> I want to have a dropdown choice in which some of the choices are of
>>>>>> different color based on the model.
>>>>>> is there any existing implementation which i can use.
>>>>>> OR how should i go about it
>>>>>> please suggset.
>>>>>>
>>>>>> full toos
>>>>>> ======
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://www.nabble.com/color-code-options-in-drop-down-choice-tp16964792p18909328.html
>>>>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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]
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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]
>>
>>
>
> ---------------------------------------------------------------------
> 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]
