You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "john (JIRA)" <ta...@jakarta.apache.org> on 2006/11/16 12:50:41 UTC
[jira] Created: (TAPESTRY-1152) Make a page designer friendly Table
component.
Make a page designer friendly Table component.
----------------------------------------------
Key: TAPESTRY-1152
URL: http://issues.apache.org/jira/browse/TAPESTRY-1152
Project: Tapestry
Issue Type: New Feature
Components: Contrib
Affects Versions: 5.0
Reporter: john
We have a Table component in contrib in 4.0. But I don't like that component. It's both too complex and not page designer friendly.
Say I'm the page designer. Adjusting the table looks is my work, but it's not easy to do it in 4.0. The adjusting includes column sizes, the column colors, etc.
Loop will work well in this situation. But it lacks the column sorting and other things. So I'd like the new Table component works much the same way like Loop, but with additional functionalities like column-name-click -sorting, maybe column location exchanging, etc.
BTW, I think that the page designer friendly is a large scale feature. It may affect many components. I care about this feature very much. It helps me very much to make it possible for the page designer to do their work separately. And It's quite convenient to transform the prototype pages to development page templates. Off course, Tapestry has done much on this point. Maybe it's the most page designer friendly web framework I've ever seen. But I don't see it in any documents. Is it a feature that Tapestry provides as a core value or just an additional benefits.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-1152) Make a page designer friendly
Table component.
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475574 ]
Howard M. Lewis Ship commented on TAPESTRY-1152:
------------------------------------------------
I'm not sure what you're expecting here.
Even contrib:Table put the designer in the drivers seat, they just had to use CSS, which is the appropriate approach in any case.
As soon as you starting talking about highly dynamic things, like column ordering, you leave the designer behind, because all they'll ever see is a static snapshot.
> Make a page designer friendly Table component.
> ----------------------------------------------
>
> Key: TAPESTRY-1152
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1152
> Project: Tapestry
> Issue Type: New Feature
> Components: Contrib
> Affects Versions: 5.0
> Reporter: john
> Fix For: 5.0
>
>
> We have a Table component in contrib in 4.0. But I don't like that component. It's both too complex and not page designer friendly.
> Say I'm the page designer. Adjusting the table looks is my work, but it's not easy to do it in 4.0. The adjusting includes column sizes, the column colors, etc.
> Loop will work well in this situation. But it lacks the column sorting and other things. So I'd like the new Table component works much the same way like Loop, but with additional functionalities like column-name-click -sorting, maybe column location exchanging, etc.
> BTW, I think that the page designer friendly is a large scale feature. It may affect many components. I care about this feature very much. It helps me very much to make it possible for the page designer to do their work separately. And It's quite convenient to transform the prototype pages to development page templates. Off course, Tapestry has done much on this point. Maybe it's the most page designer friendly web framework I've ever seen. But I don't see it in any documents. Is it a feature that Tapestry provides as a core value or just an additional benefits.
--
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] Resolved: (TAPESTRY-1152) Make a page designer friendly
Table component.
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship resolved TAPESTRY-1152.
--------------------------------------------
Resolution: Invalid
Fix Version/s: (was: 5.0)
For want of any specific idea of what is needed or desired, this is being marked as invalid.
> Make a page designer friendly Table component.
> ----------------------------------------------
>
> Key: TAPESTRY-1152
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1152
> Project: Tapestry
> Issue Type: New Feature
> Components: Contrib
> Affects Versions: 5.0
> Reporter: john
>
> We have a Table component in contrib in 4.0. But I don't like that component. It's both too complex and not page designer friendly.
> Say I'm the page designer. Adjusting the table looks is my work, but it's not easy to do it in 4.0. The adjusting includes column sizes, the column colors, etc.
> Loop will work well in this situation. But it lacks the column sorting and other things. So I'd like the new Table component works much the same way like Loop, but with additional functionalities like column-name-click -sorting, maybe column location exchanging, etc.
> BTW, I think that the page designer friendly is a large scale feature. It may affect many components. I care about this feature very much. It helps me very much to make it possible for the page designer to do their work separately. And It's quite convenient to transform the prototype pages to development page templates. Off course, Tapestry has done much on this point. Maybe it's the most page designer friendly web framework I've ever seen. But I don't see it in any documents. Is it a feature that Tapestry provides as a core value or just an additional benefits.
--
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-1152) Make a page designer friendly Table
component.
Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-1152?page=all ]
Jesse Kuhnert updated TAPESTRY-1152:
------------------------------------
Fix Version/s: 5.0
> Make a page designer friendly Table component.
> ----------------------------------------------
>
> Key: TAPESTRY-1152
> URL: http://issues.apache.org/jira/browse/TAPESTRY-1152
> Project: Tapestry
> Issue Type: New Feature
> Components: Contrib
> Affects Versions: 5.0
> Reporter: john
> Fix For: 5.0
>
>
> We have a Table component in contrib in 4.0. But I don't like that component. It's both too complex and not page designer friendly.
> Say I'm the page designer. Adjusting the table looks is my work, but it's not easy to do it in 4.0. The adjusting includes column sizes, the column colors, etc.
> Loop will work well in this situation. But it lacks the column sorting and other things. So I'd like the new Table component works much the same way like Loop, but with additional functionalities like column-name-click -sorting, maybe column location exchanging, etc.
> BTW, I think that the page designer friendly is a large scale feature. It may affect many components. I care about this feature very much. It helps me very much to make it possible for the page designer to do their work separately. And It's quite convenient to transform the prototype pages to development page templates. Off course, Tapestry has done much on this point. Maybe it's the most page designer friendly web framework I've ever seen. But I don't see it in any documents. Is it a feature that Tapestry provides as a core value or just an additional benefits.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-1152) Make a page designer friendly
Table component.
Posted by "john (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489372 ]
john commented on TAPESTRY-1152:
--------------------------------
I think previewability could be a better word for it, as it's used by tapestry's documents.
Let's imagine a use case of page designer uses Dreamweaver or any other page designer to design the table, it will be difficult for him/her to adjust the table cells like sizing and coloring.
> Make a page designer friendly Table component.
> ----------------------------------------------
>
> Key: TAPESTRY-1152
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1152
> Project: Tapestry
> Issue Type: New Feature
> Components: Contrib
> Affects Versions: 5.0
> Reporter: john
>
> We have a Table component in contrib in 4.0. But I don't like that component. It's both too complex and not page designer friendly.
> Say I'm the page designer. Adjusting the table looks is my work, but it's not easy to do it in 4.0. The adjusting includes column sizes, the column colors, etc.
> Loop will work well in this situation. But it lacks the column sorting and other things. So I'd like the new Table component works much the same way like Loop, but with additional functionalities like column-name-click -sorting, maybe column location exchanging, etc.
> BTW, I think that the page designer friendly is a large scale feature. It may affect many components. I care about this feature very much. It helps me very much to make it possible for the page designer to do their work separately. And It's quite convenient to transform the prototype pages to development page templates. Off course, Tapestry has done much on this point. Maybe it's the most page designer friendly web framework I've ever seen. But I don't see it in any documents. Is it a feature that Tapestry provides as a core value or just an additional benefits.
--
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