No, because we have discussed the naming already quite a bit and the
api is already widely used (not only in apps, but also in libraries).
Martijn
On 7/19/07, Timo Rantalaiho <[EMAIL PROTECTED]> wrote:
> On Mon, 16 Jul 2007, Igor Vaynberg wrote:
> > try calling setoutputmarkupplaceholdertag(true)
On Mon, 16 Jul 2007, Igor Vaynberg wrote:
> try calling setoutputmarkupplaceholdertag(true) on all components you are
> planning to call setvisible(false) when you create them
By the way, would it be a good idea to rename that method to
something more descriptive such as enableAjaxUpdates()? I
thi
On 7/17/07, kenixwong <[EMAIL PROTECTED]> wrote:
>
>
> :( sorry , igor... everytime when i faced the problem, i sure will search
> from net. Just i not sure what u going to write as above matter...
first search result is this
http://www.nabble.com/Changing-visibility-via-ajax-tf1974532.html#a541
:( sorry , igor... everytime when i faced the problem, i sure will search
from net. Just i not sure what u going to write as above matter...
anyway, thanks for your fast reply and help...
igor.vaynberg wrote:
>
> On 7/17/07, kenixwong <[EMAIL PROTECTED]> wrote:
>>
>>
>> sorry,igor... i cant
On 7/17/07, kenixwong <[EMAIL PROTECTED]> wrote:
>
>
> sorry,igor... i cant get what u mean ... can u explain more? or show me
> some
> example? thanks
you gotta learn how to use the internets
http://www.nabble.com/forum/Search.jtp?forum=13974&local=y&query=visible+ajax+container
try the first
sorry,igor... i cant get what u mean ... can u explain more? or show me some
example? thanks
igor.vaynberg wrote:
>
> in that case you have to call setvisible, but add the parent of the
> component to the ajaxrequesttarget instead
>
> -igor
>
>
> On 7/16/07, kenixwong <[EMAIL PROTECTED]> w
Here's the pieces that I used. Sounds like Igor's approach is better,
but here it is if you can't do it that way.
in your css:
.invisible{
display: none;
}
.visible{
display: inline;
}
Now, the component side (proficiencyChoice is a dropdown)
proficiencyChoice.setOutputMark
in that case you have to call setvisible, but add the parent of the
component to the ajaxrequesttarget instead
-igor
On 7/16/07, kenixwong <[EMAIL PROTECTED]> wrote:
i m using wicket 1.2.4, setoutputmarkupplaceholdertag(true) is came from
wicket 1.3.0?
igor.vaynberg wrote:
>
> On 7/16/07,
I am a wicket newbie too:)..
can i know how u used CSS to control it ? can give any idea to me as well?
thanks ar
James Law wrote:
>
> I am a wicket newbie, but when I had a similar thing I wanted to do, I
> just used CSS to make the component invisible/visible (display: none).
> The ajax
i m using wicket 1.2.4, setoutputmarkupplaceholdertag(true) is came from
wicket 1.3.0?
thanks
igor.vaynberg wrote:
>
> On 7/16/07, kenixwong <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>> It work, but oaly the first time. Mean after i clicked on the radio few
>> times, it nothing happen.
>
>
> try
On 7/16/07, kenixwong <[EMAIL PROTECTED]> wrote:
It work, but oaly the first time. Mean after i clicked on the radio few
times, it nothing happen.
try calling setoutputmarkupplaceholdertag(true) on all components you are
planning to call setvisible(false) when you create them
-igor
than
I am a wicket newbie, but when I had a similar thing I wanted to do, I
just used CSS to make the component invisible/visible (display: none).
The ajax behavior just changed the style. I am pretty certain setVisible
is not the best/easiest way to handle this.
James
kenixwong wrote:
> I'd like t
12 matches
Mail list logo