You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2008/02/29 00:53:51 UTC
[jira] Created: (TAPESTRY-2206) Tapestry should have a different
date type for numbers than for strings
Tapestry should have a different date type for numbers than for strings
-----------------------------------------------------------------------
Key: TAPESTRY-2206
URL: https://issues.apache.org/jira/browse/TAPESTRY-2206
Project: Tapestry
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.0.10
Reporter: Howard M. Lewis Ship
Currently, String and all Number types are lumped together because they use the same component, a TextField.
However, it is reasonable that they should be differentiated; for example, numeric fields will typically be styled to right justify the fields, whereas text fields are typically left justified.
Numbers should be data type "number" and have their own edit and display blocks.
--
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-2206) Tapestry should have a different
data type for numbers than for strings
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-2206.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.11
> Tapestry should have a different data type for numbers than for strings
> -----------------------------------------------------------------------
>
> Key: TAPESTRY-2206
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2206
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.10
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.11
>
>
> Currently, String and all Number types are lumped together because they use the same component, a TextField.
> However, it is reasonable that they should be differentiated; for example, numeric fields will typically be styled to right justify the fields, whereas text fields are typically left justified.
> Numbers should be data type "number" and have their own edit and display blocks.
--
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-2206) Tapestry should have a different
data type for numbers than for strings
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-2206:
-------------------------------------------
Summary: Tapestry should have a different data type for numbers than for strings (was: Tapestry should have a different date type for numbers than for strings)
> Tapestry should have a different data type for numbers than for strings
> -----------------------------------------------------------------------
>
> Key: TAPESTRY-2206
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2206
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.10
> Reporter: Howard M. Lewis Ship
>
> Currently, String and all Number types are lumped together because they use the same component, a TextField.
> However, it is reasonable that they should be differentiated; for example, numeric fields will typically be styled to right justify the fields, whereas text fields are typically left justified.
> Numbers should be data type "number" and have their own edit and display blocks.
--
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] Assigned: (TAPESTRY-2206) Tapestry should have a different
data type for numbers than for strings
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAPESTRY-2206:
----------------------------------------------
Assignee: Howard M. Lewis Ship
> Tapestry should have a different data type for numbers than for strings
> -----------------------------------------------------------------------
>
> Key: TAPESTRY-2206
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2206
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.10
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> Currently, String and all Number types are lumped together because they use the same component, a TextField.
> However, it is reasonable that they should be differentiated; for example, numeric fields will typically be styled to right justify the fields, whereas text fields are typically left justified.
> Numbers should be data type "number" and have their own edit and display blocks.
--
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