You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@click.apache.org by "Bob Schellink (JIRA)" <ji...@apache.org> on 2010/11/16 22:48:13 UTC

[jira] Resolved: (CLK-525) FormTable - renderTransposed functionality

     [ https://issues.apache.org/jira/browse/CLK-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bob Schellink resolved CLK-525.
-------------------------------

    Resolution: Won't Fix

Thinking about this, it doesn't look very useful. If the detail view is very complex a better pattern is master/detail where validation works properly. Another alternative is a normal Form with a standalone Paginator.

> FormTable - renderTransposed functionality
> ------------------------------------------
>
>                 Key: CLK-525
>                 URL: https://issues.apache.org/jira/browse/CLK-525
>             Project: Click
>          Issue Type: New Feature
>            Reporter: Joseph Schmidt
>            Assignee: Adrian A.
>             Fix For: 2.4.0
>
>
> Please add a "renderTranspose" functionality for FormTable, i.e., when this boolean property would be set,
> than the table would be rendered in the transposed mode (columns instead of rows and vice versa )
> Were is this very useful: 
> - forms with too many fields would need too much horizontal scroll. For better usability is a requirement to render
> transposed for those cases - vertical scroll is much more user friendly.
> - long field names
> - forms that require in table mode just a few data sets (rows) - when rendered transposed, are much more usable
> - when doing allot of comparative work (e.g. only between 2 data sets)
> Another nice option would be the possibility to set the tabulation order , e.g. 
> String tabulationOrder = "toLeft"; // toBottom
> to be able to improve the keyboard friendliness of the FromTable (in transpose mode or not)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.