You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Dan Adams (JIRA)" <de...@tapestry.apache.org> on 2007/06/29 22:38:04 UTC
[jira] Created: (TAPESTRY-1617) Change GridPager to Pager and make
it more general
Change GridPager to Pager and make it more general
--------------------------------------------------
Key: TAPESTRY-1617
URL: https://issues.apache.org/jira/browse/TAPESTRY-1617
Project: Tapestry
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.0.5
Reporter: Dan Adams
Fix For: 5.0.6
It would be great if GridPager were more generally usable. It has a dependence on GridDataSource for the number of rows that prevents it from being used in places like search result pages.
Another enhancement that could be added to this is to emit a "changepage" event when the page changes that has the page number as the context. This way pages could listen and respond specifically to when the page changes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-1617) Change GridPager to Pager and make
it more general
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-1617:
-------------------------------------------
Fix Version/s: (was: 5.0.6)
5.0.7
> Change GridPager to Pager and make it more general
> --------------------------------------------------
>
> Key: TAPESTRY-1617
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1617
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Dan Adams
> Fix For: 5.0.7
>
>
> It would be great if GridPager were more generally usable. It has a dependence on GridDataSource for the number of rows that prevents it from being used in places like search result pages.
> Another enhancement that could be added to this is to emit a "changepage" event when the page changes that has the page number as the context. This way pages could listen and respond specifically to when the page changes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-1617) Change GridPager to Pager and make
it more general
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-1617:
-------------------------------------------
Fix Version/s: 5.1
> Change GridPager to Pager and make it more general
> --------------------------------------------------
>
> Key: TAPESTRY-1617
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1617
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Dan Adams
> Fix For: 5.1
>
>
> It would be great if GridPager were more generally usable. It has a dependence on GridDataSource for the number of rows that prevents it from being used in places like search result pages.
> Another enhancement that could be added to this is to emit a "changepage" event when the page changes that has the page number as the context. This way pages could listen and respond specifically to when the page changes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Closed: (TAPESTRY-1617) Change GridPager to Pager and make
it more general
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-1617.
------------------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 5.1)
Assignee: Howard M. Lewis Ship
To support Ajax in-place updates, I had to make more changes to GridPager to make it even more closely tied to the Grid. Perhaps we can revisit this idea later, splitting functionality off into a base class.
> Change GridPager to Pager and make it more general
> --------------------------------------------------
>
> Key: TAPESTRY-1617
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1617
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Dan Adams
> Assignee: Howard M. Lewis Ship
>
> It would be great if GridPager were more generally usable. It has a dependence on GridDataSource for the number of rows that prevents it from being used in places like search result pages.
> Another enhancement that could be added to this is to emit a "changepage" event when the page changes that has the page number as the context. This way pages could listen and respond specifically to when the page changes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-1617) Change GridPager to Pager and make
it more general
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-1617:
-------------------------------------------
Fix Version/s: (was: 5.0.7)
5.0.8
> Change GridPager to Pager and make it more general
> --------------------------------------------------
>
> Key: TAPESTRY-1617
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1617
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Dan Adams
> Fix For: 5.0.8
>
>
> It would be great if GridPager were more generally usable. It has a dependence on GridDataSource for the number of rows that prevents it from being used in places like search result pages.
> Another enhancement that could be added to this is to emit a "changepage" event when the page changes that has the page number as the context. This way pages could listen and respond specifically to when the page changes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org