You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Adam Zimowski (JIRA)" <de...@tapestry.apache.org> on 2008/03/21 16:33:31 UTC
[jira] Created: (TAPESTRY-2292) Allow define Grid sort within the
template.
Allow define Grid sort within the template.
-------------------------------------------
Key: TAPESTRY-2292
URL: https://issues.apache.org/jira/browse/TAPESTRY-2292
Project: Tapestry
Issue Type: Improvement
Components: Core Components
Affects Versions: 5.0
Environment: T 5.0 - 5.0.11
Reporter: Adam Zimowski
Priority: Minor
Fix For: 5.0.12
Grid by default enables sort for all columns without providing a flexible and quick mechanism at the template level for configuring which columns to make sortable, and to allow to turn on and off sorting alltogether. Current sort default should be evaluated as lot of developers disable sorting for all columns only to enable it for a column or two, if that at all.
Proposed enhancement:
1) Change Grid to disable sort on all columns.by default (this is the least needed of all four enhancements, but it would be nice if this could be changed)
2) Add sortAll parameter which accepts boolean value. If true, then sort for all columns is enabled, if false sort for all columns is disabled. Per enhancement #1, default would be false.
3) Add sorted parameter which accepts comma delimited names of columns to be sorted. I am not sure how this would play out with existing include parameter, as some decisions have to be made as far as what if "sorted" contains a property which is excluded from display in a first place?
4) Add unsorted parameter which is opposite of sorted parameter.
--
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: (TAP5-109) Allow define Grid sort within the
template.
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-109.
-------------------------------------
Resolution: Duplicate
Assignee: Howard M. Lewis Ship
> Allow define Grid sort within the template.
> -------------------------------------------
>
> Key: TAP5-109
> URL: https://issues.apache.org/jira/browse/TAP5-109
> Project: Tapestry 5
> Issue Type: Improvement
> Affects Versions: 5.0.15
> Environment: T 5.0 - 5.0.11
> Reporter: Adam Zimowski
> Assignee: Howard M. Lewis Ship
> Priority: Minor
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> Grid by default enables sort for all columns without providing a flexible and quick mechanism at the template level for configuring which columns to make sortable, and to allow to turn on and off sorting alltogether. Current sort default should be evaluated as lot of developers disable sorting for all columns only to enable it for a column or two, if that at all.
> Proposed enhancement:
> 1) Change Grid to disable sort on all columns.by default (this is the least needed of all four enhancements, but it would be nice if this could be changed)
> 2) Add sortAll parameter which accepts boolean value. If true, then sort for all columns is enabled, if false sort for all columns is disabled. Per enhancement #1, default would be false.
> 3) Add sorted parameter which accepts comma delimited names of columns to be sorted. I am not sure how this would play out with existing include parameter, as some decisions have to be made as far as what if "sorted" contains a property which is excluded from display in a first place?
> 4) Add unsorted parameter which is opposite of sorted parameter.
--
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-2292) Allow define Grid sort within the
template.
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-2292:
-------------------------------------------
Fix Version/s: (was: 5.0.12)
5.0.13
> Allow define Grid sort within the template.
> -------------------------------------------
>
> Key: TAPESTRY-2292
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2292
> Project: Tapestry
> Issue Type: Improvement
> Components: Core Components
> Affects Versions: 5.0
> Environment: T 5.0 - 5.0.11
> Reporter: Adam Zimowski
> Priority: Minor
> Fix For: 5.0.13
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> Grid by default enables sort for all columns without providing a flexible and quick mechanism at the template level for configuring which columns to make sortable, and to allow to turn on and off sorting alltogether. Current sort default should be evaluated as lot of developers disable sorting for all columns only to enable it for a column or two, if that at all.
> Proposed enhancement:
> 1) Change Grid to disable sort on all columns.by default (this is the least needed of all four enhancements, but it would be nice if this could be changed)
> 2) Add sortAll parameter which accepts boolean value. If true, then sort for all columns is enabled, if false sort for all columns is disabled. Per enhancement #1, default would be false.
> 3) Add sorted parameter which accepts comma delimited names of columns to be sorted. I am not sure how this would play out with existing include parameter, as some decisions have to be made as far as what if "sorted" contains a property which is excluded from display in a first place?
> 4) Add unsorted parameter which is opposite of sorted parameter.
--
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-2292) Allow define Grid sort within the
template.
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-2292:
-------------------------------------------
Fix Version/s: (was: 5.0.13)
5.0
> Allow define Grid sort within the template.
> -------------------------------------------
>
> Key: TAPESTRY-2292
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2292
> Project: Tapestry
> Issue Type: Improvement
> Components: Core Components
> Affects Versions: 5.0
> Environment: T 5.0 - 5.0.11
> Reporter: Adam Zimowski
> Priority: Minor
> Fix For: 5.0
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> Grid by default enables sort for all columns without providing a flexible and quick mechanism at the template level for configuring which columns to make sortable, and to allow to turn on and off sorting alltogether. Current sort default should be evaluated as lot of developers disable sorting for all columns only to enable it for a column or two, if that at all.
> Proposed enhancement:
> 1) Change Grid to disable sort on all columns.by default (this is the least needed of all four enhancements, but it would be nice if this could be changed)
> 2) Add sortAll parameter which accepts boolean value. If true, then sort for all columns is enabled, if false sort for all columns is disabled. Per enhancement #1, default would be false.
> 3) Add sorted parameter which accepts comma delimited names of columns to be sorted. I am not sure how this would play out with existing include parameter, as some decisions have to be made as far as what if "sorted" contains a property which is excluded from display in a first place?
> 4) Add unsorted parameter which is opposite of sorted parameter.
--
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: (TAP5-109) Allow define Grid sort within the
template.
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-109:
--------------------------------------
Issue Type: Improvement (was: Bug)
> Allow define Grid sort within the template.
> -------------------------------------------
>
> Key: TAP5-109
> URL: https://issues.apache.org/jira/browse/TAP5-109
> Project: Tapestry 5
> Issue Type: Improvement
> Affects Versions: 5.0.15
> Environment: T 5.0 - 5.0.11
> Reporter: Adam Zimowski
> Priority: Minor
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> Grid by default enables sort for all columns without providing a flexible and quick mechanism at the template level for configuring which columns to make sortable, and to allow to turn on and off sorting alltogether. Current sort default should be evaluated as lot of developers disable sorting for all columns only to enable it for a column or two, if that at all.
> Proposed enhancement:
> 1) Change Grid to disable sort on all columns.by default (this is the least needed of all four enhancements, but it would be nice if this could be changed)
> 2) Add sortAll parameter which accepts boolean value. If true, then sort for all columns is enabled, if false sort for all columns is disabled. Per enhancement #1, default would be false.
> 3) Add sorted parameter which accepts comma delimited names of columns to be sorted. I am not sure how this would play out with existing include parameter, as some decisions have to be made as far as what if "sorted" contains a property which is excluded from display in a first place?
> 4) Add unsorted parameter which is opposite of sorted parameter.
--
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