T
Thomas Graf
+1 for this.
Even better if you can have an advanced select that can support different modes:
- pick any object type (like the current context property)
- pick from selected object types
- pick from a certain query
Beth
Thomas Graf, Fëdor Tarasenko you can use a text property to link to any object in your space. What is it about the context property specifically that you would wish to use in another type?
A
Aa Aaa
Beth text is handled completely differently in queries than object select/context
Context allows an easy way to only add different objects into one property. Text property is a workaround for this, not a seamless solution.
I think where context could really shine is allowing users to pick which objects can go into a context. It's like a multi selection for object select property.
T
Thomas Graf
Beth To clarify, I'm primarily thinking about a object select property that supports mixing multiple object types. Not specifically about the context property.
Text properties are "better than nothing" for this, but object select are superior for various reasons.
- Filtering/queries: For example, you want to filter by country "Niger", but it should not contain "Nigeria". Easy to do that with object selects, but partial text matches are not suitable.
- Selects feel much more effortless - less typing, less clicks for adding or removing an object. Object select has also a good re-ordering interface.
- Visuals: In the context property you can clearly see the type of the object (through colours and icons).
- Object properties allow "fixed set" selections (making it much quicker to find the right object).
Thinking about possible next steps, it would be nice to have a select box that takes all objects from a query result. Altough, this might be just a "quality of life" thing (an improvement over fixed sets) and not enable new use cases.