Tapestry
  1. Tapestry
  2. TAPESTRY-747

Add translator parameter to the Select component

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: 4.0
    • Fix Version/s: 4.1.1
    • Component/s: Framework
    • Labels:
      None

      Description

      Although most cases will use a PropertySelection, since under the hood the Select component is de facto a string based input, just like TextField or -Area, a translator parameter should be added.

        Activity

        Ron Piterman created issue -
        Brian K. Wallace made changes -
        Field Original Value New Value
        Component/s Framework [ 11280 ]
        Jesse Kuhnert made changes -
        Fix Version/s 4.1.1 [ 12312021 ]
        Hide
        Jesse Kuhnert added a comment -

        I may be misinterpreting the issue but the Select component isn't really involved in the actual "value" portion of things at all. The incoming / outgoing values it manages are purely index -based numbers corresponding to the selected options contained in the body of the select.

        Show
        Jesse Kuhnert added a comment - I may be misinterpreting the issue but the Select component isn't really involved in the actual "value" portion of things at all. The incoming / outgoing values it manages are purely index -based numbers corresponding to the selected options contained in the body of the select.
        Jesse Kuhnert made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Won't Fix [ 2 ]
        Hide
        Ron Piterman added a comment -

        So now the bug is fixed, but after reading the comment I don't know if it is fixed or not, was a translator added? there are no commits on the issue.

        Anyway, the value of the Select is not an index, but a String - which the application may interpret as it wants.
        To make the "interpretation" much easier, one could use a translator- quite straightfarword then... when reading the value, reading an arbitrary object and formatting it to a string with the translator.
        When writing the object, using the tarnslator to parse the string and writing an arbitrary object.

        Show
        Ron Piterman added a comment - So now the bug is fixed, but after reading the comment I don't know if it is fixed or not, was a translator added? there are no commits on the issue. Anyway, the value of the Select is not an index, but a String - which the application may interpret as it wants. To make the "interpretation" much easier, one could use a translator- quite straightfarword then... when reading the value, reading an arbitrary object and formatting it to a string with the translator. When writing the object, using the tarnslator to parse the string and writing an arbitrary object.
        Mark Thomas made changes -
        Workflow jira [ 12343677 ] Default workflow, editable Closed status [ 12567283 ]
        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12567283 ] jira [ 12590109 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        399d 1h 37m 1 Jesse Kuhnert 16/Dec/06 20:04

          People

          • Assignee:
            Unassigned
            Reporter:
            Ron Piterman
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development