|
From: Rogan D. (JIRA) <no...@at...> - 2007-05-02 16:41:50
|
Allow VLDockingApplicationPageFactory to reuse pages
----------------------------------------------------
Key: RCP-473
URL: http://opensource.atlassian.com/projects/spring/browse/RCP-473
Project: Spring Framework Rich Client Project
Issue Type: New Feature
Components: Helper Classes
Affects Versions: 0.3.0
Environment: Any
Reporter: Rogan Dawes
One way of implementing User controllable perspectives is to make each perspective an ApplicationPage instance, and simply change between them as required. One downside of this approach is that the current VLDockingApplicationPageFactory simply recreates the pages on every switch, discarding any state that the child PageComponents may have had.
The attached patch provides an option to allow pages to be cached and reused, thus preserving the state in those pages.
Question:
It seems that ApplicationPage.close() is not called when a new page is opened. Is this something that is wrong in my own code, or is this something that the framework should be doing for me?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/spring/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Rogan D. (JIRA) <no...@at...> - 2007-05-02 16:43:54
|
[ http://opensource.atlassian.com/projects/spring/browse/RCP-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rogan Dawes updated RCP-473:
----------------------------
Attachment: vldocking_page_reuse.patch
> Allow VLDockingApplicationPageFactory to reuse pages
> ----------------------------------------------------
>
> Key: RCP-473
> URL: http://opensource.atlassian.com/projects/spring/browse/RCP-473
> Project: Spring Framework Rich Client Project
> Issue Type: New Feature
> Components: Helper Classes
> Affects Versions: 0.3.0
> Environment: Any
> Reporter: Rogan Dawes
> Attachments: vldocking_page_reuse.patch
>
>
> One way of implementing User controllable perspectives is to make each perspective an ApplicationPage instance, and simply change between them as required. One downside of this approach is that the current VLDockingApplicationPageFactory simply recreates the pages on every switch, discarding any state that the child PageComponents may have had.
> The attached patch provides an option to allow pages to be cached and reused, thus preserving the state in those pages.
> Question:
> It seems that ApplicationPage.close() is not called when a new page is opened. Is this something that is wrong in my own code, or is this something that the framework should be doing for me?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/spring/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Geoffrey De S. (JIRA) <no...@at...> - 2007-05-12 12:46:31
|
[ http://opensource.atlassian.com/projects/spring/browse/RCP-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_23672 ]
Geoffrey De Smet commented on RCP-473:
--------------------------------------
Blocks RCP-469
> Allow VLDockingApplicationPageFactory to reuse pages
> ----------------------------------------------------
>
> Key: RCP-473
> URL: http://opensource.atlassian.com/projects/spring/browse/RCP-473
> Project: Spring Framework Rich Client Project
> Issue Type: New Feature
> Components: Helper Classes
> Affects Versions: 0.3.0
> Environment: Any
> Reporter: Rogan Dawes
> Assignee: Peter De Bruycker
> Attachments: vldocking_page_reuse.patch
>
>
> One way of implementing User controllable perspectives is to make each perspective an ApplicationPage instance, and simply change between them as required. One downside of this approach is that the current VLDockingApplicationPageFactory simply recreates the pages on every switch, discarding any state that the child PageComponents may have had.
> The attached patch provides an option to allow pages to be cached and reused, thus preserving the state in those pages.
> Question:
> It seems that ApplicationPage.close() is not called when a new page is opened. Is this something that is wrong in my own code, or is this something that the framework should be doing for me?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/spring/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Peter De B. (JIRA) <no...@sp...> - 2008-01-29 10:58:44
|
[ http://jira.springframework.org/browse/RCP-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter De Bruycker resolved RCP-473.
-----------------------------------
Resolution: Fixed
patch applied
> Allow VLDockingApplicationPageFactory to reuse pages
> ----------------------------------------------------
>
> Key: RCP-473
> URL: http://jira.springframework.org/browse/RCP-473
> Project: Spring Framework Rich Client Project
> Issue Type: New Feature
> Components: Helper Classes
> Affects Versions: 1.0.0
> Environment: Any
> Reporter: Rogan Dawes
> Assignee: Peter De Bruycker
> Attachments: vldocking_page_reuse.patch
>
>
> One way of implementing User controllable perspectives is to make each perspective an ApplicationPage instance, and simply change between them as required. One downside of this approach is that the current VLDockingApplicationPageFactory simply recreates the pages on every switch, discarding any state that the child PageComponents may have had.
> The attached patch provides an option to allow pages to be cached and reused, thus preserving the state in those pages.
> Question:
> It seems that ApplicationPage.close() is not called when a new page is opened. Is this something that is wrong in my own code, or is this something that the framework should be doing for me?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|