imagine you have a complicated (>60 components) page and different users
with different authorizations.
and you want to hide certain fields/information/possibilites for
interaction from users with lower authorizations.
instead of changing your template by adding Ifs you could just set the
visibility. if the requirements change
(User A may change field1, User B may no change field1, but can see it,
User C doesn't know anything about
field 1,...) you'd only have to set the visibility :)
... just my thoughts :)
kris
"Mike Snare"
<[EMAIL PROTECTED]
com> An
"Tapestry users"
24.03.2006 12:38 <[email protected]>
Kopie
Bitte antworten Thema
an Re: Why IComponent does not
"Tapestry users" provide a setVisiable(boolean
<[EMAIL PROTECTED] visiable) method?
karta.apache.org>
What does 'hidden' mean? If I'm writing a non-visual component (like
a scroll state tracker or an auto refresher) my component is already
hidden. Or do you mean disabled, which is different. For many
components, being hidden may make no sense at all.
You ought to be able to do whatever you are trying to do by wrapping
your component in an if.
-Mike
On 3/24/06, linuja <[EMAIL PROTECTED]> wrote:
> Why IComponent does not provide a setVisiable(boolean visiable) method?
>
> So it can be hidden component easier.
>
> tks.
>
>
---------------------------------------------------------------------
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]
