/todo

[aza]

What is?

• /todo Check this off creates a todo-styled message, which has a checkbox on the left which toggles the message's style.
• That's it.

How use?

• To use, just post and check off. Reorder them. Put them in a shared channel for a social todo list.
  • In my whisper with Wendellen, we could just /todo our grocery list
• Make three channels @user/todo/backlog, @user/todo/ready, @user/todo/done. Open them in the web client for a nice Trello-like experience. Save it as a channel set. Send it as a link.
• @user/todo can use universal permission :)
• A more feature-rich todo could be: /todo Check this off @moop cc @bop Tuesday which assigns it to @moop, notifies @bop and makes the item due Tuesday.

other.js

• simple custom message rendering, ability to handle taps on messages

[tonygentilcore]

Want this!

It begs the question about how we make this work. There are two powers needed: (1) reorder and (2) checkbox. It'd be nice if the /todo feature just had to compose those. Next we get the question of whether the client itself implemented (1) and (2).

I'd propose in the short-to-medium term the clients have to understand reordering and checkboxes as formats (e.g. /orderable, /checkbox). Then the /todo feature just registers for /todo and applies both formats to the message.

A feature installed on the channel could apply those formats to all messages in the channel. Then you could have a todo channel.

In the longer term we'll want custom rendering, but I think the ios client will need some architectural changes first and we could have this a lot sooner.

[tonygentilcore]

ps. I subtly like the idea that every JS framework out there uses TODO as their canonical intro example to show their framework off. other.js's will practically be a one-liner!

[aza]

@tonygentilcore Feel [....|.] that channel owners should be able to reorder messages regardless. Like being able to make them orderable per message, that's neat.

In the composible world, then /todo $text is /orderable /checkbox $text :)

[aza]

#want
On Thu, Aug 18, 2016 at 5:45 PM Tony Gentilcore notifications@github.com
wrote:

Want this!

It begs the question about how we make this work. There are two powers
needed: (1) reorder and (2) checkbox. It'd be nice if the /todo feature
just had to compose those. Next we get the question of whether the client
itself implemented (1) and (2).

I'd propose in the short-to-medium term the clients have to understand
reordering and checkboxes as formats (e.g. /orderable, /checkbox). Then the
/todo feature just registers for /todo and applies both formats to the
message.

A feature installed on the channel could apply those formats to all
messages in the channel. Then you could have a todo channel.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#37 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAE1iEn6-pKdAcmuYtMtbgbkUh0rUqPnks5qhPqXgaJpZM4JnNJA
.

[tonygentilcore]

This issue was moved to other-xyz/time-cone#76