Open aymanhab opened 9 years ago
@aymanhab Should this be in 4.0 or can we push to the next release?
Next release.
A related issue is replacing the "groups" functionality of sets. We can replace this functionality by introducing a tags
list property (of strings) to Component; each component can have a list of tags. Then the GUI can show all components that have a given tag. We could either do this across types or for each type separately.
This would at least work for grouping subcomponents, but it maybe could also work for grouping all kinds of properties?
If this is on a property level, it could look like this:
<assembly_accuracy tags="advanced">0.0001</assembly_accuracy>
The Property system doesn't allow for grouping of properties except as Objects, this may lead to the introduction of extra classes. A mechanism to group properties using different aspects (e.g. commonly used vs. advanced) or in some other flexible way would be desired.
Using nested classes doesn't serve this exactly since the nested classes still need to be exposed for serialization and their XML serialization uses ":" which should be reserved for Namespace specification.