Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A United Standard for To-Do Lists #53

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

MineRobber9000
Copy link

This may extend off of the lua/table format you were working on, but I just spent a night working on this and now it's finished.

@lyqyd
Copy link
Collaborator

lyqyd commented Apr 11, 2016

Thanks for the submission!

I think that this would require further fleshing out before it should be accepted. For instance, I don't see any provision for subtasks. It also appears that the language used in the standard text would need some editing to match the style used in other standards. Another nice feature might be partial completion states, denoting that some task is some percentage complete, or a fractional representation of a total goal.

@oeed
Copy link
Owner

oeed commented Apr 12, 2016

I'd agree with Lyqyd, it's some nice work but does need a little more.

Maybe instead of booleans you could use a number between 0 and 1, 0 being not complete, 1 being complete and decimals being partially complete.

provided for varying levels of completion, now on to subtasks! oh boy...
@CrazyPyroEagle
Copy link

The MIME should be in the text group, not the basic group.

@MineRobber9000
Copy link
Author

I've decided to just make this a basic To Do List format. This comes because I can't find a way to make subtasks without it breaking. Are subtasks THAT important? Anyhow, I've renamed it to "Basic To-Do List".

@lyqyd
Copy link
Collaborator

lyqyd commented Oct 28, 2016

Why not something like this for subtasks:

{
  {"Show off how minimalistic this looks.",1,},
  {
    "Find out the Doctor's name.",
    {
      {"Track down the Doctor", 1,},
      {"Ask the Doctor what their name is", 0,},
    },
  },
}

@MineRobber9000
Copy link
Author

Ooh, that might work. A lot simpler then what I was originally going for when it came to subtasks.

@MineRobber9000
Copy link
Author

image

Implemented into TDLViewer, looking good?

@MineRobber9000
Copy link
Author

TDLClient Discontinuation Blurb (ignore if you're not interested, just wanted to say this)

I've decided to get rid of TDLClient. It was a mess of spaghetti-code anyways, and implementing subtasks into it would delay the addition of subtasks to the standard. While the standard will move to 0.3.0, TDLClient will stay at 0.2.0 for the rest of the time it exists.

I'm going to update the TDLViewer pastebin to the 0.3.0 TDL standard (now with subtasks!) and update the standard document.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants