Very nice, thanks.
igor.vaynberg wrote:
>
> setResponsePage(new PreviewPage(name, dob));
> or most likely
> setResponsePage(new PreviewPage(formbean));
>
> or even better
>
> setResponsePage(new PreviewPage(PersonalDetails.this, formbean));
>
> then you can have
>
> class PreviewPage { PreviewPage(Page back, Bean bean) { add(new
> Link("edit")
> { onclick() {setresponsepage(back);}}}
>
> makes sense?
>
> -igor
>
>
> On 5/6/07, howzat <[EMAIL PROTECTED]> wrote:
>>
>>
>> I have recently come across Wicket.
>> I think it is exactly what was missing in the java presentation layer
>> space.
>> I look forward to getting proficient enough to start realising some
>> project
>> ideas we have. Thanks for giving us such a good option.
>>
>> I am using 1.2.6.
>> I have a page (PersonalDetails) with a form for the user to enter some
>> information - let's say his name and his date of birth (dob).
>> I use setResponsePage(PersonalDetailsPreview.class) in the form's
>> onSubmit()
>> method to give the user a chance to preview his input before he submits
>> it
>> to be persisted.
>> Probably naively, I have created both PersonalDetailsPreview.class &
>> PersonalDetailsPreview.html as simple copies of the respective
>> PersonalDetails files and made some minor changes to reflect the
>> read-only
>> nature of the preview page.
>> My questions are:
>> What are the options in Wicket for making the data (name & dob) from the
>> PersonalDetails available to the PersonalDetailsPreview?
>> Did I need to make PersonalDetailsPreview.class &
>> PersonalDetailsPreview.html for such a scenario (ie carrying identical
>> data
>> from one screen to the next)?
>>
>> I have not been able to find any documentation about this (and also
>> wicket
>> "page-navigation"). I tried to find some sample code on the example page
>> but
>> the old page (1.25/6? examples) seems to be unavailable now and the 1.3
>> examples' "source code" link doesn't seem to bring up the java code (just
>> html & properties files) in the pop-up.
>>
>> PS what I am trying to do may or may not be a nice feature for the user,
>> but
>> the question is really about the technical possibilities/best-practices
>> for
>> the solutions in Wicket in such cases (sharing data between pages), not
>> really about how good the user-experience is.
>>
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/sharing-model-data-tf3700094.html#a10346854
>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by DB2 Express
>> Download DB2 Express C - the FREE version of DB2 express and take
>> control of your XML. No limits. Just data. Click to get it now.
>> http://sourceforge.net/powerbar/db2/
>> _______________________________________________
>> Wicket-user mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/wicket-user
>>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Wicket-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>
>
--
View this message in context:
http://www.nabble.com/Re%3A-sharing-model-data-tf3700971.html#a10443234
Sent from the Wicket - User mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
