webjose / wj.databinding Goto Github PK

In case not all properties are wanted/needed in the data-bound control (usually a grid control), give the consumer of the class the ability to effectively remove property descriptors during data-binding in order to limit the number of columns generated in data-bound grid controls.

Create a class, much like the Container class, that does the same but for 2 or more classes. I do not yet have a clear practical use case in mind. If anyone has one, please write it down for me.

Crear una clase básicamente como la clase Container que hace lo mismo pero para 2 o más clases. No tengo aún un caso de uso práctico claro en mente. Si alguien tiene uno, por favor me lo escriben.

Give the Container class the ability to sort the properties in any way the consumer of the class desires.

Ideally, give the consumer of the class the ability to sort using an IComparer<PropertyDescriptor> or explicitly providing a list of property names.

Because the property descriptors are usually implicitly requested, the most intuitive API could be a sorting event that fires after property descriptors are collected but before they are passed on to the data-bound control that requested them.

Alternatively simply add sorting-related properties:

• OrderList: List of property names already sorted.
• SortBy: Enum with options to sort by OrderList, by property source, or by comparer object.
• Comparer: IComparable<PropertyDescriptor object to use with the sorting algorithm.

The potential problem here is that it would require to configure every object since it is strictly not documented which object is used to retrieve property descriptors.