oeed / CraftOS-Standards

Community standard file formats, communication systems, etc. for ComputerCraft and CraftOS 2.0
Other
20 stars 16 forks source link

A United Standard for To-Do Lists #53

Open MineRobber9000 opened 8 years ago

MineRobber9000 commented 8 years ago

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

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

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.

CrazyPyroEagle commented 8 years ago

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

MineRobber9000 commented 7 years ago

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

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

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

MineRobber9000 commented 7 years ago

image

Implemented into TDLViewer, looking good?

MineRobber9000 commented 7 years ago

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.