You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by abangkis <ab...@gmail.com> on 2015/04/03 04:24:23 UTC
Re: Refreshing tapestry grid content from another component.
Hi Thiago, thanks for the reply. Yes, after a few try I finally just wrap
the whole grid component in a zone.
I tried
triggering resources.triggerEvent(InternalConstants.GRID_INPLACE_UPDATE,
null, null); from onUpEvent, that trigger from an event link inside the
grid. But that didn't seem to work :)
On Tue, Mar 31, 2015 at 1:58 AM, Thiago H de Paula Figueiredo <
thiagohp@gmail.com> wrote:
> On Sun, 22 Mar 2015 06:36:49 -0300, abangkis <ab...@gmail.com> wrote:
>
> Now I'm wondering if there's any way to trigger this behavior from
>> another component.
>>
>
> Have you thought about wrapping it in a Zone?
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
http://www.mreunionlabs.net/ <http://www.mreunion-labs.net/>
twitter : @mreunionlabs @abangkis
page : https://plus.google.com/104168782385184990771
Re: Refreshing tapestry grid content from another component.
Posted by abangkis <ab...@gmail.com>.
Hi Lance, thanks for the explanation :)
On Tue, Apr 7, 2015 at 2:47 PM, Lance Java <la...@googlemail.com>
wrote:
> > I tried triggering
> resources.triggerEvent(InternalConstants.GRID_INPLACE_UPDATE,null, null);
> from onUpEvent, that trigger from an event link inside the grid. But that
> didn't seem to work
>
> This is a common misconception. Your eventlink "inside" the grid is not a
> child of the grid so the event won't bubble up to the grid. GridRows and
> GridColumns are children of the grid component, blocks defined in your page
> are not. This can be counterintuitive sometimes because the eventlink is a
> child in the clientside dom/html but not in the serverside component model.
>
--
http://www.mreunionlabs.net/ <http://www.mreunion-labs.net/>
twitter : @mreunionlabs @abangkis
page : https://plus.google.com/104168782385184990771
Re: Refreshing tapestry grid content from another component.
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
Spot-on explanation, Lance. We could try to find some client-side
JavaScript event that triggers that, but I'm in the middle of a work fire
here . . . :(
On Tue, 07 Apr 2015 04:47:50 -0300, Lance Java <la...@googlemail.com>
wrote:
>> I tried triggering
> resources.triggerEvent(InternalConstants.GRID_INPLACE_UPDATE,null, null);
> from onUpEvent, that trigger from an event link inside the grid. But that
> didn't seem to work
>
> This is a common misconception. Your eventlink "inside" the grid is not a
> child of the grid so the event won't bubble up to the grid. GridRows and
> GridColumns are children of the grid component, blocks defined in your
> page
> are not. This can be counterintuitive sometimes because the eventlink is
> a
> child in the clientside dom/html but not in the serverside component
> model.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Refreshing tapestry grid content from another component.
Posted by Lance Java <la...@googlemail.com>.
> I tried triggering
resources.triggerEvent(InternalConstants.GRID_INPLACE_UPDATE,null, null);
from onUpEvent, that trigger from an event link inside the grid. But that
didn't seem to work
This is a common misconception. Your eventlink "inside" the grid is not a
child of the grid so the event won't bubble up to the grid. GridRows and
GridColumns are children of the grid component, blocks defined in your page
are not. This can be counterintuitive sometimes because the eventlink is a
child in the clientside dom/html but not in the serverside component model.