[
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)
