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.
>
>
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
#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
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 o
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:
>>
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. Ever
