Since we can now connect to Boxes… what if we could have the to-do checkboxes on them too…
I’ve been using them in a few various ways where this would make sense.
Treating a box as a little project — so within it I have individual to-do’s as well as notes. Being able to signify right from the box heading that it’s complete would be awesome.
For Dots, I’ve started organizing our spaces by idea/feature, with each getting it’s own box. Being able to close out a Box visually like that would be huge.
Just a quick screenshot of Things that shows the Project up top has the circle/pie that can also be checked to close out the Project along with the individual to-dos.
in that Things example the title doesn’t have a checkbox, instead it has a progress indicator that looks like it’s showing the percent of tasks inside it are complete. So in the scenarios you outlined it would show completion but it’d do that automatically based on it’s contents. is that what you’re looking for?
could add clicking on it to check off all cards inside that have checkboxes. not all cards inside a box will have checkboxes though so i’d assume you want to leave those untouched
Yeah, I assumed that’d be more difficult so I was trying to reduce scope, but it’d be very cool to see the progress.
The other part, that might be unique to me, is having a box filled with non-to-do cards but still wanting to mark the box “complete”. But I’d be fine sacrificing that if the box could show dynamic progress of the to-do’s within it. (I could handle this with a single checkbox card in a corner)
Edit: I could see the mark all complete being useful (if it doesn’t touch non checkbox cards), but more as a superfluous extra if it’s easy and doesn’t expand scope too much. The progress for the box would be the main win here.
Edit 2: and I think a big part of this, for me, is making sure the progress indicator, when 100% complete, is obvious. Whether that’s fading the box name or crossing it out or something like that so it’s clear from a glance that box is complete.
I think this may have stopped working. If I load the space, my boxes with checkboxes in the initial view render as expected but then as I scroll around the cards inside lose the opacity and display as normal. If I create a new box outside of the initial view and check it, it doesn’t start with opacity. I think the bug is therefore described as: opacity on checked boxes is only applied in the initial view. Doesn’t impact initial cards, just boxes.
I think it worked, sort of. I’m no longer able to reproduce the behaviour where scrolling around changes the way the boxes are displaying but I still have some boxes where some of the cards are not displayed as grayed out. The behaviour doesn’t seem to have any pattern so I wonder if it’s user error: maybe I’ve done something to these specific cards to make them… not part of the box?
Actually, after taking the following screenshots, I can reproduce it, I returned to the tab and some of the cards within the boxes had changed their display.
The issue is very minor, a very minor inconvenience at worst (as I can still see that the box itself is checked off) but documenting what I’m seeing just in case it helps track down the issue.
Chrome Version 133.0.6943.142 (Official Build) (arm64) on a Macbook.
I’ve also tried moving cards from “Box 0” to other boxes and they continue to render with full opacity, and then moving other cards into “Box 0” renders them as faded out. I think the bug is impacting boxes other than the first box in the space. I created another new space and then created 3 boxes in it: the first box behaves as expected, but box 2 and 3 do not.
Note here, if I scroll back, things are still good. I first need to create a box or a card when the boxes are scrolled out of view, and then scroll back to see the bug.
Create box C.
Scroll back.
Observe the card B is not faded. It no longer has the is-in-checked-box class.
It seems like the state is not being updated properly.
