Re: [T5] Combine a form and response in same template/Java class
Thanks for your response. These conventions are good to know. I thought I
was being silly by keeping them separate.
Howard Lewis Ship wrote:
>
> Then you really have two pages, not one. Bundle up your query data
> into a single object that can be passed from Query page to Result
> page.
>
> On Sun, Nov 2, 2008 at 4:01 PM, thermus <[EMAIL PROTECTED]> wrote:
>>
>> #2.
>>
>>
>>
>> Sven Homburg wrote:
>>>
>>> thermus,
>>>
>>> please clarify what you want to do:
>>>
>>>
>>>1. display a query dialog to the user, user choose some value and
>>> submit
>>>the form,
>>>after submit, display grid and query form ?
>>>2. display a query dialog to the user, user choose some value and
>>> submit
>>>the form,
>>>after submit, display only grid and NOT query form ?
>>>
>>>
>>> 2008/11/2 thermus <[EMAIL PROTECTED]>
>>>
>>>>
>>>> Thanks, but what do I condition on? How can I differentiate if the
>>>> user
>>>> is
>>>> requesting the original form "page" or is flipping through the pages of
>>>> a
>>>> grid component?
>>>>
>>>>
>>>>
>>>> SergeEby wrote:
>>>> >
>>>> > Hi,
>>>> >
>>>> > You can use a block. Search for examples in the mailing list.
>>>> >
>>>> > /Serge
>>>> >
>>>> >
>>>> > thermus wrote:
>>>> >>
>>>> >> I currently have a very simple webapp. I have a form and return a
>>>> >> pageable grid component based on the form parameters. Right now, I
>>>> have
>>>> >> the form and response as separate tml/Java classes. Everything
>>>> works
>>>> >> fine, but it's getting to be a pain to keep all of these pieces in
>>>> order
>>>> >> (2 templates and 2 Java classes per query x 10 queries).
>>>> >>
>>>> >> I'd like to combine the form with response so I only have to
>>>> maintain
>>>> one
>>>> >> tml and one Java class per query. What is the logic I need in my
>>>> >> class/template to do this?
>>>> >>
>>>> >> So far, my attempts have been unsuccessful. I tried to add a
>>>> Persist
>>>> >> boolean and set it to true in the onSuccess method and included an
>>>> >> if-else in the template to render the appropriate piece. If I just
>>>> used
>>>> >> @Persist, I couldn't get back to the form to ever load again once it
>>>> was
>>>> >> submitted the first time. If I used @Persist("flash"), I could
>>>> reload
>>>> >> the form on demand, but now the grid pager links would take me back
>>>> to
>>>> >> the form (since the boolean would reset to false).
>>>> >>
>>>> >> Does anyone else combine their forms and response pages? Is this a
>>>> bad
>>>> >> practice? It just seems silly to have to keep track of 4 entities
>>>> for
>>>> a
>>>> >> simple form/response. Boy do I miss Perl.
>>>> >>
>>>> >
>>>> >
>>>>
>>>> --
>>>> View this message in context:
>>>> http://www.nabble.com/-T5--Combine-a-form-and-response-in-same-template-Java-class-tp20287170p20293925.html
>>>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>>>>
>>>>
>>>> -
>>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>>
>>>>
>>>
>>>
>>> --
>>> with regards
>>> Sven Homburg
>>> http://www.chenillekit.org
>>> http://tapestry5-components.googlecode.com
>>>
>>>
>>> -
>>> best regards
>>> Sven
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/-T5--Combine-a-form-and-response-in-same-template-Java-class-tp20287170p20294861.html
>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/-T5--Combine-a-form-and-response-in-same-template-Java-class-tp20287170p20296541.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [T5] Combine a form and response in same template/Java class
Then you really have two pages, not one. Bundle up your query data
into a single object that can be passed from Query page to Result
page.
On Sun, Nov 2, 2008 at 4:01 PM, thermus <[EMAIL PROTECTED]> wrote:
>
> #2.
>
>
>
> Sven Homburg wrote:
>>
>> thermus,
>>
>> please clarify what you want to do:
>>
>>
>>1. display a query dialog to the user, user choose some value and
>> submit
>>the form,
>>after submit, display grid and query form ?
>>2. display a query dialog to the user, user choose some value and
>> submit
>>the form,
>>after submit, display only grid and NOT query form ?
>>
>>
>> 2008/11/2 thermus <[EMAIL PROTECTED]>
>>
>>>
>>> Thanks, but what do I condition on? How can I differentiate if the user
>>> is
>>> requesting the original form "page" or is flipping through the pages of a
>>> grid component?
>>>
>>>
>>>
>>> SergeEby wrote:
>>> >
>>> > Hi,
>>> >
>>> > You can use a block. Search for examples in the mailing list.
>>> >
>>> > /Serge
>>> >
>>> >
>>> > thermus wrote:
>>> >>
>>> >> I currently have a very simple webapp. I have a form and return a
>>> >> pageable grid component based on the form parameters. Right now, I
>>> have
>>> >> the form and response as separate tml/Java classes. Everything works
>>> >> fine, but it's getting to be a pain to keep all of these pieces in
>>> order
>>> >> (2 templates and 2 Java classes per query x 10 queries).
>>> >>
>>> >> I'd like to combine the form with response so I only have to maintain
>>> one
>>> >> tml and one Java class per query. What is the logic I need in my
>>> >> class/template to do this?
>>> >>
>>> >> So far, my attempts have been unsuccessful. I tried to add a Persist
>>> >> boolean and set it to true in the onSuccess method and included an
>>> >> if-else in the template to render the appropriate piece. If I just
>>> used
>>> >> @Persist, I couldn't get back to the form to ever load again once it
>>> was
>>> >> submitted the first time. If I used @Persist("flash"), I could reload
>>> >> the form on demand, but now the grid pager links would take me back to
>>> >> the form (since the boolean would reset to false).
>>> >>
>>> >> Does anyone else combine their forms and response pages? Is this a
>>> bad
>>> >> practice? It just seems silly to have to keep track of 4 entities for
>>> a
>>> >> simple form/response. Boy do I miss Perl.
>>> >>
>>> >
>>> >
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/-T5--Combine-a-form-and-response-in-same-template-Java-class-tp20287170p20293925.html
>>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>>
>> --
>> with regards
>> Sven Homburg
>> http://www.chenillekit.org
>> http://tapestry5-components.googlecode.com
>>
>>
>> -
>> best regards
>> Sven
>>
>
> --
> View this message in context:
> http://www.nabble.com/-T5--Combine-a-form-and-response-in-same-template-Java-class-tp20287170p20294861.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [T5] Combine a form and response in same template/Java class
#2.
Sven Homburg wrote:
>
> thermus,
>
> please clarify what you want to do:
>
>
>1. display a query dialog to the user, user choose some value and
> submit
>the form,
>after submit, display grid and query form ?
>2. display a query dialog to the user, user choose some value and
> submit
>the form,
>after submit, display only grid and NOT query form ?
>
>
> 2008/11/2 thermus <[EMAIL PROTECTED]>
>
>>
>> Thanks, but what do I condition on? How can I differentiate if the user
>> is
>> requesting the original form "page" or is flipping through the pages of a
>> grid component?
>>
>>
>>
>> SergeEby wrote:
>> >
>> > Hi,
>> >
>> > You can use a block. Search for examples in the mailing list.
>> >
>> > /Serge
>> >
>> >
>> > thermus wrote:
>> >>
>> >> I currently have a very simple webapp. I have a form and return a
>> >> pageable grid component based on the form parameters. Right now, I
>> have
>> >> the form and response as separate tml/Java classes. Everything works
>> >> fine, but it's getting to be a pain to keep all of these pieces in
>> order
>> >> (2 templates and 2 Java classes per query x 10 queries).
>> >>
>> >> I'd like to combine the form with response so I only have to maintain
>> one
>> >> tml and one Java class per query. What is the logic I need in my
>> >> class/template to do this?
>> >>
>> >> So far, my attempts have been unsuccessful. I tried to add a Persist
>> >> boolean and set it to true in the onSuccess method and included an
>> >> if-else in the template to render the appropriate piece. If I just
>> used
>> >> @Persist, I couldn't get back to the form to ever load again once it
>> was
>> >> submitted the first time. If I used @Persist("flash"), I could reload
>> >> the form on demand, but now the grid pager links would take me back to
>> >> the form (since the boolean would reset to false).
>> >>
>> >> Does anyone else combine their forms and response pages? Is this a
>> bad
>> >> practice? It just seems silly to have to keep track of 4 entities for
>> a
>> >> simple form/response. Boy do I miss Perl.
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/-T5--Combine-a-form-and-response-in-same-template-Java-class-tp20287170p20293925.html
>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> with regards
> Sven Homburg
> http://www.chenillekit.org
> http://tapestry5-components.googlecode.com
>
>
> -
> best regards
> Sven
>
--
View this message in context:
http://www.nabble.com/-T5--Combine-a-form-and-response-in-same-template-Java-class-tp20287170p20294861.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [T5] Combine a form and response in same template/Java class
thermus,
please clarify what you want to do:
1. display a query dialog to the user, user choose some value and submit
the form,
after submit, display grid and query form ?
2. display a query dialog to the user, user choose some value and submit
the form,
after submit, display only grid and NOT query form ?
2008/11/2 thermus <[EMAIL PROTECTED]>
>
> Thanks, but what do I condition on? How can I differentiate if the user is
> requesting the original form "page" or is flipping through the pages of a
> grid component?
>
>
>
> SergeEby wrote:
> >
> > Hi,
> >
> > You can use a block. Search for examples in the mailing list.
> >
> > /Serge
> >
> >
> > thermus wrote:
> >>
> >> I currently have a very simple webapp. I have a form and return a
> >> pageable grid component based on the form parameters. Right now, I have
> >> the form and response as separate tml/Java classes. Everything works
> >> fine, but it's getting to be a pain to keep all of these pieces in order
> >> (2 templates and 2 Java classes per query x 10 queries).
> >>
> >> I'd like to combine the form with response so I only have to maintain
> one
> >> tml and one Java class per query. What is the logic I need in my
> >> class/template to do this?
> >>
> >> So far, my attempts have been unsuccessful. I tried to add a Persist
> >> boolean and set it to true in the onSuccess method and included an
> >> if-else in the template to render the appropriate piece. If I just used
> >> @Persist, I couldn't get back to the form to ever load again once it was
> >> submitted the first time. If I used @Persist("flash"), I could reload
> >> the form on demand, but now the grid pager links would take me back to
> >> the form (since the boolean would reset to false).
> >>
> >> Does anyone else combine their forms and response pages? Is this a bad
> >> practice? It just seems silly to have to keep track of 4 entities for a
> >> simple form/response. Boy do I miss Perl.
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/-T5--Combine-a-form-and-response-in-same-template-Java-class-tp20287170p20293925.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
with regards
Sven Homburg
http://www.chenillekit.org
http://tapestry5-components.googlecode.com
Re: [T5] Combine a form and response in same template/Java class
Thanks, but what do I condition on? How can I differentiate if the user is
requesting the original form "page" or is flipping through the pages of a
grid component?
SergeEby wrote:
>
> Hi,
>
> You can use a block. Search for examples in the mailing list.
>
> /Serge
>
>
> thermus wrote:
>>
>> I currently have a very simple webapp. I have a form and return a
>> pageable grid component based on the form parameters. Right now, I have
>> the form and response as separate tml/Java classes. Everything works
>> fine, but it's getting to be a pain to keep all of these pieces in order
>> (2 templates and 2 Java classes per query x 10 queries).
>>
>> I'd like to combine the form with response so I only have to maintain one
>> tml and one Java class per query. What is the logic I need in my
>> class/template to do this?
>>
>> So far, my attempts have been unsuccessful. I tried to add a Persist
>> boolean and set it to true in the onSuccess method and included an
>> if-else in the template to render the appropriate piece. If I just used
>> @Persist, I couldn't get back to the form to ever load again once it was
>> submitted the first time. If I used @Persist("flash"), I could reload
>> the form on demand, but now the grid pager links would take me back to
>> the form (since the boolean would reset to false).
>>
>> Does anyone else combine their forms and response pages? Is this a bad
>> practice? It just seems silly to have to keep track of 4 entities for a
>> simple form/response. Boy do I miss Perl.
>>
>
>
--
View this message in context:
http://www.nabble.com/-T5--Combine-a-form-and-response-in-same-template-Java-class-tp20287170p20293925.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [T5] Combine a form and response in same template/Java class
Hi,
You can use a block. Search for examples in the mailing list.
/Serge
thermus wrote:
>
> I currently have a very simple webapp. I have a form and return a
> pageable grid component based on the form parameters. Right now, I have
> the form and response as separate tml/Java classes. Everything works
> fine, but it's getting to be a pain to keep all of these pieces in order
> (2 templates and 2 Java classes per query x 10 queries).
>
> I'd like to combine the form with response so I only have to maintain one
> tml and one Java class per query. What is the logic I need in my
> class/template to do this?
>
> So far, my attempts have been unsuccessful. I tried to add a Persist
> boolean and set it to true in the onSuccess method and included an if-else
> in the template to render the appropriate piece. If I just used @Persist,
> I couldn't get back to the form to ever load again once it was submitted
> the first time. If I used @Persist("flash"), I could reload the form on
> demand, but now the grid pager links would take me back to the form (since
> the boolean would reset to false).
>
> Does anyone else combine their forms and response pages? Is this a bad
> practice? It just seems silly to have to keep track of 4 entities for a
> simple form/response. Boy do I miss Perl.
>
--
View this message in context:
http://www.nabble.com/-T5--Combine-a-form-and-response-in-same-template-Java-class-tp20287170p20293486.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Combine a form and response in same template/Java class
I currently have a very simple webapp. I have a form and return a pageable
grid component based on the form parameters. Right now, I have the form and
response as separate tml/Java classes. Everything works fine, but it's
getting to be a pain to keep all of these pieces in order (2 templates and 2
Java classes per query x 10 queries).
I'd like to combine the form with response so I only have to maintain one
tml and one Java class per query. What is the logic I need in my
class/template to do this?
So far, my attempts have been unsuccessful. I tried to add a Persist
boolean and set it to true in the onSuccess method and included an if-else
in the template to render the appropriate piece. If I just used @Persist, I
couldn't get back to the form to ever load again once it was submitted the
first time. If I used @Persist("flash"), I could reload the form on demand,
but now the grid pager links would take me back to the form (since the
boolean would reset to false).
Does anyone else combine their forms and response pages? Is this a bad
practice? It just seems silly to have to keep track of 4 entities for a
simple form/response. Boy do I miss Perl.
--
View this message in context:
http://www.nabble.com/Combine-a-form-and-response-in-same-template-Java-class-tp20287170p20287170.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
