Return-Path: 
 <dev-return-3229-apmail-click-dev-archive=click.apache.org@click.apache.org>
X-Original-To: apmail-click-dev-archive@www.apache.org
Delivered-To: apmail-click-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 931A91097F
	for <apmail-click-dev-archive@www.apache.org>;
 Sun,  3 Nov 2013 10:51:24 +0000 (UTC)
Received: (qmail 64635 invoked by uid 500); 3 Nov 2013 10:51:23 -0000
Delivered-To: apmail-click-dev-archive@click.apache.org
Received: (qmail 64564 invoked by uid 500); 3 Nov 2013 10:51:22 -0000
Mailing-List: contact dev-help@click.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@click.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@click.apache.org>
List-Post: <mailto:dev@click.apache.org>
List-Id: <dev.click.apache.org>
Reply-To: dev@click.apache.org
Delivered-To: mailing list dev@click.apache.org
Received: (qmail 64465 invoked by uid 99); 3 Nov 2013 10:51:18 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 Nov 2013 10:51:18 +0000
Date: Sun, 3 Nov 2013 10:51:18 +0000 (UTC)
From: "Adrian A. (JIRA)" <jira@apache.org>
To: dev@click.apache.org
Message-ID: <JIRA.12417627.1154279829000.12585.1383475878759@arcas>
In-Reply-To: <JIRA.12417627.1154279829000@arcas>
References: <JIRA.12417627.1154279829000@arcas>
Subject: [jira] [Commented] (CLK-114) Form.toString(): Customize the class
 attribute
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/CLK-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812322#comment-13812322 ] 

Adrian A. commented on CLK-114:
-------------------------------

IMHO the confusion arises from the Click's Form "auto-layout" default functionality (that is HTML table based, and tries to do it's best for most situations).

When already having ready screens, this "auto-layout" is not of much use, but the rest of the Form functionality is very much useful.

So maybe a better approach would be to separate this "auto-layout" functionality so that users can easier skip it altogether and plug-in their own.

> Form.toString(): Customize the class attribute
> ----------------------------------------------
>
>                 Key: CLK-114
>                 URL: https://issues.apache.org/jira/browse/CLK-114
>             Project: Click
>          Issue Type: Improvement
>          Components: core
>            Reporter: Ricardo Lecheta
>            Assignee: Malcolm Edgar
>             Fix For: 3.0.0
>
>
> Hi,
> The Form.toString generates the following code:
> - buffer.append("<table class=\"form\" id=\"");
> - buffer.append("<table class=\"fields\" id=\"");
> - class= buttons, errors
> We can change the css properties in the control.css file. 
> But sometimes when the project starts, we already have all prototype (pages, screens, css) already written
> The easier way is just to change the class attribute, and you can get the look-and-feel of your prototype. Might public methods to change the "class" attributes should be a good addition to click.
> So we don't need to change the control.css, and we also don't need ask help for the designer. You just have to use the correct css.
> thanks



--
This message was sent by Atlassian JIRA
(v6.1#6144)