WildcatIP / other.js

The Chatternet feature platform
GNU Affero General Public License v3.0
7 stars 1 forks source link

/todo #157

Open tonygentilcore opened 7 years ago

tonygentilcore commented 7 years ago

From @tonygentilcore on August 24, 2016 21:17

From @aza on August 18, 2016 7:25

What is?

Copied from original issue: other-xyz/other.js#37

Copied from original issue: other-xyz/time-cone#76

tonygentilcore commented 7 years ago

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 commented 7 years ago

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!

tonygentilcore commented 7 years ago

From @aza on August 19, 2016 1:14

@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 :)

tonygentilcore commented 7 years ago

From @aza on August 23, 2016 22:49

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 https://github.com/other-xyz/other.js/issues/37#issuecomment-240897434, or mute the thread https://github.com/notifications/unsubscribe-auth/AAE1iEn6-pKdAcmuYtMtbgbkUh0rUqPnks5qhPqXgaJpZM4JnNJA .