You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Borut Bolcina (JIRA)" <ji...@apache.org> on 2010/12/20 11:25:01 UTC
[jira] Created: (TAP5-1381) Page lifecycle documentation: What is
called and when
Page lifecycle documentation: What is called and when
-----------------------------------------------------
Key: TAP5-1381
URL: https://issues.apache.org/jira/browse/TAP5-1381
Project: Tapestry 5
Issue Type: Improvement
Components: documentation
Reporter: Borut Bolcina
At http://tapestry.apache.org/page-life-cycle.html the documentation about page lifecycle can be improved. It should be more clear to developers what is called and when. Maybe a diagram and short explanations along with good practices what to put in each event method would be in order.
Geoff has made a good effort at http://jumpstart.doublenegative.com.au/jumpstart/examples/navigation/whatiscalledandwhen and the logging of log4j.category.tapestry.events.com.acme.pages=debug can give clues, but I think the lifecycle is so crucial it should be explained in more detail.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-1381) Page lifecycle documentation: What is
called and when
Posted by "Bob Harner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980714#action_12980714 ]
Bob Harner commented on TAP5-1381:
----------------------------------
I fixed the broken links in the http://tapestry.apache.org/page-life-cycle.html page, but this page still needs to be improved, especially where it goes into great length about page pooling, which needs to be updated since 5.2.
> Page lifecycle documentation: What is called and when
> -----------------------------------------------------
>
> Key: TAP5-1381
> URL: https://issues.apache.org/jira/browse/TAP5-1381
> Project: Tapestry 5
> Issue Type: Improvement
> Components: documentation
> Reporter: Borut Bolcina
>
> At http://tapestry.apache.org/page-life-cycle.html the documentation about page lifecycle can be improved. It should be more clear to developers what is called and when. Maybe a diagram and short explanations along with good practices what to put in each event method would be in order.
> Geoff has made a good effort at http://jumpstart.doublenegative.com.au/jumpstart/examples/navigation/whatiscalledandwhen and the logging of log4j.category.tapestry.events.com.acme.pages=debug can give clues, but I think the lifecycle is so crucial it should be explained in more detail.
> Also, the link in the sentence "As with component rendering, you have the ability to make your components "aware" of these events by identifying methods to be invoked." is broken.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-1381) Page lifecycle documentation: What is
called and when
Posted by "Borut Bolcina (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Borut Bolcina updated TAP5-1381:
--------------------------------
Description:
At http://tapestry.apache.org/page-life-cycle.html the documentation about page lifecycle can be improved. It should be more clear to developers what is called and when. Maybe a diagram and short explanations along with good practices what to put in each event method would be in order.
Geoff has made a good effort at http://jumpstart.doublenegative.com.au/jumpstart/examples/navigation/whatiscalledandwhen and the logging of log4j.category.tapestry.events.com.acme.pages=debug can give clues, but I think the lifecycle is so crucial it should be explained in more detail.
Also, the link in the sentence "As with component rendering, you have the ability to make your components "aware" of these events by identifying methods to be invoked." is broken.
was:
At http://tapestry.apache.org/page-life-cycle.html the documentation about page lifecycle can be improved. It should be more clear to developers what is called and when. Maybe a diagram and short explanations along with good practices what to put in each event method would be in order.
Geoff has made a good effort at http://jumpstart.doublenegative.com.au/jumpstart/examples/navigation/whatiscalledandwhen and the logging of log4j.category.tapestry.events.com.acme.pages=debug can give clues, but I think the lifecycle is so crucial it should be explained in more detail.
> Page lifecycle documentation: What is called and when
> -----------------------------------------------------
>
> Key: TAP5-1381
> URL: https://issues.apache.org/jira/browse/TAP5-1381
> Project: Tapestry 5
> Issue Type: Improvement
> Components: documentation
> Reporter: Borut Bolcina
>
> At http://tapestry.apache.org/page-life-cycle.html the documentation about page lifecycle can be improved. It should be more clear to developers what is called and when. Maybe a diagram and short explanations along with good practices what to put in each event method would be in order.
> Geoff has made a good effort at http://jumpstart.doublenegative.com.au/jumpstart/examples/navigation/whatiscalledandwhen and the logging of log4j.category.tapestry.events.com.acme.pages=debug can give clues, but I think the lifecycle is so crucial it should be explained in more detail.
> Also, the link in the sentence "As with component rendering, you have the ability to make your components "aware" of these events by identifying methods to be invoked." is broken.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-1381) Page lifecycle documentation: What is
called and when
Posted by "Borut Bolcina (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Borut Bolcina updated TAP5-1381:
--------------------------------
Description:
At http://tapestry.apache.org/page-life-cycle.html the documentation about page lifecycle can be improved. It should be more clear to developers what is called and when. Maybe a diagram and short explanations along with good practices what to put in each event method would be in order.
Geoff has made a good effort at http://jumpstart.doublenegative.com.au/jumpstart/examples/navigation/whatiscalledandwhen and the logging of log4j.category.tapestry.events.com.acme.pages=debug can give clues, but I think the lifecycle is so crucial it should be explained in more detail.
Also, the link in the sentence "As with component rendering, you have the ability to make your components "aware" of these events by identifying methods to be invoked." is broken.
was:
At http://tapestry.apache.org/page-life-cycle.html the documentation about page lifecycle can be improved. It should be more clear to developers what is called and when. Maybe a diagram and short explanations along with good practices what to put in each event method would be in order.
Geoff has made a good effort at http://jumpstart.doublenegative.com.au/jumpstart/examples/navigation/whatiscalledandwhen and the logging of log4j.category.tapestry.events.com.acme.pages=debug can give clues, but I think the lifecycle is so crucial it should be explained in more detail.
> Page lifecycle documentation: What is called and when
> -----------------------------------------------------
>
> Key: TAP5-1381
> URL: https://issues.apache.org/jira/browse/TAP5-1381
> Project: Tapestry 5
> Issue Type: Improvement
> Components: documentation
> Reporter: Borut Bolcina
>
> At http://tapestry.apache.org/page-life-cycle.html the documentation about page lifecycle can be improved. It should be more clear to developers what is called and when. Maybe a diagram and short explanations along with good practices what to put in each event method would be in order.
> Geoff has made a good effort at http://jumpstart.doublenegative.com.au/jumpstart/examples/navigation/whatiscalledandwhen and the logging of log4j.category.tapestry.events.com.acme.pages=debug can give clues, but I think the lifecycle is so crucial it should be explained in more detail.
> Also, the link in the sentence "As with component rendering, you have the ability to make your components "aware" of these events by identifying methods to be invoked." is broken.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-1381) Page lifecycle documentation: What is
called and when
Posted by "Bob Harner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980714#action_12980714 ]
Bob Harner commented on TAP5-1381:
----------------------------------
I fixed the broken links in the http://tapestry.apache.org/page-life-cycle.html page, but this page still needs to be improved, especially where it goes into great length about page pooling, which needs to be updated since 5.2.
> Page lifecycle documentation: What is called and when
> -----------------------------------------------------
>
> Key: TAP5-1381
> URL: https://issues.apache.org/jira/browse/TAP5-1381
> Project: Tapestry 5
> Issue Type: Improvement
> Components: documentation
> Reporter: Borut Bolcina
>
> At http://tapestry.apache.org/page-life-cycle.html the documentation about page lifecycle can be improved. It should be more clear to developers what is called and when. Maybe a diagram and short explanations along with good practices what to put in each event method would be in order.
> Geoff has made a good effort at http://jumpstart.doublenegative.com.au/jumpstart/examples/navigation/whatiscalledandwhen and the logging of log4j.category.tapestry.events.com.acme.pages=debug can give clues, but I think the lifecycle is so crucial it should be explained in more detail.
> Also, the link in the sentence "As with component rendering, you have the ability to make your components "aware" of these events by identifying methods to be invoked." is broken.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.