Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: 5.1.0.1
    • Fix Version/s: 5.1.0.1
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      As raised in TAP5-213, we don't do enough to make the common cases of using the Select component easy enough. To this end, we should add back in the StringPropertySelectModel default implementation like T4 had (http://tapestry.apache.org/tapestry4.1/apidocs/org/apache/tapestry/form/StringPropertySelectionModel.html). Not only was it a good idea then, but it should help with a T4 migration to T5.

        Activity

        Hide
        Kevin Menard added a comment -

        As I dug into this, I came to realize that Tapestry already handles this. Just provide a List of Strings as the model parameter of the Select component. I've updated the docs to reflect this.

        There may still be cases that require an explicit SelectModel to be created, but I'd need to be sold on this before adding something to the framework that is largely already provided.

        Show
        Kevin Menard added a comment - As I dug into this, I came to realize that Tapestry already handles this. Just provide a List of Strings as the model parameter of the Select component. I've updated the docs to reflect this. There may still be cases that require an explicit SelectModel to be created, but I'd need to be sold on this before adding something to the framework that is largely already provided.

          People

          • Assignee:
            Kevin Menard
            Reporter:
            Kevin Menard
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development