If creating many objects of my custom type often, I need to search the type every time. With this, it would be much faster.
When creating all the objects at once, I guess I could go to the type page and create them there, but that is not usable every time - I was creating the objects directly into collection, so that would not help.
It could also just suggest most used/most recent types, but I don’t think that’s better.
I also made another feature request with similar benefits, not same though
Can you please share your pipeline of creation this objects. Especially do you use any set or collection to aggregate this objects? And what is the context of this objects creation: like you doing it via sets or you add it to a certain page or just create a new one via plus button. It will really help us to understand your flow in depth.
This is in relation to creating a new object trough the plus sign (you can see in the first image). Currently the types that are “starred” are always note, page, task, or collection.
They are asking for an ability to choose which types show up there instead of the default ones.
The use I wanted to use it for was having a collection To Read open and I was adding many items to it by clicking the new object row. I was adding only object of type Book into it, however every time I created it, I needed to scroll/type the type name.
However this is just one use case and I can imagine more of them.
For example if you have custom type Daily Note (or for something else) and you are creating it frequently, there would be less friction for you when creating it.
Well, for the first use use, you’re better off using a set with the type Book. When using a set by book type, it’ll use the book type as the default object when you create a new one trough the set.
I’m also wondering why would you use a collection for managing your to read books, when a set + view is a much much better solution. Doing this with a collection is a lot more cumbersome.
Same thing with the daily note. Create a set by the type, and you can quickly create new ones from there.
You can create a relation of type status or tag called Status or something similar. Then you can create a set by this relation, and then create views for each of your relation options (a view for all things to read soon, a view for all things to read later etc.). Since it’s a set by a relation, it will show all objects that have this relation, and if you then also use this relation to categorize websites too, they will also show up in this set.