Task block within a page
At the moment, it is only possible to create checklist-blocks.
There should be a task-list collection-block.
It should support nested tasks.
It should include the following options:
- Should the parent task be checked automatically when all child tasks are checked?
- Should all checked tasks be hidden or moved to the bottom?
The settings for this “task-list collection” could be configured in the top-right corner of the user interface, similar to a code block.
This would keep the focus on the items that are currently necessary.
---------------------------------------------------------------------------------------------
Current situation
Should be
UI setting like it is of Code blocks
9 Comments
Sign in to comment
·2 days agoThanks for the detailed feature request — the sketches and use case are really clear.
Just to make sure we understand the full scope: when you say "task-list collection-block," are you picturing this as a dedicated block type that lives anywhere on a page (like how code blocks work now), or as something that transforms existing checklist items? And for the nested tasks — would those be created by indenting items within the block, similar to how outline nesting usually works?
Also, on the auto-check behavior: when a parent task auto-checks because all children are done, should unchecking any child automatically uncheck the parent too, or is it one-way (parent only reflects child state)?
What do you mean by nested tasks? Anytype is a graph based system as you know, so there's no such thing as hierarchy for objects in reality. What are you expecting when it comes to nesting—that the user must designate something as being a parent task and then sub tasks being put underneath it? And do you expect this functionality to exist in the editor pages?
I've marked this issue as a duplicate because it relates to the link referenced below. If you want those other task specific features, please outline what you expect keeping in mind that Anytype is a graph system.
This is a duplicate of:
@Kaye I wanted to edit the main topic but this does not seem to be possible anymore.
So I created a video with voice explanation (Don't make fun of my English 😆) as I think this is the fastest way of explanation.
Checklist Features
Realworld Usecase
Thanks for taking the time to put this together. I sent you a message on Anytwo to checkout a series of tasks that relate to what you're trying to accomplish. One of the big differences is checkbox block vs. task object.
Checkboxes are just blocks in an editor, and they don't usually have unique behaviours because they're independent of each other (like text blocks are). You can do things like add toggles, but it's really designed to be quick and dirty tasks.
If you want more comprehensive task-like behaviour, then each task needs to be created as an object. After that, you can then use Inline Views or the Task Mini App to interact with them. Not sure if that makes sense in how they're different?
@Kayeplease forget about the Task topic!
My initial description led you down the wrong path.
I know that tasks exist, and I’ve used them successfully in AnyType so far.
For example, I’ve created project objects using a template that always includes an inline query task referencing the current object. But that’s not the issue here.
I also know that checkbox blocks are quick and dirty. And that’s how they should stay.
I don’t want a task called “Earn Trophy XY.” For me, it’s just a list of the trophies for the current game. Nothing to track, no date, nothing.
But since this is an editor-related issue for me, I brought it up because the current implementation of checkbox blocks is pretty much unusable.
If it’s not possible for the editor to recognize that one checkbox block follows another, there should be something like a checkbox block (similar to callouts or code blocks) that contains the logic.
Again, I’m talking about a pure editor feature here, not the task object.
P.S.: I wish Anytype/Anytwo had a video call feature—that would make communication a bit easier.
Ok, but how is a 'checkbox block' different from an actual 'task object block'. It sounds like what you want would be resolved by using task objects and inline views?
It sounds like you want an intermediate solution but it's not clear to me why? As far as I'm aware, checkboxes in Anytwo behave the same way as it does in other block editors? By installing these 'rich features' they're no longer just markdown-style elements on a page.
Following your logic, you could also ask what distinguishes a checkbox from a task. This would call into question the very existence of the checkbox line.
What’s the point of it, then? I need it to format my content (in this case, a list of items) stylistically.
In this case, I don’t want to create a new object or add links or anything like that.
It’s just supposed to exist within this object as a stylistic device.
By installing these 'rich features' they're no longer just markdown-style elements on a page.
It doesn't need a new element. I could also be implemented how anytype handles this by .js.
I the editor recognizes a checkbox indented under another checkbox (previous sibling) I could be formatted different and the same thing goes to the parent. You could handle these thing with css and js which is already there.
I mean there are expanded features available for Bullet lists where you get different dots for indented items. So I am having a hard time to understand why expanded features shouldn't be available for Check lists, too.