Features
Todo
Make Property a Type
Currently there isn't a way to see all the created properties.
It'd be helpful to have properties listed as a type, so we could see all the properties in a space, and what collections they are associated with. Even though it's hidden in the anytype app, it's incredibly useful to have a list of all the used properties for a space. I'd love to see that implemented in the Anytwo app also.
This would also make it easier to copy properties from one collection over to another.
5 Comments
Sign in to comment
To be clear, Anytwo does not have global properties—that is, you can't share properties across Collections. This being the case, would you still want this feature? Can you describe why you would want to use such a thing in the case where there aren't shared properties?
Even though there aren't shared properties, I'd still want a properties view, where I can also create and move/copy properties for a couple of different reasons.
Currently there isn't a way to see all the created properties. It'd be helpful to have properties listed as a type, so we could see all the properties in a space, and what collections they are associated with. Even though it's hidden in the anytype app, it's incredibly useful to have a list of all the used properties for a space.
This would also make it easier to copy properties from one collection over to another — and I'd want to be able to create new properties from that same view, not just view them read-only.
Example 1: Starting a graduate degree collection. After finishing an undergrad degree, someone starts a new collection for their grad school degree. Being able to see the full list of templates and properties would let them recreate the same structure instead of rebuilding it from memory.
Example 2: A Household Command Center. You spend a long time setting up a command center for your household. Maybe your fridge uses windows IOT and you’re able to open Any pages on it. You have todos, various codes, vendors, schedules, and where things are located. You then move to a new house and want to create a new collection. Being able to see the old house’s properties would be helpful so you can figure out what to duplicate in the new home’s command center.
To be clear, each collection would still have its own independent copy. I just want to stop rebuilding the same property setup by hand every time.
In both examples, it sounds like it'd be simpler to just duplicate both Collections (without any of the objects in it). This way you can not only keep the properties, but also all the views, templates, etc. that have been set up on them. Would you agree or do you still think you'd want to see all your properties?
If we could set up duplication so it didn't include any objects, that'd be great.
I still think it would be helpful to query properties in a centralized place to see what I've used in various collections and try to cull any superfluous properties or change them to match ones more effective from other collections. There are a lot of connections I make when viewing all the properties together that I don't notice when they're siloed into collections.
Do you think that'd be possible from views or queries in the future?
I can't speak to the implementation possibilities, but I'm having this discussion because, personally, I kind of want to avoid Anytwo becoming this 'tinkerers tool' where you have to go in and organise everything. The thing with 'power-user' features is that they're often additive, "surely having this feature is better than not having it." But the issue is that overtime it grows into bloat and the need to support many more things that may not actually provide value to 99% of users. So I want to be sure that something is truly necessary, not just a 'nice-to-have'. Especially at this stage of product development.