Juan Gabriel Arias wrote:
> 
> The second one.
> Components should check some roles and enable or disable itself.
> 
> Thanks for the answers!
> Juan
> 
> On 10/2/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
>>
>> On 10/1/07, Kent Tong <[EMAIL PROTECTED]> wrote:
>> >
>> >
>> > Juan Gabriel Arias wrote:
>> > >
>> > > Im trying to dinamically show or hide html components, like links,
>> > > buttons,
>> > > etc.
>> > >
>>
>> What do you mean by 'dynamic'? Do you want to change authorization
>> info for the components dynamically, or do you mean dynamic in that
>> components should figure out what to do at runtime?
>>
>> Eelco
> 

See this thread for a description of how I do context (or data) sensitive
roles. 
http://www.nabble.com/Best-Practices-for-accessing-repainting-sibling-cousin-components--tf3841514.html#a10895313

Chuck

-- 
View this message in context: 
http://www.nabble.com/hide-show-components---role-based-tf4550513.html#a13005139
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to