Click
  1. Click
  2. CLK-114

Form.toString(): Customize the class attribute

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 3.0.0
    • Component/s: core
    • Labels:
      None

      Description

      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

        Activity

        Hide
        Gilberto C Andrade added a comment -

        Have this feature implemented in some way?

        Show
        Gilberto C Andrade added a comment - Have this feature implemented in some way?
        Hide
        Adrian A. added a comment -

        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.

        Show
        Adrian A. added a comment - 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.

          People

          • Assignee:
            Malcolm Edgar
            Reporter:
            Ricardo Lecheta
          • Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:

              Development