The type selector is currently a drop down box. This won't scale well once the number of types increases, which is expected. That will require a different UX element then.
Description
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | gengh | T270295 Fix behaviour of SelectZObject component to make it more usable and similar to OOUI component | |||
Resolved | ArthurPSmith | T269192 Rewrite the type selector |
Event Timeline
Comment Actions
Perhaps we should seek to minimise the selection of types. More often than not, an object's type should be the same as (or a refinement of) some other object's type. I would generally prefer to define the type by explicit reference to this other object, rather than trying to re-define it at the point of re-use. I wonder whether the same reference would also imply the type's validator? For example, the type and validator definitions of the sine and cosine functions would be the same, wouldn't they?
Comment Actions
Marked T270295 as parent, because TypeSelector should just really be a SelectZObject component with a configuration parameter, so that it filters the types of objects to display to only ZTypes.