[
https://issues.apache.org/jira/browse/TAP5-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade closed TAP5-1398.
--------------------------------
Resolution: Incomplete
We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.4.1 or
newer), feel free to provide the necessary information and reopen.
> Create easier way to create specialized text fields for editing specific data
> types
> -----------------------------------------------------------------------------------
>
> Key: TAP5-1398
> URL: https://issues.apache.org/jira/browse/TAP5-1398
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Priority: Minor
> Labels: bulk-close-candidate
>
> I'd like to see a special base class that could be extended to easily provide
> server-side logic for editting a field.
> My scenario is a drop down list for selecting a country which Ajax-updates a
> drop down list for a region within a country and a text field for the city
> name (with autocomplete).
> City is represented as an entity is my schema; I'd like an easy way to
> extract the city.name property as the initial value of the field when
> rendered, and then have a way to turn the country/region/city name into a
> City entity when the form is submitted.
> I've cobbled together a mechanism using mixins, but it is a bit awkward to
> use. This seems to cry out for a simple subclass of AbstractTextField,
> perhaps EditField<T>.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
