The current design for UI widgets intermixes the logical and visual aspect of attribute handling. They should be split into 2 concepts: - Field: field is responsible for loading, storing, and validating the values, getting metadata info (e.g. data type, validation pattern, I18n label), checking the permissions, etc. - Widget: the new widget will be responsible for displaying the values, saving user input, detecting keystrokes, showing undo buttons, showing error messages, etc.
A widget could be nested inside another widget (e.g. multivalued widget, section) to allow reusing existing widgets.
master: - a17bf5e - 4bab6b7 - 863666f - 6cdf098 - e021542 - 5b26a38 - b55d154 - 9b362ce - fcba1cb - e271e80 - 6e3a21a - a902fa4 - fdee089 - 9a09916 - 2759ea2 - c5ca34f - 1ffbec9
master: 187beda
Metadata Update from @edewata: - Issue assigned to pvoborni - Issue set to the milestone: FreeIPA 3.0 Core Effort - 2011/12
Login to comment on this ticket.