[ 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to