Menu
▾
▴
springframework-rcp-dev
|
From: Joerg B. (JIRA) <no...@at...> - 2006-10-25 11:06:44
|
support for multiple/switchable ApplicationPage's
-------------------------------------------------
Key: RCP-432
URL: http://opensource.atlassian.com/projects/spring/browse/RCP-432
Project: Spring Framework Rich Client Project
Type: New Feature
Components: Application Framework
Versions: 1.0.0, 0.3.0
Reporter: Joerg Buchberger
- complex rich clients have different types of users, with different aim and needs, i.e. their collection of use cases differ
- complex rich clients also have power users that need to perform very different sets of tasks, that comprise different sets of use cases / scenarios
How can this needs be fulfilled within one rich client?
You need the ability to preconfigure/customize a whole set of ApplicationPage's, where each can be tailored to a different set of use cases ...
i.e. depending on the feature/subsystem the user needs to use, a suitable ApplicationPage can then be presented/chosen!
--
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: Arne L. (JIRA) <no...@at...> - 2006-11-02 23:23:41
|
[ http://opensource.atlassian.com/projects/spring/browse/RCP-432?page=comments#action_20614 ] Arne Limburg commented on RCP-432: ---------------------------------- The ApplicationPageFactory could do this for you. You may implement an ApplicationPageFactory that gets the properties you need to decide which page to create and can set the properties via the application-context. > support for multiple/switchable ApplicationPage's > ------------------------------------------------- > > Key: RCP-432 > URL: http://opensource.atlassian.com/projects/spring/browse/RCP-432 > Project: Spring Framework Rich Client Project > Type: New Feature > Components: Application Framework > Versions: 1.0.0, 0.3.0 > Reporter: Joerg Buchberger > > - complex rich clients have different types of users, with different aim and needs, i.e. their collection of use cases differ > - complex rich clients also have power users that need to perform very different sets of tasks, that comprise different sets of use cases / scenarios > How can this needs be fulfilled within one rich client? > You need the ability to preconfigure/customize a whole set of ApplicationPage's, where each can be tailored to a different set of use cases ... > i.e. depending on the feature/subsystem the user needs to use, a suitable ApplicationPage can then be presented/chosen! -- 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: Joerg B. (JIRA) <no...@at...> - 2006-11-03 08:13:47
|
[ http://opensource.atlassian.com/projects/spring/browse/RCP-432?page=comments#action_20617 ] Joerg Buchberger commented on RCP-432: -------------------------------------- Arne, thanks a lot for this hint. In this case, this issue perhaps should be better changed to type "improvement" and renamed to "documentation for multiple..." All related documentation I could find to date http://www.nabble.com/Spring-Rich-and-FlexDock-tf2297779.html http://spring-rich-c.sourceforge.net/apidocs/org/springframework/richclient/application/flexdock/FlexDockApplicationPageFactory.html > support for multiple/switchable ApplicationPage's > ------------------------------------------------- > > Key: RCP-432 > URL: http://opensource.atlassian.com/projects/spring/browse/RCP-432 > Project: Spring Framework Rich Client Project > Type: New Feature > Components: Application Framework > Versions: 1.0.0, 0.3.0 > Reporter: Joerg Buchberger > > - complex rich clients have different types of users, with different aim and needs, i.e. their collection of use cases differ > - complex rich clients also have power users that need to perform very different sets of tasks, that comprise different sets of use cases / scenarios > How can this needs be fulfilled within one rich client? > You need the ability to preconfigure/customize a whole set of ApplicationPage's, where each can be tailored to a different set of use cases ... > i.e. depending on the feature/subsystem the user needs to use, a suitable ApplicationPage can then be presented/chosen! -- 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: Lieven D. (JIRA) <no...@sp...> - 2008-10-09 20:05:22
|
[ http://jira.springframework.org/browse/RCP-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lieven Doclo updated RCP-432:
-----------------------------
Priority: Minor (was: Major)
Fix Version/s: 1.x
Issue Type: Improvement (was: New Feature)
> support for multiple/switchable ApplicationPage's
> -------------------------------------------------
>
> Key: RCP-432
> URL: http://jira.springframework.org/browse/RCP-432
> Project: Spring Framework Rich Client Project
> Issue Type: Improvement
> Components: Application Framework
> Affects Versions: 1.0.0, 1.x
> Reporter: Joerg Buchberger
> Priority: Minor
> Fix For: 1.x
>
>
> - complex rich clients have different types of users, with different aim and needs, i.e. their collection of use cases differ
> - complex rich clients also have power users that need to perform very different sets of tasks, that comprise different sets of use cases / scenarios
> How can this needs be fulfilled within one rich client?
> You need the ability to preconfigure/customize a whole set of ApplicationPage's, where each can be tailored to a different set of use cases ...
> i.e. depending on the feature/subsystem the user needs to use, a suitable ApplicationPage can then be presented/chosen!
--
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
|
Thanks for helping keep SourceForge clean.
X