You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Chris Mylonas <ch...@opencsta.org> on 2014/08/27 03:08:43 UTC
Grid pager no activation context stored on sorting fields
Hi Tapestry Noobs of the future!
...that come across this problem,use onPassivate to keep your app working
nicely.
I had the pleasure of using my software in a field trial (nothing exciting,
equipment tracking in a data centre) and made a few adjustments to quicken
my task though the night although forgot about onPassivate.
So where I dev'd for 15 hours for a functional field test, I gave myself a
usability conundrum for a few hours in the weeeee-small hours by not being
able to sort within a context. (The irony is I was too proud to hook up
the Internet to save wifi on my laptop - data centre is full of both
internet and power!) - So the last half a dozen cables I couldn't
trace....well there's room for another field trial!
void onActivate(Long id) { store it here....use to get your data in
setupRender() };
Long onPassivate() { return your-passed-in-parameter-usually-Long };
Happy deving!
Chris
Re: Grid pager no activation context stored on sorting fields
Posted by Geoff Callender <ge...@gmail.com>.
That example doesn't have any sorting or stuff going on within a context. Perhaps you meant the "Filter CRUD" example? The first URL is plain, whereas the second one has remembered the mode, the chosen person, and the value of the filter:
T5.4:
http://jumpstart.doublenegative.com.au/jumpstart7/together/filtercrud/persons
http://jumpstart.doublenegative.com.au/jumpstart7/together/filtercrud/persons/UPDATE/4?partialName=s
T5.3:
http://jumpstart.doublenegative.com.au/jumpstart/together/filtercrud/persons
http://jumpstart.doublenegative.com.au/jumpstart/together/filtercrud/persons/UPDATE/3?partialName=s
However, I would thoroughly recommend breaking the whole thing up into components. It's no harder to do, and you get the benefit that it's sooooo easy to rearrange the components in response to changes of UI design.
T5.4:
http://jumpstart.doublenegative.com.au/jumpstart7/together/smallercomponentscrud/persons
http://jumpstart.doublenegative.com.au/jumpstart7/together/smallercomponentscrud/persons/UPDATE/4?partialName=s
But, have I missed the point of your question?
Geoff
On 27 Aug 2014, at 11:42 pm, Chris Mylonas <ch...@opencsta.org> wrote:
> Out of curiosity, does using your "total control" jumpstart example [1] get
> around it?
> For instance, trying to implement this admin theme [2] (which is bootstrap)
> would be a problem - let's just stay away from that for the moment. that
> is commercial template btw, i'm not associated with fwiw.
>
>
> [1]
> http://jumpstart.doublenegative.com.au/jumpstart/together/totalcontrolcrud/persons
> [2] http://demo.ztapps.com/curo/v1/invoice.html
>
>
> On Wed, Aug 27, 2014 at 11:30 AM, Geoff Callender <
> geoff.callender.jumpstart@gmail.com> wrote:
>
>> It's worth noting that if your grid is in a component then activation
>> context might not be suitable. A solution is on the way:
>>
>> https://issues.apache.org/jira/browse/TAP5-2297
>>
>> Cheers,
>>
>> Geoff
>>
>> On 27 Aug 2014, at 11:08 am, Chris Mylonas <ch...@opencsta.org> wrote:
>>
>>> Hi Tapestry Noobs of the future!
>>>
>>> ...that come across this problem,use onPassivate to keep your app working
>>> nicely.
>>>
>>> I had the pleasure of using my software in a field trial (nothing
>> exciting,
>>> equipment tracking in a data centre) and made a few adjustments to
>> quicken
>>> my task though the night although forgot about onPassivate.
>>>
>>> So where I dev'd for 15 hours for a functional field test, I gave myself
>> a
>>> usability conundrum for a few hours in the weeeee-small hours by not
>> being
>>> able to sort within a context. (The irony is I was too proud to hook up
>>> the Internet to save wifi on my laptop - data centre is full of both
>>> internet and power!) - So the last half a dozen cables I couldn't
>>> trace....well there's room for another field trial!
>>>
>>>
>>> void onActivate(Long id) { store it here....use to get your data in
>>> setupRender() };
>>> Long onPassivate() { return your-passed-in-parameter-usually-Long };
>>>
>>>
>>> Happy deving!
>>> Chris
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Grid pager no activation context stored on sorting fields
Posted by Chris Mylonas <ch...@opencsta.org>.
Out of curiosity, does using your "total control" jumpstart example [1] get
around it?
For instance, trying to implement this admin theme [2] (which is bootstrap)
would be a problem - let's just stay away from that for the moment. that
is commercial template btw, i'm not associated with fwiw.
[1]
http://jumpstart.doublenegative.com.au/jumpstart/together/totalcontrolcrud/persons
[2] http://demo.ztapps.com/curo/v1/invoice.html
On Wed, Aug 27, 2014 at 11:30 AM, Geoff Callender <
geoff.callender.jumpstart@gmail.com> wrote:
> It's worth noting that if your grid is in a component then activation
> context might not be suitable. A solution is on the way:
>
> https://issues.apache.org/jira/browse/TAP5-2297
>
> Cheers,
>
> Geoff
>
> On 27 Aug 2014, at 11:08 am, Chris Mylonas <ch...@opencsta.org> wrote:
>
> > Hi Tapestry Noobs of the future!
> >
> > ...that come across this problem,use onPassivate to keep your app working
> > nicely.
> >
> > I had the pleasure of using my software in a field trial (nothing
> exciting,
> > equipment tracking in a data centre) and made a few adjustments to
> quicken
> > my task though the night although forgot about onPassivate.
> >
> > So where I dev'd for 15 hours for a functional field test, I gave myself
> a
> > usability conundrum for a few hours in the weeeee-small hours by not
> being
> > able to sort within a context. (The irony is I was too proud to hook up
> > the Internet to save wifi on my laptop - data centre is full of both
> > internet and power!) - So the last half a dozen cables I couldn't
> > trace....well there's room for another field trial!
> >
> >
> > void onActivate(Long id) { store it here....use to get your data in
> > setupRender() };
> > Long onPassivate() { return your-passed-in-parameter-usually-Long };
> >
> >
> > Happy deving!
> > Chris
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: Grid pager no activation context stored on sorting fields
Posted by Geoff Callender <ge...@gmail.com>.
It's worth noting that if your grid is in a component then activation context might not be suitable. A solution is on the way:
https://issues.apache.org/jira/browse/TAP5-2297
Cheers,
Geoff
On 27 Aug 2014, at 11:08 am, Chris Mylonas <ch...@opencsta.org> wrote:
> Hi Tapestry Noobs of the future!
>
> ...that come across this problem,use onPassivate to keep your app working
> nicely.
>
> I had the pleasure of using my software in a field trial (nothing exciting,
> equipment tracking in a data centre) and made a few adjustments to quicken
> my task though the night although forgot about onPassivate.
>
> So where I dev'd for 15 hours for a functional field test, I gave myself a
> usability conundrum for a few hours in the weeeee-small hours by not being
> able to sort within a context. (The irony is I was too proud to hook up
> the Internet to save wifi on my laptop - data centre is full of both
> internet and power!) - So the last half a dozen cables I couldn't
> trace....well there's room for another field trial!
>
>
> void onActivate(Long id) { store it here....use to get your data in
> setupRender() };
> Long onPassivate() { return your-passed-in-parameter-usually-Long };
>
>
> Happy deving!
> Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org