You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Rich Feit (JIRA)" <be...@incubator.apache.org> on 2004/11/11 02:15:24 UTC
[jira] Created: (BEEHIVE-75) Page Flow Overview - additional reasons/motivations for using Page Flow
Page Flow Overview - additional reasons/motivations for using Page Flow
-----------------------------------------------------------------------
Key: BEEHIVE-75
URL: http://nagoya.apache.org/jira/browse/BEEHIVE-75
Project: Beehive
Type: Improvement
Components: Documentation
Versions: V1Alpha
Reporter: Rich Feit
Assigned to: Steve Hanson
The Page Flow Overview at http://incubator.apache.org/beehive/pageflow/pageflow_overview.html should at mention some of the main motivations for Page Flow:
1) centralization of Controller logic, state, and metadata
2) self-contained pieces of a web application
3) reusable flows (nested page flows)
I don't think it has to go into depth on #3, but it would be nice to have a diagram or blurb about this (some bit of what's at http://dev2dev.bea.com/products/wlworkshop81/articles/pg_flows.jsp , maybe).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (BEEHIVE-75) Page Flow Overview - additional reasons/motivations for using Page Flow
Posted by "Nathan Jantz (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-75?page=all ]
Nathan Jantz closed BEEHIVE-75:
-------------------------------
Assign To: Nathan Jantz (was: Rich Feit)
Verified in 1.0m1-rc2.
> Page Flow Overview - additional reasons/motivations for using Page Flow
> -----------------------------------------------------------------------
>
> Key: BEEHIVE-75
> URL: http://issues.apache.org/jira/browse/BEEHIVE-75
> Project: Beehive
> Type: Improvement
> Components: Documentation
> Versions: V1Alpha
> Reporter: Rich Feit
> Assignee: Nathan Jantz
> Fix For: V1Alpha
>
> The Page Flow Overview at http://incubator.apache.org/beehive/pageflow/pageflow_overview.html should at mention some of the main motivations for Page Flow:
> 1) centralization of Controller logic, state, and metadata
> 2) self-contained pieces of a web application
> 3) reusable flows (nested page flows)
> I don't think it has to go into depth on #3, but it would be nice to have a diagram or blurb about this (some bit of what's at http://dev2dev.bea.com/products/wlworkshop81/articles/pg_flows.jsp , maybe).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (BEEHIVE-75) Page Flow Overview - additional reasons/motivations for using Page Flow
Posted by "Steve Hanson (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-75?page=history ]
Steve Hanson resolved BEEHIVE-75:
---------------------------------
Assign To: Rich Feit (was: Steve Hanson)
Resolution: Fixed
Hey Rich, I added the follows text to the topic. Basically stole your prose from the dev2dev article.
"
Page Flows are Nestable
Page flow nesting gives you an even greater ability to break up your project into separate, self-contained bits of functionality. At its heart, it is a way of pushing aside the current page flow temporarily and transferring control to another (nested) page flow with the intention of coming back to the original (nesting) one.
So when would you use this? Nesting is useful when you want to do one of the following tasks:
* gather data from the user, for use in the current page flow
* allow the user to correct errors or supply additional information en route to executing a desired action
* show an alternate view of data represented in the current page flow
* show the user information that will be useful in the current page flow (e.g., help screens can be easily implemented as nested page flows)
"
> Page Flow Overview - additional reasons/motivations for using Page Flow
> -----------------------------------------------------------------------
>
> Key: BEEHIVE-75
> URL: http://issues.apache.org/jira/browse/BEEHIVE-75
> Project: Beehive
> Type: Improvement
> Components: Documentation
> Versions: V1Alpha
> Reporter: Rich Feit
> Assignee: Rich Feit
> Fix For: V1Alpha
>
> The Page Flow Overview at http://incubator.apache.org/beehive/pageflow/pageflow_overview.html should at mention some of the main motivations for Page Flow:
> 1) centralization of Controller logic, state, and metadata
> 2) self-contained pieces of a web application
> 3) reusable flows (nested page flows)
> I don't think it has to go into depth on #3, but it would be nice to have a diagram or blurb about this (some bit of what's at http://dev2dev.bea.com/products/wlworkshop81/articles/pg_flows.jsp , maybe).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Resolved: (BEEHIVE-75) Page Flow Overview - additional reasons/motivations for using Page Flow
Posted by "Steve Hanson (JIRA)" <be...@incubator.apache.org>.
[ http://nagoya.apache.org/jira/browse/BEEHIVE-75?page=history ]
Steve Hanson resolved BEEHIVE-75:
---------------------------------
Assign To: (was: Steve Hanson)
Resolution: Fixed
Fix Version: V1Alpha
Take a look at the "Page Flows are Modular" section in http://incubator.apache.org/beehive/pageflow/pageflow_overview.html
> Page Flow Overview - additional reasons/motivations for using Page Flow
> -----------------------------------------------------------------------
>
> Key: BEEHIVE-75
> URL: http://nagoya.apache.org/jira/browse/BEEHIVE-75
> Project: Beehive
> Type: Improvement
> Components: Documentation
> Versions: V1Alpha
> Reporter: Rich Feit
> Fix For: V1Alpha
>
> The Page Flow Overview at http://incubator.apache.org/beehive/pageflow/pageflow_overview.html should at mention some of the main motivations for Page Flow:
> 1) centralization of Controller logic, state, and metadata
> 2) self-contained pieces of a web application
> 3) reusable flows (nested page flows)
> I don't think it has to go into depth on #3, but it would be nice to have a diagram or blurb about this (some bit of what's at http://dev2dev.bea.com/products/wlworkshop81/articles/pg_flows.jsp , maybe).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Reopened: (BEEHIVE-75) Page Flow Overview - additional reasons/motivations for using Page Flow
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://nagoya.apache.org/jira/browse/BEEHIVE-75?page=history ]
Rich Feit reopened BEEHIVE-75:
------------------------------
Assign To: Steve Hanson
I really think #3 (nested page flows) is important, and should be mentioned at least briefly...
> Page Flow Overview - additional reasons/motivations for using Page Flow
> -----------------------------------------------------------------------
>
> Key: BEEHIVE-75
> URL: http://nagoya.apache.org/jira/browse/BEEHIVE-75
> Project: Beehive
> Type: Improvement
> Components: Documentation
> Versions: V1Alpha
> Reporter: Rich Feit
> Assignee: Steve Hanson
> Fix For: V1Alpha
>
> The Page Flow Overview at http://incubator.apache.org/beehive/pageflow/pageflow_overview.html should at mention some of the main motivations for Page Flow:
> 1) centralization of Controller logic, state, and metadata
> 2) self-contained pieces of a web application
> 3) reusable flows (nested page flows)
> I don't think it has to go into depth on #3, but it would be nice to have a diagram or blurb about this (some bit of what's at http://dev2dev.bea.com/products/wlworkshop81/articles/pg_flows.jsp , maybe).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira