Return-Path: Delivered-To: apmail-click-dev-archive@www.apache.org Received: (qmail 53313 invoked from network); 16 Nov 2010 21:48:05 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 16 Nov 2010 21:48:05 -0000 Received: (qmail 36947 invoked by uid 500); 16 Nov 2010 21:48:37 -0000 Delivered-To: apmail-click-dev-archive@click.apache.org Received: (qmail 36926 invoked by uid 500); 16 Nov 2010 21:48:37 -0000 Mailing-List: contact dev-help@click.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@click.apache.org Delivered-To: mailing list dev@click.apache.org Received: (qmail 36917 invoked by uid 99); 16 Nov 2010 21:48:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Nov 2010 21:48:37 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Nov 2010 21:48:35 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oAGLmDa0014910 for ; Tue, 16 Nov 2010 21:48:13 GMT Message-ID: <30467792.127601289944093653.JavaMail.jira@thor> Date: Tue, 16 Nov 2010 16:48:13 -0500 (EST) From: "Bob Schellink (JIRA)" To: dev@click.apache.org Subject: [jira] Resolved: (CLK-525) FormTable - renderTransposed functionality MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ 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.